?

Log in

No account? Create an account
Linux Community's Journal
 
[Most Recent Entries] [Calendar View] [Friends View]

Sunday, January 18th, 2004

Time Event
3:28a
kernel can't find init... but only sometimes
recently installed Debian 3.0r2 on my Compaq laptop, with the bf24 kernel (2.4.18, I believe it is). I'm using grub for my bootloader.

sometimes, the machine gets halfway through starting up, and then I get the message that the kernel can't find INIT, and I should try giving the init= argument to the kernel. I haven't quite figured out the pattern to when it does this, although I think it might be when the machine hasn't been up for a while, for example overnight or all afternoon. It'll do this sometimes 2 or 3 times before loading finally.

I've tried giving the following different kernel commands to grub, with indistinguishable results:
grub> kernel (hd0,6)/vmlinuz
grub> kernel (hd0,6)/vmlinuz root=/dev/hda7

I've even tried this one, to no avail, although I'm not entirely sure this is how it's done:
grub> kernel (hd0,6)/vmlinuz root=/dev/hda7 init=/sbin/init

none seems to work any more frequently than any of the others.

Is there any particular reason it's doing this? I've had it work on a third or later try when the first two or several exactly identical tries have not, and can't find any rhyme or rhythm to why it decides to work when it does.

x-post: debian

Current Mood: confused
5:10p
bind 9.2.2 problems in fedora core 1
i have installed fedora core 1, but not had time to run up2date to get the lastest rpms (would this solve my problem?)

i copied my old named/bind configs from my red hat 7.3 installation, and they didn't work with fedora's bind

i found a howtos for bind 9, and did exactly as it said

at the point where you start named i didn't get an answer in the dig output

some messing with rndc later, and all i could get was this:

Stopping named: rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.


is it something obvious that is causing this to happen? or have i just broken named!
what can i do to sort this out?

Current Mood: geeky
9:12p
Multiple networks
I use 192.168.0.x for my network, and I have a friend who I visit a lot who uses 192.168.1.x. I'd like to be able to use my laptop at his house without editing any config files. The problem I'm having is with the gateway, I can't think of a way to be able to use both gateways without editing my configs. DHCP is not an option at the moment.

<< Previous Day 2004/01/18
[Calendar]
Next Day >>
About LiveJournal.com