4.5 buildworld failure: libfetch
Can someone please inform me what configs or setting do I have that leads to the following 'buildworld' error? I have upgraded a similar box from 4.4 to 4.5 with no hitch, but this one keeps failing at the same point. Even blown away /usr/src and /usr/obj but to no avail. Any help is appreciated Thank you Feisal http://www.webcraft99.com --- === libfetch cc -O -pipe -march=pentiumpro -I. -DINET6 -I/usr/obj/usr/src/i386/usr/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -c /usr/src/lib/libfetch/fetch.c -o fetch.o cc -O -pipe -march=pentiumpro -I. -DINET6 -I/usr/obj/usr/src/i386/usr/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -c /usr/src/lib/libfetch/common.c -o common.o cc1: warnings being treated as errors /usr/src/lib/libfetch/common.c: In function `_fetch_putln': /usr/src/lib/libfetch/common.c:343: warning: cast discards qualifiers from pointer target type /usr/src/lib/libfetch/common.c:345: warning: cast discards qualifiers from pointer target type *** Error code 1 Stop in /usr/src/lib/libfetch. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
samba package
I just installed my new 4.5R box using the official CDs. It looks very strange but I can't find any samba package in any of 4 CDs? Does someone have any idea why the package wasn't included to CDs? In contrast, the samba package exist in ftp. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Junior Annoying Hacker Task
Thus spake Miguel Mendez [EMAIL PROTECTED]: On Sat, 02 Feb 2002 03:29:50 -0800 Terry Lambert [EMAIL PROTECTED] wrote: Hi Terry et al, Let me know the form you want the hierarchy to take, so you can stick it into the GTK hierarchy thingy; I'll be happy to crank out some quick yacc and lex code to do the parsing of the file into that format for you. A structure definition, with links, and how you want it linked, would be ideal. 8-). I've been thinking about it and I'd like to provide two frontends, a GTK one and a ncurses one, what do you think? This is getting pretty ambitious. I'm not about to say that a procedural interface to rc.conf wouldn't be nice, or that it couldn't be done well, but when it comes down to it, what problem are we trying to solve? Certainly rc.conf supports a lot of options, and a hierarchical arrangement would simplify things. However, most people only need to deal with a small subset of the options, and organization doesn't seem to be a big issue. Of course there's also the possibility that someone could leave out a quotation mark and end up with a non-working system, but that's rare and solvable with simpler tools, as has been discussed. Besides, both Microsoft and the linuxconf people have done far worse than rc.conf---especially Microsoft. Know what to do when a bad update eats a VXD that isn't on the Windows CD? :P [I'm not subscribed to -current, so please CC me any replies if that's where this thread has drifted.] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: samba package
On Monday 04 February 2002 06:05, Rostislav wrote: I just installed my new 4.5R box using the official CDs. It looks very strange but I can't find any samba package in any of 4 CDs? Does someone have any idea why the package wasn't included to CDs? In contrast, the samba package exist in ftp. Did you check all 4 CDs? -- Bill Moran Potential Technology technical services http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
FS gurus needed! (was: Strange lock-ups during backup over nfs after adding 1024M RAM)
On Monday, February 04, 2002 Peter Jeremy [EMAIL PROTECTED] wrote: PJ On 2002-Feb-01 12:36:50 +0500, Sergey Gershtein [EMAIL PROTECTED] wrote: Here's what vmstat -m says about FFS node: Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ... FFS node152293 76147K 76479K102400K 31264670 0 512 ... PJ One oddity here is the Size - FFS node is used to allocate struct PJ inode's and they should be 256 bytes on i386. Are you using something PJ other than an i386 architecture? Unless this is a cut-and-paste PJ error, I suspect something is radically wrong with your kernel. Yes, it's i386 and it's not cut-and-paste error. The current output of vmstat -m says: ... FFS node152725 76363K 76479K102400K 92476020 0 512 ... vfscache157865 10671K 11539K102400K 96684970 0 64,128,256,512,512K ... The system uptime is 5 days, backup is temporarily disabled. I put the coplete output of 'vmstat -m', some other commands and kernel config on the web on http://storm.mplik.ru/fbsd-stable/ so you can have a look at it. By the way, on our second server running the same hardware the size of FFS node is also 512. How can it be so? PJ By default, the memory limit is 1/2 vm_kmem_size, which is 1/3 physical PJ memory, capped to 200MB. Which means you've hit the default cap. PJ You can increase this limit with the loader environment PJ kern.vm.kmem.size (see loader(8) for details). (This is also capped PJ at twice the physical memory - which won't affect you). Before you go PJ overboard increasing this, note that the kernel virtual address space PJ is only 1GB. Hmm. Not sure what to do. Shell I try to play with kern.vm.kmem.size or better not touch it? I am now thinking that removing the extra memory we've added is the best solution to the problem. I don't like this solution though. PJ How many open files do you expect on your box? PJ Is it reasonable for there to be 150,000 active inodes? ptat -T right now says: 666/4096 files 0M/511M swap space I don't expect the number of open files go beyond 1,000-1,500. The only problem is accessing a lot (more than a 1,000,000) of small files over NFS. But if I understand correctly, those files should be opened and closed one by one, not all together. Is that right? PJ Does vfscache have around the same number of InUse entries as FFS node? Yes, it seems so (see above). What does it mean? PJ What is the output of sysctl vfs? See http://storm.mplik.ru/fbsd-stable/sysctl_vfs.txt PJ PS: I'm still hoping that one of the FS gurus will step in and point PJ out what's wrong. I changed the subject of my message to catch attention of FS gurus on the list. Thank you, Sergey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: samba package
On Monday 04 February 2002 06:05, Rostislav wrote: I just installed my new 4.5R box using the official CDs. It looks very strange but I can't find any samba package in any of 4 CDs? Does someone have any idea why the package wasn't included to CDs? In contrast, the samba package exist in ftp. Did you check all 4 CDs? Yes I did. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dropping 127.* on the floor
Hi, Will this be backed out, or do you know of a work around to this issue? ---Mike At 07:17 PM 2/3/2002 -0700, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Michael Nottebrock [EMAIL PROTECTED] writes: : Greg Prosser wrote: : : FWIW, my problem was a change in the ip stack. : : We now drop 127.* packets on the floor if they come in across an interface : that is not lo0. Since ipnat redirect rules happen below the ip stack, : packets which are rewritten by ipnat to use a 127.* address get dropped on : the floor when they enter the stack. ipnat records the redirect as having : worked, but the packet just disappears silently. This totally breaks : my transparent proxy, as I forward the connections to 127.0.0.1 via ipnat. : : : Ugh. This probably means that transparent squid proxying will also break : and _that_ scares me (no touchy cvsup for my -STABLE box). You might : want to contact the committer about this. It is certainly looking like this change will be backed out. It is well intended, but breaks too many things. :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: samba package
On 4 Feb 2002 at 6:48, Bill Moran wrote: On Monday 04 February 2002 06:05, Rostislav wrote: I just installed my new 4.5R box using the official CDs. It looks very strange but I can't find any samba package in any of 4 CDs? Does someone have any idea why the package wasn't included to CDs? In contrast, the samba package exist in ftp. Did you check all 4 CDs? Well, I don't know if he did, but I did -- it ain't there. Amazing. And the KDE package(s) looked a little light too (only -base and - libs??) Oh well, as for Samba it seems that 2.2.3 is on the way, so I guess I'll hang loose a while before upgrading. Downer for those intending to do a clean install from the CD's, though. All the best, Eric -- Bill Moran Potential Technology technical services http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- * Keep it as simple as possible -- but no simpler. -- A. Einstein To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
[no subject]
-- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dropping 127.* on the floor
On Mon, Feb 04, 2002 at 08:04:20AM -0500, Mike Tancsa wrote: Hi, Will this be backed out, or do you know of a work around to this issue? The ip_input() part in question was committed to RELENG_4 in revision 1.130.2.20 by a different committer, about a year ago. I think the original poster should fix his rulesets instead. I don't believe that transparent proxying (using the IPFIREWALL_FORWARD) was broken by this change, as it doesn't bind sockets to loopback addresses. At 07:17 PM 2/3/2002 -0700, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Michael Nottebrock [EMAIL PROTECTED] writes: : Greg Prosser wrote: : : FWIW, my problem was a change in the ip stack. : : We now drop 127.* packets on the floor if they come in across an interface : that is not lo0. Since ipnat redirect rules happen below the ip stack, : packets which are rewritten by ipnat to use a 127.* address get dropped on : the floor when they enter the stack. ipnat records the redirect as having : worked, but the packet just disappears silently. This totally breaks : my transparent proxy, as I forward the connections to 127.0.0.1 via ipnat. : : : Ugh. This probably means that transparent squid proxying will also break : and _that_ scares me (no touchy cvsup for my -STABLE box). You might : want to contact the committer about this. It is certainly looking like this change will be backed out. It is well intended, but breaks too many things. :-( Warner -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: how to tell the kernel to use mfs in loader
From: [EMAIL PROTECTED] (George Michaelson) Date: Mon, 4 Feb 2002 12:56 EST What can I do in loader phase to tell a kernel to use MFSROOT as the only image? I suspect the install kernel is 'smart' - Sees a valid FS on the disk and is using it for its init path. Not an exact answer but I usually boot kernel with MFS (e.g. installer) from boot0. I also would like to know how to tell to use MFS from /boot/loader console. // Noriaki Mitsunga // To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dropping 127.* on the floor
On Mon, Feb 04, 2002 at 03:25:19PM +0200, Ruslan Ermilov wrote: On Mon, Feb 04, 2002 at 08:04:20AM -0500, Mike Tancsa wrote: Hi, Will this be backed out, or do you know of a work around to this issue? The ip_input() part in question was committed to RELENG_4 in revision 1.130.2.20 by a different committer, about a year ago. See the Bugtraq archives for the thread starting with Message-ID: [EMAIL PROTECTED], subject ``Loopback and multi-homed routing flaw in TCP/IP stack.'' for the reasons behind this change. The following URL might work. URL:http://www.securityfocus.com/cgi-bin/archive.pl?id=1[EMAIL PROTECTED] 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
