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

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 >

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

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 f

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

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

(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 ~

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 qu

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. H

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 th

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 PR