search for: wonkiti

Hi, after updating my freebsd amd64 box from 9.1 (r250841) to 9.2-RC (r254276) virtualbox crashes the machine. Seconds after starting VBOX the screen freezes and then reboots (probably a trap, cannot see it, as screen is in graphics mode). The kernel modules of vbox have been recompiled. Going back to 9.1 kernel and matching vbox modules works. In both cases VBOX 4.2.16 is used. cheers, Thomas

Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp

My xorg.conf foo is pretty weak today. Does anyone have an ATI 4250 in a dual head config? I'd be interested in looking over your xorg.conf. Sean p.s. Mine at the moment, that doesn't work very well: http://people.freebsd.org/~sbruno/4250_xorg_conf.txt

https://bugzilla.samba.org/show_bug.cgi?id=9132 Summary: [manpage] rsync.1 entry for --force-schange refers to itself Product: rsync Version: 3.0.9 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

Hi! My plea to readers: =================== Pls., people who only want strictly technical issues to read, and frown at any broader context regardless how intrinsically related, but not strictly technically related, it might be, skip all the way, all the way to, search for exact words: "strictly technical" or visually, find two lines of sole "===" characters. Thank you!

Greetings, I haven't upgraded my tree(s) for awhile. My last attempt to rebuild after an updating src && ports, resulted in nearly installing the entire ports tree, which is why I've waited so long. Try as I might, I've had great difficulty finding something that will _only_ upgrade what I already have installed, _and_ respect the "options" used during the original

So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I

>> #1. Map the physical drive slots to how they show up in FBSD so if a >> disk is removed and the machine is rebooted all the disks after that >> removed one do not have an 'off by one error'. i.e. if you have >> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >> missing ada8 drive and the next drive (that used to be ada9) is now