> >1:2345:respawn/sbin/mingetty tty1
> >
> >and there are 6 of these lines with the number fields (except for 2345)
> >substituted :} with it's respective number.
>
> Actually it's the second of these I wanted to see. The 1-6 at the beginning
> of these lines are the same numbers that "init" is using to identify the
> respawning lines.
>
So is mingetty the only thing the system respawns? Or is this the only thing it
respawns for login and after that everything else gets respawned? Or of course none
of the above?:} I assume though, like you were saying, it does this so that there
is a way to log into the system after exitting.
>
> >> whether you can find the process listed in the inittab lines above
> >> (it might be getty, agetty, mgetty, mingetty, getty_ps)
> >> with the "which" command
> >
> >Wow, this is the smallest ps ax I've seen so far. Only 8 entries. init [3],
> >[kflushd], [kupdate], [kpiod], [kswapd], [mdrecoveryd]. Then bash and ps ax. I
> >hope this answers your question.
>
> Not "ps ax" -- "which". This is a command similar to find, but that looks in
> your PATH for an executable with the name you mention. IF you enter "which
> mingetty", I'll bet you don't find one.
Sorry, I wasn't sure how to use the "which" command and forgot to state that. I did
ps ax for something else.
Anyway, which mingetty yielded:
/sbin/mingetty
> >The one thing I didn't mention. It drops me down to "enter password for
> >maintenance" and fdisk when I reboot. I'm moving a bunch of cards between boxes
> >right now. But when I get to fdisk I have no idea what I need to do. I remember
> >it saying something about a bad inode I think.
>
> "fdisk"? might it be "fsck"? This (maintenance mode) means the system finds
> some problem with your filesystem during the boot/init process. Without
> seeing the "something" it says, I can't be more specific. But init may be
> failing to find mingetty due to filesystem corruption. Try running "e2fsck
> /dev/hda1" (replace hda1 with the right designator for your root filesystem)
> and see if that helps. Or port again reporting the details of what happens
> during these unsuccessful boots.
Yer right again. I even did an fdisk at this prompt. Maybe I need to try "hookt on
fonix".
K..... it says:
/dev/hda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 64419 has illegal block(s). Clear<y>?
An Inode is a 1k block of info on the drive right? How do I know whether I want to
clear it or not?? Or don't I have a choice.
Thanks,
John
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
