|03:37||rac__ has left IRC (rac__!71148af6@gateway/web/freenode/ip.22.214.171.124, Ping timeout: 250 seconds)|
|03:38||rac_ has left IRC (rac_!71148af6@gateway/web/freenode/ip.126.96.36.199, Ping timeout: 250 seconds)|
|04:54||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|05:04||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 276 seconds)|
|06:00||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:8d78:d090:dc40:ca8e)|
|06:18||mikkel has joined IRC (email@example.com)|
|06:50||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:8d78:d090:dc40:ca8e, Ping timeout: 260 seconds)|
|07:01||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
|07:04||kjackal has joined IRC (firstname.lastname@example.org)|
|07:50||gdi2k has left IRC (email@example.com, Ping timeout: 276 seconds)|
|08:03||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|08:03||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|09:12||Buho has joined IRC (Buho!533cc51c@gateway/web/freenode/ip.188.8.131.52)|
|09:18||badgerbailey has joined IRC (badgerbailey!31e48b8a@gateway/web/freenode/ip.184.108.40.206)|
Hi, I wonder if someone could help, I installed LTSP-server-standalone, installed the ltsp image I think I setup my 2 onboard lan correctly but I cannot connect to server via virtualbox on my laptop
DHCP timeouts happening
I have a staic IP on the first network port eno1 which connects to my router for outside internet access, on my second eno2 port I set a static IP but the virtualbox doesn't seem to get an IP or begin to download the image
eno1 ststic IP is 192.168.1.50 for outside access, eno2 static IP is 192.168.0 1, anyone have any idea how to test to see where the propblem lies?
badgerbailey: dhcp broadcasts don't go to bridged adapters, if that's what you're asking
That's a #vbox issue though
If you were using an external dhcp server, it would work fine
the guide I followed suggested to set it up this way, and test with a bridged adapter from my windows laptop
Or an internal network vbox client
Are you setting up ltsp for the first time?
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
This is the best guide, if it fit your needs
thanks I'll take a look now
What are your client specs?
cpu/ram and how many?
25 clients running chrome browser and a simple office suite, thats all
my server has xeon e3 1231v2, 32gb ram
badgerbailey: how much ram do your clients have? and what cpu?
I am trying to test with pretty basic thin clients see here: http://www.inctel.com.cn/product/detail/39
It's best if the clients have enough cpu/ram to run the os locally
They'll still be diskless and netbooted, but they won't use the server cpu/ram
We call that "ltsp fat clients", it works much better than ltsp thin clients
ltsp-pnp supports both models out of the box
But if you have already bought the clients and they're allwinner, then no, fat clients won't do for you
Hmm also, those are ARM, right? Did you create an armhf chroot?
okay, before starting from scratch do you know of any guide to help me fix what I have now and check the situation to see if my NIC's are configured correctly?
badgerbailey: do you know that your clients have an ARM cpu and that you need an ARM chroot to boot them?
no i didn't, is it possible to add in this feature or will I need to start from scratch?
It makes things much more difficult for you
And guides more hard to find
How many of those clients do you already have?
only 1 for test so its not an issue to change, I'm just trying to keep the costs down, its for a charity so I am bearing the whole cost of this project
These things are like raspberry pis
They have special processors and it's more hard to manage them
It's much much easier if you have PCs as clients, x86 based
For example, those are x86: http://www.inctel.com.cn/product/35
So what I'm suggesting to you is this:
1) Start from scratch and follow the ltsp-pnp guid
2) Test with some PCs that you have around to verify that fat clients work best
3) Buy x86 clients as your ltsp clients
(and throw away that ARM client that you have, it's not worth the trouble)
these are pretty cheap also, I guess x86 x64
To evaluate clients, mark their CPUs and look it up in this site:
So the clients that you said now, have 909 score
They will work. But my 7 year old laptop has 1500 score.
So they're similar to buying an 8-10 year old computer...
For *light* surfing, 1000 score is acceptable. Normally we only buy new clients with score > 2000.
E.g. core i3 has 5000 score
okay got it
Btw with ltsp fat clients, your server can be a simple PC, it doesn't need to be expensive
okay, thanks for your info
Hello mr alkisg!
Haha, hello Hyperbyte, it looks like I'm the only one he wants to speak to :D
|10:01||eu^ip-92-42-113- has joined IRC (eu^ip-92-42-113-!5c2a716b@gateway/web/freenode/ip.220.127.116.11)|
problem: epoptes verify error:num=18:self signed certificate
..and client is not visible by epo-server...but Successfully fetched certificate from 192.168.1.140:789
Do you have something weird with regards to your root certificates?
Is your computer date/time ok?
|10:09||lbssousa has joined IRC (firstname.lastname@example.org)|
|10:10||badgerbailey has left IRC (badgerbailey!31e48b8a@gateway/web/freenode/ip.18.104.22.168, Quit: Page closed)|
time from internet
epoptes-client run great on lubuntu 15.04 but this problem is with ubuntu 15.10
eu^ip-92-42-113-: what is your server called? Did you put "server" in /etc/hosts?
yes same on ubuntu & lubuntu...
OK, can you try this from your client?
This is a single command, copy/paste it
If you run that, can you then see the client in the epoptes UI?
ok server can see my ub 15.10 great thnx ;)
This was temporary
You need to upgrade your epoptes client to 0.5.10
Use the epoptes PPA to do that
Do you know how?
put ppa to apt-get, update, iremove old ver, instal new?
sudo add-apt-repository ppa:epoptes; sudo apt-get update; sudo apt-get dist-upgrade
The problem was in socat, we've fixed it in newer epoptes versions
|10:29||robb_nl has joined IRC (email@example.com)|
|10:39||kjackal_ has joined IRC (firstname.lastname@example.org)|
|10:39||kjackal has left IRC (email@example.com, Read error: Connection reset by peer)|
|10:58||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 260 seconds)|
|11:00||adrianorg has joined IRC (email@example.com)|
|11:03||eu^ip-92-42-113- has left IRC (eu^ip-92-42-113-!5c2a716b@gateway/web/freenode/ip.22.214.171.124, Ping timeout: 250 seconds)|
|11:20||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 244 seconds)|
|11:22||adrianorg has joined IRC (email@example.com)|
|11:34||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 276 seconds)|
|11:36||adrianorg has joined IRC (email@example.com)|
|11:36||Statler_ has joined IRC (Statler_!~Georg@p54BFB071.dip0.t-ipconnect.de)|
ltsp-localapps seems not to retrun exit code?
something like "ltsp-localapps firefox || firefox" doesn't work
I have x2go-clients on the same server, where ltsp-localapps cannot have success
in these case I want to define a "fallback" to the serverside app
|11:42||robb_nl has left IRC (firstname.lastname@example.org, Quit: I'm gone, bye bye)|
|11:45||xenthree3 has joined IRC (email@example.com)|
|11:45||xenthree3 has left IRC (firstname.lastname@example.org)|
|11:45||kjackal_ has left IRC (email@example.com, Ping timeout: 252 seconds)|
|11:48||Faith has joined IRC (Faith!~paty_@unaffiliated/faith)|
|11:51||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 260 seconds)|
|11:52||adrianorg has joined IRC (email@example.com)|
|12:07||Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)|
|12:12||GodFather_ has joined IRC (GodFather_firstname.lastname@example.org)|
|12:14||GodFather_ has left IRC (GodFather_email@example.com, Client Quit)|
|12:14||GodFather_ has joined IRC (GodFather_firstname.lastname@example.org)|
|12:14||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 260 seconds)|
|12:14||GodFather_ is now known as GodFather|
|12:15||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|12:16||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e420:9361:bc6d:ca35)|
|12:17||adrianorg has joined IRC (email@example.com)|
|12:17||GodFather is now known as GodFodder|
|12:56||Leolo_2 has left IRC (Leolo_2firstname.lastname@example.org, Ping timeout: 260 seconds)|
|13:28||gdi2k has joined IRC (email@example.com)|
Statler_: You're right, it doesn't, but there's no easy way to make it to.
ltsp-localapps just sets an xprop, then asynchronously, the command is run.
There isn't a good way to pass the exit code of the program back to ltsp-localapps.
does it need to be async?
The thin client doesn't have an ssh server running on it. So the only method of communication to go back from the server to the client is via the X server itself.
X itself doesn't have any provision for an "exec" function, so what we did was define an X prop that sits on the root window.
We have a "server" that runs on the thin client, that listens for changes to this property
On the LTSP server, you essentially just change this property with the name of the program you want to execute.
On the thin client, this server process that's listening to the property changes then executes the program requested.
So the ltsp-localapps script isn't actually doing any executing, it's just setting an xprop.
So long as it succeeds at setting the xprop, ltsp-localapps "succeeds"
if the server process running on the thin client can't execute the program, the ltsp-localapps script doesn't know about it.
|13:45||jamorais has joined IRC (jamorais!bb4c818e@gateway/web/freenode/ip.126.96.36.199)|
ok! Good morning!
so to make it async, you'd need the script to wait for the client to send something back over ssh or whatever, maybe look for a file to be touched, with a timeout, which could get error prone
It would be much harder to do, yes.
My english is very poor, but let's go to chat
woulnd't be hard to implement, but would be hard to make reliable, and would likely slow down the non-thin clients a lot
This IRC is about Epoptes?
jamorais: It's about LTSP, and Epoptes. I don't know anything about Epoptes myself, however.
But ask your question, and hang around several hours for the answer, and hopefully when someone who does know sees it, they'll respond.
There any version of Epoptes that have options put time on clients?
You mean set the clock?
Yes! thirty minutes for exemple
Here is a computers labs
Oh, you mean set a login limit.
I don't know. alkisg would be the fellow to ask.
Here labs computers at school
alkisg would know. Hang around and wait for him to become active.
And the students, do not stop use a computers
Here I am testing Epoptes wiht LTSP.
|13:57||jamorais has left IRC (jamorais!bb4c818e@gateway/web/freenode/ip.188.8.131.52)|
|14:16||ben_roose has joined IRC (firstname.lastname@example.org)|
jamorais, it wasn't an epoptes issue, the easiest way to do what you wanted would be to set a screensaver that exited the session, i.e. an ltsp issue :)
so much for "hang around several hours"
|14:22||mikkel has left IRC (email@example.com, Quit: Leaving)|
Statler_: it's possible to patch ltsp-localapps / ltsp-localappsd to support an additional LTSP_COMMAND_RESULT xprop that travels the other way
If you send a proper implementation of that, I don't see why it wouldn't get accepted
alkisg: Problem with that would be, you'd somehow have to queue results.
how quickly does the client side get the message?
right now, if you do "ltsp-localapps xxx; ltsp-localapps yyy; ltsp-localapps zzz", all 3 will launch fine.
sbalneav: one easy way would be to use mktemp to get a random LTSP_COMMAND_RESULT_XXXXX name, and pass it to ltsp-localappsd
sbalneav: no it would still work fine since ltsp-localapps would wait for the reply before exiting
||cw: many processes can run in parallel though
Even from different user shells
||cw: That means you can only run one localapp at a time, though.
alkisg: Not sure how we'd do the server side, registering and listening for xprops.
Similar to how ltsp-localappsd does it, i.e. wait for LTSP_COMMAND_RESULT_XXXX to change, but only for 1-2 seconds, and return failure if the timeout passes
would a file be simpler?
I see this as a minor feature request, so no worries I'm not suggesting to implement it :D
But I wouldn't object to a proper patch that does implement it if Statler_ wanted to do it
|14:33||MRH2 has joined IRC (MRH2!~Thunderbi@184.108.40.206.in-addr.arpa)|
server touches a temp file, sends filename with the xprop, client deletes file, server sees it and returns success, but with a X second timeout where server deletes the file and returns fail
another way was to clear determine if the client is really a ltsp-client
||cw: yup, ssh can be used for that, listening on a socket is easy too
general q does the greek schools ppa get updated in to the main ltsp package?
localapps could also be implemented by listening to the ltsp's ssh stdin, i.e. right after the "echo LTSPROCKS" part
MRH2: I'm updating the greek schools ppa whenever there are significant changes in ltsp, yes
is there something in the environment variables that I can evaluate to determine if I have a ltsp-client or something else?
sorry i meant the other way around as the greek ppa seems to lead at least when i last tested the 2. or does development from the greek schools go directly in to ltsp.
MRH2: I'm an ltsp developer and I'm also maintaining the greek schools ppa. When some significant work is done in ltsp, I'm releasing new versions to the PPA. After some time, distros also get it. For Ubuntu 16.04, those two are temporarily in sync.
Statler_: echo $LTSP_CLIENT
ok cool so u release to both
i was wondering how they stay in sync
I'm not in charge of releasing to any distros, those happen by their maintainers
Although I'll probably start to maintain ltsp in ubuntu since 16.04...
tank you alkisg
I see my problem: I'm via x2go logged in ;)
I must take a thin client to test the environment
i guess i see development more on ur side and concerned about things becoming diverged
even an official ltsp-non-chroot
MRH2: all my ltsp development goes upstream, or locally in "sch-scripts", none of it goes only to the ppa
thanks for clearing that up alkisg :)
|15:08||lmds_ has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|15:18||metaf5 has left IRC (email@example.com, Ping timeout: 260 seconds)|
|15:26||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:e420:9361:bc6d:ca35, Quit: No Ping reply in 180 seconds.)|
|15:27||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2)|
|15:31||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2, Client Quit)|
|15:32||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2)|
|15:34||GodFodder has left IRC (GodFodderfirstname.lastname@example.org, Remote host closed the connection)|
|15:45||GodFather has joined IRC (GodFatheremail@example.com)|
|16:22||Leolo_2 has joined IRC (Leolo_2firstname.lastname@example.org)|
|16:28||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2, Ping timeout: 260 seconds)|
|16:34||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e420:9361:bc6d:ca35)|
|16:35||Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Remote host closed the connection)|
|16:40||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 276 seconds)|
|16:45||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:e420:9361:bc6d:ca35, Ping timeout: 260 seconds)|
|16:48||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2)|
|16:49||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|17:28||lmds_ has joined IRC (email@example.com)|
Hi, has anyone played with Edubuntu Live USB?
vsuojanen: edubuntu isn't really active any longer
is it still ..ok ? :)
No, it didn't even ship a 16.04 version
That said, it's really easy to ship a live ltsp in a usb stick
|17:36||Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)|
it was 6th or 7th in google results for 'ltsp'
alkisg: I tried the live ltsp method and I liked it. There were cons also
vsuojanen: I'm usually having a full ltsp installation in a usb stick, but instead of using /opt/ltsp/images/i386.img, I'm directly exporting /dev/sdb1, so that more caching is done, and it's a lot faster that way, and saves a lot of space
it's easy and fast to setup but there is ldm that needs connection to the server and then there is grub with default recovery feature. it has some annoyant issue with the server when it boots overlayfs
LDM on the stick? No, it's using lightdm
the annoyant issue is default grub recovery
I've never seen the issues you say, I don't know what method you used
I've never used edubuntu's live ltsp usb stick method
I followed your mehthod... it was couple months back that you mentioned that
Was it the "regular installation" method, or the "nbd image in a stick" method? looking...
Ah, that's the cow method, to prevent the stick from being overused
anyways i did not use ldm but switched to lightdm. yes. nbd image in stick method :)
No no that's a third method
It's a regular installation with cow booting
It's hard to set it up properly, but it's very flexible
To omit LDM, you create /etc/lts.conf with a couple of directives
That way you can use lightdm in cow mode
i would set up it for first ltsp installation or demo
KEEP_DEFAULT_DISPLAY_MANAGER=True or something
Also I don't see why grub recovery would be activated, I never got that bug either
to me it didn't activate grub recovery because grub or ubuntu/debian developers have made default GRUB_RECORDFAIL_TIMEOUT=30 when recordfail=1. and grub or ubuntu sets recordfail=1 in /etc/grub.d/00-header
so the annoyance was 30s timeout for booting after the very first boot
i did not go further with such small issue but I think that was related to overlayfs and ubuntu grub2 configs
It sounds reasonable... I didn't use the ubuntu grub2 configuration that's probably why I didn't see it
It would be easy to remove recordfail, or to reset it from the ltsp initramfs script
yeah. I really missed syslinux when i searched the reason for that issue
|18:04||MRH2 has left IRC (MRH2!~Thunderbi@220.127.116.11.in-addr.arpa, Quit: MRH2)|
|18:39||Statler_ has left IRC (Statler_!~Georg@p54BFB071.dip0.t-ipconnect.de, Remote host closed the connection)|
can things like LDM_FORCE_SESSION=xfce get set in lts.conf?
Leolo_2: Is that currently something we honour?
Yup to both questions :)
Actually putting it in lts.conf is exactly what it was coded for
I can't remember all the lts.conf variables anymore :D
I don't think anyone ever has, we didn't even manage to document all of them!
sbalneav: external? what's that for?
So, one of the issues is always the C coding.
we're hoping to reduce it down to libpam-sshauth, but then I got the brilliant idea.
"Can't do it. I hate the switch statement." Hahaha
What if I wrote a pam module.... that wasn't a pam module?
And code the rest of it in shell?
Instead, it just acts as a shim... and passes pam messages, via stdin and stdout, to some external program
paste: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
I was thinking to implement ldm in shell, and keep the greeter in python...!
It's not complete, but with libpam_external, and that bit of python, it does most of what libpam_sshauth does.
And all the ssh-y bits are in python.
That's a very good idea :)
I've got lightdm-webkit(2)-greeter whipped into shape
So we can write greeters in html/js
I've now got (or in the process of getting) libpam_external and libnss_external close to being in testable condition, so we can script PAM and NSS stuff in scripting language.
|19:46||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
So, apart from nss/pam_external all the stuff that LTSP6 could use would be... scripts.
We shall see. Some more work left to do. Some, haha. Lots.
But, I'm excited.
I'm writing the man page for libpam_external now.
Cool!! Hopefully me and vagrantc will make it to debconf16 and make some progress with the pam integration there
|19:49||* alkisg needs to go pick up the kids, later! :)|
ah, yeah, sa
|19:59||lbssousa has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|20:02||epoptes_user9 has joined IRC (epoptes_user9!b187c003@gateway/web/freenode/ip.18.104.22.168)|
|20:03||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2, Ping timeout: 260 seconds)|
alksig : having PAM run shell code is about as secure as something very unsecure
|20:11||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:790f:ff4d:499c:57c2)|
Leolo_2: There are already several pam modules that execute shell code.
One ships as part of pam.
pam_exec, pam_script, etc.
In fact, pam_script sets PAM_AUTHTOK and PAM_OLDAUTHTOK as environment variables :D
Which, I'd like to point out, I'm not doing. :D
If you have any comments or would like to make suggestions to the code, feel free. I'm developing it now.
just the general idea that PAM is running a shell script rubs me all wrong
yeah, pam_exec can do that... but pam_exec can't authorize anyone
|20:17||* Leolo_2 shakes his head in disbelief|
what is the world coming to !
So, do you have an *actual* objection, or do you just not like it?
Like I say, have a look at the code, and if you feel something's not right, I'm all ears.
I thought it was clear from the begining that it was "just not like it"
I've been reading LTSP code for the last week. It's very well writen
I just feel shell scripts are to fragile for something as important as PAM authentification
I am perfectly prepared to be wrong on this point
No, you said it was "about as secure as something very unsecure". I'm asking, specifically, how calling an externel helper program to do the authentication is any less secure than, say writing a pam module in pure C and verifying there's no null pointer exceptions, buffer overflows, etc?
C programs get static checks, shell scripts don't
so typos are caught early
C programers know about security issues, and while coding a PAM module (one hopes) put them utmost in their mind
I did, when I wrote libpam_sshauth
I just recently had to file a security bug for unintended root escalation in the module.
yeah, then you get libpam_sshauth which is pretty complex and depends on openssh not having errors in it (safish bet)
So? Libpam_ldap is pretty complex and depends on ldap not having errors in it :D
Errors happen, regardless. And being able to write an authentication module in a modern scripting language without buffer overflow probelms, proper exception handling, etc. Might, in the long run, be *more safe* than custom-coding a pam module in C from scratch every time.
I'm simply playing devils advocate here.
and I'm listening
your points are not invalid
To the extent that libpam_external would be "error free" and "secure", it then places any potential bugs in an authentication mechanism in a much-easier-to-understand-and-debug program than wading through a PAM module's C source.
if I have an issue with ssh sockets and fuse.unionfs, who should I file a bug with?
or do I just not bother - pretty sure everyone is going to say "not our problem"
That the source for it?
What's the issue?
ssh -S socket does a bind/listen on socket.RANDOM it then does link( "socket.RANDOM", "socket" ); unlink( "socket.RANDOM" )
this fails to create a usable socket
ok, is that the source? If so, I can dig into it this long weekend, and try to find where the problem is.
Always easier to get a problem looked at if you can a) identify exactly where in the code the problem is or b) (ideally) include a patch in the bug report :D
well if I change the link/unlink to rename, it works
in ssh? Unlikely they'll accept a patch; the openssh guys are very unwilling to accept any input from outside the "golden circle" of ssh devels.
So it'd be far easier to find out what in the unionfs-fuse semantics causes it to fail, and fix that.
We've tried before to get things looked at in ssh here in ltspland :D
another work around would be to have LDM_SSH_EXEC=/opt/openssh/ssh
and have plugins/ssh/ssh.c respect that
(11:11:00 μμ) Leolo_2: alksig : having PAM run shell code is about as secure as something very unsecure ==> security isn't in the language, it's in the programmer
Leolo_2: btw, can't you use some more recent kernel now that overlayfs is mainlined? doesn't centos have backported kernels?
!learn alkisg-todo as test the null cipher with https://launchpad.net/~yoda-jazz-kc/+archive/ubuntu/hpn-ssh
The operation succeeded.
alkisg-todo: (#1) support xnbd-proxy for local caching: https://bitbucket.org/hirofuchi/xnbd/wiki/Home#!scenario-2-simple-proxy-server-distributed-copy-on-write, or (#2) Support UEFI, or (#3) support for per-user login commands in lts.conf, or (#4) put panic=60 in the kernel cmdline, or (#5) document bind-interfaces, or (#6) test aes-ni instruction set for faster ssh, or (#7) test the null cipher with https://launchpad.net (1 more message)
!forget alkisg-todo 6
The operation succeeded.
alkisg - maybe
iirc, elrepo has more recent kernels
Leolo_2: It would make it more aligned with ltsp upstream
E.g. ltsp-update-image --cleanup also uses overlayfs, it's not only about the initramfs
How are things looking so far? Ready to ditch ltsp and go for drbl yet? :)
everything is working to my satisfaction
next week at some point I deploy
Nice! If you have any patches that should make it upstream, either under the shared dir or under redhat/ etc, do file bug reports/merge requests etc
one thing is that some of the problems are the LTSP+CentOS is too old (nbd v2 for instance)
some of the problems is that LTSP does things in ways I don't like, so I do them myself the way I like (/etc/dhcp/dhcpd.conf vs /etc/ltsp/dhcpd.client)
|22:10||* alkisg thinks dnsmasq should be the default instead of isc-dhcp...|
and some problems are because of my current set up (select french vs english based on the province a host boots in)
or at least someone that uses isc-dhcp, should support it like we do with `ltsp-config dnsmasq`
and further problems because I'm an old crmugdeon
btw ltsprepo.s3.amazonaws.com seems to be gone
http://ltsprepo.s3.amazonaws.com/rpm/el6 at least doesn't work
I don't think we have anyone at the centos/fedora/rhel etc front anymore
The only one still working with RPMs would be cyberorg, for openSUSE
So I've never even heard of those repositories
I think opensuse does offer a cross-distro build service that comes with a repository that you might be able to use...
|22:18||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 246 seconds)|
|22:24||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|22:26||GodFather has left IRC (GodFatheremail@example.com, Remote host closed the connection)|
|22:27||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|23:27||* Leolo_2 makes the mistake of running dracut -v|
all that cruft... back in my day you could boot off a floppy !
so nbd v3 doesn't work on CentOS 6
nbd-client runs fine
dd if=/dev/nbd9 of=/dev/stdout count=1024 bs=1 | hexdump -C