Re: wierd build error with -current
On 30 Jun 2001 21:59:19 -0700, Matthew Jacob wrote:
> I'm sure you're right. I guess I need to go fix the breakage.
>
> It's supposed to work. Things get built in /usr/obj, not /usr/src.
Hrm, OK. That's something I didn't know. I'm assuming that you've tried
mounting /usr/src as read-write and tried compiling again?
- andrew
--
void signature () {
cout << "Andrew Reid -- [EMAIL PROTECTED]" << endl ;
cout << "Cell: +61 401 946 813" << endl;
cout << "Quidquid latine dictum sit, altum viditur" << endl;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: wierd build error with -current
I'm sure you're right. I guess I need to go fix the breakage.
It's supposed to work. Things get built in /usr/obj, not /usr/src.
On 1 Jul 2001, Andrew Reid wrote:
> On 30 Jun 2001 09:39:15 -0700, Matthew Jacob wrote:
>
> > No, the build process is broken. It is in fact supposed to work, and
> > worked last week, to build from a read-only /usr/src.
>
> How do you qualify this? The error you got was "Permission denied". The
> build process will want to write files. Your filesystem is mounted as
> read-only.
>
> Have I missed something here?
>
>- andrew
>
> --
> void signature () {
> cout << "Andrew Reid -- [EMAIL PROTECTED]" << endl ;
> cout << "Cell: +61 401 946 813" << endl;
> cout << "Quidquid latine dictum sit, altum viditur" << endl;
> }
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: wierd build error with -current
Andrew Reid wrote: > On 30 Jun 2001 09:39:15 -0700, Matthew Jacob wrote: > >> No, the build process is broken. It is in fact supposed to work, and >> worked last week, to build from a read-only /usr/src. > > How do you qualify this? The error you got was "Permission denied". The > build process will want to write files. Your filesystem is mounted as > read-only. All writes during a buildworld are supposed to go to /usr/obj, not /usr/src. -- Ben Smithurst / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Vinum + DEVFS ?
* Patrick Hartling <[EMAIL PROTECTED]> [010630 14:04] wrote: > I just got two new hard drives, and I am preparing to set them up to do > RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS > became the default in -current), I saw a message saying that Vinum was > not yet ready for use with DEVFS. Is that still the case? I fixed that. :) Let me and Grog know if you have problems. -- -Alfred Perlstein [[EMAIL PROTECTED]] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wierd build error with -current
On 30 Jun 2001 09:39:15 -0700, Matthew Jacob wrote:
> No, the build process is broken. It is in fact supposed to work, and
> worked last week, to build from a read-only /usr/src.
How do you qualify this? The error you got was "Permission denied". The
build process will want to write files. Your filesystem is mounted as
read-only.
Have I missed something here?
- andrew
--
void signature () {
cout << "Andrew Reid -- [EMAIL PROTECTED]" << endl ;
cout << "Cell: +61 401 946 813" << endl;
cout << "Quidquid latine dictum sit, altum viditur" << endl;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bug in CURRENT's ioctl function?
I was trying to run AOL Server 3.4 on FreeBSD 5.0-CURRENT. The server will run on a non-privilaged port, but will segfault on port 80 or any other privilaged port. This behavior does not occur on FreeBSD 4.3. The idea is that the server starts as root, binds to port 80, and then suid's to a normal user. I have already gone through the AOL Server source and also run this problem past users on the AOL Server mailing list. I have attempted to run AOL Server 3.4 on two different CURRENT boxes. One was last updated in March, and the other was updated just 3 days ago. Both had the same problem. Here is the gdb output when attempting to run on port 80: [25/Jun/2001:16:30:13][15486.135540736][-main-] Notice: binder: listen(205.216.111.20,80) = 15 [25/Jun/2001:16:30:13][15486.135540736][-main-] Notice: nssock: listening on 205.216.111.20 Program received signal SIGSEGV, Segmentation fault. 0x281820ff in ioctl () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281820ff in ioctl () from /usr/lib/libc_r.so.5 #1 0x80805df in Ns_SockSetNonBlocking (sock=15) at sock.c:385 #2 0x2824551a in SockStart (server=0x8145560 "server1", label=0x8145b10 "nssock", drvDataPtr=0x8171208) at sock.cpp:474 #3 0x806e326 in NsStartDrivers (server=0x8145560 "server1") at drv.c:225 #4 0x8077491 in Ns_Main (argc=8, argv=0xbfbffadc, initProc=0x807445c ) at nsmain.c:697 #5 0x8074448 in main (argc=8, argv=0xbfbffadc) at main.c:64 #6 0x805ae7f in _start () (gdb) It seems it binds to port 80 but than segfaults as soon as it switched to a non-root user. This problem does not occur on non-privilaged ports above 1024, nor does it occur on FreeBSD 4.3 on any ports. Anyone have any ideas on what might be causing this? Thanks, Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(Almost) "ClockWork" Instability of CURRENT
Ever since about a week or 2 now (iirc) my box running CURRENT has been showing an almost ClockWork Instability. [ Output from `last reboot` ] reboot ~ Sat Jun 30 22:59 reboot ~ Fri Jun 29 22:56 reboot ~ Thu Jun 28 22:46 reboot ~ Wed Jun 27 20:07 reboot ~ Tue Jun 26 19:57 reboot ~ Mon Jun 25 19:47 reboot ~ Sun Jun 24 19:19 reboot ~ Sun Jun 24 19:04 reboot ~ Sat Jun 23 19:01 reboot ~ Fri Jun 22 18:55 reboot ~ Fri Jun 22 18:50 reboot ~ Thu Jun 21 00:44 reboot ~ Wed Jun 20 00:39 reboot ~ Tue Jun 19 00:37 reboot ~ Sun Jun 17 20:56 reboot ~ Sun Jun 17 20:42 reboot ~ Sat Jun 9 11:20 Some of these entries have been reboots for installworlds ... but a lot of them seem to show a rather frightening "clockwork" in their succession. It looks like somehow my system runs perfectly smooth up to 24 hours. Within the next 10 minutes after that ... it seems to suddenly collapse. I haven't gotten to get actually getting it to trigger so i can (hopefully) catch a console message (because of a rather busy work-schedule). If any other people are having similair issues, i would like to hear about it and try to find out what might be triggering this. If i recall correctly the instability started occuring shortly after the introduction of diskcheckd. I don't know if this might be involved or not. I have disabled it for now, and can hopefully tell if that stops the frequent crashes. [ Output from `dmesg` ] Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #36: Sun Jun 24 23:35:56 CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARSENIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 336804078 Hz CPU: AMD-K6(tm) 3D processor (336.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 100663296 (98304K bytes) avail memory = 94072832 (91868K bytes) Preloaded elf kernel "kernel" at 0xc03b3000. Preloaded elf module "random.ko" at 0xc03b309c. K6-family MTRR support enabled (2 registers) Using $PIR table, 5 entries at 0xc00f0a90 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 1.2 (no driver attached) intpm0: port 0xe800-0xe80f irq 9 at device 1.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 pcm0: port 0xd400-0xd41f irq 9 at device 9.0 on pci0 pci0: at 10.0 (no driver attached) pci0: at 11.0 (no driver attached) orm0: at iomem 0xc-0xc7fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: flags 0x4 irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, unlimited logging IPv6 packet filtering initialized, unlimited logging IPsec: Initialized Security Association Processing. ad0: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 17624MB [35808/16/63] at ata0-master UDMA33 ad1: 9671MB [19650/16/63] at ata1-master UDMA33 acd0: CD-RW at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /home was not properly dismounted /home: lost blocks 2 files 1 WARNING: /usr was not properly dismounted WARNING: /usr/obj was not properly dismounted WARNING: /usr/src was not properly dismounted WARNING: /var was not properly dismounted /var: lost blocks 50 files 1 WARNING: /var/ftp was not properly dismounted dc0: port 0xb800-0xb8ff mem 0xdf80-0xdf8000ff irq 11 at device 11.0 on pci0 d
Re: wierd build error with -current
No, the build process is broken. It is in fact supposed to work, and
worked last week, to build from a read-only /usr/src.
On 30 Jun 2001, Andrew Reid wrote:
> On 29 Jun 2001 14:46:38 -0700, Matthew Jacob wrote:
>
> > I now mount my /usr/src read-only. That should work?
>
> Ask yourself the question: "I've mounted a filesystem read-only. Should
> I be able to write to that filesystem?".
>
> > I'm now getting:
>
> [ .. ]
>
> > Permission denied
> >
> > This is strange. Is this an NFS error? What?
>
> It's not at all strange. You're trying to write to a read-only
> filesystem.
>
>- andrew
>
> --
> void signature () {
> cout << "Andrew Reid -- [EMAIL PROTECTED]" << endl ;
> cout << "Cell: +61 401 946 813" << endl;
> cout << "Quidquid latine dictum sit, altum viditur" << endl;
> }
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Vinum + DEVFS ?
I just got two new hard drives, and I am preparing to set them up to do RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS became the default in -current), I saw a message saying that Vinum was not yet ready for use with DEVFS. Is that still the case? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wierd build error with -current
On 29 Jun 2001 14:46:38 -0700, Matthew Jacob wrote:
> I now mount my /usr/src read-only. That should work?
Ask yourself the question: "I've mounted a filesystem read-only. Should
I be able to write to that filesystem?".
> I'm now getting:
[ .. ]
> Permission denied
>
> This is strange. Is this an NFS error? What?
It's not at all strange. You're trying to write to a read-only
filesystem.
- andrew
--
void signature () {
cout << "Andrew Reid -- [EMAIL PROTECTED]" << endl ;
cout << "Cell: +61 401 946 813" << endl;
cout << "Quidquid latine dictum sit, altum viditur" << endl;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current destabilization
On Fri, 29 Jun 2001, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "E.B. >Dreger" writes: > : Any best guesses when -current will be destabilized for the SMPng > : hackathon? > > October 2000. :-). Actually, D-date was 2000/09/07 01:32:48. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
