Search results

I guess because there's enough legacy software and firmware to warrant it...

What config are you using, and what version of vte is installed?

The question over the need for the 16 block offset is one I'd love answered too. I know gpart doesn't automatically set a 16 block offset for the first partition in a BSD label, and it's supposedly the "new" way of partitioning in FreeBSD. Kaminar's observations seem to show unexpected...

Looks like you should file a PR. Try test with a different NIC (and driver) if you can...

Many linuxes have wget installed as part of their "base". In FreeBSD we have fetch, and wget is in ports: ftp/wget. Many linuxes have nano as their default editor. FreeBSD has vi and ee. Again, go to ports for nano and many other editors. In FreeBSD, more and less behave (almost)...

Given the choice, I only use Intel NICs on FreeBSD. Probably the best maintained and supported ethernet drivers we have...

Same here but with SuperMicro's USAS2 controllers, and these cables. Disks connected internally, directly...

Or just build your own... make package ports

Booting GPT disks is radically different to MBR, and boot0's architecture will never work even if there were space for more code. FreeBSD's GPT boot loader is not advanced enough yet to be a boot manager either, and may never be - that's what EFI is for, I think. Perhaps you can try GRUB2 though.

Any FreeBSD running in those extreme conditions? :)

Any other errors? Looks like a hardware issue. Maybe faulty SATA cables?

Not sure about OpenBox, but I set my background from XDM. That way my login screen and login session look the same...

Also look into ng_netflow, net/pfflowd, and all Netflow data processing/graphing related ports.

Probably not much wrong with amd. I mainly wanted manual mounting abstracted enough to be easy. With amd, mounting is easy, but I guess a manual umount requires one to fumble on the command line.

boot -v at the loader prompt...

Not possible at this stage. If you want to use vfs.usermount without sudo, you will have to modify amount code. In which case you can modify the port's Makefile too. :) Hopefully 0.7 won't require sudo anymore.

Hey, I've finally submitted this as a port: http://www.freebsd.org/cgi/query-pr.cgi?pr=159631 The port version is bumped to 0.6 and receives some changes: * a proper daemon with RC script for start up (problem solved, richardpl). * read-only NTFS support. * experimental large FAT32 support...

In FreeBSD it's traditional to have at least 3 file systems: /, /usr, and /var. There should be no /home file system - that ought to be a symlink to where your home directories actually are, which is usually /usr/home. I suggest you don't have more than the above 3 traditional partitions until...

Pardon my silence folks. Been busy moving into a new country. Now hopefully I can finish some cleanup that I've been wanting to do. Glad this work so far has been useful. Public domain. :)

I got the opportunity to build another ZFS system similar to this previous one. The biggest difference is that this new system is running a Z68 board, which means I could use two Supermicro AOC-USAS2-L8i cards instead of one. All 12 disks in its pool are connected via mps, and there's still...