Re: ccd performance (was: [ GEOM tests ] vinum drives lost)

Matthew Dillon wrote: > But, again, CCD is not trying to implement 'real' RAID. It can't > rebuild a lost mirror drive, for example, and does not implement RAID-5. > IMHO A real RAID controller with NVRAM should be used for those things. FWIW, the people who sell RAID controllers wi

Re: Do we still need portmap(8)?

In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey" writes: >On Sunday, 6 October 2002 at 23:42:55 -0700, David O'Brien wrote: >> On Mon, Oct 07, 2002 at 04:02:51PM +0930, Greg 'groggy' Lehey wrote: >>> It's been a while since we've used portmap(8) on -CURRENT systems. Is >>> it still needed,

Re: Do we still need portmap(8)?

On Sunday, 6 October 2002 at 23:42:55 -0700, David O'Brien wrote: > On Mon, Oct 07, 2002 at 04:02:51PM +0930, Greg 'groggy' Lehey wrote: >> It's been a while since we've used portmap(8) on -CURRENT systems. Is >> it still needed, or can it be removed completely? At the very least, >> the man pa

New panic fun.

Decided to update my source tree today. Evidently this was not a bright move. I built my kernel and whatnot, powered off (rebooting on my laptop doesn't work...), and startx'ed. Then I ran mozilla. poof Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:

Re: xdm can not login on current

On Mon, 7 Oct 2002, suken woo wrote: > xdm broken on current when login . i knew this is the pam module > problem,but how could i fix it? Chances are, you built your X11 with an old -CURRENT system, and since then the ABI for the PAM stuff has changed in -CURRENT, so your old X11 no longer talk

Re: Do we still need portmap(8)?

On Mon, Oct 07, 2002 at 04:02:51PM +0930, Greg 'groggy' Lehey wrote: > It's been a while since we've used portmap(8) on -CURRENT systems. Is > it still needed, or can it be removed completely? At the very least, > the man page should stop claiming that it's necessary to run NFS. Are you saying

Re: ccd performance (was: [ GEOM tests ] vinum drives lost)

:> a lot of information on how to use it. I generally recommend :> using a stripe size of 1152 for multitasking loads. : :Sectors? Why particularly this value? It's described in 'tuning'. Basically you want a fairly large stripe to reduce multi-disk seeking when reading sequenti

Do we still need portmap(8)?

It's been a while since we've used portmap(8) on -CURRENT systems. Is it still needed, or can it be removed completely? At the very least, the man page should stop claiming that it's necessary to run NFS. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [

Re: xdm can not login on current

>Date: Mon, 07 Oct 2002 12:48:33 +0800 >From: suken woo <[EMAIL PROTECTED]> >xdm broken on current when login . It isn't for me, and I've been tracking -CURRENT daily for some time. >i knew this is the pam module >problem,but how could i fix it? Well, absent any clues as to why you think it

Re: [PATCH] Re: Junior Kernel Hacker page updated...

Terry Lambert wrote: > Stefan Farfeleder wrote: > > (kgdb) l *kqueue_scan+0x242 > > 0xc01a1212 is in kqueue_scan > > (/freebsd/current/src/sys/kern/kern_event.c:716). > > 713 TAILQ_INSERT_TAIL(&kq->kq_head, &marker, kn_tqe); > > 714 while (count) { > > 715

Re: panic: kmem_malloc(4096): kmem_map too small

On Mon, 7 Oct 2002, Mikhail Teterin wrote: > No... With today's kernel, machine has already _frozen_ after swappager > complained about lack of swap. Rather sad -- a not so uncommon installation > with 128Mb of memory plus twice that much of swap would still have less > virtual memory than this b

Re: My problems with GEOM

In message <[EMAIL PROTECTED]>, "Seth Hieronymus" writes: >You were right. After trying both a CD, and a zip-disk in the computer >(both together, and separately), having a zip-disk in the drive seems to >allow the boot to continue normally. ATA(PI) or SCSI interface ZIP ? -- Poul-Henning Kam

Re: My problems with GEOM

In message <[EMAIL PROTECTED]>, "Seth Hieronymus" writes: >Hello, > >After recompiling a kernel after the GEOM transition, my boot gets as >far as: > >Initializing GEOMetry subsystem >ad0: 28629MB [58168/16/63] at ata0-master UDMA33 >acd0: CDROM at ata1-master PIO4 >afd0: 239MB [239/64/32] at a

Re: panic: kmem_malloc(4096): kmem_map too small

îÅĦÌÑ 06 öÏ×ÔÅÎØ 2002 03:13 am, n0g0013 ÷É ÎÁÐÉÓÁÌÉ: > On 06.10-03:06, Mikhail Teterin wrote: > > this machine has a total of 512Mb of RAM, and no swap. > > No X was running. Just ``cvs update''-ing. > > running vinum ? i am getting this consistently with vinum (but am > taking an age to rebuild

xdm can not login on current

hello folks: xdm broken on current when login . i knew this is the pam module problem,but how could i fix it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: My problems with GEOM

Dan, From: "Dan Nelson" >In the last episode (Oct 06), Robert Watson said: >> On Sun, 6 Oct 2002, Seth Hieronymus wrote: >> > Thanks for the pointers. Here's the trace 1: >> > mi_switch(c0bb9988,14,c01bbe60,c0bb98f0,1) at mi_switch+0x290 >> > msleep(c03778a0,0,68,c03153d7,14) at msleep+0x477 >>

Re: GEOM and SCSI-cd: mount not working any more

On Sun, 6 Oct 2002, David O'Brien wrote: > On Sun, Oct 06, 2002 at 06:20:12PM +0200, Poul-Henning Kamp wrote: > > Can I get you to insert printfs like the one below all places > > in vfs_mount.c and cd9660_vfsops.c where you see it using EINVAL > > and try to find out which particular one it is ?

Re: My problems with GEOM

On Sun, Oct 06, 2002 at 08:26:03PM -0400, Robert Watson wrote: > On Sun, 6 Oct 2002, Carl Schmidt wrote: > > > > Mounting root from ufs:/dev/ad0s1a > > > > > > and hangs -- only a physical reset works. However, breaking into the > > > debugger, and running a trace, I get (hand-copied): > > Hmm

Re: My problems with GEOM

In the last episode (Oct 06), Robert Watson said: > On Sun, 6 Oct 2002, Seth Hieronymus wrote: > > Thanks for the pointers. Here's the trace 1: > > mi_switch(c0bb9988,14,c01bbe60,c0bb98f0,1) at mi_switch+0x290 > > msleep(c03778a0,0,68,c03153d7,14) at msleep+0x477 > > g_waitidle(1,c0314e10,c18f288

how to build native jdk13 with hotspot under current?

as title& thanks any help To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

RE: tcsh hang in -current (kse bug?)

On 06-Oct-2002 (23:10:55/GMT) Kris Kennaway wrote: > Can anyone else reproduce this in tcsh? > rpcgen -s `perl -e 'print "a"x5'` > Word too long. Mee too mail. Using {50,500,5000} works, hang only with 5 (not tested with others numbers). Doing: # echo {your_command} print only "word to

Re: My problems with GEOM

On Sun, 6 Oct 2002, Seth Hieronymus wrote: > Thanks for the pointers. Here's the trace 1: > mi_switch(c0bb9988,14,c01bbe60,c0bb98f0,1) at mi_switch+0x290 > msleep(c03778a0,0,68,c03153d7,14) at msleep+0x477 > g_waitidle(1,c0314e10,c18f2885,c031bd64,c0b8dc20) at g_waitidle+0x8b > g_dev_clone(0,c1

Re: My problems with GEOM

do a 'ps' in ddb On Sun, 6 Oct 2002, Seth Hieronymus wrote: > Hello, > > After recompiling a kernel after the GEOM transition, my boot gets as > far as: > > Initializing GEOMetry subsystem > ad0: 28629MB [58168/16/63] at ata0-master UDMA33 > acd0: CDROM at ata1-master PIO4 > afd0: 239MB [2

ccd performance (was: [ GEOM tests ] vinum drives lost)

On Sunday, 6 October 2002 at 11:30:16 -0700, Matthew Dillon wrote: > Yes, ccd is fairly light weight. 'man tuning' and 'man ccd' has > a lot of information on how to use it. I generally recommend > using a stripe size of 1152 for multitasking loads. Sectors? Why particularly this

Re: My problems with GEOM

From: "Robert Watson" >On Sun, 6 Oct 2002, Carl Schmidt wrote: > > > Mounting root from ufs:/dev/ad0s1a > > > > and hangs -- only a physical reset works. However, breaking into the > > debugger, and running a trace, I get (hand-copied): > >Hmm. I actually ran into this problem on some diskless b

Re: can recover /usr/src/include diretories

In the last episode (Oct 06), suken woo said: > delete the /usr/src/include dir falsely , can it recover. buildworld > again ,but allways get *.h not found. faint. If you used cvsup to update your tree, just run cvsup again and it'll fetch the files over. If you used cvs, run "cd /usr/src ; cvs

Re: kernel panic trying to utilize a da(4)/umass(4) device withohci(4)

Hi. See pr kern/43462. Happens to me. I wish it would get fixed :) On Sun, 6 Oct 2002, Brian Fundakowski Feldman wrote: > I can't get more info because crash dumps don't work when this happens, but > for what it's worth, here's a traceback which shows what happens when I > attempt to use my da0:

Re: My problems with GEOM

On Sun, 6 Oct 2002, Carl Schmidt wrote: > > Mounting root from ufs:/dev/ad0s1a > > > > and hangs -- only a physical reset works. However, breaking into the > > debugger, and running a trace, I get (hand-copied): Hmm. I actually ran into this problem on some diskless booting boxes, but it wen

Re: kernel panic from vinum during 'restore'

On Sunday, 6 October 2002 at 18:25:08 -0400, Robert Watson wrote: > > On Sun, 6 Oct 2002, fergus wrote: > >> i have a crash dump for this now if anyone is interested. it's not >> exactly the same trace as it seems to originate from a VOP_LINK request >> this time but i guess it's the same proble

Re: stdlib.h:57: redeclaration of C++ built-in type `wchar_t'

Hanspeter Roth wrote: > Hello, > > when running buildworld I get: > > ===> gnu/usr.bin/gperf/doc > c++ -O -pipe-D__FBSDID=__RCSID >-I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf >-c /usr/src/contrib/gperf/src/bool-array.cc > c++ -O -pipe-D__FBSDI

Re: stdlib.h:57: redeclaration of C++ built-in type `wchar_t'

Hanspeter Roth wrote: > /usr/include/stdlib.h:57: redeclaration of C++ built-in type `wchar_t' > *** Error code 1 > > #ifdef _BSD_SIZE_T_ > typedef _BSD_SIZE_T_size_t; > #undef _BSD_SIZE_T_ > > How can I resolve this redeclaration? You failed to delete the old header files when you upgrad

Re: tcsh hang in -current (kse bug?)

Michael Nottebrock wrote: > Kris Kennaway wrote: > >> Can anyone else reproduce this in tcsh? > > > Yup. My -CURRENT here is two weeks old. ... reproducible in -STABLE, too. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg44136/pgp0.pgp Description: PGP sig

Re: My problems with GEOM

On Sun, Oct 06, 2002 at 05:08:00PM -0600, Seth Hieronymus wrote: > Hello, > > After recompiling a kernel after the GEOM transition, my boot gets as > far as: > > Initializing GEOMetry subsystem > ad0: 28629MB [58168/16/63] at ata0-master UDMA33 > acd0: CDROM at ata1-master PIO4 > afd0: 239MB

Re: tcsh hang in -current (kse bug?)

On Mon, 2002-10-07 at 01:10, Kris Kennaway wrote: > Can anyone else reproduce this in tcsh? > > rpcgen -s `perl -e 'print "a"x5'` > Word too long. > > And then tcsh will hang in a state unresponsive to signals. > > Kris > Hangs here, too. (this is stable!) FreeBSD klamath.ankon.homeip.ne

kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

I can't get more info because crash dumps don't work when this happens, but for what it's worth, here's a traceback which shows what happens when I attempt to use my da0: Removable Direct Access SCSI-2 device on an OHCI-based controller. This was working just a few days ago with a UHCI contro

Re: tcsh hang in -current (kse bug?)

Kris Kennaway wrote: > Can anyone else reproduce this in tcsh? Yup. My -CURRENT here is two weeks old. -- Michael Nottebrock | After years of using email, I'm still to dumb to hit Reply-All | msg44132/pgp0.pgp Description: PGP signature

tcsh hang in -current (kse bug?)

Can anyone else reproduce this in tcsh? rpcgen -s `perl -e 'print "a"x5'` Word too long. And then tcsh will hang in a state unresponsive to signals. Kris msg44131/pgp0.pgp Description: PGP signature

My problems with GEOM

Hello, After recompiling a kernel after the GEOM transition, my boot gets as far as: Initializing GEOMetry subsystem ad0: 28629MB [58168/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master PIO4 afd0: 239MB [239/64/32] at ata1-slave PIO3 Mounting root from ufs:/dev/ad0s1a and hangs -- onl

Re: The official "GEOM is in the tree" speech.

On Sun, 6 Oct 2002, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Alexander Leiding > er writes: > > >> 2. Somebody to keep it updated, follow up on tasks, etc etc. > > > >No, you have a task? Commit it. Someone takes the task? The committer > >which inserted the task should update i

alpha tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

stdlib.h:57: redeclaration of C++ built-in type `wchar_t'

Hello, when running buildworld I get: ===> gnu/usr.bin/gperf/doc c++ -O -pipe-D__FBSDID=__RCSID -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/contrib/gperf/src/bool-array.cc c++ -O -pipe-D__FBSDID=__RCSID -I/usr/src/gnu/usr.bin/gper

Re: kernel panic from vinum during 'restore'

On Sun, 6 Oct 2002, fergus wrote: > i have a crash dump for this now if anyone is interested. it's not > exactly the same trace as it seems to originate from a VOP_LINK request > this time but i guess it's the same problem. To be honest, it sounds like something is simply leaking kernel memory

Re: GEOM and SCSI-cd: mount not working any more / fix

Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Michael Class writes: > > >>>Can I get you to insert printfs like the one below all places >>>in vfs_mount.c and cd9660_vfsops.c where you see it using EINVAL >>>and try to find out which particular one it is ? >>> >>> printf("EINVAL

Re: Any users of matcd(4), mcd(4), or scd(4)?

On Thu, 3 Oct 2002, John Baldwin wrote: > Are there any users who use the matcd(4), mcd(4) or scd(4) drivers? I have at least 20 Panasonic 562/563s still in service in CD-ROM server machines. They still run older versions of FreeBSD because the last time I tried to update it the matcd driver d

Re: devfs oddity?

< said: > Has our CDROM driver ever supported multiple ISO filesystems per CD? Has > it supported multi-session CDROMs? The notion of partitions on CDROMs is > a little ambiguous. I'm hoping that GEOM can improve this. Sort of, but it often gets things wrong for the more interesting CD-ROM ty

Broken ata/ad%d.

Hi After cleaning out some OBE(?) patches, the closest I can get my Libretto 110CT to booting a really recent CURRENT is terminated by a panic. Hand-written backtrace is: Debugger() panic() acpi_read_ivar() ata_dma_init() ad_attach() ata_boot_attach() run_interrupt_driven_config_hooks() mi_star

GEOM benchmarks

A number of people have asked me for performance data on GEOM already, so here are up-to-the-minute relevant numbers: On my test machine (see the details below), a 512 bytes read from the initialized first sector on a malloc-backed md(4) device takes 21.7 microsecond, for both "mdX", "mdXs1" and

suggested patch for small user ppp annoyance

Once in a while, user ppp is killed rather abruptly and it leaves a diagnostic socket behind, which blocks the creation of a diagnostic socket after reboot. Anyway, I propose adding another variable to rc.conf, something along the lines of the three patches here. The default value for pppctl_s

Re: GEOM and SCSI-cd: mount not working any more

On Sun, Oct 06, 2002 at 06:20:12PM +0200, Poul-Henning Kamp wrote: > Can I get you to insert printfs like the one below all places > in vfs_mount.c and cd9660_vfsops.c where you see it using EINVAL > and try to find out which particular one it is ? > > printf("EINVAL HERE %s %d\n", __FILE__

ACPI s3 suspend/resume and video

I've just gotten a new desktop (P4, Intel D845EBG2 motherboard, ATI Rage 128 Pro AGP 4x video), and I'm thrilled that I can suspend it to ACPI s3. That's awesome! However, when I resume I have no video. Is this a known bug? Is there anything I can do about it? Thanks for your help, Drew Co

Re: [ GEOM tests ] vinum drives lost

Yes, ccd is fairly light weight. 'man tuning' and 'man ccd' has a lot of information on how to use it. I generally recommend using a stripe size of 1152 for multitasking loads. Only use a small/tiny stripe size if you need single-tasking sequential performance (and even then

Re: SSE

Daniel Eischen writes: > [ CC list trimmed ] > > On Sat, 5 Oct 2002, Andrew Gallatin wrote: > > > > Daniel Eischen writes: > > > > > > > > 1.539 works. 1.540 crashes. The failure mode is: > > > > > > Bruce and I had a miscommunication over the setting of a flag. > > > It turns

Re: kernel panic from vinum during 'restore'

i have a crash dump for this now if anyone is interested. it's not exactly the same trace as it seems to originate from a VOP_LINK request this time but i guess it's the same problem. On 06.10-16:02, n0g0013 wrote: > On 05.10-22:16, n0g0013 wrote: > > don't currently have the kernel trace for th

Re: GEOM and SCSI-cd: mount not working any more

In message <[EMAIL PROTECTED]>, Michael Class writes: >Hello, > >just another input for a current system (with GEOM): now it seems >inpossible for me to mount a SCSI-CD > >pc-micha:/# mount -t cd9660 /dev/cd0 /cdrom >cd9660: /dev/cd0: Invalid argument Presumably this is not a GEOM problem, but r

ACPI == instant panic

Enabling acpi leads to an instant panic during boot. The panic so early that I can't get a dump and the machine does not have serial console. The motherboard is an ASUS A7V-133. Here's a hand written panic message Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986

GEOM and SCSI-cd: mount not working any more

Hello, just another input for a current system (with GEOM): now it seems inpossible for me to mount a SCSI-CD pc-micha:/# mount -t cd9660 /dev/cd0 /cdrom cd9660: /dev/cd0: Invalid argument Th system has two SCSI-CD-drives (a DVD and a CD-Burner) both have the same behavior. The CD is known to

Re: devfs oddity?

> >> > In message <[EMAIL PROTECTED]>, Steve Kargl w > >> > rites: > >> > >root[208] cdcontrol play > >> > >cdcontrol: no CD device name specified, defaulting to /dev/cd0c > >> > >cdcontrol: /dev/cd0cc: No such file or directory > >> > > > >> > >Why is an extra "c" appended to cd0c? > > > >The fir

Re: GEOM problems?

On 06.10-06:43, walt wrote: > Okay, next problem(?). Disklabel with and without the -r flag: don't know if it is a problem or not but i found that doing a null edit on the disk to make GEOM rewrite it's information to the disk eliminated the messages. -- t t z msg4

Re: vnode locking screwed up in src/sys/ufs/ffs/ffs_snapshot.c:ffs_snapshot()

On Sat, Oct 05, 2002 at 11:46:45AM -0400, Brian Fundakowski Feldman wrote: > I got a crash today because "xvp" did not have an interlock when the > call was made to vn_lock(LK_INTERLOCK): > 407 if (snapdebug) > 408 vprint("ffs_snapshot: busy vnode", xvp); > 409

Re: kernel panic from vinum during 'restore'

On 05.10-22:16, n0g0013 wrote: > don't currently have the kernel trace for this (i'm rebuilding to get > one) and the dump's not making it to disk. perhaps someone else could > try and verify in the mean time. don't know if this is related to Mikhail Teterin's post a few hours ago but i have the

lpt ppbus ppi modules

trying to build the current kernel as modular as possible but if i remove the 'ppbus' and 'lpt' from the kernel config the modules fail (the 'ppc' is still there of course). should these build as KLMs ? -- t t z msg44107/pgp0.pgp Description: PGP signature

Re: make linux_base error during rpm

On Sat, 5 Oct 2002 21:28:32 -0700 Adam Kranzel <[EMAIL PROTECTED]> wrote: > On Sat, 5 Oct 2002 21:27:07 -0700 > Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > On Sat, Oct 05, 2002 at 08:36:48PM -0700, Adam Kranzel wrote: > > > > > It has been committed, and makes it build just fine for me... > >

Re: GEOM problems?

In message <[EMAIL PROTECTED]>, walt writes: >#disklabel -r ad2s2 >#size offsetfstype [fsize bsize bps/cpg] > a: 17207240 77738354.2BSD0 0 0 # (Cyl. 483*- 1554*) >#disklabel ad2s2 >#size offsetfstype [fsize bsize bps/cpg] > a: 172

Re: GEOM problems?

Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, walt writes: >>#disklabel ad0 >>disklabel: ioctl DIOCGDINFO: Operation not supported by device > ad0 does not have a disklabel. Okay, next problem(?). Disklabel with and without the -r flag: #disklabel -r ad2s2 #size offset

Re: The official "GEOM is in the tree" speech.

In message <[EMAIL PROTECTED]>, Alexander Leiding er writes: >> 2. Somebody to keep it updated, follow up on tasks, etc etc. > >No, you have a task? Commit it. Someone takes the task? The committer >which inserted the task should update it. This was (is ?) the priciple behind our fantastic colle

Re: The official "GEOM is in the tree" speech.

On Sun, 06 Oct 2002 14:38:01 +0200 Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > >We're at the point where a public page with "things which need a > >volunteer" would be nice, aren't we (yes, something like your JKH > >page but not only for kernel parts)? > > Well, for that to happen it takes t

Re: The official "GEOM is in the tree" speech.

In message <[EMAIL PROTECTED]>, Alexander Leiding er writes: >On Sat, 05 Oct 2002 22:39:03 +0200 >Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > >> "One hand for your own code, and one hand for the infrastructure". >> >> We have several areas of the kernel which is in disrepair, the >> worst is b

Re: The official "GEOM is in the tree" speech.

On Sat, 05 Oct 2002 22:39:03 +0200 Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > "One hand for your own code, and one hand for the infrastructure". > > We have several areas of the kernel which is in disrepair, the > worst is buf/VM, but there are others as well. > > We also have people who ar

Re: devfs oddity?

In message <[EMAIL PROTECTED]>, "Matthew N. Dodd" w rites: >On Sun, 6 Oct 2002, David O'Brien wrote: >> Since when hasn't it been standard on BSD based systems? Other than >> recently on FreeBSD, all other BSD systems I've used, the "c" partition >> has been necessary when wanting to operate on t

alpha tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: panic: kmem_malloc(4096): kmem_map too small

On 06.10-03:06, Mikhail Teterin wrote: > this machine has a total of 512Mb of RAM, and no swap. > No X was running. Just ``cvs update''-ing. running vinum ? i am getting this consistently with vinum (but am taking an age to rebuild. did you get a backtrace ? . . . to vfs allocations . . . and

Re: devfs oddity?

On Sun, 6 Oct 2002, David O'Brien wrote: > Since when hasn't it been standard on BSD based systems? Other than > recently on FreeBSD, all other BSD systems I've used, the "c" partition > has been necessary when wanting to operate on the entire disk. Has our CDROM driver ever supported multiple I

Re: devfs oddity?

On Sun, Oct 06, 2002 at 08:29:52AM +0200, Poul-Henning Kamp wrote: > >The first "c" is part of the standard name for the whole of a (labelled) > >disk device. > > It's not any "standard name". It is a convention used on a minority > of UNIX platforms out there, and it is certainly not "standard"