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


Channel log from 29 March 2018   (all times are UTC)

00:58mmarconm has joined IRC (mmarconm!~mmarconm@200.163.96.109)
00:58mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
02:00jgee has left IRC (jgee!~jgee@181.56.72.152, Ping timeout: 264 seconds)
04:54quinox1 has joined IRC (quinox1!~quinox@ghost.qtea.nl)
04:56quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Ping timeout: 248 seconds)
04:57mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)
05:34Statler|Home has joined IRC (Statler|Home!~Georg@p54897C6F.dip0.t-ipconnect.de)
06:36ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:39Natureshadow has joined IRC (Natureshadow!~Naturesha@commu.teckids.org)
06:44evan has joined IRC (evan!c5e79336@gateway/web/freenode/ip.197.231.147.54)
06:44
<evan>
Hi Alkisg
06:44evan is now known as Guest87610
06:45
<Guest87610>
we've sort've got the pxe with uefi boot working, it seems to load the bootx64.efi image
06:49
error: no such device: "uuid of the ltsp server"
06:50
error: file '/boot/vmlinuz-4.13.0-041300-generic' not found
06:50
alloc magic is broken at 0x7bafda0: 7b5c33c0
06:50
aborted. press any key to exit
07:45
<alkisg>
Guest87610: yeah uefi can be tricky; btw make sure you're using an uefi capable kernel
07:46
Guest87610: I'm available for hire for any ltsp-related task, if you end up needing someone
07:46
E.g. "add uefi support in upstream ltsp"
07:48
<fiesh>
I'll hire you again if you can solve the task "make uefi go away as an industry standard" :-)
07:49
<alkisg>
Haha, I'd do that for free if I were able to! :D
07:49
<fiesh>
hehe
07:53Statler|Home has left IRC (Statler|Home!~Georg@p54897C6F.dip0.t-ipconnect.de, Remote host closed the connection)
07:54
<Guest87610>
I believe I am using an uefi capable kernel atm
07:55
it's almost like it is trying to boot into the main server
07:55
instead of using a network boot
07:58
also have you tried ipxe boot?
07:58
<alkisg>
When I tried uefi, I had managed to do it with 3 different ways, ipxe, syslinux and grub
07:58
And some combinations of those
07:58
Each had its benefits and its drawbacks
07:59
That was 3 years ago if I remember well...
08:00
<Guest87610>
btw
08:00
I would try and get my log files to you
08:01
with my issue with the i915 driver not working correctly with legacy boot on this particular machine
08:01
but it goes into a self testing loop
08:01
so I literally cannot do anything
08:02
I must mention that when I plug in an external display it works, but the screen on the all in one unit goes into a self testing loop
08:02
<alkisg>
There are many ways to log with persistence, even over the network
08:03
If you want me to work on it, I'm sure we'll be able to find ways to solve it
08:19Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de)
09:14Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de)
09:14Statler_Office has left IRC (Statler_Office!~Georg@gwrz3.lohn24.de, Ping timeout: 276 seconds)
10:04sutula has left IRC (sutula!~sutula@207-118-154-150.dyn.centurytel.net, Ping timeout: 264 seconds)
10:04sutula has joined IRC (sutula!~sutula@207-118-154-150.dyn.centurytel.net)
10:24Statler__ has joined IRC (Statler__!~Georg@gwrz3.lohn24.de)
10:25Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Ping timeout: 240 seconds)
10:30Statler__ has left IRC (Statler__!~Georg@gwrz3.lohn24.de, Ping timeout: 240 seconds)
10:31Statler__ has joined IRC (Statler__!~Georg@gwrz3.lohn24.de)
11:39lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
12:22Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
13:27Statler__ has left IRC (Statler__!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
13:35ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:54Statler|Home has joined IRC (Statler|Home!~Georg@p54897C6F.dip0.t-ipconnect.de)
14:48Natureshadow has left IRC (Natureshadow!~Naturesha@commu.teckids.org, Quit: Gateway shutdown)
15:47Guest87610 has left IRC (Guest87610!c5e79336@gateway/web/freenode/ip.197.231.147.54, Quit: Page closed)
16:26vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:05lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
17:35bitchecker has left IRC (bitchecker!~bitchecke@31.131.20.132, Remote host closed the connection)
17:36bitchecker has joined IRC (bitchecker!~bitchecke@31.131.20.132)
17:36Natureshadow has joined IRC (Natureshadow!~Naturesha@commu.teckids.org)
17:41bitchecker has left IRC (bitchecker!~bitchecke@31.131.20.132, Quit: bye!)
17:41bitchecker has joined IRC (bitchecker!~bitchecke@31.131.20.132)
17:48
<alkisg>
vagrantc: is it policy compliant if we move our policy-rc.d handler to ltsp-client itself, instead of server/ltsp-build-client?
17:49
It will make it easier to just install ltsp-client over existing chroots, without having to bother with "oh what's the difference from an ltsp-build-client chroot"
17:50
And better yet, instead of using LTSP_HANDLE_DAEMONS, to just check if we're in a chroot or not
18:19lucascastro has joined IRC (lucascastro!~lucas@200.141.207.18)
18:40
<vagrantc>
alkisg: no
18:41
<alkisg>
Meh, update-alternatives and everything and it's still not policy compliant :D
18:41
<vagrantc>
alkisg: it's the obvious thing to do, but packages aren't allowed to install it
18:41* vagrantc double-checks
18:42
<vagrantc>
hrm. not mentioned in debian policy ...
18:42
it was definitely somewhere
18:58lucas_ has joined IRC (lucas_!~lucas@170.78.53.20)
18:58lucascastro has left IRC (lucascastro!~lucas@200.141.207.18, Read error: Connection reset by peer)
19:07lucascastro has joined IRC (lucascastro!~lucas@200.141.207.18)
19:07lucas_ has left IRC (lucas_!~lucas@170.78.53.20, Read error: Connection reset by peer)
19:14
<alkisg>
vagrantc: https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt says:
19:14
The /usr/sbin/policy-rc.d file *must* be managed through the alternatives system (/usr/sbin/update-alternatives) by any packages providing it.
19:14
<vagrantc>
oh, then maybe we can
19:14
we might even be able to leave it out entirely with systemd
19:15
<alkisg>
In the future, maybe, but currently (e.g. Ubuntu 18.04) I've seen packages break chroot installations without it
19:15
<vagrantc>
hrm.
19:15
was really hoping to drop it... it's an ugly hack
19:15
<alkisg>
install mate-desktop => installs blueman => tries to restart dbus => dies
19:16
<vagrantc>
sure
19:16
<alkisg>
I'm thinking that if we want to replace ltsp-build-client with something newer, the necessary functionality should be moved in ltsp-client,
19:16
even if it's administrator-invoked, like ltsp-config client or something, if policy mandates that...
19:17
<vagrantc>
agreed
19:17
<alkisg>
Or we could drop chroot support and only support lxc or VMs, where we won't mind about services being started :D
19:18
<vagrantc>
i think ltsp-build-client or a replacement should be reduced to very minimal functionality
19:18
what's there now is overengineered
19:19
<alkisg>
kvm /path/to/iso /path/to/disk; install; ltsp-update-image /path/to/disk...and we can use standard installers
19:20
<vagrantc>
it's not as automatable
19:20* alkisg wonders if lxc works cross-arch, like, running an armhf chroot in an amd64 host, without having issues if dbus wants to restart itself... stgraber? Eh, stgraber no longer here :D
19:20
<vagrantc>
yes, lxc works if you've got qemu-user-static installed correctly
19:20
<alkisg>
And does it solve the services issue?
19:20
<vagrantc>
ah, but as far as daemons restarting...
19:20
it *should* solve that issue
19:20
<alkisg>
Is lxc relatively cross-distro?
19:21
<vagrantc>
no
19:21
<alkisg>
Meh. Maybe docker then.
19:21
<vagrantc>
i like just gutting/rewriting ltsp-build-client better
19:22
<alkisg>
Then we'll still need the policy-rc.d stuff, which means, let's move it into the client...
19:40lucas_ has joined IRC (lucas_!~lucas@200.141.207.18)
19:40csguy has left IRC (csguy!931a646a@gateway/web/freenode/ip.147.26.100.106, Quit: Page closed)
19:40lucascastro has left IRC (lucascastro!~lucas@200.141.207.18, Read error: Connection reset by peer)
19:51
<vagrantc>
alkisg: i'm not sure if it differs, but hopefully /usr/share/doc/init-system-helpers/README.policy-rc.d.gz is a better source for current status
19:54
/usr/share/doc/init-system-helpers/README.policy-rc.d.gz
19:55
ops
19:55
what i meant was:
19:56
invoke-rc.d: could not determine current runlevel
19:56
invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block.
19:56
saw this on a chroot ... but it's probably not got any init system installed
19:56
<alkisg>
Yeah that doesn't sound like policy-rc.d was involved
19:57
<vagrantc>
yes, but it's doing what we want without policy-rc.d
19:58
simple enough to add policy-rc.d and just use the alternatives system
19:58
i think when it was initially implemented, it wasn't possible for packages to use it with the alternatives system or something
20:22Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:56lucas_ has left IRC (lucas_!~lucas@200.141.207.18, Remote host closed the connection)
20:57lucas_ has joined IRC (lucas_!~lucas@200.141.207.18)
21:07ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:16lucas_ has left IRC (lucas_!~lucas@200.141.207.18, Ping timeout: 248 seconds)
21:45lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
21:53lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Ping timeout: 248 seconds)
21:58lucascastro has joined IRC (lucascastro!~lucas@138.68.106.79)
22:25lucascastro has left IRC (lucascastro!~lucas@138.68.106.79, Remote host closed the connection)
22:43Statler|Home has left IRC (Statler|Home!~Georg@p54897C6F.dip0.t-ipconnect.de, Remote host closed the connection)
22:44lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
22:46lucas_ has joined IRC (lucas_!~lucas@138.68.106.79)
22:49lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Ping timeout: 256 seconds)
22:51lucas_ has left IRC (lucas_!~lucas@138.68.106.79, Client Quit)
22:51lucascastro has joined IRC (lucascastro!~lucas@138.68.106.79)
23:25ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
23:39vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)