Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-07 Thread David O'Brien
On Fri, Dec 08, 2000 at 01:44:47PM +1030, Matthew Thyer wrote: > Regardless /dev/da18s1 should work as for /dev/da18 Correct me if I'm wrong, but /dev/da18s1 would only work if you installed a true slice vs. a dedicated configuaation of the disk something like ``disklabel da18 auto''. -- -- D

possibly related data point - (was) Re: Current Broken!

2000-12-07 Thread atrens
John, I'm not a constraints expert either, but I noticed that when I try to build a kernel WITHOUT any optimization, I get a failure in /usr/src/sys/i386/atomic.h . # make atomic.o cc -c -O0 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit

Current Broken!

2000-12-07 Thread John Baldwin
On 08-Dec-00 The Hermit Hacker wrote: > > Just upgraded the kernel, rebooted and it hung/panic'd with: > > panic: spin lock sched lock held by 0x0xc02a73el for > 5 seconds > cpuid = 1; lapic.id = 0100 > Debugger("panic") > > I have DDB enabled, and ctl-alt-esc doesn't break to the debugger

Current CVS kernel panic ...

2000-12-07 Thread The Hermit Hacker
Just upgraded the kernel, rebooted and it hung/panic'd with: panic: spin lock sched lock held by 0x0xc02a73el for > 5 seconds cpuid = 1; lapic.id = 0100 Debugger("panic") I have DDB enabled, and ctl-alt-esc doesn't break to the debugger, so its totally hung here ... dual-cpu celeron, smp e

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-07 Thread Matthew Thyer
Mike Smith wrote: > > > Mike Smith wrote: > > > > The program works on Compaq True64 UNIX v 4.0d > > > > It also works on Solaris 7 (only tested sparc). > > > > > > > > So it seems FreeBSD is broken here. > > > > > > FreeBSD just behaves differently. If you want to write to the whole > > > disk,

Hangs during 'make world -j4' on recent current

2000-12-07 Thread Greg Lehey
For over a week now, I have been unable to complete a 'make world' on my -CURRENT box if I specify -j4. The system hangs and is completely unresponsive. This is a dual Celeron and an Abit BP6 motherboard. As far as I can tell, nobody knows what's causing this, nor even how to attack the problem

Re: ffs_valloc: dup alloc panics with stable/current

2000-12-07 Thread Tomi Vainio - Sun Finland -
Mark Newton writes: > > > sense = 3 asc = 11 asq = 0 > > This is not so bad but 5-30 minutes after this command system will > > always panic. > > Are you surprised? The system is complaining that it's having intermittent > difficulty accessing the disk, so it shouldn't be at all surpr

Re: ffs_valloc: dup alloc panics with stable/current

2000-12-07 Thread Mark Newton
On Fri, Dec 08, 2000 at 03:44:28AM +0200, Tomi Vainio - Sun Finland - wrote: > sense = 3 asc = 11 asq = 0 > This is not so bad but 5-30 minutes after this command system will > always panic. Are you surprised? The system is complaining that it's having intermittent difficulty accessing the d

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-07 Thread Mike Smith
> Mike Smith wrote: > > > The program works on Compaq True64 UNIX v 4.0d > > > It also works on Solaris 7 (only tested sparc). > > > > > > So it seems FreeBSD is broken here. > > > > FreeBSD just behaves differently. If you want to write to the whole > > disk, open the whole-disk device, not the

ffs_valloc: dup alloc panics with stable/current

2000-12-07 Thread Tomi Vainio - Sun Finland -
Hi, We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System is working quite

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-07 Thread Matthew Thyer
Mike Smith wrote: > > The program works on Compaq True64 UNIX v 4.0d > > It also works on Solaris 7 (only tested sparc). > > > > So it seems FreeBSD is broken here. > > FreeBSD just behaves differently. If you want to write to the whole > disk, open the whole-disk device, not the 'c' partition.

Re: growfs(8) for FreeBSD

2000-12-07 Thread Michael C . Wu
On Thu, Dec 07, 2000 at 10:34:44AM -0800, Christoph Herrmann scribbled: | Due to vinum it is no problem to add disks and grow your volumes but up to | now you couldn't easily make use of that new space for a file system, except | using sequence of ufsdump/newfs/ufsrestore or something similar. |

Re: growfs(8) for FreeBSD

2000-12-07 Thread The Hermit Hacker
Erk, I fear you mis-understand ... FreeBSD has a feature called 'VINUM', which is a volume manager ... basically, it allows you to create RAID or Stripe'd file systems (or concat ones) ... what growfs allows is someone to add an n+1 drive to their RAID/Stripe and increase the size of the file sys

RE: Current kernel build failure -- >>cam_periph.c

