Search results

Just coming here to say that I hope that you get the necessary feedback for this as it is a very welcome initiative. I would also mention this to the guys over at PC-BSD because they have created an entire desktop environment (Lumina) aiming to get around these kinds of things. They would...

Reviving this. The recent interview of Josh Paetzel on BSDNow really shed some light on a lot of the above. I think it is well worth listening to. http://www.jupiterbroadcasting.com/92416/zfs-in-the-trenches-bsd-now-123/

I second the cooltrainer guide! It is a very nicely written. Although some of it might be overkill if one is looking for a very simple desktop set up without all the bells and whistles. The desktop-installer works sometimes and sometimes it doesn't. I actually tried to use it today with KDE and...

Would PC-BSD be an option for you? You get a desktop environment out of the box on install. From there you can check out some of the config files to see whats in them. Its a good way to learn. Although there are easier steps, this tutorial will give you a working FreeBSD desktop with a GUI...

Thanks! This is quite informative. I had a hunch that the scrub, being quite thorough in what it does (as well as disk intensive), could be used in this way as an ad hoc burn-in tool.

Hmm. Either no one has ever considered this before, or it was a really silly idea.

Do let us know how it turned out. Its always nice to know whether something ends up working for someone or not.

Here you go https://forums.freebsd.org/threads/autofs-for-nfs-mounts-looking-for-help-and-example-configurations.54201/#post-306744

Hmm. Sounds similar to an issue that I had some time ago. You might want to give the new autofs a shot. I posted some notes about how I set it up for my use case some time ago. I'll repost it here in a second.

Thanks for confirming this. This is exactly why I was hesitant to do anything serious with this board and why is just a test bed for various things. I did end up solving the FreeBSD boot issue though!! I toggled the installer to "GPT + Active". Works fine now hopefully this might help others in...

After reading in depth about how ZFS scrub carries out its work, I wondered whether it could be a useful tool for "burning-in" new disks in much the same way we would use memtest for testing RAM? For example, by setting up a test pool and then generating some random data to fill the pool...

Strange. Why not let pkg automatically choose the repository instead of choosing one of the quarterlys? Also you can make SSHing into your VM easier by selecting "bridged adapter" in the Network tab. Your VM will then have its own ip assuming you are connected to a router that gives out...

You may also want to try pkg upgrade -f to ensure that KDE has all the recent/requested versions of the applications it needs to run. I know I've gotten bitten by KDE hiccups when installing many applications at the same time. Some applications get removed for whatever reason during install...

Yep, you beat me to it. I suspected that hald_enable="YES" dbus_enabl="YES" may not have been loaded. I remember somewhere reading that the recent versions of xorg won't need it but as far as I know a number of the desktop environments do.

Can you paste the contents of your /etc/rc.conf file?

I just wanted to come back to report the ZFS on root now definitely does work for the t420s with the GPT + LenovoFix option selected in the ZFS install menu. The T420s is a very nice laptop, can support up to 3 disk drives (2 HDDs and 1 mSATA). It also has a USB 3 port and is pretty lightweight...

Well the European Parliament's researchers surely have enough faith in OpenBSD to mention them in a report designed to increase awareness about information security and increase investment in open source security tools...

Yes, it requires more work and simpler solutions are available. With the HAMMER slave option there is a lot of behind the scenes stuff that needs to be done.

No, no need to. Its a time time all in one configuration designed for a workstations.

I tried it actually. One just needs to change /dev/serno/xx to /dev/da0 so that the newly cloned disks don't go looking for the serial number of the original source disk. Other than that, clones from a dd'd source drive work fine.