I’m interested to install TrueOS to test it out as a main desktop system (meaning I hope for GUI interface, web-browsing, youtube, some office/productivity, programming/develeopment, and testing out how my graphics card runs with it). Before going TrueOS “all the way”, I had thought to install it all by itself on a disk that I’ve just wiped blank. the only thing on the wiped disk after installing TrueOS would be TrueOS! No non-TrueOS partitions and no non-TrueOS data! Before I proceed to do anything, I had a few questions/concerns I thought to post here before taking action and installing anything or writing to any disk!
Suppose, I plug in my wiped disk into the system (it’s a SATA disk) along with 3 other disks (which are in use at this moment as I type!). Suppose I boot into the TrueOS DVD (TrueOS-Desktop-18.03-x64-DVD.iso) and also see in the disk install selection the wiped disk along with the other disks and suppose I’m able to unambiguously tell which disk is which (the wiped disk vs the other ones that are installed which are important as I use them to boot into Ubuntu and Windows when I need to get work done). Finally suppose I select for TrueOS to be installed on the wiped disk. My question/concern is if I select the wiped disk and proceed to install on it (and not select any other disk), will the TrueOS installation write to or touch any other disk? I would expect TrueOS to only write on the disk selected for install. Will it change any other boot loader or boot-up configuration on a disk not selected for install?? I saw this post (Hosed partition but not selected in install) and thought to go ahead and post here about my concern. Currently, I run grub on another disk (with a partition that has a “boot” flag) and use it to boot into either Ubuntu18.04 or Windows 10 from a menu. I would not want TrueOS to mess with the grub configuration or touch the other disks so that if I need to boot into either Windows or Ubuntu I can and get work done. I would not expect TrueOS to touch during its install a different disk except for the one selected to be installed on. I am sorry if I’m seeming paranoid or if I seem excessively worried about this, but I have NO experience at all with TrueOS and no experience at all with BSD and I’m anxious before taking any action so I post here first.
That leads me to my second question which is perhaps not a TrueOS specific question… but I mention here anyway in case someone might comment on it. First, my BIOS is set in BIOS/legacy mode (not UEFI). All of the partition tables on the disks are msdos partition tables. One disk (Ubuntu) is set with the boot-flag on its main partition and loads grub each time I boot and I’ll use it to boot into either Windows or Ubuntu. I would hope that after installing TrueOS on the wiped disk, that I’d be able to boot into linux, run “update-grub” and that it would find the TrueOS installation and I’d be able to select it among the other OS’es to boot into. Does anybody by chance know if that would work? Can TrueOS be on a legacy/BIOS system (as opposed to UEFI)
would the grub install needs for all partitions to all be either MBR or GPT when having them in the menu to choose from to boot into? Assuming that the system boots into TrueOS after the installation with no grub, and assuming that its installation leaves other disks alone, I figure, I’d be able to adjust the boot flags on the partitions (remove the boot flag from the TrueOS disk and make sure that the one for grub is checked; I have an ubuntu liveCD and gparted liveCD that can enable me to do so) to get back to Ubuntu.
thanks anybody for any comments/info!