Re: How to interrupt the boot process?
On Sun, 13 Oct 1996, Toni Mueller wrote: > - How can I stop the boot process half-way to get a single-user root shell? There was a key which I don't remember. You may type "linux single" from lilo prompt. Vadik. ++_ Vadik V. (_`[EMAIL PROTECTED] alias: [EMAIL PROTECTED] Vygonets (_.lf For PGP public key, email me with sibject "get pgpkey" Behind every great computer sits a skinny little geek. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: How to interrupt the boot process?
On Sun, 13 Oct 1996 11:23:52 +0200 Toni Mueller ([EMAIL PROTECTED]) wrote: > - How can I stop the boot process half-way to get a single-user root shell? > > All I did in terms of ^C, ^Q@(#*$& and Alt-any-key didn't help, regardless > of where in the boot process I press them. Go to the lilo prompt (press SHIFT or ALT or CTRL) when the prompt appears. Type `linux single' (or whatever name you've put) (press TAB to get a list). You should boot linux in single-user mode. Note that it will try to mount partitions. If the above doesn't work, you can try `linux emergency' which will only boot the kernel and fork a shell. No init script is called. This should always work unless your root partition is unreadable and/or you screwed something up with the shared libraries. In this last case, you can resort to using a boot/root disk. But `linux emergency' should work for you. > - Is there an equivalent to chroot in Debian Linux (I only can compare to > BSD* here). Yep, it's in /usr/sbin, and only root can use it. > - When having a set of kernels how do I manage to get them all have their > individual System.map? During the boot phase, before klogd is started, symlink it to one of your system.map-. > - As a quick fix, could somebody of you please point me to a dpkg working > under BSD*? Er, don't know that one. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: How to interrupt the boot process?
If you are using a boot loader like lilo/syslinux that is simple: just pass the '-b' switch to the kernel. Eg: LILO: vmlinux -b -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The text above represents my personal opinion and does not represent the official position of my employer on the issue(s) discussed. Any official statement made on behalf of my employer by me is marked as such. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: How to interrupt the boot process?
Hi Toni, there may have been much more profound answers to your questions, bu t in case, there were none, here is what I do when in trouble: > > Now I have some questions: > > - How can I stop the boot process half-way to get a single-user root shell? At the beginning, just after your POST completes (BIOS checking the system), hit CAPS LOCK once -> this is prerequisit for Lilo to prompt you for further input befor bootstraping Linux... At the "Lilo: " prompt, you may alter some kernel-driver parameters, as well as the init-behaviour. the keyword "single" at the Lilo-prompt will bootstrap Linux in single-user mode... > All I did in terms of ^C, ^Q@(#*$& and Alt-any-key didn't help, regardless > of where in the boot process I press them. I don't know of such keypresses, that equal the SPARC Boot Interruption...:-? > > - Is there an equivalent to chroot in Debian Linux (I only can compare to > BSD* here). Yes there is an equal chroot. I'd better cut&past portion of the man-page :-) --- NAME chroot - change root directory SYNOPSIS chroot newroot [command] DESCRIPTION The chroot command changes its root directory to the supplied directory newroot and exec's command, if supplied, or an interactive copy of your shell. Note, command or the shell are run as your real-user-id. Note also that in the Debian GNU/Linux version only chroot(2) is called. In the original 4.4BSD-Lite version both chdir(2) and chroot(2) are called. -- > > - When having a set of kernels how do I manage to get them all have their > individual System.map? don't know if you can...but it isn't critical during bootstraping. Hope this helps. regards, Stoyan -- Stoyan Kenderov/ NTG Netzwerk und Telematic GmbH \/ phone: +49 721 9652 220 Geschaeftsbereich/\ LINK fax: +49 721 9652 210 Vincenz-Priessnitz-Str. 3 /___ email: [EMAIL PROTECTED] D-76131 Karlsruhe, Germany http://www.xlink.net/~kenderov PGP: http://www.xlink.net/~kenderov/public.key.asc -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]