Remote upgrading (was: /etc/make.conf question)
On 3/12/02 at 11:41 AM Michael Lucas wrote: |[snip] |Remember, the correct dance for an upgrade these days includes the |following: | |make buildworld |make buildkernel |make installkernel | |make installworld |mergemaster | |[snip] = I manage a remote FreeBSD server, a single-user reboot is not at all practical. So my question is: how important, and for what reason, is the urging to go into single-user mode? On my remote server, I can assure that I am the only person logged in, I just cannot get into single-user mode. Will the 'make installworld' and 'mergemaster' steps not work properly in my scenario? Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: DMA problem fallback to PIO mode
> I have a problem with hdd: > > ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn > 86162431; cn 5363 tn 92 sn 40)ad4s1f: hard error readi > ng fsbn 86162431 of 40472032-40472063 (ad4s1 bn 86162431; cn 5363 tn 92 sn > 40) status=59 error=40 > ad4: DMA problem fallback to PIO mode > ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn > 86162431; cn 5363 tn 92 sn 40) status=59 error=40 > ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn > 86162431; cn 5363 tn 92 sn 40) status=59 error=40 > ad4s1f: hard error reading fsbn 86162431 of 40472032-40472063 (ad4s1 bn > 86162431; cn 5363 tn 92 sn 40) status=59 error=40 Does it produce same errors when disk is under pressure (du -h on /) ? I had same problem few months ago and i had to replace the disk. -- Dejan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /etc/make.conf question
On Tue, Mar 12, 2002 at 04:56:18PM +0100, Cliff Sarginson wrote: > On Tue, Mar 12, 2002 at 07:43:49AM -0500, Michael Lucas wrote: > > That's easy: none. > > > > I'm a fairly advanced user, and here's my make.conf: > > > > #for world > > CPUTYPE=i686 > > COMPAT22=yes > > COMPAT3x=yes > > KERNCONF=BLEEDING > > > Can I ask, does the KERNCONF definition make any difference to > buildworld ? I would not have thought so..but ? Buildworld, no. Buildkernel, yes. Remember, the correct dance for an upgrade these days includes the following: make buildworld make buildkernel make installkernel make installworld mergemaster If you have a custom kernel configuration, you can use it automatically at stage 2 & 3 by including KERNCONF in /etc/make.conf. Otherwise, you must include it on the command line. On a three-way-boot laptop, remembering which config you have at the moment is a pain. :-) -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /etc/make.conf question
On Tue, Mar 12, 2002 at 04:04:44PM +, Ceri wrote: > On Tue, Mar 12, 2002 at 04:56:18PM +0100, Cliff Sarginson wrote: > > On Tue, Mar 12, 2002 at 07:43:49AM -0500, Michael Lucas wrote: > > > That's easy: none. > > > > > > I'm a fairly advanced user, and here's my make.conf: > > > > > > #for world > > > CPUTYPE=i686 > > > COMPAT22=yes > > > COMPAT3x=yes > > > KERNCONF=BLEEDING > > > > > Can I ask, does the KERNCONF definition make any difference to > > buildworld ? I would not have thought so..but ? > > If it's set in make.conf then you can just do "make kernel". > It doesn't have anything to do with building world, though. > > Ceri Ok, I guessed that it was a convenience feature :) -- Regards Cliff Sarginson -- <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /etc/make.conf question
On Tue, Mar 12, 2002 at 04:56:18PM +0100, Cliff Sarginson wrote: > On Tue, Mar 12, 2002 at 07:43:49AM -0500, Michael Lucas wrote: > > That's easy: none. > > > > I'm a fairly advanced user, and here's my make.conf: > > > > #for world > > CPUTYPE=i686 > > COMPAT22=yes > > COMPAT3x=yes > > KERNCONF=BLEEDING > > > Can I ask, does the KERNCONF definition make any difference to > buildworld ? I would not have thought so..but ? If it's set in make.conf then you can just do "make kernel". It doesn't have anything to do with building world, though. Ceri -- keep a mild groove on To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: libusb build problems
On Tue, Mar 12, 2002 at 09:02:15AM -0700, John Reynolds~ wrote: > > it doesn't work for me either, however, I found the problem. There's a typo in > the patch. The preproc boiler plate around the changes look like this: > > #if (__FreeBSD_version > 5 && __FreeBSD_version < 500031) || \ > (__FreeBSD_version < 450001) > > and should look like this: > > #if (__FreeBSD_version > 50 && __FreeBSD_version < 500031) || \ > (__FreeBSD_version < 450001) > > (notice 5 -> 50). > > Josef, can you make this change and get this committed? Done. Thanks, Joe msg42427/pgp0.pgp Description: PGP signature
Re: libusb build problems
[ On Tuesday, March 12, stan wrote: ] > On Mon, Mar 11, 2002 at 12:29:31AM +, Josef Karthauser wrote: > > On Sun, Mar 10, 2002 at 07:05:06PM -0500, stan wrote: > > > I have been having problems building the libusb port for the last couple of > > > weeks. > > > > > > More and more of teh ports I use are becoming dependent on it. > > > > > > I'm enclosing a script of the build atempt. > > > > I've committed a fix to libusb that was posted to this list by > > John Reynolds a few weeks ago. It should be on your cvsup mirror in a > > few hours time. > > Sorry to say, this is still failing as of this mroning. I just cvsup'd and > tried to build the port. > > Here are the results: > it doesn't work for me either, however, I found the problem. There's a typo in the patch. The preproc boiler plate around the changes look like this: #if (__FreeBSD_version > 5 && __FreeBSD_version < 500031) || \ (__FreeBSD_version < 450001) and should look like this: #if (__FreeBSD_version > 50 && __FreeBSD_version < 500031) || \ (__FreeBSD_version < 450001) (notice 5 -> 50). Josef, can you make this change and get this committed? -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |John Reynolds Sr. Component Design Engineer - ICG/EID/Si Engineering | |Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | |[EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /etc/make.conf question
On Tue, Mar 12, 2002 at 07:43:49AM -0500, Michael Lucas wrote: > That's easy: none. > > I'm a fairly advanced user, and here's my make.conf: > > #for world > CPUTYPE=i686 > COMPAT22=yes > COMPAT3x=yes > KERNCONF=BLEEDING > Can I ask, does the KERNCONF definition make any difference to buildworld ? I would not have thought so..but ? -- Regards Cliff Sarginson -- <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: zlib security advisory
On Mon, Mar 11, 2002 at 06:59:24PM -0500, Alan Eldridge wrote: > FWIW RH notes several things that either have their own copy of zlib > that needs to be patched or that statically link and so need to be rebuilt. > > Has anyone produced such a list for FBSD, or is it not applicable to us? > > I suppose, to be safe, an inventory of ports needs to be done, too. Urk. I have such a list generated from the packages found on ftp2.freebsd.org. I found approximately 774 binaries (some ports including more than one executable or shared object, of course) that referenced zlib in the packages. I also searched the distfiles on ftp2.freebsd.org for applications that included their own copy of zlib. There are approximately 78 of those. (The above numbers are from Feb 18.) I did not count applications which statically link zlib. I don't believe that we are affected, so the information did not turn out to be very useful :-) Cheers, -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: libusb build problems
On Mon, Mar 11, 2002 at 12:29:31AM +, Josef Karthauser wrote: > On Sun, Mar 10, 2002 at 07:05:06PM -0500, stan wrote: > > I have been having problems building the libusb port for the last couple of > > weeks. > > > > More and more of teh ports I use are becoming dependent on it. > > > > I'm enclosing a script of the build atempt. > > I've committed a fix to libusb that was posted to this list by > John Reynolds a few weeks ago. It should be on your cvsup mirror in a > few hours time. Sorry to say, this is still failing as of this mroning. I just cvsup'd and tried to build the port. Here are the results: Script started on Tue Mar 12 09:56:51 2002 black# make ===> Building for libusb-0.1.5 make all-recursive Making all in . source='bsd.c' object='bsd.lo' libtool=yes depfile='.deps/bsd.Plo' tmpdepfile='.deps/bsd.TPlo' depmode=gcc /bin/sh ./depcomp /bin/sh ./libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -O -pipe -march=k6 -Wall -c -o bsd.lo `test -f bsd.c || echo './'`bsd.c rm -f .libs/bsd.lo cc -DHAVE_CONFIG_H -I. -I. -I. -O -pipe -march=k6 -Wall -c bsd.c -Wp,-MD,.deps/bsd.TPlo -fPIC -DPIC -o .libs/bsd.lo bsd.c: In function `usb_set_altinterface': bsd.c:156: structure has no member named `interface_index' bsd.c:157: structure has no member named `alt_no' bsd.c: In function `usb_control_msg': bsd.c:294: structure has no member named `request' bsd.c:295: structure has no member named `request' bsd.c:296: structure has no member named `request' bsd.c:296: structure has no member named `request' bsd.c:296: warning: left-hand operand of comma expression has no effect bsd.c:297: structure has no member named `request' bsd.c:297: structure has no member named `request' bsd.c:297: warning: left-hand operand of comma expression has no effect bsd.c:298: structure has no member named `request' bsd.c:298: structure has no member named `request' bsd.c:298: warning: left-hand operand of comma expression has no effect bsd.c:300: structure has no member named `data' bsd.c:301: structure has no member named `flags' bsd.c:324: structure has no member named `request' bsd.c:324: structure has no member named `request' bsd.c:328: warning: control reaches end of non-void function bsd.c: In function `usb_find_devices_on_bus': bsd.c:346: structure has no member named `addr' bsd.c:356: structure has no member named `devnames' bsd.c:365: structure has no member named `devnames' *** Error code 1 Stop in /usr/ports/devel/libusb/work/libusb-0.1.5. *** Error code 1 Stop in /usr/ports/devel/libusb/work/libusb-0.1.5. *** Error code 1 Stop in /usr/ports/devel/libusb/work/libusb-0.1.5. *** Error code 1 Stop in /usr/ports/devel/libusb. *** Error code 1 Stop in /usr/ports/devel/libusb. *** Error code 1 Stop in /usr/ports/devel/libusb. black# ^Dexit Script done on Tue Mar 12 09:56:58 2002 Any sugestiosn? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
zlib vulnerability in FreeBSD
I just stumbled across an article about a vulnerability in the zlib compression library at msnbc.com. Here is the link: http://www.msnbc.com/news/722605.asp?0si=- It mentions that CERT will be making a statement about it, so I went to CERT's site and found this: http://www.kb.cert.org/vuls/id/368819 It says that FreeBSD is vulnerable as of 28-Feb-2002. It also said that there was no "known" exploit code. I'm sure that will change quickly now that this is public. I went and looked at the FreeBSD CVS repository for zlib (http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libz/) and it appears that zlib 1.1.4 has been imported into the "vendor" branch. I'm not familiar with the "vendor" branch. Could someone enlighten me? I went to the zlib site at http://www.gzip.org/zlib and found that zlib 1.1.4 contains the vulnerability fix, so it appears that steps are being taken to fix this in FreeBSD. Anyone have any idea how long it will take to make it into RELENG_4_5? Just curious since I have several machines to upgrade when it does. -- Warren Smith Analyst/Programmer DST Output [EMAIL PROTECTED] 816-843-9084 *** The contents of this message are the sole responsibility of Warren Smith and do NOT reflect the opinions or positions of DST Output. *** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ATA suggestion
Hello, Recently I had some problems with my ATA drive; I was using the CMD 649 chipset on auxilary controller card and my system halted several times with errors on resetting the first drive (which was running in UDMA 100 mode). I took a different controler (CMD 649 compatible, different vendor), but that didn't work. I'm suspecting that the drive doesn't like the UDMA 100 mode (although it says it does ;). It worked fine on 33 for more than one year. The point is that I miss some option to downgrade the ATA mode - like I want to set UDMA 66 for that drive, not UDMA 100 (maybe it would help), but I couldn't find any option to do so. Is it hard to make some sysctl setting which would force given mode (assuming the drive supports it of course)? Some time ago I had a similar problem with a drive that was detected as 66 on 40-wire cable (it was a slave drive; the master was an ATAPI CDROM working in UDMA 33 mode, hw.ata.atapi_dma turned on). The drive failed to work in DMA at all, and it dropped to PIO mode. I think the solutian would be just forcing the 33 mode.. but.. -- Winfried mail: [EMAIL PROTECTED] http://violent.dream.vg JS500-RIPE Warning: Never underestimate the power of stupid people in large numbers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
device changes
i upgraded my web server from fbsd 4.3 to 4.5 (stable): FreeBSD binnacle.wantabe.com 4.5-RELEASE-p2 FreeBSD 4.5-RELEASE-p2 #0: Sat Mar 9 20:36:33 CST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/BINNACLE i386 i think there were maybe some /dev changes? i'm seeing log entries like the following: Mar 12 00:03:18 binnacle /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Mar 12 00:03:18 binnacle /kernel: ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable can i get an explanation? and maybe pointer to any action i should be taking? thanks in advance. jeff -- | |\+--+ Jeffrey J. Libman, ops. mgr.| \ | Wantabe Internet Services | Wantabe, Inc. |__\ +--+ [EMAIL PROTECTED]<-|--> (281) 345-0215 __,.-=\'`^`'~=-../__,.-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
