GUIXSD - The most advanced and freedom distro!

Is this the best Distro, nowadays?

- Free as in freedom
- No kernel blobs
- No SystemD '''(NSA init system)'''
- No proprietary software '''(faac, cisco openH264 )'''
- Stable and security distro

**inb4: gentoo, crux and voidlinux are great options but have close source codes (Spywares).**

Other urls found in this thread:

dustycloud.org/misc/talks/guix/chicagolug_2015/guix_talk.html
fosdem.org/2017/schedule/event/guixhurd/
gnu.org/software/guix/manual/html_node/Invoking-guix-system.html#Invoking-guix-system
twitter.com/AnonBabble

>but have close source codes (Spywares).**

DAILY REMINDER to not forget taking your daily pills.

>muh systemd is botnet
enjoy your barely working init system.

>openH264
>Proprietary software
What?

There's some neat things you can do with Guix (pkg manager) and GuixSD (distro based on said pkg manager with Guile init, that isn't production ready yet). Here's a presentation to get the gist of Guix dustycloud.org/misc/talks/guix/chicagolug_2015/guix_talk.html

The main advantage is root is no longer required to install whatever programs you want. You can run 100 diff versions of the same software/libraries in harmony with each other instead of breaking shit and having to do symbolic links to fix multiple versions running on the same system. You don't need GuixSD to do this, just add Guix pkg manager to any existing Debian or other linux install. With Guix no data is destroyed, so you can effortlessly move back in time and roll back updates with ease. In other words, your system will never break again.

Also, containers. They are completely declarative, without needing a disk image. No imperative shit like Dockerfiles means that you don't have to worry about order of operations, something that you have to think about constantly when using Docker and other shit container solutions. The dependency graph of your container can be reproduced exactly anywhere, and they are tiny compared to huge VM disk images.

GuixSD will use a scheme init system and GNU dmd, so you get all the advantages of Guile's libraries/API so can run your server(s) and desktop from emacs. You could also just abstract your server or container farm into a simple data structure to be manipulated in a program you make, so updating and maint of vast fleets of servers are automated, and guaranteed to work since configuration is declarative and reproducible. Your program can pass an error and then automatically roll back an update without you ever being involved.

It's a really awesome distro, I use it for everything these days though as mentioned, not ready for production use yet unless you're willing to workaround the few issues left.

Can I use flags yet?

itll have to hold me off till gnu/hurd shows up :)

Informative post; thanks for saving me the trouble of looking that up.

>not ready for production use yet unless you're willing to workaround the few issues left
Anything specific to share?

They are porting Hurd to GuixSD
fosdem.org/2017/schedule/event/guixhurd/

You can already use Guix as a package manager on top of a Hurd system (e.g. Debian GNU/Hurd). I play around with it sometimes. If you are interested in crazy parallel systems that can all run independently then try out Guix + Debian/Hurd sometime. You can have Hurd modules running all over the world like a kind of AI botnet that can't be taken down.

>no .iso file

tfw Stallman uploads his consciousness to self-replicating Hurd modules worldwide and has the ability to interject until the end of days

Marty you're not thinking 4th dimensionally. Guix doesn't use file images, it's just textfiles that describe dependencies.

...I am interested.

>Marty you're not thinking 4th dimensionally. Guix doesn't use file images, it's just textfiles that describe dependencies.
>tfw

GNU dmd was renamed to GNU Shepherd.

There is also Nix and NixOS which is what GNU Guix and GuixSD is based on.

>emacs

Stinking shit.

Basically you copy a small kernel image to USB and reboot, or use any Linux live CD/usb. When rebooted you edit a system text file using scheme to describe what you want. Then invoke 'guix system' and it just automagically gives you that exact system down to what you want running on boot or specific fine grain dependencies or general vague default deployment. Change it anytime by altering that one file and redeploy, if you don't like it, roll back to any previous install no data is ever destroyed and it doesn't need to store large prev disk images or anything. With Hurd, you can change the system without rebooting.

oh wow!
thats really great to hear!
thanks for the info :)

seems i got some experimenting to do!
haha

I.. I..
I've seen the light..

Haha :)

