theamigan

joined 2 years ago
[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (7 children)

To what? Provide the error message and stop asking to be spoonfed? And you can hit ^L to make the install refresh the screen like with any curses program, fyi.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (2 children)

You need to read the handbook before you start spouting judgments about the releng process.

STABLE is cut from CURRENT. RELEASE is cut from STABLE.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago* (last edited 1 year ago)

The same as you can in regular FreeBSD, under a bhyve VM running Linux. You can also use the linux ABI in a jail.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (13 children)

Again, it is because you are using CURRENT. Don't use it.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (15 children)

That almost certainly untrue. Do not run CURRENT, it has INVARIANTS and WITNESS enabled that will make it painfully slow.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (17 children)

Install on ZFS root, snapshot a known good, then you can rollback as you wish.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago* (last edited 1 year ago) (2 children)

I know how docker and lxc work and the difference between them and chroots. But you're talking about persistence of changes breaking things. You are right that chroot only operates on the VFS namespace. Jails are the kind of isolation you are after, and in fact were in FreeBSD before containerization was even a word.

Things like remapping user IDs start to pervert the line between userspace and what the kernel gives a shit about. Linux containerization technologies are many things, but elegant they are not.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago* (last edited 1 year ago) (21 children)

I use Arch too. I've been using FreeBSD for 21 years, though. I run everything on it, even this Lemmy instance.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (4 children)

More isolated in which way? You should probably read up on how all this stuff is actually implemented, it will clarify your understanding of what is going on rather than just throwing commands at the wall and seeing what sticks.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (23 children)

Yes, you are wrong. FreeBSD is a general purpose operating system. You install what you need and configure what you need. GhostBSD and its ilk are for weenies.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (6 children)

My advice is to ditch GhostBSD, you are basically putting yourself further into the corner than you already are by trying to use FreeBSD on the desktop.

Linux binaries run just by a syscall shim. There's not much to trust or distrust. If all the syscalls are implemented and mapped to native FreeBSD syscalls, the thing works. Otherwise, it doesn't.

[–] theamigan@lemmy.dynatron.me 1 points 1 year ago (8 children)

Spotify is just an electron app. You can disable any GPU access just like you can with chrome via a flag.

My point is, unless spotify is trying to call a heretofore unimplemented syscall, it can be made to run. The linuxulator is basically as good as native.

view more: ‹ prev next ›