Re: [PATCH] Fancy rc startup style RFC
Coleman Kane wrote: On Wed, May 24, 2006 at 12:29:28PM -0500, Eric Anderson wrote, and it was proclaimed: Eric Anderson wrote: Coleman Kane wrote: On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: Brooks Davis wrote: On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: Brooks Davis wrote: On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: Coleman Kane wrote: On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: Eric Anderson wrote: Actually, some other things got changed somewhere in the history, that broke some things and assumptions I was making. This patch has them fixed, and I've tested it with all the different options: http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 It's missing the defaults/rc.conf diffs, but you should already know those. Eric I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. This allows the use of: rc_fancy="YES"---> Turns on fancy reporting (w/o color) rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs rc_fancy="YES" rc_fancy_colour="YES" ---> Same as above for you on the other side of the pond. rc_fancy_verbose="YES" --> Turn on more verbose activity messages. This will cause what appear to be "false positives", where an unused service is "OK" instead of "SKIP". You can also customize the colors, the widths of the message brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and the contents of the message (OK versus GOOD versus BUENO). Also, we have the following message combinations: OK ---> Universal good message SKIP,SKIPPED ---> Two methods for conveying the same idea? ERROR,FAILED ---> Ditto above, for failure cases Should we just have 3 different messages, rather than 5 messages in 3 categories? Yes, that's something that started with my first patch, and never got ironed out. I think it should be: OK SKIPPED FAILED and possibly also: ERROR The difference between FAILED and ERROR would be that FAILED means the service did not start at all, and ERROR means it started but had some kind of error response. FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs FAILED or ERROR. True, however I still see a difference between FAILED and WARNING. For instance, as an example: a FAILED RAID is different than a RAID with a WARNING. For that level of detail, the ability to provide additional output seems like the appropriate solution. Yes, true, but you'd still want to show something (I would think) in the [ ]'s to keep it consistent. My feeling is that anything short of complete success should report WARNING and a message unless it actually totally failed in which case FAILED or ERROR (I slightly perfer ERROR) should be used. -- Brooks What situations are we determining get flagged as ERROR versus FAILED? Is FAILED considered to be 'I was able to run the command, but it returned an error code', versus ERROR being 'I could not even run the command!' like bad path, file not found, etc... This point still kind of confuses me (and needs to be well defined). I am an advocate of having three distinct messages: OK, SKIPPED, ERROR. And not even bothering with the different types of ERROR/FAILED other than having extra reporting output. I'm ok with just OK, SKIPPED, ERROR.. If there's ever a need for more, it's easy to add it. Eric Is this still planned to make it into -CURRENT? Thanks, Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology Anything that works is better than anything that doesn't. Yeah, I've been working on it in my spare time. I am investigating some avenues regarding status reporting from the rc scripts to the console. Also been slow getting some hardware together to put cokane.org back up and online. Mostly real-life just got in the way of freebsd for a little while. -- coleman kane Ok - just making sure it had not been forgotten. :) Thanks Coleman! Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology Anything that works is better than anything that doesn't. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up a serial console..
- Original Message - From: "Thierry Herbelot" <[EMAIL PROTECTED]> To: Cc: "OxY" <[EMAIL PROTECTED]> Sent: Thursday, May 25, 2006 8:39 PM Subject: Re: setting up a serial console.. Le Thursday 25 May 2006 17:16, OxY a écrit : hi! i have a simple question, but i didn't found the answer. after i set console=comconsole in the /boot/loader.conf and rebooted every output has been sent to the serial console, it's normal... in /boot/defaults/loader.conf you will find the following line : #console="vidconsole" # A comma separated list of console(s) you can have both a serial console and a video console by setting : console="vidconsole,comconsole" awesome, thx! TfH ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up a serial console..
Hello OxY, Thursday, May 25, 2006, 5:16:57 PM, you wrote: > hi! > i have a simple question, but i didn't found the answer. > after i set console=comconsole in the /boot/loader.conf > and rebooted every output has been sent to the serial console, > it's normal... > but! what if anything goes wrong, serial console not working, box cannot boot > up.. > how can i change the comconsole setting back to vidconsole? > is it possible? You should read more Handbook, it's a gread source of information: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html -- Sincerely, Daniel Gerzo ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting up a serial console..
Le Thursday 25 May 2006 17:16, OxY a écrit : > hi! > > i have a simple question, but i didn't found the answer. > > after i set console=comconsole in the /boot/loader.conf > and rebooted every output has been sent to the serial console, > it's normal... in /boot/defaults/loader.conf you will find the following line : #console="vidconsole" # A comma separated list of console(s) you can have both a serial console and a video console by setting : console="vidconsole,comconsole" TfH ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
setting up a serial console..
hi! i have a simple question, but i didn't found the answer. after i set console=comconsole in the /boot/loader.conf and rebooted every output has been sent to the serial console, it's normal... but! what if anything goes wrong, serial console not working, box cannot boot up.. how can i change the comconsole setting back to vidconsole? is it possible? thx! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[ANN] unionfs patchset-12 release
Hi Guys! It is my pleasure and honor to announce the availability of the unionfs patchset-12. Patchset-12: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p12.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p12.diff Changes in unionfs-p12.diff - Fixed a bug that responses without lock when share lock is requested with VOP_LOOKUP. - Fixed a bug that leads lock-around panic on FreeBSD 6.x. - others, misc bug fixes The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) Guys taking some panic troubles with p11, please try the p12 :) We think that p12 is better stable than p11. Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NOW: version 0.58 (Re: kldfind, updated for version 0.56 )
See the manpage for sysexits(3). Both should return EX_USAGE (64) in this case. You should only return EX_OK (0) if the command was successful. If you're spitting out usage text, return EX_USAGE. or a multi-line usage (e.g. something like bsdlabel(1)): kldfind [-qv] -c category ... kldfind [-qv] -s string ... kldfind -h Hi Rick, Greats for your feedback, i accept your sugestion and update kldfind and man for version v058, http://ricardo.epm.br/freebsd/script/kldfind/kldfind-v058. One questions !! What is necessary for include kldfind in HEAD ? -- Atenciosamente Ricardo A. Reis UNIFESP Unix and Network Adm ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
