Could we not send all the text on screen with a command like ? >> all_screen_text.txt Now I am happy to test this out, but what is the '?' command, and what is the "Autoexec.bat" file equivalent in Linux, to insert the line. "Paul W. Abrahams" wrote:
Landy Roman wrote:
I have a question. Is there a way to temporarily stop the boot up process so that you can read/study the messages? I've looked at dmesg, but not all of the messages are in there. like the error messages
don't
show up. Weird! or, where are the error messages written?
Thanks, Jerry VB did u chk /var/log/boot.msg
I believe dmesg simply gives the contents of /var/log/boot.msg, which records only those actions taken by the kernel itself during bootup. The question no one seems to have a good answer for is how to see the messages resulting from the scripts in /sbin/init.d, e.g., the ones that mount the filesystems. Shift-PgUp shows some of them, but not always all of them.
Paul Abrahams
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
e richards wrote:
Could we not send all the text on screen with a command like ? >> all_screen_text.txt
Now I am happy to test this out, but what is the '?' command, and what is the "Autoexec.bat" file equivalent in Linux, to insert the line.
At the time of initial boot there is no disk mounted, so there is no convenient place to dump the output. There is another way to record the boot messages: the serial port.
"Paul W. Abrahams" wrote:
Landy Roman wrote:
I have a question. Is there a way to temporarily stop the boot up process so that you can read/study the messages? I've looked at dmesg, but not all of the messages are in there. like the error messages don't show up. Weird! or, where are the error messages written? did u chk /var/log/boot.msg
I believe dmesg simply gives the contents of /var/log/boot.msg, which records only those actions taken by the kernel itself during bootup. The question no one seems to have a good answer for is how to see the messages resulting from the scripts in /sbin/init.d, e.g., the ones that mount the filesystems. Shift-PgUp shows some of them, but not always all of them.
If you have two computers and available serial ports, just purchase a serial cable, those with 9 and 25 pins (female) are the most convenient. The steps I follow are: 1. Hook up the computers 2. Start an X terminal, eg. 'xterm -sb -sl 1000', and run minicom in it. Bring out the configuration panel, Alt-Z -> O -> Serial port setup -> E, Tell it to use the serial port you connected the cable to (/dev/ttyS0, /dev/ttyS1, etc.) Set up the serial port to 9600, no parity 8 bit data, 1 stop bit. 3. Boot linux on the machine you want to monitor with: LILO: linux console=ttyS0,9600n8 The above means that all console messages go to the first serial port. The default settings are 9600 bauds, 8 bits, no parity, so the above is a little redundant, but you can use it to up the speed. 4. The status line of minicom should indicate if you are offline or online. If it works, you should see all the boot messages and you can save them by copying and pasting. -- Rafael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
"Rafael E. Herrera" wrote:
e richards wrote:
Could we not send all the text on screen with a command like ? >> all_screen_text.txt
Now I am happy to test this out, but what is the '?' command, and what is the "Autoexec.bat" file equivalent in Linux, to insert the line.
At the time of initial boot there is no disk mounted, so there is no convenient place to dump the output. There is another way to record the boot messages: the serial port.
I like your serial port method. How about the screen buffer? Apparently the screen buffer holds all the boot messages, since I can scroll back with <control-pageup>. The buffer contents are still there at the login prompt, so how would you just dump the scrollback buffer to a file? Make sense or am I missing some point? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Documentation/lang/en/Configure.help;\ fi make -C scripts/lxdialog all make[1]: Entering directory `/usr/src/linux-2.2.16.SuSE/scripts/lxdialog' gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC="
" -c -o lxdialog.o lxdialog.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o checklist.o checklist.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o menubox.o menubox.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o textbox.o textbox.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o yesno.o yesno.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o inputbox.o inputbox.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o util.o util.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE -DCURSES_LOC=" " -c -o msgbox.o msgbox.c gcc -s -L . lxdialog.o checklist.o menubox.o textbox.o yesno.o inputbox.o util. o msgbox.o -lncurses -o lxdialog make[1]: Leaving directory `/usr/src/linux-2.2.16.SuSE/scripts/lxdialog' make -C scripts cfconv make[1]: Entering directory `/usr/src/linux-2.2.16.SuSE/scripts' sparc64-linux-gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -m64 -pipe -mno-fpu -mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -fcall-used-g5 -fcall-used-g7 -Wno-sign-compare -c -o cfparse.o cfparse.c In file included from /usr/include/stdio.h:57, from cfparse.c:5: /usr/include/libio.h:363: conflicting types for `__restrict' /usr/include/libio.h:363: previous declaration of `__restrict' /usr/include/libio.h:364: conflicting types for `__restrict' /usr/include/libio.h:363: previous declaration of `__restrict' /usr/include/libio.h:365: conflicting types for `__restrict' /usr/include/libio.h:365: previous declaration of `__restrict' In file included from cfparse.c:5: /usr/include/stdio.h:182: parse error before `__filename' /usr/include/stdio.h:185: parse error before `__filename' /usr/include/stdio.h:232: parse error before `__stream' /usr/include/stdio.h:236: parse error before `__stream' /usr/include/stdio.h:242: parse error before `__stream' /usr/include/stdio.h:251: parse error before `__stream' /usr/include/stdio.h:254: parse error before `__format' /usr/include/stdio.h:256: parse error before `__s' /usr/include/stdio.h:260: parse error before `__s' /usr/include/stdio.h:264: parse error before `__format' /usr/include/stdio.h:267: parse error before `__s' /usr/include/stdio.h:273: parse error before `__s' /usr/include/stdio.h:277: parse error before `__s' /usr/include/stdio.h:281: parse error before `__s' /usr/include/stdio.h:310: parse error before `__stream' /usr/include/stdio.h:313: parse error before `__format' /usr/include/stdio.h:315: parse error before `__s' /usr/include/stdio.h:393: parse error before `__s' /usr/include/stdio.h:428: parse error before `__s' /usr/include/stdio.h:446: parse error before `__ptr' /usr/include/stdio.h:449: parse error before `__ptr' /usr/include/stdio.h:454: parse error before `__ptr' /usr/include/stdio.h:456: parse error before `__ptr' /usr/include/stdio.h:499: parse error before `__stream' In file included from /usr/include/stdio.h:633, from cfparse.c:5: /usr/include/bits/stdio.h:33: parse error before `__fmt' /usr/include/bits/stdio.h:34: warning: function declaration isn't a
Dear Friends, I got SuSE Linux to run on a Sun Ultra 10 SPARC machine, and after installing it, i'm trying to change the kernel but after issuing make menuconfig, i get the following error: bash-2.04# cd /usr/src/linux bash-2.04# make menuconfig Creating new version.h for 2.2.16 rm -f include/asm ( cd include ; ln -sf asm-sparc64 asm) if [ ! -s Documentation/lang/en/Configure.help ]; then \ cp Documentation/lang/configlang.help.en Documentation/lang/en/Configure.help;\cat Documentation/Configure.help prototype /usr/include/bits/stdio.h: In function `vprintf': /usr/include/bits/stdio.h:35: `__fmt' undeclared (first use in this function) /usr/include/bits/stdio.h:35: (Each undeclared identifier is reported only once/usr/include/bits/stdio.h:35: for each function it appears in.) /usr/include/bits/stdio.h:35: `__arg' undeclared (first use in this function) /usr/include/stdlib.h: At top level: In file included from cfparse.c:6: /usr/include/stdlib.h:96: parse error before `__nptr' /usr/include/stdlib.h:109: parse error before `__nptr' /usr/include/stdlib.h:112: parse error before `__nptr' /usr/include/stdlib.h:119: parse error before `__nptr' /usr/include/stdlib.h:123: parse error before `__nptr' /usr/include/stdlib.h:133: parse error before `__nptr' /usr/include/stdlib.h:137: parse error before `__nptr' /usr/include/stdlib.h:196: parse error before `__nptr' /usr/include/stdlib.h:199: parse error before `__nptr' /usr/include/stdlib.h:202: parse error before `__nptr' /usr/include/stdlib.h:206: parse error before `__nptr' /usr/include/stdlib.h:213: parse error before `__nptr' /usr/include/stdlib.h:221: parse error before `__nptr' /usr/include/stdlib.h:229: parse error before `__nptr' /usr/include/stdlib.h:243: parse error before `__nptr' /usr/include/stdlib.h:244: warning: function declaration isn't a prototype /usr/include/stdlib.h: In function `strtod': /usr/include/stdlib.h:245: `__nptr' undeclared (first use in this function) /usr/include/stdlib.h:245: `__endptr' undeclared (first use in this function) /usr/include/stdlib.h: At top level: /usr/include/stdlib.h:248: parse error before `__nptr' /usr/include/stdlib.h:250: warning: function declaration isn't a prototype /usr/include/stdlib.h: In function `strtol': /usr/include/stdlib.h:251: `__nptr' undeclared (first use in this function) /usr/include/stdlib.h:251: `__endptr' undeclared (first use in this function) /usr/include/stdlib.h:251: `__base' undeclared (first use in this function) /usr/include/stdlib.h: At top level: /usr/include/stdlib.h:254: parse error before `__nptr' /usr/include/stdlib.h:256: warning: function declaration isn't a prototype /usr/include/stdlib.h: In function `strtoul': /usr/include/stdlib.h:257: `__nptr' undeclared (first use in this function) /usr/include/stdlib.h:257: `__endptr' undeclared (first use in this function) /usr/include/stdlib.h:257: `__base' undeclared (first use in this function) /usr/include/stdlib.h: At top level: /usr/include/stdlib.h:275: parse error before `__nptr' /usr/include/stdlib.h:277: warning: function declaration isn't a prototype /usr/include/stdlib.h: In function `strtoq': /usr/include/stdlib.h:278: `__nptr' undeclared (first use in this function) /usr/include/stdlib.h:278: `__endptr' undeclared (first use in this function) /usr/include/stdlib.h:278: `__base' undeclared (first use in this function) /usr/include/stdlib.h: At top level: /usr/include/stdlib.h:281: parse error before `__nptr' /usr/include/stdlib.h:293: `__base' undeclared (first use in this function) /usr/include/stdlib.h: At top level: /usr/include/stdlib.h:296: parse error before `__nptr' /usr/include/stdlib.h:298: warning: function declaration isn't a prototype /usr/include/stdlib.h: In function `strtoull': /usr/include/stdlib.h:299: `__nptr' undeclared (first use in this function) /usr/include/stdlib.h:299: `__endptr' undeclared (first use in this function) /usr/include/stdlib.h:299: `__base' undeclared (first use in this function) /usr/include/stdlib.h: At top level: In file included from cfparse.c:6: /usr/include/stdlib.h:379: parse error before `__buf' /usr/include/stdlib.h:385: parse error before `__statebuf' /usr/include/stdlib.h:389: parse error before `__statebuf' /usr/include/stdlib.h:438: parse error before `__buffer' /usr/include/stdlib.h:441: parse error before `__buffer' /usr/include/stdlib.h:445: parse error before `__buffer' /usr/include/stdlib.h:448: parse error before `__buffer' /usr/include/stdlib.h:452: parse error before `__buffer' /usr/include/stdlib.h:455: parse error before `__buffer' In file included from cfparse.c:6: /usr/include/stdlib.h:595: parse error before `__name' /usr/include/stdlib.h:651: parse error before `__decpt' /usr/include/stdlib.h:657: parse error before `__decpt' /usr/include/stdlib.h:667: parse error before `__decpt' /usr/include/stdlib.h:669: parse error before `__decpt' /usr/include/stdlib.h:676: parse error before `__decpt' /usr/include/stdlib.h:679: parse error before `__decpt' /usr/include/stdlib.h:684: parse error before `__decpt' /usr/include/stdlib.h:687: parse error before `__decpt' /usr/include/stdlib.h:698: parse error before `__pwc' /usr/include/stdlib.h:706: parse error before `__pwcs' /usr/include/stdlib.h:709: parse error before `__s' In file included from cfparse.c:7: /usr/include/string.h:37: parse error before `__dest' /usr/include/string.h:71: parse error before `__dest' /usr/include/string.h:74: parse error before `__dest' /usr/include/string.h:78: parse error before `__dest' /usr/include/string.h:81: parse error before `__dest' /usr/include/string.h:92: parse error before `__dest' /usr/include/string.h:176: parse error before `__s' /usr/include/string.h:181: parse error before `__s' /usr/include/string.h:185: parse error before `__s' /usr/include/string.h:282: parse error before `__stringp' make[1]: *** [cfparse.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.2.16.SuSE/scripts' make: *** [menuconfig] Error 2 bash-2.04# Is there someone aware of this error and how to correct it? (this message is being sent to the englisch and german lists. THX in advance for any help. -- Paulo J V Wollny ---------------- mailto:paulo@wollny.com.br phone/fax: +55 (21) 512-4380 Rio de Janeiro / Brazil -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi, On Thu, 5 Oct 2000, Paulo Wollny wrote:
I got SuSE Linux to run on a Sun Ultra 10 SPARC machine, and after installing it, i'm trying to change the kernel but after issuing make menuconfig, i get the following error:
[BIG ERROR SNIP]
Is there someone aware of this error and how to correct it?
Sorry, no clue. You might want to consider to subscribe to suse-sparc@suse.com, this is where the experts are :) Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Too often justice is incidental to law and order. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
zentara wrote:
"Rafael E. Herrera" wrote:
At the time of initial boot there is no disk mounted, so there is no convenient place to dump the output. There is another way to record the boot messages: the serial port.
I like your serial port method. How about the screen buffer? Apparently the screen buffer holds all the boot messages, since I can scroll back with <control-pageup>. The buffer contents are still there at the login prompt, so how would you just dump the scrollback buffer to a file?
Make sense or am I missing some point?
In some instances all the boot messages will be lost: if you switch consoles, including booting all the way graphics mode; when you load a different console font; sometimes the messages are too may, the buffers is overrun. If all the messages are available in your console (by Shift PgUp/PgDown) and you have loaded gpm, then just copy and paste (I haven't tried this, but I don't think it won't work.) Rafael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
"Rafael E. Herrera" wrote:
zentara wrote:
"Rafael E. Herrera" wrote:
At the time of initial boot there is no disk mounted, so there is no convenient place to dump the output. There is another way to record the boot messages: the serial port.
I like your serial port method. How about the screen buffer? Apparently the screen buffer holds all the boot messages, since I can scroll back with <control-pageup>. The buffer contents are still there at the login prompt, so how would you just dump the scrollback buffer to a file?
Make sense or am I missing some point?
In some instances all the boot messages will be lost: if you switch consoles, including booting all the way graphics mode; when you load a different console font; sometimes the messages are too may, the buffers is overrun.
If all the messages are available in your console (by Shift PgUp/PgDown) and you have loaded gpm, then just copy and paste (I haven't tried this, but I don't think it won't work.)
Rafael
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Nobody has answered my original question. Is there a way to temporarily suspend the boot up process? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Jerry VB wrote:
Nobody has answered my original question.
Is there a way to temporarily suspend the boot up process?
Yes and no. The messages you get when the kernel loads may not be stoppable. After init is started, it first runs the /sbin/init.d/boot script. See if you can edit it and add pauses or something. init also runs the scripts in /sbin/init.d according to the run level you set up. If you don't know what init is or does then you should look at documentaion on how linux is booted before messing with it. -- Rafael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
"Rafael E. Herrera" wrote:
Jerry VB wrote:
Nobody has answered my original question.
Is there a way to temporarily suspend the boot up process?
Yes and no. The messages you get when the kernel loads may not be stoppable. After init is started, it first runs the /sbin/init.d/boot script. See if you can edit it and add pauses or something. init also runs the scripts in /sbin/init.d according to the run level you set up. If you don't know what init is or does then you should look at documentaion on how linux is booted before messing with it.
How about booting lilo with "init=/bin/sh" That will stop the boot process right before init starts. Then manually start the real init. At least it will give you a stop point. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Is there a way to temporarily suspend the boot up process?
Yes and no. The messages you get when the kernel loads may not be stoppable. After init is started, it first runs the /sbin/init.d/boot script. See if you can edit it and add pauses or something. init also runs the scripts in /sbin/init.d according to the run level you set up. If you don't know what init is or does then you should look at documentaion on how linux is booted before messing with it.
How about booting lilo with "init=/bin/sh" That will stop the boot process right before init starts. Then manually start the real init. At least it will give you a stop point.
init gets PID 1, which is a special one, it doesn't get recycled and who knows what other magic. It may work for debugging your system, I don't know what will be the effects of setting a machine to boot that way. How about just adding a sleep command at the top of /sbin/init.d/boot, that should stop the boot process. -- Rafael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Message-Id: <5.0.2.1.2.20001213092056.00b7f970@mail.ods.co.cr>
Date: Wed, 13 Dec 2000 09:24:01 -0600
From: Linux News User
Hi to all !! 1. Happy new year ! 2. I remember that SuSE has enable an FTP foreign server to allow to download of the SSH package from SuSE and other security packages. Could any one send me that URL ? I try to find that URL on SuSE site's because I remember a Security News that explain that situation but I can't find it ! :( Thanks bye --ed
On Tue, Jan 02, 2001 at 02:18:12PM -0600, Linux News User wrote:
Hi to all !!
1. Happy new year !
2. I remember that SuSE has enable an FTP foreign server to allow to download of the SSH package from SuSE and other security packages. Could any one send me that URL ? I try to find that URL on SuSE site's because I remember a Security News that explain that situation but I can't find it ! :(
Try one of the mirror sites, like ftp.gwdg.de. It should be somewhere under /linux/suse/7.0 HTH, Kastus
Thanks
bye
--ed
Hi Fellows !! I just receive as a gift a LifeView'98 PCI TV Card. I have SuSE 7.0 installed on my home PC. Does any one know from where I can get instructions about hot to setup it ? thanks --ed
On Tue, 9 Jan 2001, Linux News User wrote: <*]Hi Fellows !! <*] <*]I just receive as a gift a LifeView'98 PCI TV Card. <*] <*]I have SuSE 7.0 installed on my home PC. <*] <*]Does any one know from where I can get instructions about hot to setup it ? Hi, Documentation related to TV Cards can be found in the kernel sources: /usr/src/linux/Documentation/video4linux/bttv And, of course, on Video4Linux web page: http://roadrunner.swansea.linux.org.uk/v4l.shtml http://www.exploits.org/v4l/ You will need Video4Linux support compiled in the kernel as well as support for tv cards (bt848 compatible cards...) Cheers. /NB ________________ Nicolas Beaulieu Economics Department, Universite Laval Centre de Recherches en Economie et Finances Appliquees (CREFA) Quebec, Canada mailto:nicolas.beaulieu@ecn.ulaval.ca _________________ http://patagonia.dyndns.org ICQ 15933500 Teamwork is essential: it allows you to blame someone else. _________________
On Tue, Jan 09, 2001 at 02:33:10PM -0600 or thereabouts, Linux News User wrote:
Hi Fellows !!
I just receive as a gift a LifeView'98 PCI TV Card.
I have SuSE 7.0 installed on my home PC.
Does any one know from where I can get instructions about hot to setup it ?
you might want just to turn the thing on, as it is now built into the standard kernel in V7. That is what I did, and it fired up immediately. Did'nt have to do a thing. Either use xawtv or kwintv. -- Best regards, Gary Today's thought: BREAKFAST.COM Halted - Cereal port not responding.
Hi Fellows !! Does any one have used and AHA-19160 SCSI Controller card successfully with SuSE 7.x ? Thanks --ed
yape..... :)
----- Original Message -----
From: "Linux News User"
Hi Fellows !!
Does any one have used and AHA-19160 SCSI Controller card successfully with SuSE 7.x ?
Thanks
--ed
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Jerry VB wrote:
Nobody has answered my original question.
Is there a way to temporarily suspend the boot up process?
kernel messages: no :( rc scripts: scroll-lock :) scroll-lock locks :) the screen until you press it again (or the control-? counterparts: control-s activate, control-q deactivate) but sometimes in the process of booting (near file system checks) it unlocks itself (maybe some script sends a escape sequence to the console unlocking it) REgards, Adilson -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (13)
-
adilson＠rapunza.org -
e.richards＠clear.net.nz -
Gary -
grimmer＠suse.de -
jerryvb＠mindspring.com -
kastus＠tsoft.com -
kh -
Linux News User -
linux＠ods.co.cr
-
Nicolas Beaulieu -
paulo＠wollny.com.br -
raffo＠neuronet.pitt.edu -
zentara＠gypsyfarm.com