Re: recent apm changes
In message <[EMAIL PROTECTED]> Eric Hodel writes: : I've got a -current machine (no cvsups in a few months) that wakes up : immediately after suspending. (sleeps 0 seconds) Hmmm, some laptops will wakeup on a keyboard interrupt. The interrupt that is waking you up may be the key up from the return you hit to make the event happen. PAO has a small sleep in the apm driver, while -current didn't the last time I looked. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
anoncvs
I have anoncvs working now (straight anoncvs, not pserver): setenv CVSROOT [EMAIL PROTECTED]:/cvs cvs get [some path] I wasn't aware of anyone using pserver method. Any users of anoncvs, could you please test this for me? IMPORTANT!! Reply directly to me, anyone scragging the list will be anathematized!! +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
On Fri, Aug 06, 1999 at 11:49:33PM +0900, Kazutaka YOKOTA wrote: > > >> >At this point we must still be in freebsd xinit, then XF86_VMware(linux > >> >server) get started. I'm running a linux X server under freebsd. Under > >> >3.2R all I had to do was change the symlink for X to point to XF86_VMware, > >> >under -current /dev/tty0 can't be found. > >> > > >> >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the > >> >kernel device struct changed under -current? > >> > > >> >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave > >> ~ ~ > >> Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. > >> > >> Notice ttyv*, not ttyp* > >> ~ ~ > >Hello > > > > I had tried it both ways, when I said having them symlinked to > >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I > >use ttyp0 and ttyp4 respectfully. > > I don't think ttyp* will work. I don't know who suggested it to you. > I have never run Linux X server binaries on FreeBSD, but, I can assure > you that ttyp* won't work. I dont know what tty0 is in linux - but why should vmware need a virtual terminal? > > The ttyp* refers to the "pseudo" tty. The Linux X server opens tty0 > and tty4 which are "virtual terminals" in Linux. Virtual terminals > are named ttyv* in FreeBSD. If the Linux X server are ever made to > work in FreeBSD, it must be ttyv* which the X server should be fooled > to access. > > VT_ACTIVATE, VT_WAITACTIVE and VT_GETMODE ioctls are valid only for > virtual terminals ttyv* and certainly result in error for pseudo ttys. > > I suspect that the fatal trap you are seeing has little to do with > ttyv* symlinks and the real culprit lies somewhere else. > I agree - even with the maybe wrong symlinks to ttyp* I was able to get the vmware window. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
On Fri, Aug 06, 1999 at 01:07:13PM +0200, Marcel Moolenaar wrote: > Bernd Walter wrote: > > > It needs ttyp0 as tty0 and so on. > > I tried it myself under current and got the X11 window. > > but it complained that it can't find /proc/cpuinfo. > > I never beleaved that it would work after that. > > I assume you didn't try to make a regular file called cpuinfo in > /compat/linux/proc with the proper contents? Damnit no - I was afraid that it was searching in /proc ... I will try it on monday. Thanks for the info and file contents. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMP and threads...
Why haven't changes like these been committed? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Russell L. Carter > Sent: Friday, August 06, 1999 12:10 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: SMP and threads... > > > > |"David E. Cross" <[EMAIL PROTECTED]> wrote: > |>I have a threaded appilcation that is only running on one > processor. > |>I remember there was discussion about this in the past, and > there was a > |>solution, I think it involved a patch. > |> > |>Any pointers? > | > |http://lt.tar.com > > And don't be turned off by the "outdated" tunnel Richard stuck > up there, delete the two references to deferred signals in > the libc_r code that gets copied over into the port. > Then you get a thread implementation that still works better > than libc_r for things like TAO. (Although I haven't had > a chance to rerun the tests with the libc_r changes this > week). > > Russell > > | > |Tony. > |-- > |f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED]e pluribus unix > | > | > |To Unsubscribe: send mail to [EMAIL PROTECTED] > |with "unsubscribe freebsd-current" in the body of the message > | > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP and threads...
|"David E. Cross" <[EMAIL PROTECTED]> wrote: |>I have a threaded appilcation that is only running on one processor. |>I remember there was discussion about this in the past, and there was a |>solution, I think it involved a patch. |> |>Any pointers? | |http://lt.tar.com And don't be turned off by the "outdated" tunnel Richard stuck up there, delete the two references to deferred signals in the libc_r code that gets copied over into the port. Then you get a thread implementation that still works better than libc_r for things like TAO. (Although I haven't had a chance to rerun the tests with the libc_r changes this week). Russell | |Tony. |-- |f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED]e pluribus unix | | |To Unsubscribe: send mail to [EMAIL PROTECTED] |with "unsubscribe freebsd-current" in the body of the message | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with last src/sys/pccard changes
It was my fault :( Now it's working. Thanks a lot! Val --- Warner Losh <[EMAIL PROTECTED]> wrote: > You may need to do a make includes as well to get > the proper include > files (or if you are afraid of that, you can copy > src/sys/pccard/cardinfo.h to > /usr/include/pccard/cardinfo.h) > > Warner > === Valentin S. Chopov 2301 West Bethel Ave., #53 Muncie, IN 47304-2112 Phone/Fax: (765)-214-0504 E-Mail: [EMAIL PROTECTED] URL:http://profiles.yahoo.com/valsho _ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with last src/sys/pccard changes
In message <[EMAIL PROTECTED]> "Valentin S. Chopov" writes: : I wrote, I cvsuped both src/sys/pccard and : src/usr.sbin/pccard and compiled and installed of : course. Problem appears with new kernel code and new : pccardd code, but is is OK with old kernel code an new : pccardd code. But I already wrote this... : BTW , my notebook is ISA only, w/o compiled PCI code. You may need to do a make includes as well to get the proper include files (or if you are afraid of that, you can copy src/sys/pccard/cardinfo.h to /usr/include/pccard/cardinfo.h) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote: > >Hello > > > > I had tried it both ways, when I said having them symlinked to > >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I > >use ttyp0 and ttyp4 respectfully. > > I don't think ttyp* will work. I don't know who suggested it to you. > I have never run Linux X server binaries on FreeBSD, but, I can assure > you that ttyp* won't work. > > The ttyp* refers to the "pseudo" tty. The Linux X server opens tty0 > and tty4 which are "virtual terminals" in Linux. Virtual terminals > are named ttyv* in FreeBSD. If the Linux X server are ever made to > work in FreeBSD, it must be ttyv* which the X server should be fooled > to access. > > VT_ACTIVATE, VT_WAITACTIVE and VT_GETMODE ioctls are valid only for > virtual terminals ttyv* and certainly result in error for pseudo ttys. > > I suspect that the fatal trap you are seeing has little to do with > ttyv* symlinks and the real culprit lies somewhere else. > > Kazu Hello Kazu This I understand, as I believe it's somewhere else in the emulation changes between 3.2R and -current. The devices are what we see as the result of the error. Major changes I see to the emulation code from 3.2 to -current: 1. A number of ioctl and VT_ changes 2. divorce dev_t from major|minor bitmap. I would expect one of these change is causing the problem. Thanks again, Eric To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
>> >At this point we must still be in freebsd xinit, then XF86_VMware(linux >> >server) get started. I'm running a linux X server under freebsd. Under >> >3.2R all I had to do was change the symlink for X to point to XF86_VMware, >> >under -current /dev/tty0 can't be found. >> > >> >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the >> >kernel device struct changed under -current? >> > >> >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave >> ~ ~ >> Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. >> >> Notice ttyv*, not ttyp* >> ~ ~ >Hello > > I had tried it both ways, when I said having them symlinked to >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I >use ttyp0 and ttyp4 respectfully. I don't think ttyp* will work. I don't know who suggested it to you. I have never run Linux X server binaries on FreeBSD, but, I can assure you that ttyp* won't work. The ttyp* refers to the "pseudo" tty. The Linux X server opens tty0 and tty4 which are "virtual terminals" in Linux. Virtual terminals are named ttyv* in FreeBSD. If the Linux X server are ever made to work in FreeBSD, it must be ttyv* which the X server should be fooled to access. VT_ACTIVATE, VT_WAITACTIVE and VT_GETMODE ioctls are valid only for virtual terminals ttyv* and certainly result in error for pseudo ttys. I suspect that the fatal trap you are seeing has little to do with ttyv* symlinks and the real culprit lies somewhere else. Kazu >Are you running a linux Xserver under freebsd, XF86_VMware? Why arn't >these needed under emulation with freebsd 3.2R? This is the main thing >I'm looking for in the code. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP and threads...
"David E. Cross" <[EMAIL PROTECTED]> wrote: >I have a threaded appilcation that is only running on one processor. >I remember there was discussion about this in the past, and there was a >solution, I think it involved a patch. > >Any pointers? http://lt.tar.com Tony. -- f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED]e pluribus unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote: > > >At this point we must still be in freebsd xinit, then XF86_VMware(linux > >server) get started. I'm running a linux X server under freebsd. Under > >3.2R all I had to do was change the symlink for X to point to XF86_VMware, > >under -current /dev/tty0 can't be found. > > > >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the > >kernel device struct changed under -current? > > > >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave > ~ ~ > Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. > > Notice ttyv*, not ttyp* > ~ ~ Hello I had tried it both ways, when I said having them symlinked to ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I use ttyp0 and ttyp4 respectfully. Are you running a linux Xserver under freebsd, XF86_VMware? Why arn't these needed under emulation with freebsd 3.2R? This is the main thing I'm looking for in the code. Thanks, Eric > Kazu > > >me errors with VT_ACTIVE, VT_WAITACTIVE, VT_GETMODE. I should have to > >make these symlinks they should be handled under emulation, just like > >3.2R. > Eric Chet -> [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA Kenpo JuJitsu the Ultimate in Self Defense, Tai Chi for Life cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
>At this point we must still be in freebsd xinit, then XF86_VMware(linux >server) get started. I'm running a linux X server under freebsd. Under >3.2R all I had to do was change the symlink for X to point to XF86_VMware, >under -current /dev/tty0 can't be found. > >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the >kernel device struct changed under -current? > >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave ~ ~ Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. Notice ttyv*, not ttyp* ~ ~ Kazu >me errors with VT_ACTIVE, VT_WAITACTIVE, VT_GETMODE. I should have to >make these symlinks they should be handled under emulation, just like >3.2R. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
On Fri, 6 Aug 1999, Marcel Moolenaar wrote:
> "Eric J. Chet" wrote:
> >
> > On Wed, 4 Aug 1999, Bernd Walter wrote:
> >
> > > It needs ttyp0 as tty0 and so on.
> > > I tried it myself under current and got the X11 window.
> > > but it complained that it can't find /proc/cpuinfo.
> > > I never beleaved that it would work after that.
> >
> > Hello
> > It should work, I used it under fbsd-3.2R for over two weeks with
> > X11 without any problems. I guess I might have to down grade to 3.2R.
>
> >From the X server truss file:
> .
> .
> .
> syscall open("/var/run/ld-elf.so.hints",0,05001316750)
> returns 3 (0x3)
> .
> .
> .
> syscall open("/usr/lib/libc.so.3",0,05001316750)
> returns 3 (0x3)
> .
> .
> .
>
> You say it's a Linux binary. What is it doing with these FreeBSD
> files/libraries then?
>
At this point we must still be in freebsd xinit, then XF86_VMware(linux
server) get started. I'm running a linux X server under freebsd. Under
3.2R all I had to do was change the symlink for X to point to XF86_VMware,
under -current /dev/tty0 can't be found.
Where was linux "/dev/tty0" coming from under emulation in 3.2R, the
kernel device struct changed under -current?
I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave
me errors with VT_ACTIVE, VT_WAITACTIVE, VT_GETMODE. I should have to
make these symlinks they should be handled under emulation, just like
3.2R.
BTW: Another release of vmware for NT is out today.
Thanks for your help,
ejc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: problem with last src/sys/pccard changes
I wrote, I cvsuped both src/sys/pccard and src/usr.sbin/pccard and compiled and installed of course. Problem appears with new kernel code and new pccardd code, but is is OK with old kernel code an new pccardd code. But I already wrote this... BTW , my notebook is ISA only, w/o compiled PCI code. Val --- Warner Losh <[EMAIL PROTECTED]> wrote: > In message > <[EMAIL PROTECTED]> > "Valentin S. Chopov" writes: > : > : After cvsup of src/sys/pccard and > src/usr.sbin/pccard > : from Aug 1, PCMCIA net card is not working. Te > message > : from pccardd is : > : > : Aug 3 02:28:42 valsho pccardd[256]: driver > allocation > : failed for IC-CARD(IC-CARD): Inappropriate ioctl > for > : device > : > : Also new pccardd is working with old kernel > code... > : So, may be te problem is in src/sys/pccard. > > Read UPDATING. You must recompile pccardd for the > new kernel. The > ioctl changed to pass the length of the io port > range into the kernel > rather than just the bottom end of the range. > > Warner > === Valentin S. Chopov 2301 West Bethel Ave., #53 Muncie, IN 47304-2112 Phone/Fax: (765)-214-0504 E-Mail: [EMAIL PROTECTED] URL:http://profiles.yahoo.com/valsho _ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMware X11 and -current
Bernd Walter wrote: > It needs ttyp0 as tty0 and so on. > I tried it myself under current and got the X11 window. > but it complained that it can't find /proc/cpuinfo. > I never beleaved that it would work after that. I assume you didn't try to make a regular file called cpuinfo in /compat/linux/proc with the proper contents? An example is attached. -- Marcel Moolenaar mailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 processor : 0 vendor_id : AuthenticAMD cpu family : 4 model : 14 model name : Am5x86-WT stepping: 4 fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu bogomips: 65.74
Re: VMware X11 and -current
"Eric J. Chet" wrote:
>
> On Wed, 4 Aug 1999, Bernd Walter wrote:
>
> > It needs ttyp0 as tty0 and so on.
> > I tried it myself under current and got the X11 window.
> > but it complained that it can't find /proc/cpuinfo.
> > I never beleaved that it would work after that.
>
> Hello
> It should work, I used it under fbsd-3.2R for over two weeks with
> X11 without any problems. I guess I might have to down grade to 3.2R.
>From the X server truss file:
.
.
.
syscall open("/var/run/ld-elf.so.hints",0,05001316750)
returns 3 (0x3)
.
.
.
syscall open("/usr/lib/libc.so.3",0,05001316750)
returns 3 (0x3)
.
.
.
You say it's a Linux binary. What is it doing with these FreeBSD
files/libraries then?
--
Marcel Moolenaar mailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
Amsterdam, The Netherlands tel: +31 20 4200655
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Promise/IDE (and NICs too!)
On Thu, 5 Aug 1999, Soren Schmidt wrote: > Thats the promise controller, try the ata driver instead an use the > following patch, let me know if it works... The patch applied cleanly... I still get: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Aug 6 01:12:13 PDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/SNAFU Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 299942752 Hz CPU: Pentium II (299.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127594496 (124604K bytes) Pentium Pro MTRR support enabled Probing for PnP devices: CSN 1 Vendor ID: CTL00c7 [0xc7008c0e] Serial 0x1c422c08 Comp ID: PNPb02f [0x2fb0d041] npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 9 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: irq 11 at device 7.2 on pci0 chip2: at device 7.3 on pci0 pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9 pn0: <82c169 PNIC 10/100BaseTX> irq 11 at device 16.0 on pci0 pn0: Ethernet address: 00:c0:f0:48:18:51 pn0: autoneg complete, link status good (half-duplex, 10Mbps) isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 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: configured irq 3 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ata1: unwanted interrupt 1 status = ff ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata1 as master acd0: drive speed 4133 - 4134KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s1a I'm seeing the onboard controller and its devices, but nothing from the Promise card. Out of curiosity, is this all I really need in my kernel config: controller ata0 device atadisk0# ATA disk drives device atapicd0# ATAPI CDROM drives Just double checking... although I must admit, I've toyed with every permutation imaginable. Oh, on a side note, the NIC's been changed from xl0 to pn0 (yes, I know, both are crapy cards - someday maybe an Intel will fall into my poor lap)... reason is my network connection seems to 'come and go'. By that I mean I'll be fine (IRC, mail, ping, etc.) one minute, then *boom* I loose all connectivity - can't even ping my gateway... This happened with xl0, so I tried pn0... still happens... is my DSL provider to blame, or is something up with -current? Traceroutes from outside boxes to me during these times die at my box, not within my provider's network... -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: "prepdisk"
>>>It differs in that you can boot from the disk afterwards with my script, >>>you cant with disklabel -w wd0 auto. > >>That may be because you forgot to supply the -r or -B args to disklabel, >>[...] > >No it is because the fool BIOS belives the 5 in the MBR. This problem can be avoided by using fdisk to install a proper MBR before running disklabel. disklabel will then avoid writing to the MBR. fdisk even has reasonable defaults, but not what you want. Its default seems to be to create a proper MBR with slice 4 starting at sector 1 (0-based) and having size (size of disk rounded down to a fdisk's idea of a cylinder boundary) - 1. You want start 0 and size (size of disk). Of course, BIOSes could reasonably consider this partition as garbage since it overlaps the MBR. Similarly for partitions with start 1, since they overlap the first track. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
