Re: strange ATA behavior with -STABLE
On Wed, 10 Jul 2002, Mike Tancsa wrote: At 10:50 AM 10/07/2002 -0700, Bill Jones wrote: The obvious answer to me is Most common platform someone installs FreeBSD on for the first time. ... Then its good that Soren committed his changes. The misplaced splx() patch corrected the problem for some but not all which is in the .1 release. Please correct me if I'm wrong but I don't think the splx patch does anything to help people with broken CD-ROM drives. Cheers Michiel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: No root crontab in 4.6-RELEASE?
Thomas == Thomas Seck [EMAIL PROTECTED] writes: Thomas * Michael Sperber [Mr. Preprocessor] ([EMAIL PROTECTED]): Thomas == Thomas Seck [EMAIL PROTECTED] writes: Thomas [...] Cron also searches /etc/crontab Thomas Thomas The original poster obviously did not bother to read this document. Thomas Failing to read documentation and posting false claims on a public Thomas mailing list is a behaviour that drives me up the wall. That would be me, I guess. I never claimed there's no /etc/crontab file. I claimed there's no root crontab which, as some posters have noted, is something different. Thomas Uh, oh. My mind thought of the posting I originally replied to. Thomas What my hands made of it is what was finally sent out. Sorry. No problem! On the 4.3 systems I have around here, there's a root crontab starting like this: # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/adcrcln339/crontab installed on Mon Jun 11 20:53:28 2001) # (Cron version -- $FreeBSD: src/usr.sbin/cron/crontab/crontab.c,v 1.12.2.2 2000/12/11 01:03:31 obrien Exp $) It's no big deal. I was just wondering where that came from and why I'm no longer seeing it. Thomas I get your meaning. According to cvs, the behaviour of 'crontab -u root' Thomas was changed in version 1.12.2.3 of crontab.c, committed 2001/05/03 to Thomas RELENG_4. ... and here, finally, is the answer to my question. I never thought of looking at the history of crontab.c. Many thanks! -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Upcoming 4.6.1
I think 4.6.1 should contain following kernel fixes: 1. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=100548+0+archive/2002/freebsd-stable/20020630.freebsd-stable 2. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1982827+0+archive/2002/cvs-all/20020630.cvs-all 3. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1209006+0+archive/2002/cvs-all/20020707.cvs-all 4. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=351587+0+archive/2002/cvs-all/20020630.cvs-all Igor Sysoev http://sysoev.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.6-RELEASE - 4.5-RELENG
On Thu, 11 Jul 2002, Shannon -jj Behrens wrote: SjB While there are a few niggles, the proper sequence is: SjB mergemaster -p (This is NEW!) SjB make buildworld SjB make kernel KERNCONF=your_kernel_conf_name SjB REBOOT into single-user mode! (This does not mean drop to single user.) SjB fsck -p SjB mount -a -t ufs SjB cd /usr/src SjB make installworld SjB mergemaster -i (-a is a bit inadequate unless you go back and clean up SjB the mess it often leaves before going to multi-user SjB mode.) SjB exit (to multi-user mode) SjB SjB Shouldn't make installkernel come after make kernel...? Nope. kernel target is buildkernel then installkernel Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: strange ATA behavior with -STABLE
An interesting point. Perhaps my perspective has been coming across as arguing the wrong side. I agree that new installs are the most important. Changes which enable FreeBSD to work on what sort of systems people are purchasing at Dell, Best Buy, Circuit City and other retailers should matter greatly. Secondary, but still important, is making sure the changes break the least amount of legacy hardware as possible. I'd consider 5-6 years a good rule of thumb. If the hardware has gone unsupported for 5 years, then if it's not a huge installed base, losing support for it in BSD will have minimal impact. There have been problems with 4.6-RELEASE with new installs -- CD- ROM problems come to mind immediately. These are related to the ata commits. I would like to see 4.6.1 remedy this situation before our reputation as simple-to-install, always-works OS begins to falter. Admittedly, I can't argue as strongly for my case and the fact that I haven't upgraded. After all, I'm already running FreeBSD. :) I'll hop off the soapbox now. [EMAIL PROTECTED] wrote: But the new drivers probably support more first-time installs than the old one does. I know that it corrected multiple problems for me. I *am* running on a laptop, though. OTOH, that's sure getting to be more common rather than less over time. The *problem* is that it also broke some old hardware that previously worked. If you agree that the most important is what will work for most *new* installs, I believe that you are probably arguing the wrong side of the issue, or at the very least it's not clear what the right side of the issue would be. If you want to argue that the commit was a bad idea, then you'd have a much stronger case by arguing that FreeBSD shouldn't break what previously worked so that people aren't afraid to upgrade. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: strange ATA behavior with -STABLE
Thus spake Bill Jones [EMAIL PROTECTED]: There have been problems with 4.6-RELEASE with new installs -- CD- ROM problems come to mind immediately. These are related to the ata commits. I would like to see 4.6.1 remedy this situation before our reputation as simple-to-install, always-works OS begins to falter. FreeBSD has a reputation of being easy to install? ... Well, I guess that's true if you're not using sysinstall. ``What do you mean `I have to choose /exit/ to proceed to the next step of the installation'?'' :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Software raid 1 on root partition?
On Thu, 11 Jul 2002 09:10:15 -0500 Jim C. Nasby [EMAIL PROTECTED] wrote: JCN No, there is no support for software raid on the root partition. This is JCN on the vinum wishlist, though, so hopefully it will happen at some Er - have you seen man atacontrol in RELENG_4 lately ? I will quote the most pertinent extract: Allthough the ATA driver allows for creating an ATA RAID on disks on any controller, there are restrictions. It is only pos sible to boot on an array if its either located on a real ATA RAID controller like the Promise or Highpoint controllers, or if the RAID declared is of RAID1 or SPAN type, in case of a SPAN the partition to boot must reside on the first disk in the SPAN So the answer is - yes you can. -- C:WIN | Directable Mirrors The computer obeys and wins.|A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.6-RELEASE - 4.5-RELENG
On Wed, Jul 10, 2002 at 15:17 -0700, Kevin Oberman wrote: Date: Wed, 10 Jul 2002 21:40:51 +0200 From: Gerhard Sittig [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Wed, Jul 10, 2002 at 10:56 -0700, Kevin Oberman wrote: [ ... upgrading from source ... ] While there are a few niggles, the proper sequence is: mergemaster -p (This is NEW!) Should this read sh usr.sbin/mergemaster/mergemaster.sh -p for the case where your in $PATH mergemaster(8) is just old enough to not know the -p switch or where it lacks needed preparation steps for the buildworld run to come? Actually, I believe that it should. Thanks for pointing this out. I just checked rev $FreeBSD: src/UPDATING,v 1.73.2.72 2002/07/05 12:48:52 des Exp $ of the UPDATING file (i.e. the one in the -STABLE tree). While the 20020415 and 20020404 entries talk about using the new version of mergemaster and especially the latter mentions the -p option, the COMMON ITEMS section only has the (non special) mergemaster invocation after the installworld run. How about the following addition? (I didn't think too long about the 3.x - 4.x cross update since I'm not too familiar with it while I did a 4.0 - 4.6 update just last week:) Index: UPDATING === RCS file: /CVSREPO/FreeBSD/src/UPDATING,v retrieving revision 1.73.2.72 diff -u -r1.73.2.72 UPDATING --- UPDATING2002/07/05 12:48:52 1.73.2.72 +++ UPDATING2002/07/11 17:01:01 @@ -447,6 +447,7 @@ To update from 4.0-RELEASE or later to the most current 4.x-STABLE -- + sh usr.sbin/mergemaster/mergemaster.sh -p [3] make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE @@ -466,6 +467,12 @@ [2] If you do not run mergemaster, you will likely hit a number of show stopper problems. The biggest one is that your /etc/pam.conf won't let you log in using ssh. + [3] Sometimes building or installing the new source tree + has prerequisites an older system doesn't satisfy. This + is what the pre buildworld mode of mergemaster was + introduced for. Make sure to either install the new + version of mergemaster before buildworld or run mergemaster + from its source directory where the new version is available. What follows are older entries for those people upgrading from earlier versions of -stable/-current. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s get gpg key [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Software raid 1 on root partition?
On Thu, Jul 11, 2002 at 14:14 +0200, Lasse Laursen wrote: I'm currently in the process of upgrading our Linux servers to FreeBSD. The Linux servers uses software raid 1 on the boot/root partitions - is there a way to do the same under FreeBSD 4.6? The trick is to load a kernel with software RAID support even before you have a root filesystem with your kernel and modules on it. :) This is not different between Linux and FreeBSD. Putting everything you need to boot into a ramdisk and loading it with your favourite boot manager is the solution. (I'm not sure but maybe the newly created livecd port is of help, too. Or you have a look at how installation media are done.) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s get gpg key [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /bin/sh, $MAIL and login.conf
On Thu, Jul 11, 2002 at 02:49:11PM +0200, Marc Olzheim wrote: On Mon, Jul 08, 2002 at 10:31:30PM +0200, Cyrille Lefevre wrote: 2) Is there (going to be) an 'unsetenv' possibility in login.conf, so that I can still use 'default' for all classes and just unsetenv MAIL for sysadmins and root ? yes ;) root:\ :ignorenologin:\ :setenv=BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ :tc=default: Cyrille. Ah, of course. ;-) I somehow thought the 'setenv=' part to be accumulative... they are not cumulative, in the present sample, the root's setenv override the default's setenv. it doesn't complement the later. Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
4.6-STABLE panics wirh MROUTING
Hello there colleagues. After upgrading one of our gateways I'd encountered reproducible kernel panics in multicast-related situations. processes involved are mrouted (from base system) and ospfd from zebra-0.92a_1 FreeBSD gw-f.rinet.ru 4.6-STABLE FreeBSD 4.6-STABLE #2: Wed Jul 10 15:05:26 MSD 2002 [EMAIL PROTECTED]:/var/obj/lh/src/sys/gwfn i386 I suspect options MROUTING being The Evil [tm], but had no time to check it thoroughly (it's production gateway, you know, so now I'd simply stick it out with about 40 statics both there and on border Cisco ;-) kernel config file follows (it's 4-ethernet router + COM multiport console server) Any thoughts? Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** machine i386 cpu I686_CPU ident GWF maxusers0 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options NFS_NOSERVER#Completely disable server code options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV# install a CDEV entry in /dev options NO_F00F_HACK# we are not on buggy Pentium options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION options MROUTING# Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets #optionsIPFIREWALL_FORWARD #enable transparent proxy support #optionsIPFIREWALL_VERBOSE_LIMIT=100#limit verbosity options DUMMYNET#dummynet shaper options HZ=1000 options NMBCLUSTERS=16384 device isa device pci # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device vga0at isa? # splash screen/screen saver #pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 options COM_MULTIPORT #code for some cards with shared IRQs # 4-port AST device sio2at isa? port 0x2a0 flags 0x501 device sio3at isa? port 0x2a8 flags 0x501 device sio4at isa? port 0x2b0 flags 0x501 device sio5at isa? port 0x2b8 flags 0x501 irq 7 # 8-port Omega device sio6at isa? port 0x100 flags 0x605 irq 12 device sio7at isa? port 0x108 flags 0x605 device sio8at isa? port 0x110 flags 0x605 device sio9at isa? port 0x118 flags 0x605 device sio10 at isa? port 0x120 flags 0x605 device sio11 at isa? port 0x128 flags 0x605 device sio12 at isa? port 0x130 flags 0x605 device sio13 at isa? port 0x138 flags 0x605 # PCI Ethernet NICs. #device ed # NE1000/2000 and compatibles #device ed0 at isa? port 0x300 irq 10 iomem 0xd8000 device miibus device rl # NE1000/2000 and compatibles device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys
Re: tuning(7) request was: Re: Performance boost with kernel options in FBSD 4.6
: :Hi, :If it's possible this makes a difference can we get a note about HZ :added to the tuning(7) man page? : :Thanks Ken I could put a general admonition in tuning(7) about Hz, but the performance effects are going to be highly dependant on the situation. Generally speaking aggregate performance will not improve if you increase Hz, but I can see how perceived performance might improve in certain specific situations such as having a lot of X clients talking to the server at the same time. The issue with X clients is that a single interactive operation done on the client may result in dozens of interactive packet ops occuring between client and server, many of which cannot be pipelined. In this situation the priority scheduling mechanism tends to break down because the server processes are utilizing a huge amount of cpu but are still classified as being interactive due to short term I/O waits. Several clients may monopolize the server in this fashion and cause obvious lag for the remaining clients. For example, if a couple of clients run 'xengine' the other clients could suffer greatly. An increased switching rate (increasing HZ) may be useful in the above situation. Still, I would not recommend increasing Hz above 500 (2ms). 1 (100uS) is just plain insane. I think it is high time that we changed the system default on 'fast' machines (anything over 300 MHz) from 100 to 250. 100 is archaic. We will not see detrimental cache side effects until we get above 1000 or so (my guess) so I think '250' as a default instead of 100 is a good idea. But for most people it just doesn't matter. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Software raid 1 on root partition?
Excuse me if I step in here... Gerhard Sittig wrote: The trick is to load a kernel with software RAID support even before you have a root filesystem with your kernel and modules on it. :) This is not different between Linux and FreeBSD. Putting everything you need to boot into a ramdisk and loading it with your favourite boot manager is the solution. Ahm... where's the beef? I.e. where does this RAM-Disk Image come from? It's safe to *read* from one of the two disks, but what I don't understand is: Asume there are 4 disks: disk #1+#3 are RAID1 for -STABLE, disk #2+#4 are for -current. I want to boot -stable, so I try to load the RAM-Disk Image from disk #1 - but it's crashed. How do I know what disk to use next? Please answer per Mail too, I'm reading this list via docs.freebsd.org -- Ciao/BSD - Matthias Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany) Powered by FreeBSD 4.6-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: intel etherexpress pro and fxp status??
Date: Thu, 11 Jul 2002 11:05:38 +0100 From: Pete French [EMAIL PROTECTED] Thanks, bye. The only threads I remember around this were some people with specific problems on specific SMP motherboards. I dont recall any mass problems with the fxp cards... For what its worth, we have deployed some 50 The SMP problems also turned out to be nothing to do with the fxp cards and everything to do with shared interrupts. But cards which generate a lot of interrpts show this up well, hence it first showed up on FXP and has been misrememberd by people as the fxp problem. just make sure you arent sharing interrupts on an SMP box and you will do fine. - -pcf. Holger Kipp sent me a message back on June 21 that says his problems with freezing/IRQ issues on an SMP box that uses a Symbios SCSI controller were solved with a patch/workaround from Gerard Roudier who said he was planning to commit a polished version as soon as he got some time. (Not sure if it's there yet, and I'm not very good at looking at CVS repositories, but a box here updated on 7/7 still shows old date stamps on the sym drivers, and the last apparent change to the module in question (sym_hipd.c) was around 4/26, based on the the FreeBSD CVS webpage.) Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: strange ATA behavior with -STABLE
* Michiel Boland ([EMAIL PROTECTED]): Please correct me if I'm wrong but I don't think the splx patch does anything to help people with broken CD-ROM drives. You are right. It fixes a coding mistake which panicked boxes using TQ. All other issues are still present. -- Thomas Seck This message was sent to a mailinglist I am subscribed to. Please send your replies to the list only and do *not* CC me. Thank you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: tuning(7) request was: Re: Performance boost with kernel options in FBSD 4.6
Well, the main thing you need to figure out is whether your problem is due to cpu monopolization or disk monopolization. 'I/O' load itself can effect the scheduler, but is unlikely to overload the machine. Disk loads are far more likely to overload the physical hard drives. For example, if you have a user logged into a shell whos 30MB mailbox is on the same hard drive as, say, a heavily loaded MySQL database which is saturating the drive, simply reading the mailbox sequentially could take 10 seconds when it would only take 1 second on an idle drive. So the first thing you need to do is determine your drive loads and map out where the different applications/users are going. 'systat -vm 1' helps a lot there because it tells you the hard drive % utilization. The thing about Databases and Web serving is that they can generate a lot of seeking on a drive which can easily saturate the drive (100% utilization). If you determine that drive load is your problem then the logical solution is to add more drives or distribute the partitions differently or add memory (increased caching == reduced disk I/O) or add more hard drives. If you determine that cpu monopolization is the problem and drive load is not the problem then you can try things like raising HZ, renicing processes a little (I recommend no more then +/- 8), reducing the parallelism on some of the server processes, upgrading the cpus, and so forth. There are lots of potential solutions. -Matt :Hi Matt, : Regarding your comment about highly IO intensive programs; many of :us run SQL databases (highly intensive IO). I have noticed a tendency :for a single process to monopolize the CPU with MySQL, to the :exclusion of other users. I do understand the detrimental effects of :state changes on a CPU, so I can relate to not setting this value too :high. I wonder if we might see an effect with this as well? : :I don't remember seeing this discussed here. I do not mean to bring :up a topic that has been discussed before, either here or another :list. However, the effect on IO for a server with several hundred :simultaneous connections could be noticeable. I am not sure a simple :benchmark would should any advantage, although I am planning to play :with the value and run some benchmarks. If I come up with meaningful :numbers I will post them. : :The main thing I was wondering is what effects I might watch for, and :any hints as to what I should not waste my time on. In our :environment we run FreeBSD,Apache,PHP, MySQL for about a thousand :users. It is an interactive database application so this may have :similarities to the X situation you described. I am always looking to :boost performance (can't wait to see 5.0! ). I am just not sure what :kind of an effect I might see. But I will play around as soon as I :return from vacation (unless someone else gets to it first! :). All :the security problems lately have really kept me busy. : :Thanks for the input, :Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: tuning(7) request was: Re: Performance boost with kernel options in FBSD 4.6
Matthew Dillon wrote: An increased switching rate (increasing HZ) may be useful in the above situation. Still, I would not recommend increasing Hz above 500 (2ms). 1 (100uS) is just plain insane. from actual experience, any p-III with a clock rate above 500MHz (that is, any recent CPU) can sustain Hz=5000, which I used to run trafific-shaped packet blasters (admittedly a narrow focus ...) with very good results (better than special-purpose test boxes). As is said in the dummynet man page, FreeBSD can be a very good traffic shaper, if the userland scheduling rate is high enough (will it be the same with threads in -current, with KSE ?). many of my machines run with GENERIC and kern.hz=1000 in /boot/loader.conf (I still have to look if NTIMECOUNTER is upped in the same porportion : USTL !) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
