You are not logged in.
- Topics: Active | Unanswered
#1476 Re: Forum Feedback » How to do some formatting little things in Dev1galaxy Forums » 2017-03-30 12:17:09
dev1galaxy only uses BBCode, which you can find documented following the BBCode link below the Quick reply box, where it says "BBCode: on". The "BBCode" text is a link, to
https://dev1galaxy.org/help.php#bbcode which documents the extent of available markup.
Also, there is a Profile tick box in the "privacy" section for opting-in on getting subscribed to your topics. It might be possible to have that as default, and rather "force" people to to opt-out instead.
#1477 Re: Hardware & System Configuration » No wpa_supplicant or iw? » 2017-03-20 05:34:56
Maybe I misunderstood; my
devuan_jessie_1.0.0-beta2_amd64_CD.iso (from files.devuan.org)
includes /pool/DEBIAN/main/w/wpa/wpasupplicant_2.3-1+deb8u4_amd64.deb
#1478 News & Announcements » git.devuan.org comes to the dev1galaxy forum » 2017-03-07 07:07:13
- ralph.ronnquist
- Replies: 0
The newest addition to the dev1galaxy.org forum intends to make git.devuan.org (gdo) more directly accessible and understandable to Devuan users as well as to (hopefully) help solve outstanding project issues posted at gdo.
Every project and issue at gdo can now be found on dev1galaxy via the two special "Projects" and "Issues" forums in the new "git.devuan.org" section.
The Projects forum (https://dev1galaxy.org/viewforum.php?id=18) organizes Devuan projects into two categories - "devuan-packages / infrastructure" and "other projects". Both categories are presented as alphabetical and activity ordered lists. The project lists offer a short description (if available) and a convenient, single-click access to all projects at git.devuan.org.
The Issues forum (https://dev1galaxy.org/viewforum.php?id=19) holds threads that are automagically created by dev1galaxy's trusty "gdolink" bot, from all open issues at git.devuan.org. The bot will add newly opened issues (if any) to the Issue lists, every 30 minutes. Posting these issues on d1g will give greater exposure to issues that are currently buried in the gdo 'cave' (which is perceived as inaccessible by some). Opening parallel forum threads provides opportunity for discussion and collaborative problem solving that will accelerate Devuan's progress and usability.
Note that the posts in these issue threads are distinct from the comment discussion on gdo. However, when a post suggests a solution to an issue, or has information to advance it, a project team member will be able to capture the post as an original issue comment at gdo.
Finally, the "gdo Help Desk" is the place to ask questions about gdo and to post tips that will help familiarize users with how gdo works.
#1479 Re: Installation » help to install nvidia-legacy-304xx-driver *No devices detected.* » 2017-02-26 07:01:29
I saw on IRC that you've done many things trying to get it to work.
What does dmesg say now?
#1480 Re: Installation » help to install nvidia-legacy-304xx-driver *No devices detected.* » 2017-02-26 06:38:28
Perhaps it's ok to remove the BusID phrase instead?
#1481 Re: Installation » help to install nvidia-legacy-304xx-driver *No devices detected.* » 2017-02-26 05:12:26
You should probably use the longer one, "0000:00:0d.0"
Also, if you would put listings etc in code blocks, i.e. within a pair of [code] and [/code], it'd be easier to read.
#1482 Re: News & Announcements » About "login via git.devuan.org" » 2017-02-19 22:49:20
This function is has been improved, and you are now able to both have a password log in and to log in via git.devuan.org.
Like before, when you log in via git.devuan.org, your account is promoted into a "via git.devuan.org" account. This is then remembered by the forum through any subsequent log in, whether via password or via git.devuan.org, until you go through the "Forgot my password" procedure.
#1483 Re: Other Issues » General Questions » 2017-02-10 23:26:57
It's a bit scary to reply to this, because you've raised a fair few issues in the one breath :-)
How about splitting them up into several (is it 3 or is it 4?) threads.
As for the the last issue, "compiling without systemd", I believe a search in the
dyne.org's mailing list may bring up some discussions. That would be my first target for "FAQs in one spot"; though I wouldn't be surprised if there are more spots than one available.
#1484 News & Announcements » About "login via git.devuan.org" » 2017-02-09 21:54:41
- ralph.ronnquist
- Replies: 1
The Dev1 Galaxy Forum now lets you use your git.devuan.org login to log in, where you need authorize the forum to access your user information. Just click the link on the login page and follow the prompts. If you run into problems, contact the forum administrators, or drop a line at freenode#d1g-users for assistance.
As a new forum user, you will be automatically registered with the git.devuan.org username and email, unless of course, there is a clash with an existing account.
As an existing user, with the same username and email, you will automatically "promote" your account to a "via git.devuan.org" account.
As an existing user, with different username or email, you will be automatically registered with the git.devuan.org username and email, unless of course, there is a clash with an existing account.
To revert your account (back?) to a password account, you need to follow the "Forgot my password" route, and set a new password whilst avoiding to log in via git.devuan.org.
Welcome!
#1485 Re: Installation » [Solved] Removable media unaccessible as normal user (PCManFM/Thunar) » 2017-02-05 03:15:27
Not sure what 'the standard way' means to you, but for example, the group name 'storage' is not listed at https://wiki.debian.org/SystemGroups. I suppose, that might not be normative for Devuan, since Devuan is not Debian, but to me it implies that polkit is not standard.
In any case, whether standard or not doesn't help towards your problem, which rather seems to be, how to configure udisks and/or polkit to work the way you want.
#1486 Re: Installation » [Solved] Removable media unaccessible as normal user (PCManFM/Thunar) » 2017-02-04 20:24:23
What was wrong with using pmount/pumount ?
#1487 Re: Forum Feedback » Discussion on possible new spam control » 2017-01-25 03:06:15
Maybe https://www.stopforumspam.com could be of some use?
#1488 Re: Documentation » How to make the 'sleep' button work if yours doesn't » 2017-01-23 20:38:03
It's worth to note that some buttons generate many events, with different arguments. E.g., my lid button has "open" or "close" as (third) arguments . The script (or the recognition rule) will then need to distinguish appropriately, to get the right thing done for the right event(s).
#1489 Re: DIY » DIY "rrq Parental Internet Packet Filtering" » 2017-01-21 03:27:59
I've moved this project to gitlab, https://git.devuan.org/ralph.ronnquist/rrq.git, and included control scripts with a full setup of tun interfaces, routing and iptables rules, as an OOTB filtering solution. Though, it doesn't include block list files; I only have the ones I bought, and no free ones.
There's also an HTTP admin tool for the brave hearted.
#1490 Re: Desktop and Multimedia » [solved] XFCE icon labels » 2017-01-20 02:09:44
Sigh. Several people have told me how wrong I am: apparently in computing, anything older than 6 years is ancient ...
#1491 Re: Desktop and Multimedia » [solved] XFCE icon labels » 2017-01-18 22:38:11
My friend, to use "ancient" about things from some 30 or so years ago is also a way to climb the scale. In any case, I got a good answer to my question. We can meet up and discuss the rest sometime, somewhere.
#1492 Re: Hardware & System Configuration » Sleep button doesn't work » 2017-01-18 03:08:29
If the button results in an ACPI event, you could deal with it through that: a "rules file" in /etc/acpi/events to recognize it and map to a script, and that script invoking pm-suspend, habitually placed in /etc/acpi.
#1493 Re: Desktop and Multimedia » [solved] XFCE icon labels » 2017-01-18 03:04:03
Thanks.
have no idea what your talking about . . . I didn't know a kernel had a color!! LOL!
yes :-) a while ago I thought to experiment with the C-A-f1 console, to have black text on white instead of the washed out gray on black (or sometimes dirty dark green). I then found out that those console colours are hardcoded into the kernel, in a palette of 8 named colours, with "white" conveniently naming the gray colour. This seems to have happened many years ago, but that doesn't place it lower on the stupid scale. In any case, I eventually worked out how to achieve black on actual white on the console, and that it's not worth fighting for.
#1494 Desktop and Multimedia » [solved] XFCE icon labels » 2017-01-18 00:15:51
- ralph.ronnquist
- Replies: 6
Is there an easy way for me to have the (beta2) XFCE desktop icon labels text in black?
Just a vanilla installation with everything default.
(and I think whoever made the "white" kernel colour be gray should have a separate talking-to)
#1495 DIY » DIY "rrq Parental Internet Packet Filtering" » 2017-01-16 06:49:39
- ralph.ronnquist
- Replies: 1
Announcing https://github.com/ralph-ronnquist/rrq
This Parental Internet Packet Filtering is a blacklist based network traffic filter to block access to certain domain names for all or some outbound and/or forwarded HTTP and SSL traffic.
The blocking principle is simply to detect and discard any IP packet that constitutes the initial handshake of an HTTP or SSL connection to a blocked domain. By discarding these initial packets, the blocked domains become inaccessible.
The project includes two alterantive daemons: "rrq_nfq" for iptables based filtering, and "rrq_vde" for use on a VDE cable chain. Includes "make deb" for building a Devuan (.deb) package.
#1496 Re: Hardware & System Configuration » vdev testing » 2017-01-08 11:21:28
As I restarted a vdev setup from scratch, I was reminded that the dvb adapter end points get rather restrictive file permissions, e.g:
crw------- 1 root root 212, 0 Jan 8 21:54 demux0
crw------- 1 root root 212, 1 Jan 8 21:54 dvr0
crw------- 1 root root 212, 3 Jan 8 21:54 frontend0
crw------- 1 root root 212, 2 Jan 8 21:54 netThis is something one can remedy by an action, say, "/etc/vdev/actions/dvb.act" as follows:
[vdev-action]
event=add
path=^dvb/adapter[0-9]+/[^/]+$
VAR_PERMISSIONS_GROUP=video
VAR_PERMISSIONS_MODE=0660
helper=permissions.shI.e., give rw permission for group video to all endpoints. I'm adding that action to the standard set in a forth-coming version.
The script in detail: the "event" category is limited to act on new path names, and the path name (following "/dev/") is restricted (through a POSIX regular expression) to the "adapterN/blah" end points. This action utilises the standard permissions setting helper, which makes good use of the given "VAR_*" variables.
#1497 Re: Hardware & System Configuration » vdev testing » 2017-01-08 00:42:27
btw, re (8):
8) I attached an external USB HDTV adapter (PCTV 290e) and the expected /dev/dvb devices were created.
However for to test this further on a proper multi-tuner mythtv backend (with the need for consistent and meaningful names), I would need to be able to recreate the following udev rules in vdev:# PCTV 290e single tuner USB stick
# --------------------------------
# Create symlinks /dev/dvb/adapterPCTV290e/* pointing to PCTV 290e adapter (has unique attributes, so can find wherever it is)
I think I would consider having a separate naming script, with code like
ln -sTf adapter0 /dev/dvb/adapterPCTV290eto be run when starting the mythtv app, or manually, rather than making it vdevd magic; especially since there might be several adapters of the same brand.
E.g., for my own TV system I have 4 receivers of the same brand, so I can't use your approach off hand. (A separate comment is that it's enough to symlink to the adapterX directory rather than symlink each "control interface" [or what it's called]) As you might know, the product name for /dev/dvb/adapterX is (currently) available at e.g.
cat /sys/class/dvb/dvbX.demux0/device/productBut, I suppose there could be a helper script improvement for this in some way.
#1498 Re: Hardware & System Configuration » vdev testing » 2017-01-07 23:29:12
ok. I've added (A) as issue for https://git.devuan.org/ralph.ronnquist/vdev. The daemon should indeed be robust against malformed action declarations as well as helper script errors.
Re (B): yes, most of the error messages are at a severe extreme of cryptic. Mostly they are s.c. standard error codes, and -22 would be called EINVAL. In your case, I'm guessing there was some output lines before that error line, such as:
Failed to set mountpoint, config->mountpoint = ...or similar, which sometimes could help a geek to pinpoint the problem.
#1499 Re: Hardware & System Configuration » vdev testing » 2017-01-06 06:09:49
Re USB, (7): the overall issue is that several packages have been coded to utilize udev, via the rules files, for automagic hotplug handling, and they (of course) don't include a corresponding configuration (action+helper) for utilizing vdev. I did start on a "udev rules"-to-"vdev conf", but stopped (apart from incorporating scanner recognition into vdev), as I rather quickly saw it leading to insanity (mine). So, this aspect is in a state of pass the bucket game, where it really should be up to those other package developers to add their hotplug configuration wrt vdev.
That leads to your pt.8, and highlights the need for more/better documentations (and tools?) of how to "program" vdev.
(sorry. right now it's too hot here to think; I'll try again in the weekend...)
#1500 Re: Documentation » vdev documentation » 2016-12-15 21:51:57
I'm of course using vdev myself, and as of last week, it's with a beta2 installation on the 20 Gb SSD of my Asus laptop. I've uncovered two faults in the vdev actions (it locks down /dev/fuse and /dev/net/tun too much), and otherwise had no grief. But I can't say I'm very inventive in changing its hardware anyhow, so it's not a very impressive vdev workout.
The documentation needs a lot of work, with possibly the major thing being a change of perspective so it, more than telling what vdev does, it tells what a person needs to do to make vdev do something more/else for them. This includes how to make changes to the current (documented) actions, and more significantly how to add new actions/helpers to deal with new hardware. At the end of the day it's just the hotplugging sub system, which really is (or should be) simple for any particular set up, but made complicated in the attempt to be capable of handling any and all possible set ups.
Board footer
