Re: gmirror with hot spare
On 4/25/06, Vladimir Terziev [EMAIL PROTECTED] wrote: Hi hackers, is there a way to assign a hot spare disk/partition to a gmirror -ed disks/partitions ? There's no sense in it, is there? When we have RAID5 hot spare is needed, because we don't know what drive will fail first. When we have gmirror, it doesn't matter! Just add another drive to gmirror and take it easy. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
config(8), include, and INCLUDE_CONFIG_FILE
Dear colleagues, Since include statement has been invented in config(8), option INCLUDE_CONFIG_FILE is broken, as it's embedding only highest level config file into the kernel. I looked through the sources, but it seems fixing this is not very easy. The most natural way for me seems tracking all config while lex/yacc parsing into memory buffer, as configfile() is invoked after full config parse. Any thoughts? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Zero Copy, FreeBSD and Linus Torvalds opinion
Hello guys, in bsdnews.com i found this link http://kerneltrap.org/node/6506 and particulary this: I claim that Mach people (and apparently FreeBSD) are incompetent idiots. Playing games with VM is bad. memory copies are _also_ bad, but quite frankly, memory copies often have _less_ downside than VM games, and bigger caches will only continue to drive that point home. What do you think about it? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Zero Copy, FreeBSD and Linus Torvalds opinion
On Mon, May 01, 2006 at 12:09:29AM +0300, Iantcho Vassilev wrote.. Hello guys, in bsdnews.com i found this link http://kerneltrap.org/node/6506 and particulary this: I claim that Mach people (and apparently FreeBSD) are incompetent idiots. Playing games with VM is bad. memory copies are _also_ bad, but quite frankly, memory copies often have _less_ downside than VM games, and bigger caches will only continue to drive that point home. What do you think about it? That you are a bit late in discovering this one ;) Enough time has been wasted on it, at least on the project-internal lists, so please let it rest. -- Wilko Bulte [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: Zero Copy, FreeBSD and Linus Torvalds opinion
The implementation is 7 years old, not used by default, and was intended for a specific application. There really isn't much to say. -Kip On 4/30/06, Iantcho Vassilev [EMAIL PROTECTED] wrote: Hello guys, in bsdnews.com i found this link http://kerneltrap.org/node/6506 and particulary this: I claim that Mach people (and apparently FreeBSD) are incompetent idiots. Playing games with VM is bad. memory copies are _also_ bad, but quite frankly, memory copies often have _less_ downside than VM games, and bigger caches will only continue to drive that point home. What do you think about it? ___ 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: Zero Copy, FreeBSD and Linus Torvalds opinion
Iantcho Vassilev wrote: Hello guys, in bsdnews.com i found this link http://kerneltrap.org/node/6506 and particulary this: I claim that Mach people (and apparently FreeBSD) are incompetent idiots. Playing games with VM is bad. memory copies are _also_ bad, but quite frankly, memory copies often have _less_ downside than VM games, and bigger caches will only continue to drive that point home. What do you think about it? I claim that Linus is an attention whore. How about that? Scott ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Zero Copy, FreeBSD and Linus Torvalds opinion
On Sunday 30 April 2006 5:15 pm, Wilko Bulte wrote: On Mon, May 01, 2006 at 12:09:29AM +0300, Iantcho Vassilev wrote.. Hello guys, in bsdnews.com i found this link http://kerneltrap.org/node/6506 and particulary this: I claim that Mach people (and apparently FreeBSD) are incompetent idiots. Playing games with VM is bad. memory copies are _also_ bad, but quite frankly, memory copies often have _less_ downside than VM games, and bigger caches will only continue to drive that point home. What do you think about it? I've known for quite some time that things like this are said. One thing no one points out is how Linus is actually a fan of BSD. Sometimes things he says are mis quoted though. If you watch Revolution OS, Linus points out that his main thing for doing Linux was that he wanted something like he had used at the university he was at and he says it was SunOS. Sun OS / Solaris, are straight BSD. For info on where I get this, get the movie 20 years of Berkeley UNIX. I own that and Revolution OS, Linus Loves BSD even though he's sometimes mis quoted or even joking. -Allen A Linux and BSD and BeOS user. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] Fancy rc startup style RFC
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? TODO: One thing I am trying to figure out is how to get the terminal to report its width, in columns (which is something that VT100+ supports). I just don't know how to do it from a script. TODO: Get better reporting from the rc.d/* scripts (and whatever other services we track). Right now, if verbose is on, many services respond with OK when they aren't initialized, and some respond with SKIP/SKIPPED/FAILED. E.g.: pcvt will show SKIP, but geli2 will show OK. Neither of these two are enabled for me though. You may get it from here: http://www.cokane.org/files/rc_fancy-cokane5.patch Further: I am very open to suggestions regarding the rc.d/* system and its reporting mechanisms. I am even thinking that it might be a good idea to offer an overhauled set of scripts that forces functionality into the following framework: rc job offers result code (from which the OK,SKIP,ERROR, etc... are picked) rc job offers short ( 20 char) status message. This could be printed in a nice fashion just after the Running start XXX, Running stop YYY, which we currently display. rc job (or rc itself) offers name of job (geli2, moused, etc...). Thus, the lines are nice, consistent, and fluid. The short status message above would most likely be truncated to 20 chars (or so.). Hopefully, some of this can then start to be put into an rc-reporter such that I could run a command that could give me a nice report of rc/init: moused FAILEDshort message Gentoo has a nice script named rc-status that does similar. Though I am not too fond of its output format (job name at left, status at right edge, hard to find out what failed in a multiline report). Try this latest version, and drop a line back with your thoughts, criticisms, etc -- Coleman Kane [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: [PATCH] Fancy rc startup style RFC
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. TODO: One thing I am trying to figure out is how to get the terminal to report its width, in columns (which is something that VT100+ supports). I just don't know how to do it from a script. I looked into that too, without finding a good way to do that. TODO: Get better reporting from the rc.d/* scripts (and whatever other services we track). Right now, if verbose is on, many services respond with OK when they aren't initialized, and some respond with SKIP/SKIPPED/FAILED. E.g.: pcvt will show SKIP, but geli2 will show OK. Neither of these two are enabled for me though. I agree here, and started looking into many of the scripts there now. There are a lot that need tweaking, but in the long run, I think it would be very nice and clean, and allow for some nice reporting and logging. You may get it from here: http://www.cokane.org/files/rc_fancy-cokane5.patch Further: I am very open to suggestions regarding the rc.d/* system and its reporting mechanisms. I am even thinking that it might be a good idea to offer an overhauled set of scripts that forces functionality into the following framework: rc job offers result code (from which the OK,SKIP,ERROR, etc... are picked) rc job offers short ( 20 char) status message. This could be printed in a nice fashion just after the Running start XXX, Running stop YYY, which we currently display. rc job (or rc itself) offers name of job (geli2, moused, etc...). Thus, the lines are nice, consistent, and fluid. The short status message above would most likely be truncated to 20 chars (or so.). Hopefully, some of this can then start to be put into an rc-reporter such that I could run a command that could give me a nice report of rc/init: moused FAILEDshort message Gentoo has a nice script named rc-status that does similar. Though I am not too fond of its output format (job name at left, status at right edge, hard to find out what failed in a multiline report). Try this latest version, and drop a line back with your thoughts, criticisms, etc Thanks again for taking hold of this and driving it further! 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]
Boot manager beep (revisited)
This thread: http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html mentions a patch to disable the boot manager beep, and also discusses having it optional. I don't have enough asm-fu to make that option happen, but I can tell you, that on laptops, that beep is really annoying, and amazingly loud. Is this just waiting for an able minded person to code up the options and submit? 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: Boot manager beep (revisited)
Eric Anderson wrote: This thread: http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html mentions a patch to disable the boot manager beep, and also discusses having it optional. I don't have enough asm-fu to make that option happen, but I can tell you, that on laptops, that beep is really annoying, and amazingly loud. Is this just waiting for an able minded person to code up the options and submit? Most laptops have a PC speaker volume control or on/off at boot in the BIOS. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Zero Copy, FreeBSD and Linus Torvalds opinion
On Mon, 2006-05-01 at 00:09 +0300, Iantcho Vassilev wrote: incompetent idiots. quote What do you think about it? It is better to remain silent and be thought a fool, than to speak, and remove all doubt. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot manager beep (revisited)
On 2006-04-30 22:34, Eric Anderson [EMAIL PROTECTED] wrote:
This thread:
http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html
mentions a patch to disable the boot manager beep, and also
discusses having it optional. I don't have enough asm-fu to make
that option happen, but I can tell you, that on laptops, that beep
is really annoying, and amazingly loud. Is this just waiting for an
able minded person to code up the options and submit?
I don't like the beep either, so I usually patch my systems manually
to include something very similar:
# Index: boot0.S
# ===
# --- boot0.S (.../branches/ncvs/src/sys/boot/i386/boot0) (revision 45)
# +++ boot0.S (.../trunk/src/sys/boot/i386/boot0) (revision 45)
# @@ -201,9 +201,7 @@
# /*
# * Start of input loop. Beep and take note of time
# */
# -main.10: movb $ASCII_BEL,%al # Signal
# - callw putchr# beep!
# - xorb %ah,%ah# BIOS: Get
# +main.10: xorb %ah,%ah# BIOS: Get
# int $0x1a # system time
# movw %dx,%di# Ticks when
# addw _TICKS(%bp),%di# timeout
Since this is asm, and it runs very very early in the boot process, we
don't have the luxury of making this tunable in `/boot/loader.conf',
but there's nothing wrong with making it tunable through an option in
our modern `/etc/src.conf' option system. We could use something like
the following:
WITHOUT_BOOTEASY_BEEP= yes
and then we can add the necessary Makefile-foo in `/usr/src/sys/boot'
to turn this to a preprocessor #define.
Does something like the following sound reasonable (I haven't had a
chance to run this through a build-test, so use with care). The
default behavior should be to *include* a beep, but it can be turned
off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'.
# Index: boot0.S
# ===
# --- boot0.S (.../branches/ncvs/src/sys/boot/i386/boot0) (revision 47)
# +++ boot0.S (.../trunk/src/sys/boot/i386/boot0) (revision 47)
# @@ -201,8 +201,11 @@
# /*
# * Start of input loop. Beep and take note of time
# */
# -main.10: movb $ASCII_BEL,%al # Signal
# +main.10:
# +#ifdef BOOTEASY_BEEP
# + movb $ASCII_BEL,%al # Signal
# callw putchr# beep!
# +#endif
# xorb %ah,%ah# BIOS: Get
# int $0x1a # system time
# movw %dx,%di# Ticks when
# Index: Makefile
# ===
# --- Makefile(.../branches/ncvs/src/sys/boot/i386/boot0) (revision 47)
# +++ Makefile(.../trunk/src/sys/boot/i386/boot0) (revision 47)
# @@ -54,6 +54,10 @@
# -DTICKS=${BOOT_BOOT0_TICKS} \
# -DCOMSPEED=${BOOT_BOOT0_COMCONSOLE_SPEED}
#
# +.if !defined(WITHOUT_BOOTEASY_BEEP) || (${WITHOUT_BOOTEASY_BEEP} != no
${WITHOUT_BOOTEASY_BEEP} != NO)
# +CFLAGS+=-DBOOTEASY_BEEP
# +.endif
# +
# LDFLAGS=-N -e start -Ttext ${BOOT_BOOT0_ORG} -Wl,-S,--oformat,binary
#
# .include bsd.prog.mk
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
