All BSD thread, including Darwin.
What is your BSD of choice?
How's NeXTBSD and DragonFly doing?
Holy fucking shit, Darwin isn't BSD, it doesn't have a BSD kernel, fucking stop being an Apple shill.
I'd use OpenBSD if I didn't have an Nvidia graphics card. Unfortunately, I do, so I use FreeBSD.
I use it as a desktop. It runs the music production and astronomy programs I need.
You can also run Linux programs too if you install a compatibility package, but I avoid doing so.
>kernel with BSD subsystem is non-bsd
>you care about an important hardware piece what is wrong with you
grow up m8
FreeBSD is a great system and I enjoyed learning and tinkering with the base but the hardware support (ex you cant switch to a tty if X.org is open) and the filesystem slowness in non-raid configurations is too much for me to bear.
I'm pretty sure the only thing windows ever borrowed directly from the BSDs was the TCP/IP stack. At least until just recently when Microsoft donated to OpenBSD and started borrowing OpenSSH
you could do some benchmarking yourself with hdparm -Tt (you might have to install the package first tho) but for me it cuts my 550mb/s read to 220mb/read (UFS 4k here) i tried with ZFS and it's even worse.
Stuff for OSX already mostly runs on other *nix OSes after recompiling anyway. If you wanted to make a clone something like Darwin + GNUstep + heavy amounts of customization would bring you pretty close.
Darwin doesn't support many hardware platforms though and its code is mostly borrowed from other open source projects anyway. Using GNU/Linux or one the BSDs as a base would make the most sense.
Yeah, found the same info. Gotta take my younger sister somewhere, so take my paste.ada0
512 # sectorsize
240057409536 # mediasize in bytes (224G)
468862128 # mediasize in sectors
4096 # stripesize
0 # stripeoffset
465141 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
CVTR545405JS240CGN # Disk ident.
Full stroke: 250 iter in 0.009425 sec = 0.038 msec
Half stroke: 250 iter in 0.010856 sec = 0.043 msec
Quarter stroke: 500 iter in 0.024486 sec = 0.049 msec
Short forward: 400 iter in 0.013940 sec = 0.035 msec
Short backward: 400 iter in 0.014878 sec = 0.037 msec
Seq outer: 2048 iter in 0.077970 sec = 0.038 msec
Seq inner: 2048 iter in 0.073564 sec = 0.036 msec
outside: 102400 kbytes in 0.271308 sec = 377431 kbytes/sec
middle: 102400 kbytes in 0.213711 sec = 479152 kbytes/sec
inside: 102400 kbytes in 0.217416 sec = 470986 kbytes/sec
Not running Darwin BSD. Son I am disappoint.
Project been dead for a long time. Apple made it specifically so you can't compile it on non-apple hardware / put together a good base system while screaming "open sores open sores"
I've used Free and OpenBSD over the years.
I have FreeBSD on my rpi right now.
After trying out Debian (still as shit as I always remembered it) and various buggy minimal Lunix distros, it was nice having something that just werks like BSD does.
It's macabre to think, but Linux has probably gotten *worse* since I was using it regularly five years ago. I'm sticking with BSD and OS X.
Fun to use though.
Limited filesystem support I can understand getting upset with, but I thought you could do an install on zfs now (even without the raid options). OSX used to use the same ufs as bsd, and abandoned it for HFS+, which is really horrible.
The x vs tty thing never bothered me. I only notice it on any system when something like compiz takes a dump and I have to switch out to kill it. And I usually don't use BSD on a workstation.
BSD has never just worked on my systems like Linux has. I don't know why. If love to try it out though at some point--i just don't think the support is completely there just yet.
I'm not shitposting either, this is completely legitimate.
>No idea what pacbsd is.
It's the arch linux base but uses the freebsd kernel instead of the linux kernel. Because it cannot use systemd it makes use of sysvint/openrc for init and daemon management.
It's kinda obscure, I doubt you'll find many that have used it. Honestly I can't see the need for something like pacbsd. The main draw to the FreeBSD kernel is the support for jails, zfs and dtrace but those are typically workstation features and a workstation isn't really a place for rolling releases where stability isn't ensured.
Yes thinkpads have good support (Touchpad, trackpoint, wifi, brightness, automatic suspend/resume).
OpenBSD devs mainly work on thinkpads and ultrabooks atm.
>(ex you cant switch to a tty if X.org is open)
Are you saying OpenBSD can do this? Do you hit a shortcut key for a tty and it keeps the X session open in the background? Is that even possible?
Running a dev environment, freebsd within freebsd via bhyve. Both have ZFS, and the VM is backed by a ZVOL.
Does it make more sense to enable compression on the ZVOL or within the VM? For io speed? For compression ratio?
Also, what sync options should I use in both the VM and the host's ZVOL? Need to insure data integrity, I don't want a stray kernel panic curdling either system.
>(ex you cant switch to a tty if X.org is open)
This has been fixed, not sure at what point though. Switching to tty no longer gives a black screen.
If you are on an old release that doesn't support it, keep in mind that even though the screen is black that the keyboard still works, so you can login to reboot or startx again or whatever.