On Thu, Oct 27, 2011 at 01:06:59PM +1100, Brian May wrote:
Any ideas?
more info needed: text mode booting. boot logging. verbose boot. IMO, most of the settings below should be default, not disabled or hidden or undocumented. 1. edit /etc/default/grub and get rid of the "quiet". i routinely change the top of my /etc/default grub to: GRUB_DEFAULT=saved GRUB_SAVEDEFAULT=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" # Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL=console 2. edit /etc/default/bootlogd to enable boot logging # Run bootlogd at startup ? BOOTLOGD_ENABLE=Yes 3. edit /etc/default/rcS and enable verbose booting. here's what mine looks like: # Time files in /tmp are kept in days. TMPTIME=0 # Set to yes if you want sulogin to be spawned on bootup SULOGIN=no # Set to no if you want to be able to login over telnet/rlogin # before system startup is complete (as soon as inetd is started) DELAYLOGIN=yes # Set UTC=yes if your system clock is set to UTC (GMT), and UTC=no if not. UTC=yes # Set VERBOSE to "no" if you would like a more quiet bootup. VERBOSE=yes # Set EDITMOTD to "no" if you don't want /etc/motd to be editted automatically EDITMOTD=yes # Set FSCKFIX to "yes" if you want to add "-y" to the fsck at startup. FSCKFIX=yes
Is there anyway of creating another virtual console within recovery mode?
open or openvt, depending on which version you have installed. probably openvt. craig -- craig sanders <cas@taz.net.au> BOFH excuse #42: spaghetti cable cause packet failure