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
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
6 matches
Mail list logo