I use OpenRC on Arch Linux without any kind of issue. I switched not for the freedom meme, but because systemd has way too much bloat, and in fact as I result I got a huge improvement in RAM usage and boot time, and less shit like the system not booting because fstab can't mount a disk

I really like this, but I don't have a libre machine.
I use NixOS instead, which is this but systemd and some proprietary shit.

Yes.

>I use NixOS instead, which is this but systemd and some proprietary shit.
sounds awful
anything we can do to help?

>faac
isn't even closed-source, just restrictively licensed.

Open source != free software

> NSA init system
> open-source
This board is full of retards

I've tried to install it in a VM but I've never got it to work. Looks interesting though. Hope to use it someday.

Can you people convince why should I invest my time with this and not Source Mage? I am being serious, you don't have USE flags yet nad SMGL seems equally (if not more) promising.

lisp

So basically guix pkg manager does what snappy does, just it is sponsored by freedom instead of canonical?

see But systemd is free software. Stallman approves of it. There are no proofs that it's got a backdoor or anything, and since it's fully open source, someone would've found it already.

1) RMS approves of the way it is legally licensed, which is a very different thing.
2) Just because something is free software doesn't mean it should be used.
3) With how fast it has grown and how quickly it changes, a full audit that would be in any way meaningful just isn't possible. You have absolutely no reason to just blindly trust something something this important, and every reason not to.

Tried it, killed my drive ffs

nope, back to OpenBSD

Not even stage3 images?

t .retard

Did you file a bug report? If not then kys.

I use it, it's very good, especially if you like Lispy systems to begin with. The whole distro integrates into my workflow very nicely.

One thing to note is that it's not at all minimal. For example installing xorg without a login manager is unsupported and requires rolling your own package configurations.

>installing xorg without a login manager is unsupported

It has a really nice packaging system. That's really what sets it apart from other distros but you gnutard didn't even mention, because muh gnu and muh freedom is the only thing that matters to you.

Also
>Stable and security distro
I wouldn't call it stable. They're at version 0.13, so there hasn't even been a full release yet

Is that really the case? Logging in from TTY and using startx is a valid configuration and does not require any more tinkering than normal in NixOS.

This.
On my old x41 any systemD based distro takes up to 2mins to boot while openRC based distros boot in a fast 30 seconds

>barely working init system.
Of all the components systems implements, the init system is probably the simplest to write on your own. It's literally 'what run level is this, start X and write "OK" if the exit code from daemon is 0'.

People had this shit sorted out thirty years ago.

This post inspired me to checkout Guix's containers.

Guix's containerization is nowhere near as good as Docker's. Here's why:
(1) You must be root to run a container [1]
(2) No support for health-checks
(3) No support for load-balancing
(4) No support for service-discovery
(5) No ability to configure NAT for containers (at least, I can't find this)

>No imperative shit like Dockerfiles means that you don't have to worry about order of operations

This is a non-issue in the Docker world. You simply install the required packages, add whatever else you need, and ship the image. Furthermore, the imperative nature of Dockerfiles is an asset - we can build and reuse layers of an image.

>GuixSD will use a scheme init system and GNU dmd, so you get all the advantages of Guile's libraries/API so can run your server(s) and desktop from emacs

Big if they deliver. I'd really like this.

> You could also just abstract your server or container farm into a simple data structure to be manipulated in a program you make, so updating and maint of vast fleets of servers are automated, and guaranteed to work since configuration is declarative and reproducible. Your program can pass an error and then automatically roll back an update without you ever being involved.

We already do this __today__ with docker. We run Alpine w/ basically every single core system service running in a container, with a versioned-control `docker-compose.yml` that brings each system online. Docker already supports automatic rollbacks based on failed (user-definable!) health checks.

Guix definitely looks cool. As a lisper, I like the idea. If they really work on what's being talked about in
then they could build something that upsets the status-quo. We still don't really have self-healing infrastructure perfected yet. Otherwise, this might be another nice idea that went nowhere.

[1] gnu.org/software/guix/manual/html_node/Invoking-guix-system.html#Invoking-guix-system

I think that Guix's containers aren't really for enterprise-y deployment. It's more for developers running simple containers on their desktops, at least for now.