On 05/22 20:20 Miquel van Smoorenburg wrote:
In article <[EMAIL PROTECTED]>,
Colin Watson <[EMAIL PROTECTED]> wrote:
>http://bugs.debian.org/132870
Why use "ini" instead of "init"; this is Linux anyway.
Was fixed quite some time ago in 2.84-3, which I apparently forgot
to upload. Hmm, since it isn't release critical this isn't going
to make it into woody, so we'll be stuck with it for the next 2 years ;/
I use sid; there's no reason to get stuck, right?
So I guess, apt-get install sysvinit would fix it.
A fix might be to add some extra arguments to the init command
line, try adding
append="panic=30"
(generally harmless but useful kernel command line, which is passed
to init as well) to /etc/lilo.conf, re-run lilo, reboot, see
if it helps.
You can also try
append="-z 123456789"
as that is a special "ignore" command line option for init.
So basically, those two appends are "no-ops", right?
I see, I'll try.
Oki
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