2000-12-07 Thread John Baldwin
On 07-Dec-00 Manfred Antar wrote: > At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: > >>On 07-Dec-00 John Baldwin wrote: >>> >>> On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: >

Re: cvs-cur.6925.gz appears to be corrupt

2000-12-07 Thread Stephen Hocking
> It's fine with me. > BTW, I got my cvs delta through ctm-cvs-cur mailing list, and here's > the check sum for it. > > $ ls -l cvs-cur.6925.gz > -rw-r--r-- 1 daemon wheel 24114 Dec 6 19:34 cvs-cur.6925.gz > $ md5 cvs-cur.6925.gz > MD5 (cvs-cur.6925.gz) = 7751af95fb0821338f3bc

Re: cvs-cur.6925.gz appears to be corrupt

2000-12-07 Thread Munehiro Matsuda
From: Stephen Hocking <[EMAIL PROTECTED]> Date: Wed, 06 Dec 2000 15:20:23 -0600 ::With ::# ctm -b /cvs cvs-cur.6925.gz :: ::I get :: :: FR: /cvs/CVSROOT/history md5 mismatch. ::cvs-cur.6925.gz Fatal error: Corrupt patch. ::Expected "\n" but didn't find it {20}. ::ctm: exit(96) :: :: Anybody

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-07 Thread Mike Smith
> CC: to -current as that's what I'm running. > > "John W. De Boskey" wrote: > > > > Hi, > > > >I can't answer your questions directly, but you might want > > to checkout the sources to newfs (/usr/src/sbin/newfs/newfs.c or > > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/newfs/newfs.c?an

Re: Lucent Orinoco Gold PCCard?

2000-12-07 Thread Nick Sayer
Christopher Masto wrote: > > On Wed, Dec 06, 2000 at 07:23:40PM -0800, Charlie Root wrote: > > There is definately a trend to lower prices. I just found this. A > > new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia > > cards for $699. The access point sounds interesting. I per

Re: Lucent Orinoco Gold PCCard?

2000-12-07 Thread Christopher Masto
On Wed, Dec 06, 2000 at 07:23:40PM -0800, Charlie Root wrote: > There is definately a trend to lower prices. I just found this. A > new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia > cards for $699. The access point sounds interesting. I personally > would like to use it as a

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-07 Thread Matthew Thyer
CC: to -current as that's what I'm running. "John W. De Boskey" wrote: > > Hi, > >I can't answer your questions directly, but you might want > to checkout the sources to newfs (/usr/src/sbin/newfs/newfs.c or > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/newfs/newfs.c?annotate=1.31 > line

Re: growfs(8) for FreeBSD

2000-12-07 Thread Soren Schmidt
It seems Christoph Herrmann wrote: Sounds very cool, but there is no URL :) > Due to vinum it is no problem to add disks and grow your volumes but up to > now you couldn't easily make use of that new space for a file system, except > using sequence of ufsdump/newfs/ufsrestore or something simila

Re: growfs(8) for FreeBSD

2000-12-07 Thread Rogier R. Mulhuijzen
Is it also capable of shrinking filesystems? I've sometimes wanted to grow my /var or / slice using space freed by shrinking /usr (on a default partitioned disk). Up to now I've solved it through symlinks, but that doesn't really deserve the beauty award. I'd imagine a lot of new users wouldn'

[CFR] IPv6 support for lpd, syslogd and logger

2000-12-07 Thread Hajimu UMEMOTO
Hi, I'd like to add IPv6 support for lpd, syslogd and logger. You can find the patches from: http://www.imasy.or.jp/~ume/ipv6/FreeBSD/logger-ipv6-20001201.diff http://www.imasy.or.jp/~ume/ipv6/FreeBSD/lpr-ipv6-20001206.diff http://www.imasy.or.jp/~ume/ipv6/FreeBSD/syslogd-ipv6-20001

growfs(8) for FreeBSD

2000-12-07 Thread Christoph Herrmann
Hi, Due to vinum it is no problem to add disks and grow your volumes but up to now you couldn't easily make use of that new space for a file system, except using sequence of ufsdump/newfs/ufsrestore or something similar. Thomas ([EMAIL PROTECTED]) and me ([EMAIL PROTECTED]) have written a growfs

LINT broken

2000-12-07 Thread Poul-Henning Kamp
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensio ns -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -DGPROF -D_KERNEL -include opt_global.h -elf

Re: Progress report: Multilingual sysinstall for -current

2000-12-07 Thread Daniel C. Sobral
Kazutaka YOKOTA wrote: > > I don't think importing multilingual sysinstall will detract effort > from libh. You see, even if it is maintained separately from the > -current, it has its own maintainers and developers. I expect they > are the same people who will maintain and develop I18N sysinst