From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where to put mknod & chmod
Date: Wed, 11 Oct 2006 18:24:30 +0200 [thread overview]
Message-ID: <200610111824.30084.alan@linuxholdings.co.za> (raw)
In-Reply-To: <20061011160032.72049.qmail@web31706.mail.mud.yahoo.com>
On Wednesday 11 October 2006 18:00, maxim wexler wrote:
> Hi group,
>
> One of my morning chores after booting linux is to su
> and enter #mknod /dev/ppp c 108 0 and #chmod a+rw
> /dev/parport0.
>
> Where can I park these commands to automate the
> process?
udev is supposed to create these nodes and set the permissions. I don't
have a ppp node as a) i don't use ppp anymore and b) when I did, kppp
make the node itself. But I have a parport rule:
alan@gentoo /etc/udev $ grep -r parport *
permissions.d/50-udev.permissions:parport*:root:lp:0660
rules.d/50-udev.rules:KERNEL=="parport*", NAME="%k", GROUP="lp"
What baselayout and udev version are you using?
alan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-11 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 16:00 [gentoo-user] where to put mknod & chmod maxim wexler
2006-10-11 16:24 ` Alan McKinnon [this message]
2006-10-12 14:44 ` maxim wexler
2006-10-12 17:10 ` Alan McKinnon
2006-10-13 15:22 ` maxim wexler
2006-10-13 15:33 ` Neil Bothwick
2006-10-15 4:40 ` [gentoo-user] Is it possible to protect *INDIVIDUAL FILES* against etc-update? Walter Dnes
2006-10-15 7:06 ` Bo Ørsted Andresen
2006-10-16 21:57 ` Walter Dnes
2006-10-17 0:47 ` Richard Fish
2006-10-18 4:09 ` Walter Dnes
2006-10-17 13:11 ` Neil Bothwick
2006-10-15 12:27 ` Neil Bothwick
2006-10-17 13:16 ` Bo Ørsted Andresen
2006-10-17 14:28 ` Neil Bothwick
2006-10-13 23:51 ` [gentoo-user] where to put mknod & chmod Drew
2006-10-11 18:09 ` Neil Bothwick
2006-10-11 21:31 ` [gentoo-user] where to put mknod & chmo Richard Fish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610111824.30084.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox