Also wondering, if this isn't a kernel issue then why does
70-persistent-cd.rules get generated if it's missing under kernel 3.2.29,
but under 3.6.7 it does not?
On Sat, Nov 24, 2012 at 1:44 PM, Nelson wrote:
> Using udevadm as you suggested yielded some interesting results. U
with ENV{ID_SERIAL_SHORT}, I was wondering if the lack of ID_PATH
is because of a turned off option in the kernel or the removal of it?
On Sat, Nov 24, 2012 at 8:29 AM, Kay Sievers wrote:
> On Sat, Nov 24, 2012 at 8:55 AM, Nelson wrote:
> > While my issue is still with udev 182 and ker
While my issue is still with udev 182 and kernel 3.6.7,
does 70-persistent-cd.rules even get USED at all if it was created
beforehand with 183?
On Sat, Nov 24, 2012 at 12:35 AM, Jan Engelhardt wrote:
>
> On Saturday 2012-11-24 06:08, Nelson wrote:
>
> >Currently on Slackware 14.
Currently on Slackware 14.0 and that came with udev 182 and kernel 3.2.29.
Under this configuration udev works properly, specifically
/etc/udev/rules.d/70-persistent-cd.rules gets recreated if it doesn't exist
and it is also USED to create certain links and dev nodes such as
/dev/dvdrom. Once I m
On 7/16/2011 1:20 PM, Lennart Poettering wrote:
On Sat, 16.07.11 10:43, Ryan Nelson (ryan.freedesk...@rnelnet.com) wrote:
Ok, so I read more on systemd (and the man page for inittab) and
came up with a basic vgetty.service that I'm using with systemd.
After doing little ready its pretty
ption=Program to answer voice calls using Vgetty
After=syslog.target
[Service]
ExecStart=-/sbin/vgetty /dev/ttyS2
Restart=always
RestartSec=0
KillMode=process
[Install]
WantedBy=multi-user.target
--end snip--
thanks,
Ryan
On 7/15/2011 10:35 AM, Ryan Nelson wrote:
I did a minimal search on your lis
I did a minimal search on your list and longer on the web about trying
to get vgetty working under systemd. Forgive me although I just
learning about systemd.
So I use to have vgetty a program under the mgetty software working as
an answering machine. I would get calls would be picked up and the
