Re: [gentoo-user] What the £$%^ happened?
On Fri, 2003-02-07 at 09:10, Matt Tucker wrote: -- John Nilsson [EMAIL PROTECTED] spake thusly: Can you in bash script redirect output to two files? i.e. stdout to stdout AND boot.log, stderr to boot.log? And would this caputre the output of scriptes executed from this script? $ man tee thanx, just what I needed, I suppose I could redirect stdout and stderr via tee to logfiles in the /sbin/rc script... working on it /John -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What the £$%^ happened?
On Fri, 2003-02-07 at 11:37, MAL wrote: On a similar note, does anyone else think it would be a good idea for emerge to collate the 'information' text that packages such as portage dump to the console while emerging, to display at the end of a long emerge? OK, portage isn't a problem any more, because it halts the emerge, but when I emerge a lot of other packages together, useful info messages that the package designer obviously wants read, speed by and are lost... only to be found by reading the ebuild :/ That has been discussed many times over, and I believe it's being worked on (wasn't that a feature mentioned in a weekly newsletter?) -- Mike Williams [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] What the £$%^ happened?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | At the end of every install/update emerge will tell you if there are any | config files to update, *UPDATE THEM*! The tool to do so was moved into | portage for this very reason. | I do update them. I'm not an idiot and I understand the reasons for doing so. If this problem was caused by a config problem then it must be that I updated the file incorrectly, or completely disregarded the updates in preference to keeping the old file. This leads me to the reason I don't like updating baselayout - it contains lots of config files, and it takes a lot of time to go through them and OK all the changes and it's easy to make mistakes. I think work is being done on automating some of this in particular auto-updating files that the user has never altered, which is a very good thing. Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Q6MuX3TTUvZURBERAkYHAKCEZ5mRTD7g0u5Dm/6a/6cJoKU7TwCdGzGa 6An9JKFaXm+PMkAiDQXlcLI= =uFdg -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What the $%^ happened?
Mike Williams wrote: On Fri, 2003-02-07 at 11:37, MAL wrote: On a similar note, does anyone else think it would be a good idea for emerge to collate the 'information' text that packages such as portage dump to the console while emerging, to display at the end of a long emerge? OK, portage isn't a problem any more, because it halts the emerge, but when I emerge a lot of other packages together, useful info messages that the package designer obviously wants read, speed by and are lost... only to be found by reading the ebuild :/ That has been discussed many times over, and I believe it's being worked on (wasn't that a feature mentioned in a weekly newsletter?) Thanks, and sorry for repeating then :) (I didn't notice it) MAL -- [EMAIL PROTECTED] mailing list
[gentoo-user] What the £$%^ happened?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I did my updates today, which I believe included baselayout and everything seems to have gone a bit weird. The first time I rebooted I got an error message and the boot stopped and dropped me into emergency maintenence mode telling me to recreate /var/state/init.d/ or else the system couldn't boot. This I did, then restarted and the system came up and appears to be fine, other than the fact that I get a whole assload of error messages appear on bootup. The first one complains about a runlevel (sysinit?) being missing, the others appear to be various things from mount and other stuff, but they go past too quickly to get a good look. (sidenote: Is the output produced on boot captured anywhere? I think Redhat gives you a /var/log/boot.log.. does Gentoo have an equivalent?) What happened? Is this something I should have expected or is something broken? It's getting to the stage that I loathe to see baselayout come up for an ~ emerge, because it always seems to indicate trouble a brewing. ;) Cheers, Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+QunCX3TTUvZURBERAmyXAJ9ee8MFc4mNERnET6RtVU6QP+NeqwCfTSL4 F/YrL4aGCVGs7FdCcONwNAk= =ZFWV -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What the £$%^ happened?
On Thu, 6 Feb 2003, Andy Arbon wrote: (sidenote: Is the output produced on boot captured anywhere? I think Redhat gives you a /var/log/boot.log.. does Gentoo have an equivalent?) dmesg -- Larry Herzog Jr.Do nothing out of selfish ambition or vain ZRXOA #1029 conceit, but in humility consider others [EMAIL PROTECTED] better than yourselves. - Philippians 2:3 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What the £$%^ happened?
On Thursday 06 February 2003 21:49, Collins Richey wrote: On Thu, 06 Feb 2003 23:17:58 + Andy Arbon [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: |(sidenote: Is the output produced on boot captured anywhere? I think |Redhat gives you a /var/log/boot.log.. does Gentoo have an | |equivalent?) | dmesg Thanks for the suggestion, but that's not quite what I was after... That~ seems to be messages from the kernel during bootup, whereas I was after the output from the entire boot process - basically everything you see go past onscreen as the system starts up. I, too, would love to see this feature. For example, my ALSA sound card module produces error messages when loading, but nothing is captured in DMESG. The sound card works just fine in spite of the error messages, so I haven't pursued the matter. It would be nice if all the boot scripts had a debugging option that would append what goes to the console to a file. # echo '/bin/dmesg -s 65536 /var/log/dmesg' /etc/conf.d/local.start -- D. Wollmann gpg 58A7 2C9A FCBC 8B4A 6F76 1BF1 9BE0 FB93 34C8 8A21 msg00724/pgp0.pgp Description: signature
