Re: Resolver Issues (non valid hostname characters)
Date: Tue, 25 Mar 2003 16:46:27 -0600 From: Marius Strom [EMAIL PROTECTED] I've submitted a PR for this: misc/50299 documenting the RFC mis-following (is that a word?) as well as a patch for res_comp.c. As Mark Andrews pointed out in a private message, this is not a BIND issue. It's a resolver issue. The resolver does enforce the RFC limiting the characters used for host names in accordance with the RFC. BIND will handle anything. A big issue is that ICANN appears to have authorized internationalized names and those appear certain to break LOTS of things. But this PR is probably not correct as BIND does adhere to the RFC. RFC952 still holds sway as confirmed in RFC1123. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: which video cards work best for stable
From: Eriq [EMAIL PROTECTED] Date: Sat, 11 Jan 2003 01:52:56 -0500 Sender: [EMAIL PROTECTED] nvidia or ati, need to know what to build new system with. I am now running a server w/ savage4 and it runs fine but next box I was thinking ati as price per profomance seems good in 8500. But what do you think. This is more an XFree86 issue than a FreeBSD issue ([EMAIL PROTECTED]). I have found ATi is supportive of the open-source community and results have been quite good. As of today and V4.2.1, all ATi cards except the 9500 and 9700 are supported in 2D. 3D is available for the 7500 and may be there of the 8500. Support for the newer ATi cards in in CVS and the 4.3 pre-release distros (4.2.99). 4.3 is expected out shortly. I have no experience with nVidia, but they do provide a binary FreeBSD driver for 3D support of their new cards. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 . To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
Date: Mon, 25 Nov 2002 10:23:23 -0800 From: Wes Peters [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] P.A.Osborne wrote: On Mon, Nov 25, 2002 at 07:54:32AM -0800, Wes Peters wrote: cual0 (or sio0) is almost certainly NOT your winmodem. I suspect it is an onboard serial or IR port, as is sio1. More reading of the ltmdm documentation might reveal how to discover what sio device node is associated with the winmodem when the module attaches. You'll then need to use the /dev/MAKEDEV script to create /dev entries for that sio node if you don't already have them. Thats the problem exactly! If I *knew* what device it really mapped to then I would be laughing, finding that out seems to be nigh on impossible, hence my mail asking if anyone had been round these hoops and succeeded. The last time I tried ltmdm (quite some time ago) it seemed to take the first non-allocated sio, which would be sio2 in your case. It's at least a good starting point. Or you could do like the rest of us and buy a pccard modem that doesn't suck. ;^) That is something that I don't want to do until I am certain that the winmodem is not an option. If you do get it working you're not likely to be impressed by the through- put or the load imposed on your system. I certainly wasn't. I believe IBM is now using the ICH3 chipset which includes the Agre (nee Lucent) AC'97 WinModem. This is a different beast from the older Lucent WinModems and, unless something has recently changed, it is not supported under FreeBSD with the ltmdm port. FWIW, under Windows, the new modem is vastly superior to my older internal modem on my 600E. I get better data rates and more reliable connections, but it does load the CPU quite a bit. Still, as little as I use a modem, it would be fine if there was an available driver. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
Sender: [EMAIL PROTECTED] Date: Mon, 25 Nov 2002 13:21:15 -0800 From: Wes Peters [EMAIL PROTECTED] I believe IBM is now using the ICH3 chipset which includes the Agre (nee Lucent) AC'97 WinModem. This is a different beast from the older Lucent WinModems and, unless something has recently changed, it is not supported under FreeBSD with the ltmdm port. FWIW, under Windows, the new modem is vastly superior to my older internal modem on my 600E. I get better data rates and more reliable connections, but it does load the CPU quite a bit. Still, as little as I use a modem, it would be fine if there was an available driver. Thanks for the update. It might be worth checking to see if the new chipset is supported under Linux. Porting the changes for the chipset to FreeBSD may be easier than porting the entire driver. It is supported under Linux with a binary-only driver supplied by Agre. Of course, this driver will not run under FreeBSD, so it will be necessary to write shims similar to those in the ltmdm port. I believe Watanabe-san was either working on these or he was posting information from others working on them on his web page. Because this modem is included in the very popular ICH sets, I am hopeful that it won't take too much longer, but I don't have a clue about Linux kernel modules, so I am not in a position to contribute much to this. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
To rudely follow up my own posts, I have been unable to reach Watanabe-san's web page. At least the English language page seems to have moved or gone away. Also the message I had seen that I thought implied he was working on it really was relating to an issue of a different flavor of Lucent WinModem. At this time I am unsure if anyone is working on this seriously. Larry Rosenman was trying to track something down on this, but I have not seen any recent messages. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Fwd: Re: DVD quality problem
If your DVD is ATAPI, make sure that you have DMA enabled. It is off by default. hw.ata.ata_dma and hw.ata.atapi_dma should both be 1. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 From: alexis georges [EMAIL PROTECTED] Date: Mon, 18 Nov 2002 15:37:50 + Sender: [EMAIL PROTECTED] great..thanks that fixed it..and it works really well..the only thing i have is that my audio is kinda 'cripsy..i get a few small cracks repeatedly..is there a way to fix this? thanks From: Andrew Thompson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: DVD quality problem Date: Mon, 18 Nov 2002 15:44:56 +1300 alexis georges wrote: Hey guys, i thought i would give a shot to playing a couple of dvd's on my new freebsd machine..so i installed ogle..thats fine..i put in the dvd..launch ogle, goes well..until the movie actually starts..the quality is really choppy..especially when the camera makes a quick movement..i have the nvidia drivers installed..i didn't understand why i would get that choppy video (and crisping in the sound)..so i posted on freebsdforums.org..: Try mplayer. I also get choppy video with ogle but mplayer is fine. mplayer -dvd 1 should do it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kernel crashes during boot
Date: Fri, 11 Oct 2002 18:27:25 -0400 From: Bryan Berch [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Sean McNeil wrote: I just cvsup'd my STABLE sources and recompiled. My new kernel now panics on bootup. I couldn't get the info but I think it was a page fault 12 or something like that. AMD processor. Anyone else experiencing this? If not I will try to capture all the relevant info. Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message After cvsup on 10/10/02, I get the same error after reboot to make installworld. This was first reported several hours ago. Looks like something did not get committed in a timely manner. In any case, the two people to report it this morning did another cvsup and it was fine. My system, updated at about 10:00 (-7) this morning, was fine. The problem systems had run cvsup about an hour to 2 hours earlier. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Updating world with least downtime
Date: Fri, 30 Aug 2002 17:20:24 -0700 From: David Schultz [EMAIL PROTECTED] Thus spake Kevin Oberman [EMAIL PROTECTED]: For a modern system and a reasonable disk, this is trivial. I have a system which MUST not be down for over 15 minutes and I can do it quite easily unless I really fumble something in mergemaster. I do always merge a few files later and tend to install most changes very quickly, having ode the same upgrade on a non-critical system just before I do the critical one so I know what to expect. The actual installworld time on my 1GHZ system is about 5 minutes (5:34 last time). Nice record. There ought to be a better solution than ``run mergemaster really fast and hope nothing goes wrong,'' though. For example, you could use mergemaster with -D on a copy of /etc and commit the copy in single user mode. No. I run mergemaster on another system to confirm what needs to be merged before reboot or can be installed with no complications. Then plan what I will have to do with any files that require merging. This is far different from just rushing through things and risking s disaster. It is, as the subject of the thread states, Updating world with least downtime. I like the idea of an early-run using -D, though. I might do that next time I update a system. Should be even faster than what I do and less prone to error. Thanks for the suggestion. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.6 stable to 4.6.2 stable
Date: Sun, 25 Aug 2002 13:56:21 +0100 From: Jeff Penn [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Sun, Aug 25, 2002 at 03:23:59PM +0400, RUS wrote: #cd /usr/src #make buildworld #make buildkernel KERNCONF=mykernel #make installkernel KERNCONF=mykernel after reboot to single mode #make installworld #margemaster and reboot I always clean out /usr/obj. You can also add the 2 new mergemaster calls using -p -C options: cd /usr/obj chflags -R noschg * rm -rf * cd /usr/src mergemaster -p make buildworld make buildkernel KERNCONF=MYKERNEL make installkernel KERNCONF=MYKERNEL shutdown -r now boot -s fsck -p mount -u / mount -a -t ufs swapon -a cd /usr/src make installworld mergemaster mergemaster -C And, don't forget 'adjkerntz -i' before you 'make installworld' so that you won't be installing files before they were built. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cdrom: device not configured error
Doug, Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to re-create them? The new ATA drivers require this as the minor mode must change. If you did a mergemaster after any upgrade, this should have been taken care of. ls -l /dev/acd* crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0a crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0c crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1a crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1c Note the major (117) and minor (0) mode of acd0?. If yours does not match, that is likely your problem. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 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?
Date: Tue, 9 Jul 2002 09:51:03 -0700 (PDT) From: Matthew Dillon [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] :* Jason Andresen ([EMAIL PROTECTED]): : :[/etc/crontab vs. crontab -u root] : : ??? More visible? New people to the system can never find that file. : Heck, I'm always forgetting where it is. It wouldn't be so bad if : it just weren't so inconsistent. : :See cron(8), second paragraph. : :-- :Thomas Seck : /etc/crontab should probably not be touched, nor should /etc/periodic, or upgrading the system will be nightmware. If you want to use the periodic mechanisms you can create your own periodic directory hierarchy ala /usr/local/etc/periodic, and if you just want to mess with your own root crontab you should use 'crontab -e' as root. If you want to override the system default /etc/periodic you can create your own /etc/periodic.conf (else the system uses the default /etc/defaults/periodic.conf). It's simple. See man periodic.conf. Also, as far as I know, the use of local periodic(8) scripts via periodic.conf(5) entries in 999.local is supported. mergemaster(8) should catch changes in periodic.conf(5). R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ssh to remote machines problem after cvsup
Date: Tue, 09 Jul 2002 10:09:29 -0700 From: Doug Barton [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Jay Sachs wrote: There are those of us who consider the protocol switch a good change, So you are free to do that on your systems. The problem is, whether you think it's a good idea or not, it's already catching people by surprise, and locking them out of their systems. The change should be reverted. Doug, This was discussed on stable (admittedly a bit late in the game) and every comment I saw favored making the change in Stable. An entry was made in UPDATING to warn people of the change. From a security standpoint alone the change is justified as protocol V1.5 has long required kludges to work around its problems while V2 was much more carefully crafted from the ground up and has no known problems. I am only talking about the protocol and no particular implementation. People should really be using V2 protocols in all cases except where remote systems still don't support it. (And, do you REALLY want to connect to those systems?) I will admit that I had pretty much converted everything of mine to use V2 long before this came up, so this really didn't have an impact on me. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.6-RELEASE problems with xinit, Xircom pccard ethernet
Date: Wed, 3 Jul 2002 19:41:51 -0400 From: Guy Middleton [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I just installed 4.6-RELEASE on a laptop, I'm having a couple of problems. First, when I run xinit (as a non-superuser), the Xserver fails to start because it tries and fails to write to a log file (/var/log/XFree86.0.log). This never happened in previous versions -- is this a bug, or do I need to set some new flag to stop it writing log files? X --help gives no useful hints. 2 problems: 1. Use startx. Don't run xinit directly. This has never been supported though it often works 2. Re-install wrappers. You need to do this whenever the X server changes. If you have portupgrade, simply 'portupgrade -f wrapper'. If not, 'cd /usr/ports/x11/wrapper; make deinstall make reinstall' Second, my Xircom pccard ethernet/modem is not being recognized correctly: Jul 3 19:34:40 blink /kernel: pccard: card inserted, slot 0 Jul 3 19:34:46 blink pccardd[48]: Card Xircom(16-bit Ethernet + Modem 56) [REM10] [1.00] matched Xircom (16-bit Ethernet + Modem 56) [(null)] [(null)] Jul 3 19:34:51 blink pccardd[48]: driver allocation failed for Xircom(16-bit Ethernet + Modem 56): Device not configured Is there some configuration that has to be done here? I believe that the pccard setup is otherwise correct, since my Lucent 802.11b wireless card works fine. This is a known problem with the new pccard support and the xedriver on some systems. Try adding the line machdep.pccard.mem_start=0xd to /boot/loader.conf. See Scott Mitchell's response to the same question on freebsd-mobile on June 16. If you do a Google search on mailing.freebsd.mobile and search for Xircom Scott, it will be about the most recent. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Upgrade from 4,5Stable-4,5-RELASE . refuse to accept setting from rc.conf
From: Dennis Pedersen [EMAIL PROTECTED] Date: Sun, 21 Apr 2002 22:32:24 +0200 Sender: [EMAIL PROTECTED] - Original Message - From: Norbert Augenstein [EMAIL PROTECTED] To: Steve Kargl [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, April 21, 2002 10:26 PM Subject: Re: Upgrade from 4,5Stable-4,5-RELASE . refuse to accept setting from rc.conf On Sun, 21 Apr 2002 12:42:50 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Apr 21, 2002 at 08:57:33PM +0200, Dennis Pedersen wrote: After running the cmd above the ldonfig -r shows the entry. What best thing to do now? , migrate back to STABLE (and avoid any other strange problems) or try to fix the current install? (it still wont accept the ifconfig statements in rc.conf) cvsup should now work. I would go back to FreeBSD-stable. Do this by changing to tag=RELENG_4. From the above, I take it you have to manually run ifconfig to get your machine on the net. Once connect, get update your tree and do the standard sequence of make buildworld make buildkernel KERNCONF=MYKERNEL make installkernel make installworld mergemaster reboot And, yes I know some people recommend a reboot to single user mode. and a reboot after make installkernel to use the new kernel for installworld (installworld could fail if you dont) Dumping the box into single user wont do the trick? , it has to be a reboot? (Im doing the update part all over again and i want to do it right this time ;)) No, dropping into single-user mode will NOT do the trick. The whole point is to make REALLY sure that you have a running kernel BEFORE you blow away the existing user land with the installworld. If the new kernel won't boot, it's pretty easy to back up to kernel.old and modules.old and try to figure out whet went wrong. If the kernel is broken and you have already installed world, you have the potential of having no choice but to rebuild the system from scratch, not something you want to do. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: *** HEAD'S UP ***
Date: Fri, 19 Apr 2002 15:37:27 -0700 (PDT) From: Doug Barton [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Howdy, Apparently my last message wasn't clear enough, for which I apologize. In addition to the general, non-life-threatening changes to /etc I did recently, a few more fundamental things have changed as well, specifically to /etc/defaults/rc.conf. Rather than focus on the specifics, I'd like to suggest a more general solution. I highly recommend backing up your existing rc.conf[.local], and copying /etc/defaults/rc.conf to /etc/rc.conf. Then, go through the whole file, and explicitly include your choices for anything that you care about, whether they are the defaults or not. In this way, you can be sure that the system will always behave the way you want it to. In addition to this, I generally include the settings that are specific to the individual machine (like hostname, gateway, ifconfig_) in /etc/rc.conf.local. That way it's easier to blat the rc.conf file periodically. I also added an option to mergemaster to compare your rc.conf[.local] stuff to what's in /etc/defaults/rc.conf after you're done updating. To take advantage of that, use 'mergemaster -C', or 'echo COMP_CONFS=yes .mergemasterrc'. What this won't show you is differences to the defaults that you don't have in /etc/rc.conf[.local]. For that, you're expected to pay attention to the diff of /etc/defaults/rc.conf as you install it. :) Any questions, comments, or suggestions... fire away. OK. You asked for it... I really hate to see the suggestion that people copy files from /etc/defaults to /etc. This really breaks the paradigm of having only changes in defaults in /etc so that defaults can be changed with a normal system update. While the new mergemaster option helps with this, I would really rather not see rc.conf (and other files) become large and not trivial to scan over. A suggestion to scan through /etc/defaults/rc.conf is not unreasonable. Of course, people SHOULD pay attention to whet mergemaster has to say, but even I have messed up when updating an important server and not watching all of the things mergemaster showed in an effort to get the system back on-line quickly. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: options PNPBIOS
From: Drew Tomlinson [EMAIL PROTECTED] Date: Thu, 18 Apr 2002 10:24:00 -0700 Sender: [EMAIL PROTECTED] I compiled a kernel with options PNPBIOS as instructed in LINT to get my sound card working. The machine is a Pentium II Pro. I have ensured that the BIOS is configured for PNP OS but still get these messages: unknown: PNP can't assign resources unknown: PNP0303 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0c01 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources I've searched Google and found others with this problem but no solutions. Is PNPBIOS documented somewhere? Where should I start? These are always present with PNPBIOS as there are several things that identify themselves via PNP that FreeBSD does not know/care about. They can almost always be ignored. As I understand it, PNPBIOS and having BIOS configured for PNP are very different things and the general advice I have seen is to not turn on PNP in BIOS. As I understand it, PNPBIOS causes FreeBSD to query BIOS for device information on all device. It eliminates the need to specify all sorts of stuff like iomem, irq, and drq in the kernel for ISA devices. I generally find it annoying and go ahead and define all of the parameters in my kernel config. Of course, it's entirely possible that I don't understand it. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Network stalls with 4.5
From: Aaron Baugher [EMAIL PROTECTED] Date: 19 Mar 2002 14:32:11 -0600 Sender: [EMAIL PROTECTED] David Wolfskill [EMAIL PROTECTED] writes: You might try doing something as crude as while (1) netstat -ni sleep 10 end and use that to see of you're getting errors or collisions durng the stalls. Thanks. They've all been up for 20-30 days, and show zero errors or collisions. Also, we're not having this problem with the Linux or OpenBSD boxes on the same LAN, so it doesn't seem to be a cabling or hub problem. Aaron, This may be simple confusion on terminology, but hub normally is the term used for a multi-port Ethernet device that acts as a simple repeater with all connections in a common collision domain and all running half-duplex. If this is the case, zero collisions is VERY hard to believe. Collisions will always happen in a half-duplex LAN on a system that does any significant amount of writing to the network. Simple matter of statistics. Is the connecting box a hub (repeater) or a switch (bridge)? If it's a bridge, you should probably be running full-duplex and would ALWAYS have zero collisions as collision detection is disabled in that case. If it's a hub or if the interface is running half-duplex, it's possible that the NIC is defective and that could be the source of the problems. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: parameterize named log
From: Randy Bush [EMAIL PROTECTED] Date: Mon, 11 Mar 2002 03:13:22 -0800 Sender: [EMAIL PROTECTED] 470.status-named has /var/log/messages hard coded. those of us with heavy load name servers tend to separate named logging to one or more separate files. hence, it would be nice if periodic.conf would allow configuration of the filename. i can supply the trivial patch if anyone cares. Randy, I would appreciate it. It's been on my TODO list or a while and I just printed out the periodic job yesterday in hopes of doing exactly what you did. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Request for testers of MFC'd ATA driver take 2.
Soren, I have installed the latest patches on all the the system that had problems with the prior patches and all is well. Both the Dell and the ThinkPad are over their panics. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: XFree86 4.2
Date: Tue, 5 Mar 2002 16:25:26 -0500 From: stan [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Tue, Mar 05, 2002 at 09:31:47AM -0800, Kevin Oberman wrote: From: Mike Murphree [EMAIL PROTECTED] Date: Tue, 5 Mar 2002 06:32:34 -0600 Sender: [EMAIL PROTECTED] On Tuesday 05 March 2002 04:03 am, Herve Quiroz wrote: I have not been member of this list until recently so I have probably missed some discussion on the topic. Anyway, what is going on with Xfree86 v4.2 ? I once had seen XFree86 4.2 on freshports.org but then it came back to 4.1 few days later... NetBSD has already 4.2 in -stable so why not FreeBSD ? The port was at 4.2.0 shortly before the release of FreeBSD 4.5 and it was rolled back to 4.1.9 because of insufficient testing time before the release. It has never been put back... I've been running 4.2.0 since that time with zero problems. This is not why the 4.2 port was pulled. The main reason was that XF86-4.2 was added to the ports just prior to the release of FreeBSD 4.5. It was felt that it was unwise to include a new release of XFree86 that was largely untested in a new release of FreeBSD, so the port was pulled. At the same time it was decided that it was a good time to convert XFree86 from a port to a meta-port. This has been under discussion for some time and the 4.2 release looked like a good time to cut over. So the 4.2 port appeared and disappeared from the tree, but is still available and works fine. (If you don't know what a meta-port is, look at /usr/ports/x11/gnome/Makefile.) So what are teh _advantegse_ of a metaport? O'm dealing with on _disdvantage_ at the moment. For reasons involving my own stupidity, I find myself with a broken Gnome installlation even though the ports db thinks it' fine. But since it's a metaport, I can't just do portupgrade -f gnome :-( Must be a positive side to this, right? Otherwise you could just install all of it with a trivial shell loop over the various appropriate directories in the ports tree. Hmm. You have hit on the problem with meta-ports. I don't install the gnome meta-port for just that reason. But a meta-port is a good thing because it allows a bunch of ports that go together to be easily installed. In you case the only good solutions are to either delete all of the ports in the meta-port and then re-install it or to do a portupgrade -f on each of the dependent ports. At least it's easy to spot them in the Makefile for gnome. In the case of X (and not too different from Gnome) you have a very large port that can take a VERY long time to build and install. But normally there is no really reason to rebuild the whole thing. Better to just update the part that actually changed. So the trick is to set up a meta-port. This allows the easy installation of XF86-4 but it only required that you update the pieces that have changed and not the whole monster. If the server is patched, the installation of clients, libraries, and fonts is a total waste of time. When XF86-4.2 is available as a meta-port I will probably not install it. I will remove the existing XFree86 and look at the Makefile and simply do a portinstall on each of the dependencies in the port. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: compile error
Date: Wed, 6 Feb 2002 22:46:12 -0800 From: John Merryweather Cooper [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Follow the instructions in the documentation for building a kernel. 'make all' is NOT the way to do it. :) Generally, one builds a world to make sure that world stays in sync with the kernel (or else very bad things may happen). Then (and only then) does a kernel get built. Assuming you have a working kernel configuration file in /sys/i386/conf with SOME_NAME, the safe-and-sane build sequence, usually looks like (from memory): # cd /usr/src # make buildworld # make buildkernel KERNCONF=SOME_NAME # make installkernel KERNCONF=SOME_NAME # make installworld You may need to reboot into single-user mode to successfully install (that will depend on your configuration, etc.) And the order may have changed (read the documentation); and there are shortcuts for the brave-or-foolhardy (which I won't discuss here). But don't trust me, read the doc. :) Yes, you really want to reboot to single-user mode to installworld, even though the installworld works fine in multi-user mode. The problems is that you are installing a new userland while running the old kernel. The next time you re-boot it is possible that the kernel won't work. You can boot with kernel.old, but that leaves you with a partly functioning system since the kernel and userland are not only out of sync, but in the wrong way, and it's virtually impossible to uninstallworld. You usually have to re-install! That all said, many people do the entire installation without a reboot and do it remotely with no console access. (I've done it and probably will again.) It USUALLY works, but when it fails, you are in VERY deep weeds! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvsup to 4.4-stable
From: Kaming [EMAIL PROTECTED] Date: 08 Jan 2002 14:52:40 +0800 Sender: [EMAIL PROTECTED] Hi all, I am a newbie of freebsd I tried to cvsup by just type cvsup /usr/share/example/cvsup/stable-supfile and then copy the /etc/default/make.conf to /etc and do the 'make buildworld; make installworld'. After that I compile kernel and reboot it. I found that it is 4.5-PRERELEASE. I just do the same thing few week ago and it showed that it is 4.4-STABLE. Did I do sth wrong?? I hope to make it to be 4.4-STABLE Anyone can help??? You have cvsuped to the stable branch of FreeBSD V4 which is tagged RELENG_4 and is currently named 4.5-PRERELEASE. It will soon be named 4.5-RC1 and eventually 4.5-STABLE. All are stable at different points on the path that produces a snapshot that is tagged as a release. (So you did nothing wrong.) Please refer to the handbook section on The Cutting Edge for a detailed description. Also, DON'T copy and /etc/defaults file into etc! The way it works is that /etc files carry CHANGES to the values supplied in the /etc/defaults files. SO never edit the /etc/defaults and don't copy them into etc. Just create a /etc file with changes you wish to make to the defaults. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
From: Mike Squires [EMAIL PROTECTED] Date: Wed, 2 Jan 2002 09:09:36 -0500 (EST) Sender: [EMAIL PROTECTED] There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. I had this when I forgot that 4.4 installs sshd as a default and reinstalled it from /usr/ports. I just removed the /usr/local/etc/ entry, since I'm going to rerun buildworld, etc., after 4.5-RELEASE. (I'm running 4.5-PRE #2 right now) OK. Let me try to explain what is happening and the appropriate response based on what version of sshd you want to run. You have installed the ssh port which means you probably have 3.0.1 or 3.0.2. You are running 4.5-Prerelease, so you have 2.9 installed in the base system. If you have sshd_enable=YES in /etc/rc.conf, rc will start 2.9 from /usr/sbin. To prevent this from happening, edit your /etc/rc.conf file and comment out the sshd line. If you have /usr/local/etc/rc.d/sshd.sh, v3.0.? is being started. If V2.9 is already running, this will fail. To prevent the system from trying to start V3, pkg_delete openssh or chmod 644 /usr/local/etc/rc.d/sshd.sh. Unless you have a specific reason to run V3 of openssh, I'd really suggest that you stick to the installed, standard V2.9. It's not quite the latest and greatest, but it does get all security patches and is consistent across FreeBSD systems. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5-RELEASE
Date: Mon, 31 Dec 2001 11:34:57 -0800 (PST) From: Holt Grendal [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi, Its 4.5-RELEASE still planned for January 15, 2002? The latest information is always at http://www.freebsd.org/releases/ It's January 20, 2002. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Ports not building!
From: Julio Merino [EMAIL PROTECTED] Date: 21 Dec 2001 23:06:28 +0100 Sender: [EMAIL PROTECTED] Hi all I'm getting mad. The ports system is not working... I've updated today all my system to see if it was because a broken build, but wrong. I'm now with 4.5-PRERELEASE and with a clean checkout of the ports tree. And, when I try to build _any_ port, I got the following errors (the example from emacs20): - klamath# make build (all the configuration is already done) === Building for emacs-20.7_1 /bin/rm -rf /usr/obj/usr/ports/editors/emacs20/work/emacs-20.7/info/* /usr/ports/editors/emacs20/Makefile:26: *** missing separator. Stop. *** Error code 2 Stop in /usr/ports/editors/emacs20. *** Error code 1 - I've checked the make binary, that is in place (/usr/bin), and it works, cos I've been able to do a make world. And the gnu make binary is in /usr/local/bin, with gmake name. Very strange. I can't imagine where the problem is coming from. First, I though the problem came from a broken build of the -stable branch because after it, no more ports compiled. But now, that I've redone the built, it still happens. Maybe I have a corrupted configuration file? Which one would be? Do you have any idea? ANY help will be highly appreciated. Thanks a lot. Julio, You didn't, by any chance, do something that made gmake run for make, did your? which make should show /usr/bin/make and /usr/bin/make should be about 200 KB long. If it's only about 135 KB, you have replaced make with gmake. It's also possible that gmake is really aliased to make. This won't work, either since emacs20 uses gnu make while the ports part of the make uses make. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: SSH Problem
Date: Tue, 2 Oct 2001 22:54:22 -0400 From: parv [EMAIL PROTECTED] this was, on the fateful occasion around Oct 02 21:07 -0400, sent by Kevin Oberman It does not distribute 2.3 with either stable or current. It was included (with security patches) in 4.4-release. From 4.4-stable: ssh -V OpenSSH_2.9 FreeBSD localisations 20010713, SSH protocols 1.5/2.0, OpenSSL 0x0090601f really? i get... SSH Version OpenSSH_2.3.0 FreeBSD localisations 20010713, protocol versions 1.5/2.0. Compiled with SSL (0x0090601f). ...i cvusp'd sources on sep 21 2001 6.30.41 utc. when did you build your world? cvsuped on Sat. the 29th. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: hw.ata.wc hw.ata.tags softupdates short question
Date: Fri, 21 Sep 2001 12:18:32 +0930 (CST) From: Daniel O'Connor [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On 20-Sep-2001 Nuno Teixeira wrote: For what I heard, I concluded that we shouldn't use softupdates with write cache turned on. The first time that I tried this I loose a lot of work due to a power failure. You shouldn't use write caching, period. Well you can but if you lose power you WILL lose data. If you just want speed and care naught about your data go ahead :) (I guess a UPS would increase your confidence) 1. Can I use softupdates with hw.ata.wc=1 and hw.ata.tags=1 safely? 2. Does hw.ata.tags=1 allows write caching to be safely turned on really? No, write caching tells the drive Please lie to me about command completion so when the OS performs a write the drive caches it and says yes that's on disk, when it isn't. OK. I've seen some questionable information in this thread and some that I'm almost sure is simply wrong. I'm going to describe the situation as I understand it and if you are SURE something I say is wrong, please correct it. (Especially if you write disk drivers for FreeBSD. I have written disk drivers, but not in FreeBSD and not for ATA disks, so am not really competent.) 1. IBM drives that do tagging are claimed to be safe. The way tagging works should assure that the critical metadata is always written to disk. And tagging depends on write cache to work, but you don't need to turn it on as turning on tagging DOES turn on write cache as it is used by tagging and attempting to turn it on with the hw.ata.wc sysctl is meaningless and ignored. 2. On a disk that has a lot of writes like a news server is especially susceptible to data loss. If a system is not UPS protected and running software to shutdown cleanly before the UPS dies, write cache on a server is with ATA disks is probably a bad idea. But then again, ATA disks on a server are probably a bad idea. 3. The combination of soft updates and WC is especially risky as you might lose both the last bit of data written to disk, but metadata that can lead to a major corruption. Even then, it's reasonably unlikely, but I don't think reasonably unlikely is reasonable. 4. Some disks always write data (eventually). Some NEVER write out data that is re-written frequently. It's just about impossible to tell which a drive does and the only documentation is the drive's micro-code which you are very unlikely to ever see and less likely to understand unless you write disk code. (I have a friend who does and it is about as opaque a bunch of C++ as I have ever seen unless you REALLY understand disk design.) 5. Many disks seem to make NO attempt to write the data on power outage. I run with WC on my laptop because it's extremely unlikely to lose power. But I also back up the disk (dd mirroring) on a regular basis just in case. It's also worth noting that Soren reversed himself and made wc default a few months after 4.3 was released. I assume it defaults to on in 4.4, although I have not checked. This makes me suspect that he decided that the risk was reasonable. But I really should not speak for him. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Please test boot patch
Date: Mon, 13 Aug 2001 12:58:36 -0700 (PDT) From: John Baldwin [EMAIL PROTECTED] On 13-Aug-01 Kevin Oberman wrote: Date: Mon, 13 Aug 2001 11:52:59 -0700 (PDT) From: John Baldwin [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] If for some reason this doesn't work (it should work fine), then you will want to boot off of a floppy or CD, then do 'disklabel -B ad0' as root to restore the old boot blocks. John, I tried but had a couple of problems. First, after the 'make all' there was no boot2 file in the /sys/boot/i386/boot2 directory. boot2.c was there along with bbot2.c.orig, but no output from the make all. It's probably located in /usr/obj then, in which case you can do 'cd /usr/obj/usr/src/sys/boot/i386/boot2' and then run disklabel. Also, the suggestion to boot from CD if it fails is probably not a good one. :-) If you have any of the CDROM's you can just boot up the loader, then stop the countdown and load the kenrel from the hard drive and boot. You can do the same deal using a kern.flp floppy. OK. After finding the files in /usr/obj and blindly cutting and pasting, I had to reboot off of CD. (Thanks for the suggestion, John. I never thought about being able to do that!) Trying again with the correct command, it works fine. Of course, I have no CD that uses the new boot to confirm that it actually fixes the problem... R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: USB question
Date: Fri, 03 Aug 2001 04:10:51 -0700 From: Mike Smith [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I was attempting to install my new MS optical Intellimouse on the USB port instead of the PS/2 port, but I am getting the following when I do a 'dmesg' after recompliing my kernel with the correct usb drivers: uhci0: Intel 82371AB/EB (PIIX4) USB controller at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS PNP is turned off in the bios, and the intellimouse works on the USB port in when I'm changing the bios (so I know it's not hardware) You're stuffed until Warner gets the PCI interrupt routing code into -stable. Welcome to the Plug and Play universe. 8/ If you want to live a bit dangerously, Warner has patches for stable available now. They are working for several people (and not working for others). http://people.freebsd.org/~imp/pcic-stable.diff.15b (the version is subject to change and may be different by now.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: soft update should be default
Date: Sat, 05 May 2001 09:31:09 -0700 From: Nick Sayer [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] That may be the original intent, but cheap IDE drives let you turn on write caching, and they're for sure not battery-backed (nor do they attempt to store enough power at power-off to write back the cache with the remaining rotational latency or any such trickery). They lie about it. Write caching is evil unless you specifically know that it's being battery backed. 99.44% of the time, that's not the case. An obvious exception is the laptop. I always turn on write cache on my laptop as I know that it has a LONG battery backup. For a worst-case type of operation (dd), I get 4x faster writes with write-cache enabled on my laptop. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: secure-supfile ?
Date: Fri, 27 Apr 2001 13:12:50 +0100 From: Vincent D Murphy [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] = Ruslan Ermilov [EMAIL PROTECTED] [20010427 1254]: Uhh, secure-supfile is gone over almost a year ago. Remove the SUPFILE1= line from your /etc/make.conf. I will fix src/etc/defaults/make.conf. just to confirm: i did cp /etc/defaults/make.conf /etc/make.conf a while back. i can't remember why, but i think there is no file there by default and i needed one for some reason. This is normal. The idea is NOT to copy the /etc/defaults files to /etc. The idea is to place specific changes from defaults into a file in /etc. The /etc/defaults files contain the normal defaults for a great many things and should not be modified. That way, should OS changes require it, defaults can be changed easily (POLA). Rules for files in /etc/defaults: 1. Don't ever modify these files! 2. Don't ever copy them into /etc 3. Should defaults need to be changed, create or edit the /etc file of the same name to contain just the items requiring non-default behavior. If you do this, the odds of things failing after a system software upgrade are substantially reduced. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Garbled keymaps in RC1
I just installed RC1. It was a new installation on an empty slice. In the configuration portion of the install, I chose the us.unix keymap. When I reached the point of needing to make a text entry, the character map was very garbled. It may have been Dvorak, but it as sure not qwerty. I've normally used this keymap in the past with no problems. I switched to us.iso and everything was back to normal. I then had to re-enter the root password as it was totally hosed when entered in sysinstall. Has anyone else seen this? R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Files in /usr/src
Today I ran cvsupchk over my source tree to see if there was any old cruft to clean up. I've done this for my ports, but never for src. In any case, it spotted some stuff I had edited, as I would expect, but it also found object and other files in sys/modules/agp, sys/modules/if_tap, and sys/modules/netgraph/ether. all files were created back in July and August of last year. I can't imagine how I could have causes these to be created, but I thought that FreeBSD never touched the src tree during a make world, so I am uncertain if it's save to remove these. Could there have been some weirdness back then in the buildkernel stuff? I seem to recall that the building of modules was moved out of buildworld and into buildkernel at about that time. Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 EXTRA: /usr/src/sys/modules/agp/@ EXTRA: /usr/src/sys/modules/agp/machine EXTRA: /usr/src/sys/modules/agp/device_if.h EXTRA: /usr/src/sys/modules/agp/bus_if.h EXTRA: /usr/src/sys/modules/agp/agp_if.h EXTRA: /usr/src/sys/modules/agp/pci_if.h EXTRA: /usr/src/sys/modules/agp/opt_bdg.h EXTRA: /usr/src/sys/modules/agp/opt_bus.h EXTRA: /usr/src/sys/modules/agp/opt_pci.h EXTRA: /usr/src/sys/modules/agp/opt_smp.h EXTRA: /usr/src/sys/modules/agp/agp.o EXTRA: /usr/src/sys/modules/agp/agp_intel.o EXTRA: /usr/src/sys/modules/agp/agp_via.o EXTRA: /usr/src/sys/modules/agp/agp_sis.o EXTRA: /usr/src/sys/modules/agp/agp_ali.o EXTRA: /usr/src/sys/modules/agp/agp_amd.o EXTRA: /usr/src/sys/modules/agp/agp_i810.o EXTRA: /usr/src/sys/modules/agp/agp_if.c EXTRA: /usr/src/sys/modules/agp/agp_if.o EXTRA: /usr/src/sys/modules/agp/agp.kld EXTRA: /usr/src/sys/modules/agp/setdefs.h EXTRA: /usr/src/sys/modules/agp/setdef0.c EXTRA: /usr/src/sys/modules/agp/setdef1.c EXTRA: /usr/src/sys/modules/agp/setdef0.o EXTRA: /usr/src/sys/modules/agp/setdef1.o EXTRA: /usr/src/sys/modules/agp/agp.ko EXTRA: /usr/src/sys/modules/if_tap/@ EXTRA: /usr/src/sys/modules/if_tap/machine EXTRA: /usr/src/sys/modules/if_tap/opt_devfs.h EXTRA: /usr/src/sys/modules/if_tap/opt_inet.h EXTRA: /usr/src/sys/modules/if_tap/vnode_if.h EXTRA: /usr/src/sys/modules/if_tap/if_tap.o EXTRA: /usr/src/sys/modules/if_tap/if_tap.kld EXTRA: /usr/src/sys/modules/if_tap/setdefs.h EXTRA: /usr/src/sys/modules/if_tap/setdef0.c EXTRA: /usr/src/sys/modules/if_tap/setdef1.c EXTRA: /usr/src/sys/modules/if_tap/setdef0.o EXTRA: /usr/src/sys/modules/if_tap/setdef1.o EXTRA: /usr/src/sys/modules/if_tap/if_tap.ko EXTRA: /usr/src/sys/modules/netgraph/ether/@ EXTRA: /usr/src/sys/modules/netgraph/ether/machine EXTRA: /usr/src/sys/modules/netgraph/ether/ng_ether.o EXTRA: /usr/src/sys/modules/netgraph/ether/ng_ether.kld EXTRA: /usr/src/sys/modules/netgraph/ether/__netgraph_hack_dep.c EXTRA: /usr/src/sys/modules/netgraph/ether/netgraph EXTRA: /usr/src/sys/modules/netgraph/ether/setdefs.h EXTRA: /usr/src/sys/modules/netgraph/ether/setdef0.c EXTRA: /usr/src/sys/modules/netgraph/ether/setdef1.c EXTRA: /usr/src/sys/modules/netgraph/ether/setdef0.o EXTRA: /usr/src/sys/modules/netgraph/ether/setdef1.o EXTRA: /usr/src/sys/modules/netgraph/ether/ng_ether.ko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: options USER_LDT *(solved)
Date: Wed, 27 Dec 2000 16:44:08 -0500 (EST) From: Donn Miller [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Wed, 27 Dec 2000, Evren Yurtesen wrote: is it enough if I make make buildworld ? anyway thanks for the help. now I could compile kernel without any problem. I didnt know that I have to make world etc. Since when this is required? (or is it required?) I knew it was the problem, since I've done the same thing myself. :-) Generally, "make buildkernel" is used in conjunction with a "make world" to update the world and kernel simulaneously. I think it's just a convenience to make kernel building easier when you make the world. It's NOT just a convenience! Another explanation of this appears to be in order: "make buildkernel" makes use of the special knowledge make has of the new, uninstalled system to build the kernel using the updated tools. This assures that the kernel and user files are synchronized. ALWAYS use buildkernel/installkernel when you have updated sources and done a fresh buildworld. NEVER use buildkernel/installkernel if you have not previously done a buildworld. If /usr/obj is not populated, buildkernel will fail. If you are simply modifying the kernel configuration and rebuilding, the best way is to: cd /sys/i386/conf config YOURKERNELNAME and follow the instructions provided. This does not require that the /usr/src or /usr/obj trees be populated. If you have previously done a buildworld and installworld and have not updated your sources, the kernel may be built either way with identical results, but buildkernel/installkernel takes a bit longer. I hope that's clear. If you are confused, get back to me and I'll try to clarify. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Small ssh problem in latest STABLE
uname -a FreeBSD puppeteer.es.net 4.2-BETA FreeBSD 4.2-BETA #0: Thu Nov 2 10:43:54 PST 2000 [EMAIL PROTECTED]:/scratch/obj/scratch/src/sys/THINKPAD i386 Just cvsuped and re-built and X forwarding via ssh did not work. I edited /etc/ssh/ssh_config by uncommenting the ForwardX11=yes and it started working again. It looks like defaults have changed with no changes to the /usr/src/crypto/openssh/ssh_config to match. The man page IS correct, but with no change in ssh_config, mergemaster does not provide and alert that something needs to be changed. I suspect that the same is true of sshd_config. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
Brad, We can agree that the 40 bit stuff is not worth the trouble. My 128 bit Lucent card says "128-bit RC-4 encryption". Last I heard, RC-4 was not considered a "safe" algorithm. Also, in any multi-user environment, the secret must be too public. (I believe that when I know something, it's secure. When I tell someone, it's secret. When someone else is told, it's public.) Using an encrypted link is fine, but I worry that people will believe far too much in its security. (Especially when they see "128-bit".) If I'm wrong and it is 3DES, never mind! But still use ssh whenever possible. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: some problems with 4.1 stable
Date: Mon, 4 Sep 2000 18:08:51 +0200 From: Michel TALON [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I have just made world from cvsup done last friday. All went fine but from 3 hours of compilation on a Pentium 300 with 256Megs (when doing 3.* it was not much than 1 hour). The machine works except some problems. First i wanted to use sysinstall to format a new disk. It ends out with no disks found. Thinking a new sysinstall was needed i tried to recompile it. But no luck! cc -Os -march=pentiumpro -pipe -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -c kget.c kget.c:40: machine/uc_device.h: No such file or directory kget.c: In function `kget': kget.c:83: sizeof applied to an incomplete type kget.c:85: dereferencing pointer to incomplete type kget.c:86: dereferencing pointer to incomplete type kget.c: You do need to rebuild sysinstall. To do so, go to /usr/src/release/sysinstall and "make all install". Builds fine on all of my systems, but you are using somewhat different compile options. I use: "cc -O -pipe -Wall". I can't see why the -march option should cause these errors, though. I would be more suspicious of -Os. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
pcm device locks on some errors
I have noticed that if I have problems with the pcm device (like a very busy CPU that can't keep it fed), the pcm device fails and I can't use it again without a reboot. Is this a known problem? Is there a workaround that can clear it? ThinkPad 600E running 4.1-Stable from August 18 using the integral Crystal Semiconductor audio and the pcm device. Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Crystal Semi (pcm) Audio card probing problem
This may be related to the problem reported in the "pcm0 play interrupt timeout, channel dead" thread. The problem in that the Crystal Audio sound card on my ThinkPad 600E is inconsistently probed. The result is that it is sometimes pcm0 and sometimes pcm1. If I get this from my device probe, the CS423x is pcm1: csa0: Crystal Semiconductor CS4610/4611 Audio accelerator mem 0x5000-0x500f,0x5010-0x50100fff irq 11 at device 6.0 on pci0 pcm0: CS461x PCM Audio on csa0 pcm0: ac97 codec invalid or not present (id == 0) device_probe_and_attach: pcm0 attach returned 6 pcm1: CS423x-PCI at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 But, it it probes like this, the "real" sound device is pcm0: csa0: Crystal Semiconductor CS4610/4611 Audio accelerator mem 0x5000-0x500f,0x5010-0x50100fff irq 11 at device 6.0 on pci0 device_probe_and_attach: csa0 attach returned 6 pcm0: CS423x-PCI at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 It seems about 50/50 on which way it probes for any given reboot. Of course, every time it flips, I need to log in a s root and switch the device over. This is at least a bit of a pain. Has anyone got an explanation of why this happens and if there is a chance of getting it fixed? It bothers me when my system acts in a non-deterministic fashion in something that should be as repeatable as a device probe! It also wastes irq 11 in the first case and I have a tight IRQ situation on that system, in any case. It's been doing this since I upgraded to 4.0-Stable about a month after 4.0 was released and about three days after Xircom Ethernet support went in. It may have been doing it under 3.4, but I never used the audio, so I really don't know. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: can't load kernel after build/install world/kernel
From: "Russell D. Murphy Jr." [EMAIL PROTECTED]
Date: Tue, 25 Jul 2000 12:14:44 -0400 (EDT)
Sender: [EMAIL PROTECTED]
I seem to have shot myself in the foot. I ran cvsup, buildworld,
installworld, buildkernel, and installkernel yesterday on my laptop as
well as my desktop. The laptop will no longer boot FreeBSD; the
desktop is fine. The laptop shows:
F1 DOS
F2 FreeBSD
Default: F2
BTX loader 1.00 BTX version is 1.01
Console: internal video/keryboard
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 639kB/64448kB available memory
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Mon Jul 24 14.53.22 EDT 2000)
Hit [Enter] to boot immediately, or any other key ofr command prompt.
Booting [kernel]...
can't load 'kernel'
can't load 'kernel.old'
ok ls
open '/' failed: no such file or directory
ok lsdev
disk @0x10738
disk0: BIOS drive A
disk1: BIOS drive C
pxe @ 0xe4dc
The machine boots up in W95.
The machine was running 4.0-Stable from a few weeks ago.
I have a script which runs the sequence of build/install steps; the
script on the laptop stopped because the laptop was running under a
different machine name than usual and so the script did not find the
kernel config file. I ran buildkernel and installkernel by hand for
my kernel config file and for GENERIC. I believe I followed the
UPDATING instructions (but something's not working, so I probably
missed something).
Any suggestions?
You say you did a buildkernel. Did you specify a kernel name? If not,
you can try GENERIC.
Boot to the boot prompt ("ok") and enter "boot GENERIC -s". That
should load and boot a kernel named 'GENERIC'. If you specified a
kernel name to buildkernel and installkernel, use that name in place
of 'GENERIC'.
You can always boot this way, although, if the 'kernel' file exists,
you need to so an 'unload' before booting.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Custom boot disks
Date: Thu, 30 Mar 2000 02:08:06 -0800 From: "Jordan K. Hubbard" [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I have several systems with broken PCI chipsets that I need to upgrade to 3.4-R from 2.2.7-R. I've patched 'pcibus.c' to fix the problem on these systems (reversed the config mode probe order) but now I need to build boot/install stiffies to get these machines up and running. Is there any quick/simple way to do this without going through a 'make release' process? Just make a kernel and make sure you keep "options MFS" and "options MFS_ROOT" in there. Then whap it over the kernel on kern.flp, which you can mount as a normal floppy. One step Jordan forgot to mention is that you need to gzip the kernel file before trying to move it to the floppy or it will never fit! Of course this is pretty obvious from the name of the kernel file on the floppy...kernel.gz. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
