Re: adding Samba to config.scm
> now I have a second account with a password. > I don´t know this password to log into it. > > (password (crypt "firsttimepass" "$6$abc")) > > how can I find out the password? The "firsttimepass" will be the "initial" password of the new account. After that I just usually use passwd to change the account password into something not written in cleartext. The "guix system reconfigure" command does not change the password for existing users, only sets them for the created ones. -- Hope that helps, Ignas Lapėnas
Help! I just killed my Guix System!
or "the day I lost my `head`" or "happy ever after only lasts 6 years" Hi Guix, TL;DR my Guix System refuses to boot and I’m left with a "scheme screen of death". It’s a single system+data encrypted partition. How am I supposed to fix that? This morning, I turned on my computer and… everything went I usual! I logged in and did what I had been happily doing weekly for the last six years: ``` $ sudo guix system delete-generations; and guix home delete-generations; and guix pull --delete-generations; and guix gc; and guix pull ``` Everything went as usual. After that, I started working and quickly realized that something was awfully wrong: basic commands like `head` were missing. It’s the first one I noticed, but `env` was also missing for instance. So I did what any act-and-think-later person would have done: I took a deep breath… and rebooted! You know… "Have you tried to turn it off and on again" kind of thinking. After having typed my encryption passphrase twice (actually, it was three times, for I never managed to type it right the first time), I ended up on the "scheme screen of death": ``` making `/var…` the current system… populating /etc from /gnu… ice-9/boot-9.scm… in procedure symlink: File exists … scheme@(guile-user)> ``` As I `system delete-gererations`-ed few minutes ago, I have no way to boot on the previous-now-gone system. Anyway, it was apparently broken. Had it been a system only partition like the one I have at home, I would have reinstalled it right away. But it’s not! It’s a single system+data encrypted partition. I guess there a way to fix this somehow. But the only thing I can thing of is to reinstall on another disk and copy my data over, which sounds suboptimal. Can someone think of a clever way to fix it from the "scheme screen of death" or a way to voodoo-cross reinstall without wiping out the data. Any help would be greatly appreciated! Regards, -- Tanguy
Re: Help! I just killed my Guix System!
Hi Tanguy "Tanguy Le Carrour" writes: > or "the day I lost my `head`" > or "happy ever after only lasts 6 years" > > Hi Guix, > > TL;DR my Guix System refuses to boot and I’m left with a "scheme screen of > death". It’s a single system+data encrypted partition. How am I supposed to > fix > that? > > This morning, I turned on my computer and… everything went I usual! I logged > in > and did what I had been happily doing weekly for the last six years: > > ``` > $ sudo guix system delete-generations; and guix home delete-generations; and > guix pull --delete-generations; and guix gc; and guix pull > ``` > > Everything went as usual. After that, I started working and quickly realized > that something was awfully wrong: basic commands like `head` were missing. > It’s > the first one I noticed, but `env` was also missing for instance. > > So I did what any act-and-think-later person would have done: I took a deep > breath… and rebooted! You know… "Have you tried to turn it off and on again" > kind of thinking. > > After having typed my encryption passphrase twice (actually, it was three > times, > for I never managed to type it right the first time), I ended up on the > "scheme > screen of death": > > ``` > making `/var…` the current system… > populating /etc from /gnu… > ice-9/boot-9.scm… > in procedure symlink: File exists Let me guess, you have /etc/guix/acl file pointing to a non existing store location. See https://issues.guix.gnu.org/77201, there is a bug with that that has the same symptom as you're experiencing. To fix it, delete this file in a live iso, and you should be good to go further. I am not sure in what state your system is, so I can't tell you if you will be able to boot. The commands you shared definitely should not cause the issues you are experiencing normally, something must've went wrong. If you still won't be able to boot, it's possible your generation is still somehow corrupted. In that case, it's probably easiest to boot into a live iso and reconfigure from a chroot. See the manual for instructions. (12.1 Chrooting into an existing system) > … > scheme@(guile-user)> > ``` > > As I `system delete-gererations`-ed few minutes ago, I have no way to boot on > the previous-now-gone system. Anyway, it was apparently broken. > Had it been a system only partition like the one I have at home, I would have > reinstalled it right away. But it’s not! It’s a single system+data encrypted > partition. > > I guess there a way to fix this somehow. But the only thing I can thing of is > to > reinstall on another disk and copy my data over, which sounds suboptimal. > > Can someone think of a clever way to fix it from the "scheme screen of death" > or a way to voodoo-cross reinstall without wiping out the data. You can reinstall(reinit) guix system without losing any data, you can always delete /gnu/store and /var/guix, and run guix system init from a live iso. That way you won't lose any data. But there might not be the need to do this for you, first try what I suggested above. (but note that since of the bug I outlined, you will still need to remove /etc/guix/acl) Just to make stuff faster in case it's not /etc/guix/acl, check also for special files (/bin/sh and /usr/bin/env by default, maybe you have more in your config), and see if there is file in the folder, but with .new extension. This is one other think that can cause symlink: File exists (but the log should look differently from what you sent, so I don't think that's it) Good luck, Rutherther
Re: Help! I just killed my Guix System!
Hi, On Mon Apr 7, 2025 at 12:18 PM CEST, Rutherther wrote: > "Tanguy Le Carrour" writes: > >> Hi Rutherther, >> >> On Mon Apr 7, 2025 at 10:22 AM CEST, Rutherther wrote: >>> Let me guess, you have /etc/guix/acl file pointing to a non existing >>> store location. >>> See https://issues.guix.gnu.org/77201, there is a bug with that that has >>> the same symptom as you're experiencing. Actually, my problem might come from some code I found it the cookbook: ``` (privileged-programs (cons (privileged-program (program (file-append qemu "/libexec/qemu-bridge-helper")) (setuid? #t)) %default-privileged-programs)) (extra-special-file "/etc/qemu/host.conf" "allow br0\n") (service iptables-service-type (iptables-configuration (ipv4-rules (plain-file "iptables.rules" "\ *filter :INPUT ACCEPT [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [0:0] -A FORWARD -i br0 -o br0 -j ACCEPT COMMIT ")) ``` https://guix.gnu.org/cookbook/en/html_node/Network-bridge-for-QEMU.html >> Sounds like something that could have happened, as last week, I was trying to >> setup qemu/libvirt! >> >> I’ll read that and give a try to what you’re suggesting… I soon as I dare to >> go >> back to work as I’m surrounded by Debian Sysadmins that love to make fun of >> me >> and my "funny OS"! 😅 >> Their first reaction this morning was suggesting me to install Debian! 😁 > > PS: if you wanted to do it from the interactive guile repl, it would be > `(delete-file "/etc/guix/acl")` - it's safe to delete at any time, it will > get symlinked on next boot again. Even better, thanks! I’ll give it a try on thursday. Regards, -- Tanguy
Re: Help! I just killed my Guix System!
"Tanguy Le Carrour" writes: > Hi Rutherther, > > On Mon Apr 7, 2025 at 10:22 AM CEST, Rutherther wrote: >> Let me guess, you have /etc/guix/acl file pointing to a non existing >> store location. >> See https://issues.guix.gnu.org/77201, there is a bug with that that has >> the same symptom as you're experiencing. > > Sounds like something that could have happened, as last week, I was trying to > setup qemu/libvirt! > > I’ll read that and give a try to what you’re suggesting… I soon as I dare to > go > back to work as I’m surrounded by Debian Sysadmins that love to make fun of me > and my "funny OS"! 😅 > Their first reaction this morning was suggesting me to install Debian! 😁 PS: if you wanted to do it from the interactive guile repl, it would be `(delete-file "/etc/guix/acl")` - it's safe to delete at any time, it will get symlinked on next boot again. > > Regards, > > -- > Tanguy
Re: How can empty generated files in the store happen? Has someone experienced this?
On Mon, Apr 7, 2025, at 15:53, Nicolas Graves wrote: > As in my critical december failure, I happen once again to have empty > files for files expected in my store: Is it this bug? https://issues.guix.gnu.org/77086
Re: adding Samba to config.scm
Hi,
thanks, it worked as I copied this into my config.scm
and did a sudo guix system reconfigure /etc/config.scm
now I have a second account with a password.
I don´t know this password to log into it.
(password (crypt "firsttimepass" "$6$abc"))
how can I find out the password?
thanks
Gottfried
Am 07.04.25 um 06:55 schrieb Ignas Lapėnas:
So what do I have to do in Guix to add a new user and create a samba
login for that user?
My guess would be to add the user like other regular users in Guix
```
(operating-system
(users (cons* (user-account
(name "myuser")
(comment "My Regular User")
(group "users")
(password (crypt "first-time-pass" "$6$abc"))
(home-directory "/home/myuser")
(supplementary-groups '("wheel" "netdev" "audio" "video")))
(user-account
(name "gast")
(comment "The Samba Public User")
(group "users")
(password (crypt "firsttimepass" "$6$abc"))
(home-directory "/home/mariuszidonis")
(supplementary-groups '()))
%base-user-accounts))
...
)
```
To use smbpasswd to create a samba login, you should just have
smbpasswd program available in your profile.
OpenPGP_0xD9E413C6C4BB32CE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
Re: Help! I just killed my Guix System!
Hi Tobias,
On Mon Apr 7, 2025 at 10:29 AM CEST, Tobias Geerinckx-Rice wrote:
> Once the initial panic wears off & as long as your file system isn't actually
> hosed, Guix Systems are actually extremely easy to re{pair,build,deploy}.
> More so than others. I've become rather cavalier about ‘breaking’ my system.
It’s my first time. I’m still shaky and recovering from the shock. 😵
>>Can someone think of a clever way to fix it from the "scheme screen of death"
>>or a way to voodoo-cross reinstall without wiping out the data.
>
> Well, I'd do neither.
I was expecting a response like this! 😅
> If you can still luksOpen & fsck & mount the partition(s) from an external
> system… such as the Guix System installer, you can simply ‘guix system init’
> from your existing system configuration, no?
Definitively! I’ll give it a try!
Thanks!
--
Tanguy
Re: How can empty generated files in the store happen? Has someone experienced this?
Possibly but I'm not 100% sure as I'm only able to diagnose it after the fact. Here it happened as a side-effect of another bug (probably 76554, laptop screen blank after kexec reboot). It hangs indefinitely so at some point I have to force halt the computer from the power button. Maybe that was the cause of the corruption I observe at reboot. It started to happen to me as soon as november / december. I'm running shepherd 1.0.3 now so it doesn't seem fixed by that. On 2025-04-07 15:59, Leo Famulari wrote: > On Mon, Apr 7, 2025, at 15:53, Nicolas Graves wrote: >> As in my critical december failure, I happen once again to have empty >> files for files expected in my store: > > Is it this bug? > > https://issues.guix.gnu.org/77086 -- Best regards, Nicolas Graves
Re: How can empty generated files in the store happen? Has someone experienced this?
Incidentally, a third bug comes into play here, it's not possible to easily determine which live object blocks the corrupted files, that is quite annoying as well: $ guix gc -D /gnu/store/l0hs8cydj71z1l38d79bjzizr2lmarq9-upgrade-shepherd-services.scm.drv finding garbage collector roots... guix gc: erreur : cannot delete path `/gnu/store/l0hs8cydj71z1l38d79bjzizr2lmarq9-upgrade-shepherd-ser ices.scm.drv' since it is still alive zsh: exit 1 guix gc -D $ guix gc --referrers /gnu/store/l0hs8cydj71z1l38d79bjzizr2lmarq9-upgrade-shepherd-services.scm.drv $ guix gc --derivers /gnu/store/l0hs8cydj71z1l38d79bjzizr2lmarq9-upgrade-shepherd-services.scm.drv -- Best regards, Nicolas Graves
Re: Help! I just killed my Guix System!
>Definitively! I’ll give it a try! Try Rutherther's suggestion first, they seem to be aware of a specific bug of which I'm ignorant. Otherwise, happy downloading. Kind regards, T G-R Sent on the go. Excuse or enjoy my brevity.
