I have enjoyed all your various videos. I have been moving from Mac to Linux to BSD. I particularly want to master Freebsd, however have found it to be a challenge to install on my admittedly newer laptops. I recently acquired some thinkpads and was able to maneuver around some of the hardware issues that were stumbling blocks due to my lack of knowledge. Your videos have been a great help. Ghostbsd has been useful to get a usable FreeBSD based system up and I have now been able to follow your guidance and get a FreeBSD system going. Nomad is likely a next try and the ideas presented here may help me capture and preserve installed versions where I have solved some of my difficulties. Keep it up and I continue to applaud your work.
This is well timed. It's a perfect out-of-the-blue gift for my wife. According to her diary, she gets no privacy at all. This should cheer her up! Merci.
:-) This would could be a great birthday present, knowing how you like to show your generous side.... Buy a cheap generic USB, any will do, no need to be too extravagant - wrap it up in recycled Amazon packages (we all have to do our bit) - and voila. Mrs Bailey will be overjoyed, job done! Good luck :-)
Very cool Christopher, I am going to do this with one of my old nvme drives and external enclosure for my Debian KDE notebook. Cheers my friend, thanks for the video !
Very nice indeed, RN. One thing I really liked about NomadBSD (bsides its minimality) was that there were no issues connecting to wifi on my laptops. Is there a wifi driver package (or group of packages) that could be installed on the FreeBSD USB system that would allow it to be used with a range of laptops? Cheers from Wisconsin!
The wifi config is normally done manually, but you can use a semi-graphical tool called bsdconfig and do it from that, it works well with FreeBSD supported wifi adapters, and that Andrew, is where you may stumble... You would have to use it on different laptop models unless they use the same chipset OR you use a wifi dingle on each laptop that you know works.... I think the best option is to try it and see :-)
My use case is to have a FreeBSD USB installation tryout while not disturbing the main Linux system, for example. AFAIR, FreeBSD has complex relations to HDD partitioning which makes dual-boot quite complicated. Here, having a 1TB SSD is quite an excellent solution that does not break anything, easy to cancel and try if FreeBSD works on different hardware. Your way of using installer UI for creating such USB is way better than manually issuing a lot of commands like in a manual that I've found :-)
This is far from being just you "messing with a usb stick". Such a thing is a great tool. I always assumed it would be slow, but it is not that bad, and it can have many uses. Thank you! Any particular reason it has to be ZFS?
I chose ZFS because of the easy way to encrypt using Geli, doing this before installation is much easier than trying to do it after, and as far as I know there isn't any easy way to encrypt using UFS...but I may be wrong on that...
Great video. I would strongly suggest at least 32GB (target) USB, though, considering future applications. upgrades, extra stuff. I recall suffered a few times due to lack of space/storage. Cheers,.
Very useful. There is a method to install the system in the USB stick - like NomadBSD - on hard drive? There is a graphical installer for it? My project is to create MintBSD. Do you think i'm crazy?
Those were about the ugliest USB devices I've seen in a long time. Made me think three legged dog! Good video; messing around is the universal way of learning things at a deeper level.
There may be better ways, but for me, I had the bright idea of treating the USB as a remove HDD, and it worked.... sometimes old dogs can learn new tricks :-) It would be cool to see a Gentoo video on this :-) *wink wink*
I have since made a FreeBSD live usb, but I burnt a dvd and installed from it. No problems booting that way. Had to install Intel drivers to get X working. Thanks for all your great videos!
You sure do make it look easy. I successfully installed 13.1 next to a Windows 11, and an Arch partition, and ended up getting lost in the boot process. I still have the installation intact, but I can't boot into it, and none of the research I've tried has worked.
I don't advocate dual boots, it's something I run away from screaming :-) So the only thing I can offer you is have a look here: forums.freebsd.org/threads/install-freebsd-13-0-alongside-with-other-oss-on-uefi-system-via-grub2-multiboot.74818/ FreeBSD in general likes to grab the primary partition, so sometimes that can be the cause of some issues.... Let me know if you solve this as this is an areas I lack experience in.... :-)
@@RoboNuggie I haven't quite nailed down the science of it just yet, but the instructions provided in the link you sent were very helpful! It was as easy as mounting my EFI partition, making a directory, and copying over the bootloader. This surprised me because the drive FreeBSD is installed to has it's own partition labeled 'FreeBSD Boot', so I assumed I would be booting from that partition. What fixed it for me was copying over the bootloader to the EFI partition on my Windows drive instead. Fortunately this worked great because I already had refind installed. Refind wasn't finding the bootloader before I copied the files over, but once done picked it up no problem, and the system is booting. Thank you for the great resource! 🙂 Now...To get X, sddm, and Kde working with an RTX 3060....
Thank you again @RoboNuggie! Between the instructions you kindly provided here and the video you did on 'desktop-installer', everything is up and running, and the operating system is starting to make some sense. 🙂 Very grateful! Cheers from the SW US!
I follow your step by step guide but this is what I got an error message no pools available to import swapon: /dev/da1p3: No such file or directory Starting file system checks: Can't open /dev/da1p1 /dev/da1p1: UNEXPECTED INCONSISTENCY: RUN fsck_msdosfs MANUALLY. THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: msdosfs: /dev/da1p1 (/boot/efi) Automatic file system check failed; help! ERROR ABORTING BOOT (sending SIGTERM to parent)! 2022-11-17T00:54:32.125230+08:00 - init 1 - - /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter root password, or ^D to go multi-user Password:
