IRC chat logs for #ltsp on irc.libera.chat (webchat)


Channel log from 22 May 2026   (all times are UTC)

00:39vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Ping timeout: 252 seconds)
11:31quinox has left IRC (quinox!~quinox@ghost.qtea.nl, *.net *.split)
11:35quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
12:06ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
13:40danboid has joined IRC (danboid!~danboid@remote.salford.ac.uk)
13:42
<danboid>
I'm trying to troubleshoot a new Debian 13 LTS image by enabling root login in ltsp.conf but the way that worked for me with Ubuntu isn't working for Debian.
13:44
The way that used to work for me with Ubuntu was to add the lines:
13:44
POST_INIT_SET_ROOT_HASH="section_set_root_hash"
13:44
[set_root_hash]
13:44
sed 's|^root:[^:]*:|root:HASHEDPASSWORD:|' -i /etc/shadow
13:45
Replacing HASHEDPASSWORD with a password hashed by mkpasswd
13:47
Gemini also suggested I try:
13:47
POST_INIT_SET_ROOT_HASH="usermod --password '$6$rounds=656000$re8X1v9K3J...$u81W4pXm...' root" in /etc/ltsp/ltsp.conf but that hasn't worked either
14:13
I then ran `ltsp initrd` before booting my client but I cannot login as root
14:15
<quinox>
do you see /etc/shadow getting modified with your desired hash?
14:16
<danboid>
When the clients booting?
14:16
<quinox>
it should happen during booting, but you can check once it's fully booted
14:17
<danboid>
How would I check once booted if I can't login and I can't scrollback?
14:17
I'm trying to troubleshoot LDAP not working
14:18
<quinox>
ah
14:19
there's DEBUG_SHELL you can set to 1, it will put you in a root terminal when errors happen
14:20
<danboid>
I'll give that a go then
14:21
<quinox>
I myself use this one to set a root password: POST_ROOT="echo 'root:something' | chpasswd"
14:21
but there are many ways to Rome, your sed should be okay
14:22
(Assming the hash is fine, the hash algo is supported etc.)
14:23
not being able to log in to debug is tricky
14:24
you can do something like this: one 1 machine run "nc -l 1234", then put POST_INIT_ZZZZZZ="cat /etc/shadow | nc <ip of yuor 1 machine> 1234"
14:25
it sets up a listening process on 1 machine, and it sends data over during booting on the client
14:25
if stuff shows up you'll be able to see the content of /etc/shadow
14:27
if nothing shows up the command might not have triggered, it might not be able to reach your IP, etc
14:28
if you have a CDRom drive you can also try POST_TESTING="eject", it should open the tray during the boot :-)
14:30
<danboid>
I knew there was a reason we should've kept optical drives
14:58
I think I'mm still running an ltsp from 2023. Do I need to upgrade for it to work with Debian 13 images?
15:09
<quinox>
does Debian 13 use dracut?
15:09
If so: LTSP is not yet compatible with that
15:14
if it's from 2023 it should already be the new LTSP I think - works great for ubuntu, I don't know about Debian
15:14
stick around and someone with more knowledge will give a response
15:14
<danboid>
Apparently not. At least one person on the LTSP github forum has said they've got debian 13 working with ltsp
15:15
I mean it appartently doesn'y use dracut
15:15
<quinox>
https://ltsp.org/guides/netconsole/
15:15
do you build from a chroot or a vm?
15:16
I myself have LDAP working, but since I'm using a VM I can usually debug it in there
15:17
<danboid>
vm
15:17
<quinox>
and can you login on the VM using the LDAP?
15:20
<danboid>
For some reason my nslcd config that was working under Ubuntu 20.04 doesn't seem to be working under Debian 13
15:20
Are you using nslcd?
15:22
<quinox>
I'm using libpam-ldap
15:22
<danboid>
I think thats what nslcd uses. You can use it standalone?
15:26
<quinox>
not sure what you mean with standalone; I can log in on my VM using LDAP, and it works for booted LTSP as well
15:27
I have a bindpassword, the rest is all vanilla
16:10danboid has left IRC (danboid!~danboid@remote.salford.ac.uk, Quit: Client closed)
21:58ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)