Making FreeBSD my primary operating system

bda65 said:
It's what i've made before using only FreeBSD. Arch Linux as main OS and FreeBSD as secondary.
Or you can use a VM. In full screen, i'ts great for learning.
Click to expand...
Something to think about, but I think that if I've put this much work into it, then I'm probably past the point of wanting to play with a VM.
 
jardows said:
pkg lock packagename
Click to expand...
Would this prevent my nvidia driver, which I installed via pkg, from being corrupted as the above poster described? I've seen other people describe this happening to them, and I want to make sure I understand this before I take the big plunge.
 
I feel this thread is incomplete without mentioning boot environments and snapshots. Both of which can be used to mitigate a loss of applications during an update or otherwise. I, like others, have had the experience of an app being removed during an upgrade. If the app was critical, I just rolled back or switched back to the prior snapshot or boot environment.

Cedric62, if you are pressed for additional computing resources, I agree with others that a VM is probably best for starting out. Believe me, I want you to take the plug but not if it will result in a loss (whether of data, time or enthusiasm). I was fortunate enough to be able to get another physical machine and dedicate it to FreeBSD -- it's my daily driver and Windows is a backup for when things don't work in FreeBSD.
 
bda65 said:
See pkg lock.
Or look carefully what packages are upgraded / removed before typing Y.
Click to expand...

Ya - when MY system was trashed there were north of "300" packages (pkg) all being simultaneously updated all at once.

I guess I should have said "N" then huh?

There is a 100% chance your going to get rained on some time !
 
Cedric62 said:
Would this prevent my nvidia driver, which I installed via pkg, from being corrupted as the above poster described? I've seen other people describe this happening to them, and I want to make sure I understand this before I take the big plunge.
Click to expand...

You will need to pkg lock MORE than a single pkg on your FreeBSD installation. You will need to track these all down - it's just a hand full, so not too many. I did not do that in my case and that (later) resulted in the loss of my working NVIDIA driver.

The hope, of course, is that when a brand new NVIDIA driver is downloaded and installed on to your system will still work. But ... well... that's not 100%. I actually run a REALLY common NVIDIA card: Geforce RTX 4080 -- and that stopped working. I quickly switched my FreeBSD system from using the NVIDIA driver to being a server (as I wrote - above) and now I am not as vulnerable to FreeBSD NVIDIA graphic driver loss.

You can read the details here (FreeBSD forums - LINK): URGENT - NVIDIA - REL15.0: 580.119.02_1 of nvidia driver/drm61/kmod - ARE KNOWN BROKEN
 
Cedric62 said:
Would this prevent my nvidia driver, which I installed via pkg, from being corrupted as the above poster described? I've seen other people describe this happening to them, and I want to make sure I understand this before I take the big plunge.
Click to expand...
My use for locking packages is a little different. Against the advise of most, I do mix packages and ports, mainly to get rid of pulseaudio in some of the multimedia programs I use, This is a scenario that poudriere is designed to address, and I have been working with learning that system.

For your scenario, what 'pkg lock' will do is prevent that specific package from being upgraded with the base 'pkg upgrade' command. This will not necessarily prevent any package that it is dependent upon from being upgraded, so it could help, but won't be 100% guaranteed. For Nvidia drivers though, it could be a good thing to prevent an automatic upgrade to a new driver version that may drop support for an older video card.
 
You must log in or register to reply here.
Back
Top