by dick » Wed, 11 Apr 2001 18:54:29
tia,
dicky.
by Christopher Alber » Wed, 11 Apr 2001 19:03:59
> I normally run slackware linux, and "boot: single" or "init 1" will drop
> to a login prompt.
> I have noticed that this does not happen with redhat, you get the bash
> prompt without having to login as root.
> Is there an easy way to make redhat present a login prompt when going to
> single user?
> I have been tracing through the (never-ending redhat) script files and
> can not find an answer.
> Any hints will be received gratefully.
> tia,
>*y.
You can do this with lilo. See the entries in
man lilo.conf
corresponding to "password" and "restricted".
Chris
by dick » Wed, 11 Apr 2001 19:11:49
> You can do this with lilo. See the entries in
> man lilo.conf
> corresponding to "password" and "restricted".
> Chris
thanks anyway.
dicky.
by Tim Hayne » Wed, 11 Apr 2001 20:43:10
> > You can do this with lilo. See the entries in man lilo.conf
> > corresponding to "password" and "restricted".
> > Chris
> I have seen that and it works for the 'boot:single' case, what I am
> really curious about is where slackware and redhat differ once running,
> slackware always drops to a login prompt while redhat never does.
~Tim
--
12:42:18 up 5 days, 20:47, 8 users, load average: 0.12, 0.06, 0.07
http://piglet.is.dreaming.org |Came the tranquil and the calm,
|On the ridge of the mighty Atlantic.
by Peter Swedi » Wed, 11 Apr 2001 23:33:30
To my understanding, this is because RH uses sysV init, with actualQuote:> I normally run slackware linux, and "boot: single" or "init 1" will drop
> to a login prompt.
> I have noticed that this does not happen with redhat, you get the bash
> prompt without having to login as root.
> Is there an easy way to make redhat present a login prompt when going to
> single user?
> I have been tracing through the (never-ending redhat) script files and
> can not find an answer.
> Any hints will be received gratefully.
> tia,
>*y.
Good luck.
Pete
by David Griffit » Thu, 12 Apr 2001 02:59:11
> > > You can do this with lilo. See the entries in man lilo.conf
> > > corresponding to "password" and "restricted".
> > > Chris
> > I have seen that and it works for the 'boot:single' case, what I am
> > really curious about is where slackware and redhat differ once running,
> > slackware always drops to a login prompt while redhat never does.
> Investigate how slackware does it; I think you'll find a reference to
> `sulogin' in the what-to-do-in-single-user line/s of /etc/inittab that
> might be of interest.
> ~Tim
> --
> 12:42:18 up 5 days, 20:47, 8 users, load average: 0.12, 0.06, 0.07
> http://piglet.is.dreaming.org |Came the tranquil and the calm,
> |On the ridge of the mighty Atlantic.
by wint.. » Thu, 12 Apr 2001 04:07:50
> > tia,
> >*y.
> To my understanding, this is because RH uses sysV init, with actual
> runlevels,
> and Slackware uses the BSD init, with /etc/rc.d scripts.
> You can look in there. Also, as someone previously stated, this can (I
> think), be
> set in lilo
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
restricted
password=foobar
image=/boot/vmlinuz-2.2.16-22
label=linux
initrd=/boot/initrd-2.2.16-22.img
read-only
root=/dev/sda2
All the versions of lilo() I've used complain about permissions if you
don't set lilo.conf's mode to 600 (or 660 if owned root:root I guess) b/c
the password's in the file in clear text. Makes sense t'me.
You can also drop the "restricted" and "password=" option-pair into each
image's section. I'm guessing that it'd prompt for password when trying
to boot that particular image (into any runlevel?), but I've never done
that so I can't comment.
D.
by Peter Swedi » Thu, 12 Apr 2001 16:12:12
Hey, that's useful, thank you!Quote:> Yup. An example /etc/lilo.conf off a stock RH 7.0 install, with the
> password set in the global section:
> boot=/dev/sda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> linear
> default=linux
> restricted
> password=foobar
> image=/boot/vmlinuz-2.2.16-22
> label=linux
> initrd=/boot/initrd-2.2.16-22.img
> read-only
> root=/dev/sda2
> All the versions of lilo() I've used complain about permissions if you
> don't set lilo.conf's mode to 600 (or 660 if owned root:root I guess) b/c
> the password's in the file in clear text. Makes sense t'me.
> You can also drop the "restricted" and "password=" option-pair into each
> image's section. I'm guessing that it'd prompt for password when trying
> to boot that particular image (into any runlevel?), but I've never done
> that so I can't comment.
> D.
1. RedHat 5.2, "/boot/System.map" and "/boot/System.map"
Hello,
Would someone know how to configure modules with the
"/boot/System.map" and "/boot/System.map" files in RedHat 5.2?
I can't seem to find any references on the RedHat site to these files.
In 5.1 all you had to do was rename your kernel with a name like
"vmlinuz-2.0.35.x" and an accompanying modules directory called
"/lib/modules/2.0.35.x" and the modules were loaded properly. It took
me awhile to figure that one out...and RedHat goes and changes the rules
again ;-\
Thanks, Luc.
2. WABI 24-bit patch (103587-??)
3. Q: diff btwn "LILO: linux single" and "LILO: linux 1" ?
4. HElp!!!
5. GETSERVBYNAME()????????????????????"""""""""""""
6. Help! problems with apache-ssl installation
7. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""
8. linux and nt
9. rss" and "stack" and "data" in /etc/security/limits file
10. Newbie "Boot" or not to "Boot"
11. "pump" or "dhcpcp" for single machine ppp0 dialup
12. How do i configure my "boot-device" and "boot-file" (LinuxPPC)?
13. graphical LILO and booting "linux single"