Re: continuous backup solution for FreeBSD
Mike Meyer writes: > On Mon, 6 Oct 2008 14:24:32 -0700 > George Hartzell <[EMAIL PROTECTED]> wrote: > > There were a couple of threads about using kqueue or other FreeBSD > > tools to build something like Mac OS X's Time Machine. R1soft's > > software sounds very similar. > > Time machine doesn't do continuous backups, it does them once an hour > or so. People have built similar systems on top of rsync; I did it on > top of zfs (turned out to be to fragile, though). You then just need a > spiffy GUI for wondering through the backups. On the other hand Time Machine does take advantage of a kernel based mechanism that watches file activity and does its best to take advantage of that information to avoid scanning the filesystem when it does a backup. That's the context of the message thread that I pointed to (again, for completeness) http://lists.freebsd.org/pipermail/freebsd-hackers/2008-June/024730.html The thread seemed relevant given the context of backup systems that watch filesystem io. g. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: continuous backup solution for FreeBSD
Bakul Shah writes: > On Mon, 06 Oct 2008 18:09:06 +0300 "Vlad GALU" <[EMAIL PROTECTED]> wrote: > > On Mon, Oct 6, 2008 at 5:33 PM, Evren Yurtesen <[EMAIL PROTECTED]> wrote: > > > Bob Bishop wrote: > > > > > >>> Does anybody have free time and skills to give a hand? Please see: > > >>> http://forum.r1soft.com/showpost.php?p=3414&postcount=9 > > >> > > >> Should be possible to do this with a geom(4) class? > > >> > > > > > > I am not saying it is impossible. They just need somebody to put them to > > > right track I guess. I personally cant do that. It would be nice if > > > somebod > > y > > > who has knowledge in this area contacts r1soft. At the very least r1soft > > > seems to be willing to communicate on this issue. > > > > > > Continuous backups as well as bare-metal-restore seem to be a key feature > > > for many hosters. FreeBSD is loosing users because of this issue. > > > >gmirror+ggate come to mind as a nifty solution ... > > My guess is these guys do something simpler like keep keep > track of changed blocks since the last backup and > periodically dump those blocks to a server. This is good > enough for backups (but not mirroring) and it has low memory > overhead (1 or 2 bits per block), lower network overhead than > remote mirroring (you send a block at most once every sync > interval), and a tiny loss of performance (over no backups). > May be someone ought to do a garchive device! There were a couple of threads about using kqueue or other FreeBSD tools to build something like Mac OS X's Time Machine. R1soft's software sounds very similar. The conclusion seemed to be that it'd be doable. Here's a pointer to the start of one of the threads. http://lists.freebsd.org/pipermail/freebsd-hackers/2008-June/024730.html g. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3D for AMD64 (was Re: Lack of Flash support is no longer acceptable. Bounty established...)
Mike Meyer writes: > [...] > I'm not sure those are the drivers Theierry wants. The proprietary > driver was called fglrx, not "radeon" or "radeonhd". Those two drivers > have been in the X open source trees for quite a while now. I first > started using the radeon driver on amd64 in late 2006. The versions I > have checked out for FreeBSD are documented as > > Radeonhd has no 2d or 3d acceleration. > Radeon has both, but only works for older cards. > > That is also on 7-stable, but I haven't updated the sources in a > while. radeonhd does offer 2d acceleration, and 3-d is a work-in-progress, with existing support for some of the newish cards. You can get more info here: http://www.x.org/wiki/radeonhd Actually, the entire thing is still a work-in-progress, but the community is supportive. If you try to build from the git sources, you'll need to have the devel/xorg-macros port/package installed for the autogen.sh step to work. g. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BDB corrupt
Kurt J. Lidl writes: > On Wed, May 14, 2008 at 12:25:16AM -0700, Garrett Cooper wrote: > > Most of the complaints about other DBs is licensing related, but SQLite's > > complaint was also the fact that the past stability record was a bit rocky. > > One other thing to watch for in SQLite is the lack of atomicity > in updates. It's not ACID, just like BDB 1.8x isn't ACID. > > Without a write-ahead log, you cannot be sure that the data written > actually made it to stable storage, and as such, you cannot be sure > that your database didn't get corrupted when the process stops in a > non-optimal way. In what way is SQLite not atomic? The documentation, Atomic Commit In SQLite, suggests that it is: http://www.sqlite.org/atomiccommit.html I don't know that it supports fully ACID (atomic, consist, isolated, durable) transactions or how it handles the various SQL standard transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) but I believe that updates are atomic and that it does as well as any db (in the face of lying synch. operations, etc...) to handle "non-optimal" stops. g. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: powerd feature proposal...(and a small problem)
Evren Yurtesen writes: > Hi, > > The problem is with an 8 processor system. If a process is not threaded and > starts using 100% cpu time of a single processor, the system still shows > over > 80% idle. Whereas this single process works really slow if the system is > already > at the slowest speed. Is there a simple way to fix this problem? It is not > so > big problem but sometimes it is quite annoying :) > [...] I edited /etc/rc.d/powerd and just after the command line I added command_arg="-r 84 -i 93" [values determined by trial and error] g. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Picture CDs ?
Zera William Holladay writes: > > > On Mon, 10 Jan 2005, Pedro F. Giffuni wrote: > > > It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is pretty > > weird as Windows reports it is just CDFS and some jpeg files plus some > > windows > > software that let's you view it. I don't know... how can I get it wrong: > > mount > > /cdrom right? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > > or > > man mount I'm not sure about a "Picture CD", but I just double checked and I can't mount a Kodak Photo CD on 5.3. It's not '-t cd9660' and it's not '-t msdos'. Googling around a bit shows that it's a multisession cd, and I get the following devices when I stick on in the drive (satchel)[1:35pm]~>>ls -l /dev/*cd* crw-r--r-- 1 root operator4, 20 Jan 5 16:04 /dev/acd0 crw-r- 1 root operator4, 22 Jan 7 01:03 /dev/acd0t01 crw-r- 1 root operator4, 47 Jan 7 01:03 /dev/acd0t02 crw-r- 1 root operator4, 48 Jan 7 01:03 /dev/acd0t03 crw-r- 1 root operator4, 49 Jan 7 01:03 /dev/acd0t04 crw-r- 1 root operator4, 50 Jan 7 01:03 /dev/acd0t05 crw-r- 1 root operator4, 51 Jan 7 01:03 /dev/acd0t06 crw-r- 1 root operator4, 52 Jan 7 01:03 /dev/acd0t07 crw-r- 1 root operator4, 53 Jan 7 01:03 /dev/acd0t08 crw-r- 1 root operator4, 54 Jan 7 01:03 /dev/acd0t09 crw-r- 1 root operator4, 55 Jan 7 01:03 /dev/acd0t10 crw-r- 1 root operator4, 56 Jan 7 01:03 /dev/acd0t11 crw-r--r-- 1 root operator4, 21 Jan 4 18:03 /dev/cd0 (satchel)[1:36pm]~>>cdcontrol info -f /dev/acd0 Starting track = 1, ending track = 11, TOC size = 98 bytes track start duration block length type - 1 0:02.00 1:01.21 04596 data 2 1:03.21 5:25.604596 24435 data 3 6:29.06 2:11.57 290319882 data 4 8:40.63 3:18.13 38913 14863 data 5 11:59.01 2:50.64 53776 12814 data 6 14:49.65 3:15.22 66590 14647 data 7 18:05.12 3:14.38 81237 14588 data 8 21:19.50 4:02.57 95825 18207 data 9 25:22.32 2:32.45 114032 11445 data 10 27:55.02 0:59.33 1254774458 data 11 28:54.35 0:22.03 1299351653 data 170 29:16.38 - 131588 - - (satchel)[1:36pm]~>> If I cat /dev/acd0t02 into a file, it turns out to be a (satchel)[1:36pm]~>>sudo cat /dev/acd0t02 > /tmp/ape (satchel)[1:37pm]~>>file /tmp/ape /tmp/ape: Kodak Photo CD image pack file , landscape mode And display (from the imagemagick suite) is able to show me one of (the first, in fact) image from the CD. It doesn't seem like it's one track per image though, since there are 51 images on the disk. Has anyone worked with PhotoCD's on FreeBSD? g. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Grub and FreeBSD 4.9
db writes:
> Hi all
>
> I'm trying to get grub working on my FreeBSD 4.9 test-box.
> [...]
Here's a description of how I did it, from the freebsd-current list in
late Februrary 2003. It was part of an ongoing thread that you might
find useful.
g.
George Hartzell writes:
> Andrew Boothman writes:
> > [...]
> > OK Guys, I think I'm still a little confused here.
> >
> > I've just had a few botched installs of GRUB so I think I need a little more
> > direction, if you could :)
> >
> > I've got GRUB on a floppy and it boots fine. If I type :
> > rootnoverify (hd0,0)
> > makeactive
> > chainloader +1
> > boot
> >
> > I get Win2k booted no problem!
> >
> > So, following the instructions in the Grub Manual, I typed
> > root(fd0)
> > setup(hd0)
> >
> > I remove the floppy from the drive and reboot
> >
> > On boot I get "Loading GRUB... Please Wait..." but after that I get "GRUB
> > Error 17" which according to the manual means that GRUB doesn't know how to
> > load the selected partition. Even though when I boot from the floppy it
> > starts no problem and I can type commands to get it to boot Win2k
>
> That told it to install GRUB into the beginning of (hd0) [e.g. the
> Master Boot record], but configured it to use (fd0) as the root of the
> place to find stuff. Since the floppy wasn't in when you booted, it
> didn't do anything useful.
>
> There are some grub things that need to be on the disk that you give
> the "root" designation too, e.g. "stage1", etc...
>
> I don't know how/where to install those files into an NTFS partition,
> I assume that GRUB can read NTFS filesystems, and you could tuck them
> there, but I don't know for sure.
>
> Here's what I'd do.
>
> Get yourself booted into freebsd any way that you can.
>
> PRINT OUT THE INFORMATION ABOUT YOUR BIOS PARTITION TABLE AND YOUR
> FREEBSD DISKLABEL, AND SAVE IT. "fdisk -s" and "disklabel -r
> diskname" are your friends
>
> Build grub from the ports tree and install it. It installs all of the
> juicy bits into some directory in
> /usr/local/share/grub/i386-freebsd/..., which doesn't seem to be a
> place where grub can find it. I make a directory called /boot/grub
> and copy all of them there.
>
> Start grub (e.g. boot from your grub floppy). Under the 5.0 systems,
> GEOM is picky about letting you doink with disks that you have
> mounted, so you either need the "let me shoot myself in the foot
> sysctl patch
> (ftp://ftp.jurai.net/users/winter/patches/geom-foot.patch) or boot
> from something else (e.g. floppy, live cdrom, ...)
>
> Make sure that grub can see it's various interesting bits:
>
> grub> find /boot/grub/stage1
>
> and it should say:
>
> (hd0,1,a)
>
> assuming that you have Something Else (e.g. windows) in the first
> primary BIOS partition/slice, a set of FreeBSD slices in the second
> primary BIOS partition/slice, and the /boot/grub stuff is in the first
> ("a") BSD_DISKLABEL/slice.
>
> If you have the grub bits living in a Linux filesystem in the third
> primary BIOS partition, it'd say (hd0,2). If you had them in a Linux
> filesystem living in the first extended partition, it'd say (hd0,4),
> etc
>
> That's the drive that you want to declare as your root, which just
> configures the low level grub code that "setup" installs so that it
> knows where to look for it's various useful bits.
>
> e.g.
>
> grub> root (hd0,1,a)
>
> Then you need to install grub onto somewhere where the computer will
> trip over it and boot it.
>
> One possibility is to install it into the master boot record, which
> would be:
>
> grub> setup (hd0)
>
> Here you boot process would be
>
> power on->bios->load the MBR which is really GRUB->grub loads its stage1,...
>
> Or you could leave a "normal" MBR at the beginning of the disk and
> install GRUB into the beginning of the FreeBSD BIOS partition
> (assuming that FreeBSD is in the second primary parition):
>
> grub> setup (hd0,1)
>
> If that's all that you do, thing's won't quite boot. You'll need to
> also mark that partition active, so that the stock MBR code will jump
> to it. I always do that by getting to this point, booting by hook or
> by crook (e.g. a grub boot floppy, a bootable freebsd CD, a boot
Re: Problem opening /dev/ad0{,s2} O_RDWR (also disklabel, grub) on 5.0.
Daniel Lang writes:
> Hi George,
>
> George Hartzell wrote on Sat, Jan 25, 2003 at 06:38:07PM -0800:
> [..]
> > open("/dev/ad0", 1)', and 'call open("/dev/ad0", 2)' made it clear
> > that anything that would write to the disk was failing.
> [..]
> > disklabel: /dev/ad0s2: Operation not permitted
> [..]
> > So, my questions are:
> >
> > 1) does this ring a bell with anyone?
> >
> > 2) Is there something in 5.0 that requires special magic to write to
> > the raw disk devices?
> >
> You need to run in securelevel < 1.
>
> Check "sysctl kern.securelevel", and read init(8).
>
> I guess you have some rc.conf entry that raises
> your securelevel, most probably resulting from the sysinstall.
That's not it,
kern.securelevel is -1
and this is in /etc/rc.conf
kern_securelevel_enable="NO".
Any other thoughts?
g.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Problem opening /dev/ad0{,s2} O_RDWR (also disklabel, grub) on 5.0.
Hi
I'm trying to set up my first 5.0 machine, and I've run into a problem
right off of the bat.
The machine is a Dell OptiPlex GX110 that has three slices. The first
contains Windows 2000, the second has historically contained FreeBSD
4.7,and the third contains Linux. Since I use the system to test
stuff before I roll it onto my laptop, and since the laptop seems to
need it's original MBR in place so that suspend to disk works
properly, I've been running the Dell with GRUB installed in the
beginning of the freebsd slice (which is active) [(hd0,1) or
/dev/ad0s2] and it's been working great.
I tried to do a standard install from the 5.0 release ISO images.
After answering all of the standard questions and telling it to go
ahead, it spat out an error message as it was presumably setting up
the disk. The screen redraws fast enough that I cant' catch the
message, but I've tried a couple of times and it's happened each
time.
When I tried to boot up, I get a message about an unbootable operating
system from the code in the MBR. Booting from CD 2, interrupting the
loader, setting currdev=disk1s2a: and then "boot /boot/kernel/kernel"
brings the machine up just fine.
I tried building grub and it wouldn't admit that there was an (hd0,1).
Oddly enough, starting grub with --read-only made it able to see
(hd0,1). Inside gdb, I noticed that an open of "/dev/ad0" with O_RDWR
was returning -1 and setting errno = 1 (EPERM, "Operation not
permitted"). Some playing with 'call open("/dev/ad0", 0)', 'call
open("/dev/ad0", 1)', and 'call open("/dev/ad0", 2)' made it clear
that anything that would write to the disk was failing.
I stepped back and started digging around with disklabel, and got some
results that seem similar.
disklabel -B /dev/ad0s2 auto
should reinstall the boot stuff on that slice, but instead it says
disklabel: /dev/ad0s2: Operation not permitted
and I get the same error message from
disklabel -W /dev/ad0s2.
So, my questions are:
1) does this ring a bell with anyone?
2) Is there something in 5.0 that requires special magic to write to
the raw disk devices?
3) Am I being a bonehead?
g.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: usb keychain memory disk doesn't work on 4.7p3
Matthew Dillon writes:
> [...]
> Urk! Sorry! I plugged in the names for one of my keychains. Don't
> use Stormblue :-) Use yours. Try:
>
> {
> /*
> * Sony Memory Stick adapter MSAC-US1 and
> * Sony PCG-C1VJ Internal Memory Stick Slot (MSC-U01).
> * Make all sony MS* products use this quirk.
> */
> {T_DIRECT, SIP_MEDIA_REMOVABLE, "LEXAR*", "*", "*"},
> /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE
> },
>
> And als osend me the output of 'usbdevs -v' (with either the old kernel
> or the new one).
It works! Cool, I've got a quirk. Wow! Thanks!
> sudo usbdevs -v
Controller /dev/usb0:
addr 1: self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00
port 1 powered
port 2 addr 2: power 90 mA, config 1, LEXR PLUG DRIVE(0x0080), LEXR PLUG
DRIVE(0x05dc), rev 0.01
>
g.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: usb keychain memory disk doesn't work on 4.7p3
Randi Harper writes: > Can't reply to list because my IP doesn't reverse resolve... > > but did you try using da0s1? ;) Yep, but just did it again for kicks. > sudo newfs_msdos -F 32 /dev/da0s1 newfs_msdos: /dev/da0s1: Input/output error > sudo newfs_msdos -F 32 /dev/da0s1a newfs_msdos: /dev/da0s1a: Input/output error > sudo newfs_msdos -F 32 /dev/da0s1b newfs_msdos: /dev/da0s1b: Input/output error > sudo newfs_msdos -F 32 /dev/da0s1c newfs_msdos: /dev/da0s1c: Input/output error g. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: usb keychain memory disk doesn't work on 4.7p3
Paul Halliday writes: > On Sun, 12 Jan 2003, George Hartzell wrote: > > > I can't make my little Lexar JumpDrive 128Mb USB keychain memory > > "disk" work. The device works on a windows machine, and worked on > > this very laptop back when it was running Redhat Linux 7.2 w/ > > RedHat's various updates. I got the same failure trying to use the > > device on a Dell OptiPlex GX110. > > Try newfs_msdos on the device first. Seems un-necessary, since it alreay has a valid FAT32 filesystem on it (which works and is mountable under Windows 2000 and Linux). But, in the interest of trying everything: Here's the command line: > sudo newfs_msdos -F 32 /dev/da0 Password: newfs_msdos: /dev/da0: Input/output error and here's /var/log/messages: Jan 12 17:35:26 rosebud /kernel: umass0: LEXR PLUG DRIVE LEXR PLUG DRIVE, rev 1.10/0.01, addr 2 Jan 12 17:35:26 rosebud /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jan 12 17:35:26 rosebud /kernel: da0: Removable Direct Access SCSI-2 device Jan 12 17:35:26 rosebud /kernel: da0: 650KB/s transfers Jan 12 17:35:26 rosebud /kernel: da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) Jan 12 17:37:10 rosebud sudo: hartzell : TTY=ttyp0 ; PWD=/usr/home/hartzell ; USER=root ; COMMAND=/sbin/newfs_msdos -F 32 /dev/da0 Jan 12 17:37:10 rosebud /kernel: da0: reading primary partition table: error reading fsbn 0 Same result on the other /dev/da0* devices. Anyone have any other suggestions? g. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
usb keychain memory disk doesn't work on 4.7p3
I can't make my little Lexar JumpDrive 128Mb USB keychain memory "disk" work. The device works on a windows machine, and worked on this very laptop back when it was running Redhat Linux 7.2 w/ RedHat's various updates. I got the same failure trying to use the device on a Dell OptiPlex GX110. I'm using: - Sony Vaio PCG-Z505JE - FreeBSD 4.7p3 from cvs When I insert the device, I get this in /var/log/messages: Jan 12 12:04:28 rosebud /kernel: umass0: LEXR PLUG DRIVE LEXR PLUG DRIVE, rev 1.10/0.01, addr 2 Jan 12 12:04:28 rosebud /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jan 12 12:04:28 rosebud /kernel: da0: Removable Direct Access SCSI-2 device Jan 12 12:04:28 rosebud /kernel: da0: 650KB/s transfers Jan 12 12:04:28 rosebud /kernel: da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) With this in my /etc/fstab: /dev/da0c /mnt/jumpdrive msdos rw,noauto 0 0 I get this when I try a mount: > sudo mount /mnt/jumpdrive msdos: /dev/da0c: Input/output error And this in /var/log/messages: Jan 12 12:05:02 rosebud /kernel: da0: reading primary partition table: error reading fsbn 0 I've tried every device in /dev/da0*: /dev/da0 /dev/da0c /dev/da0f /dev/da0s1 /dev/da0s1c /dev/da0s1f /dev/da0s2 /dev/da0a /dev/da0d /dev/da0g /dev/da0s1a /dev/da0s1d /dev/da0s1g /dev/da0s3 /dev/da0b /dev/da0e /dev/da0h /dev/da0s1b /dev/da0s1e /dev/da0s1h /dev/da0s4 and get the same result with all of them. I've attached my dmesg info below: Can anyone either suggest a fix or a place to start looking? g. Copyright (c) 1992-2002 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 4.7-RELEASE-p3 #2: Wed Jan 8 11:17:28 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ROSEBUD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (496.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 335478784 (327616K bytes) avail memory = 320507904 (312996K bytes) Preloaded elf kernel "kernel" at 0xc0567000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00fdf50 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0x1040-0x104f at device 7.3 on pci0 pci0: (vendor=0x104d, dev=0x8039) at 8.0 irq 9 pcm0: port 0xfc8c-0xfc8f,0xfcc0-0xfcff mem 0xfedf8000-0xfedf irq 9 at device 9.0 on pci0 pci0: (vendor=0x14f1, dev=0x2443) at 10.0 irq 9 fxp0: port 0xfc40-0xfc7f mem 0xfec0-0xfecf,0xfedf6000-0xfedf6fff irq 9 at device 11.0 on pci0 fxp0: Ethernet address 08:00:46:07:71:d5 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci_cfgintr_linked: linked (61) to hard-routed irq 9 pci_cfgintr: 0:12 INTA routed to irq 9 pcic0: irq 9 at device 12.0 on pci0 pcic0: PCI Memory allocated: 0x8800 pccard0: on pcic0 pci0: (vendor=0x104d, dev=0x808a) at 13.0 irq 0 orm0: at iomem 0xc-0xcbfff,0xdc000-0xd on isa0 fdc0: ready for input in output fdc0: cmd 3 failed at out byte 1 of 3 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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: parallel port not found. ad0: 28615MB [58140/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized fxp0: promiscuous mode enabled vmnet1: promiscuous mode enabled To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
