Ah, the old local.start hack
Apparently we should never use it for things like
this. But we all
do :-)
As a solution it's OK to do this, as long as you
always remember that
you put it there - future updates often end up doing
strange things
because of the contents of local.start,
On Fri, 13 Oct 2006 08:22:04 -0700 (PDT), maxim wexler wrote:
IIRC the last time I updated baselayout it overwrote
some important files and my system was un-usable. In
all the excitement I failed to note what they were.
That wasn't baselayout, it was you when running etc-update.
Is there a
On 10/11/06, Alan McKinnon [EMAIL PROTECTED] wrote:
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
What baselayout and udev version are you using?
Thanks Alan,
I added the commands to local.start and that seems to
have done the trick.
But here's the baselayout and udev info:
[EMAIL PROTECTED] ~ $ emerge -pv baselayout
These are the packages that would be merged, in order:
Calculating
On Thursday 12 October 2006 16:44, maxim wexler wrote:
What baselayout and udev version are you using?
Thanks Alan,
I added the commands to local.start and that seems to
have done the trick.
Ah, the old local.start hack
Apparently we should never use it for things like this. But we all
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?
-Maxim
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the
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
On Mon, 22 Aug 2005 02:41:31 +0100, Ciaran McCreesh wrote:
/dev is a managed filesystem. You shouldn't be tinkering with it
manually.
You shouldn't need to tinker with it manually, but sometimes you need to
as not everything is supported yet. Until recently, the only way to get
IEEE1394
On Mon, 22 Aug 2005 08:45:52 +0100 Neil Bothwick [EMAIL PROTECTED]
wrote:
| On Mon, 22 Aug 2005 02:41:31 +0100, Ciaran McCreesh wrote:
| /dev is a managed filesystem. You shouldn't be tinkering with it
| manually.
|
| You shouldn't need to tinker with it manually, but sometimes you need
| to as
On Mon, 22 Aug 2005 17:28:03 +0100, Ciaran McCreesh wrote:
No, the correct thing to do is to add sysfs support to the devices in
question. It's probably the easiest form of kernel hacking there is.
Eating lighted matches is probably the easiest form of fire-eating there
is. That doesn't mean I
Hello everyone,
Another post-emerge -u world wrinkle: before I can
/usr/sbin/pon must now
mknod /dev/ppp c 108 0.
Where does one put this command? I didn't see any
likely candidates in /etc/conf.d, /etc/init.d.
-mw
Start
On Sun, 21 Aug 2005 07:39:05 -0700 (PDT) maxim wexler
[EMAIL PROTECTED] wrote:
| Another post-emerge -u world wrinkle: before I can
| /usr/sbin/pon must now
|
| mknod /dev/ppp c 108 0.
|
| Where does one put this command? I didn't see any
| likely candidates in /etc/conf.d, /etc/init.d.
Don't
--- Ciaran McCreesh [EMAIL PROTECTED] wrote:
On Sun, 21 Aug 2005 07:39:05 -0700 (PDT) maxim
wexler
[EMAIL PROTECTED] wrote:
| Another post-emerge -u world wrinkle: before I can
| /usr/sbin/pon must now
|
| mknod /dev/ppp c 108 0.
|
| Where does one put this command? I didn't see any
On Sun, 21 Aug 2005 17:27:25 -0700 (PDT) maxim wexler
[EMAIL PROTECTED] wrote:
| | Where does one put this command? I didn't see any
| | likely candidates in /etc/conf.d, /etc/init.d.
|
| Don't do that. Instead, fix your udev rules.
|
| I did(put it in local.start) and it works fine! Please
14 matches
Mail list logo
