00:59 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
01:29 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
01:36 | gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.27, Ping timeout: 268 seconds) | |
01:45 | gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.28) | |
07:57 | woernie has joined IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de) | |
09:09 | woernie has left IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de, Remote host closed the connection) | |
09:30 | statler has joined IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de) | |
12:28 | woernie has joined IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de) | |
12:55 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:8935:6f19:56e7:ea3c) | |
13:10 | toile has joined IRC (toile!b0fb57d3@gateway/web/cgi-irc/kiwiirc.com/ip.176.251.87.211) | |
13:34 | kidar has joined IRC (kidar!29904eb5@41.144.78.181) | |
13:38 | kidar has left IRC (kidar!29904eb5@41.144.78.181, Remote host closed the connection) | |
14:05 | toile has left IRC (toile!b0fb57d3@gateway/web/cgi-irc/kiwiirc.com/ip.176.251.87.211) | |
14:33 | kidar has joined IRC (kidar!29904e56@41.144.78.86) | |
14:33 | <kidar> Hi I want to know if I can run use ltsp on fedora 30?
| |
14:39 | kidar has left IRC (kidar!29904e56@41.144.78.86, Remote host closed the connection) | |
17:53 | GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 276 seconds) | |
17:58 | kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:8935:6f19:56e7:ea3c, Ping timeout: 246 seconds) | |
18:09 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
19:35 | statler has left IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de, Remote host closed the connection) | |
20:50 | woernie has left IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de, Remote host closed the connection) | |
21:55 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
22:22 | <alkisg> vagrantc: your snponly.efi worked fine, although in my client it needed 20 seconds to show the ipxe menu; that reminded me that I had applied a patch from an upstream developer in "my" snponly.efi, to bypass some super slow UEFI cryptographic functions, and show the menu in 1 second...
| |
22:23 | But if you're becoming the new ipxe maintainer, yey, we can do things like that! :D
| |
22:26 | (so, I meant, that your snponly.efi was the same as the normal upstream one; and that your packaging is fine; just my client is bad and needs a workaround)
| |
22:53 | <vagrantc> alkisg: i touched almost all the open bugs on ipxe and locally built a version from current upstream git ... so i'm dangerously close to maintaining it ...
| |
22:53 | alkisg: that said, i'd probably have a strong leaning for most patches to land upstream first
| |
22:53 | alkisg: i'll ask waldi about maintainence and/or co-maintenance or something
| |