01:45 | lee has left IRC (lee!~lee@loathe.ms, Ping timeout: 252 seconds) | |
01:46 | lee has joined IRC (lee!~lee@loathe.ms) | |
02:07 | fiesh has left IRC (fiesh!~fiesh@hq.wsoptics.de, Ping timeout: 276 seconds) | |
02:17 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
02:44 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Ping timeout: 256 seconds) | |
02:52 | fiesh has joined IRC (fiesh!~fiesh@hq.wsoptics.de) | |
05:15 | nehemiah has left IRC (nehemiah!~nehemiah@137.26.129.150, Ping timeout: 246 seconds) | |
05:54 | <alkisg> fiesh: my gentoo client here lost its ip as well
| |
05:54 | That's good news, it's reproducible, so it's a matter of time to find which gentoo service is removing the ip
| |
05:55 | eth0 is still UP, but it no longer has an ipv4 address
| |
06:09 | nehemiah has joined IRC (nehemiah!~nehemiah@137.26.129.150) | |
06:20 | <alkisg> I'll do this test today: leave it on without a user logged in, and with `ifconfig` and `ip` binaries replaced with a script of mine that does nothing except than log that they were called, along with ps faux
| |
06:20 | So if it's an initscript calling ifconfig eth0 0.0.0.0, I should be able to pinpoint it by tomorrow morning...
| |
06:47 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:40 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3106:a00:20f1:d03:a77a:e1a) | |
09:52 | Chris___ has joined IRC (Chris___!d9141f22@gateway/web/freenode/ip.217.20.31.34) | |
10:00 | Chris___ has left IRC (Chris___!d9141f22@gateway/web/freenode/ip.217.20.31.34, Ping timeout: 260 seconds) | |
11:32 | vlt has left IRC (vlt!~vlt@2a01:488:66:1000:57e6:5dd1:0:1, Ping timeout: 276 seconds) | |
11:36 | vlt has joined IRC (vlt!~vlt@2a01:488:66:1000:57e6:5dd1:0:1) | |
11:43 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
12:04 | lee has left IRC (lee!~lee@loathe.ms, Ping timeout: 240 seconds) | |
12:05 | lee has joined IRC (lee!~lee@loathe.ms) | |
12:25 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
12:29 | lee has left IRC (lee!~lee@loathe.ms, Ping timeout: 264 seconds) | |
12:31 | lee has joined IRC (lee!~lee@loathe.ms) | |
14:24 | krlos has joined IRC (krlos!c9d8bc6e@gateway/web/freenode/ip.201.216.188.110) | |
14:24 | <krlos> Good morning
| |
14:25 | can anybody help me ?
| |
14:31 | <||cw> you have to ask a question first...
| |
14:34 | <krlos> LTSP can be configured so that clients start with the hard disk instead of the network card?
| |
14:46 | LTSP can be configured so that clients start with the hard disk instead of the network card?
| |
14:50 | <alkisg> !win32-loader
| |
14:50 | <ltsp> win32-loader: win32-loader.exe adds a "PXE - Network boot" option to the Windows boot manager. It's developed for Debian and it uses http://ipxe.org for the network booting. Download it from http://ftp.debian.org/debian/tools/win32-loader/stable. More info at http://goo.gl/FPD7Zv
| |
14:50 | <alkisg> !ipxe
| |
14:50 | <ltsp> ipxe: iPXE is the successor to the etherboot/gPXE project, and can be used to netboot clients that don't have a NIC ROM with a PXE stack. To add it to grub, see !grub-ipxe. To add it to the Windows boot loader, see !win32-loader. To download floppy, CD or USB images, visit http://ipxe.org or install the ipxe package.
| |
14:51 | <alkisg> krlos: do you mean those?
| |
14:58 | <fiesh> alkisg: great! it seems the hard-wired ip address is doing fine, at least my client is still running
| |
14:58 | <krlos> ok thanks. For linux enviroment clients ?
| |
14:58 | <fiesh> if it's not crashed by tomorrow, I know for sure that it's dhcp
| |
15:02 | <krlos> ok thanks. For linux enviroment clients ?
| |
15:07 | alkisg: I need to boot the clients with hard disk and environment linux, will this be possible?
| |
15:08 | krlos has left IRC (krlos!c9d8bc6e@gateway/web/freenode/ip.201.216.188.110, Quit: Page closed) | |
15:09 | krlos has joined IRC (krlos!c9d8bc6e@gateway/web/freenode/ip.201.216.188.110) | |
15:10 | <krlos> need to boot the clients with hard drive and linux environment, will this be possible?
| |
15:10 | I need to boot the clients with hard drive and linux environment, will this be possible?
| |
15:15 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection) | |
15:18 | <alkisg> krlos: can you write a full paragraph of what you want to do?
| |
15:19 | Because "hard disk and environment linux" means "install any linux distribution you like; debian, ubuntu, whatever, without ltsp"
| |
15:20 | fiesh: great, then we can slowly do tests to see exactly what in gentoo is that decides to unset the ip after a day
| |
15:22 | <||cw> krlos: a more generic option is to modify the pxelinux.cfg files on your server to default to local disk with a timeout. that way you don't have to modify client OS boot menus
| |
15:23 | <alkisg> ||cw: did you understand what he wants? :)
| |
15:23 | I'm still not sure if he's asking to write the squashfs image to the client disk, or to boot with ipxe, or just to not use ltsp at all
| |
15:24 | <||cw> alkisg: from the first Q, just that LTSP would be optional, local boot by default and choose ltsp as needed
| |
15:24 | <alkisg> I can't say that this is what I understand from his first Q
| |
15:24 | <||cw> but yeah, I can see other interpretations. there's clearly a language barrier, which is fine, just more details are needed
| |
15:26 | <krlos> alkisg: I mean that clients can boot from the hard drive and not by the network card to have virtual desktops with ltsp
| |
15:26 | <||cw> krlos: ltsp isn't exactly virtual desktops
| |
15:27 | so, why do you need hard drive booting to do this
| |
15:27 | the biggest advantage to ltsp is that there are no hard drives in the clients
| |
15:30 | <krlos> ok I understand, but I have a router in my remote sites and that prevents the ltsp from delivering dynamic addresses in my subnets
| |
15:31 | <alkisg> !x2go
| |
15:31 | <ltsp> x2go: x2go is an NX-based suite of applications that allow logging in to a remote X server from any OS. It's much more efficient than VNC over slow network. More info: http://www.x2go.org/
| |
15:31 | <alkisg> Maybe you're looking for a remote desktop solution and not a remote booting solution
| |
15:32 | x2go is remote desktop, ltsp is remote booting
| |
15:32 | !local-boot
| |
15:32 | <ltsp> local-boot: If you want LTSP fat clients on a low-speed network, you can put i386.img on e.g. C:\Boot\LTSP\i386.img and use this command line in pxelinux.cfg: APPEND ro initrd=ltsp/i386/initrd.img init=/sbin/init-ltsp root=/dev/sda1 rootflags=ro loop=/Boot/LTSP/i386.img; IPAPPEND 3
| |
15:32 | <alkisg> If you really want ltsp locally, here is how ^
| |
15:32 | <||cw> yeah, I woulnd't do remote booting over a router either. x2go is a nice remote desktop solution
| |
15:33 | krlos has left IRC (krlos!c9d8bc6e@gateway/web/freenode/ip.201.216.188.110, Quit: Page closed) | |
15:33 | <||cw> ltsp is more about remote booting, which can use x11 forwarding or local. x2go is more efficient than x11 forwarding for WAN links
| |
15:33 | krlos has joined IRC (krlos!c9d8bc6e@gateway/web/freenode/ip.201.216.188.110) | |
15:33 | <||cw> fwiw, my remote site has its own ltsp server.
| |
15:34 | ltsp is more about remote booting, which can use x11 forwarding or local. x2go is more efficient than x11 forwarding for WAN links. my remote sites have their own ltsp server, which is even more WAN efficient
| |
15:34 | <krlos> sorry, the session closed,
| |
15:34 | but I have a router in my remote sites and that prevents the ltsp from delivering dynamic addresses in my subnet
| |
15:37 | ok, it will then be necessary to place an ltsp in each remote site
| |
15:37 | <||cw> krlos: that is not the source problem
| |
15:37 | each site SHOULD have its own subnets.
| |
15:38 | <krlos> it is right
| |
15:38 | <||cw> you can route the tftp requests over your router/VPN if you like, but unless you have metro fiber of 100Mbits or more it's going to get painfully slow.
| |
15:39 | <krlos> ok I understand,
| |
15:40 | <||cw> if you're OK with the remote site having disks, you can run x2go on your ltsp server side by side
| |
15:40 | local uses ltsp, remote uses x2go, both get the same environment
| |
15:42 | <krlos> excellent,
| |
15:48 | <alkisg> krlos: what is the network speed between the 2 sites/
| |
15:49 | E.g. 10 mbps, gigabit?
| |
16:01 | jgee has joined IRC (jgee!~jgee@181.56.72.152) | |
16:10 | <krlos> 100 mbps
| |
16:28 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154) | |
16:39 | <alkisg> krlos: then you can very easily boot from the network using only a local kernel
| |
16:39 | or just ipxe, it supports tftp and http downloads
| |
16:39 | !local
| |
16:39 | <ltsp> I do not know about 'local', but I do know about these similar topics: 'install-localapp', 'localdev', 'RDP-localdev', 'LocaldevCommonGroupWorkaround', 'localxterm', 'local-disks', 'local-boot', 'localapps'
| |
16:39 | <alkisg> !kernel
| |
16:39 | <ltsp> I do not know about 'kernel', but I do know about these similar topics: 'ltsp-update-kernels'
| |
16:44 | lucas_ has joined IRC (lucas_!~lucas@138.68.106.79) | |
16:47 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Ping timeout: 256 seconds) | |
17:02 | lucas_ has left IRC (lucas_!~lucas@138.68.106.79, Quit: Leaving) | |
17:02 | lucascastro has joined IRC (lucascastro!~lucas@138.68.106.79) | |
17:14 | jgee_ has joined IRC (jgee_!~jgee@181.56.72.152) | |
17:17 | jgee_ has left IRC (jgee_!~jgee@181.56.72.152, Quit: jgee_) | |
17:18 | jgee_ has joined IRC (jgee_!~jorge@181.56.72.152) | |
17:20 | jgee_ has left IRC (jgee_!~jorge@181.56.72.152, Client Quit) | |
17:41 | lucascastro has left IRC (lucascastro!~lucas@138.68.106.79, Remote host closed the connection) | |
17:57 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
18:03 | tarzeau has left IRC (tarzeau!~gurkan@mail.aiei.ch, Remote host closed the connection) | |
18:13 | Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E973.dip0.t-ipconnect.de) | |
18:23 | lucascastro has joined IRC (lucascastro!~lucas@186.193.178.113.jupiter.com.br) | |
18:38 | lucascastro has left IRC (lucascastro!~lucas@186.193.178.113.jupiter.com.br, Remote host closed the connection) | |
18:39 | lucascastro has joined IRC (lucascastro!~lucas@186.193.178.113.jupiter.com.br) | |
18:41 | lucascastro has left IRC (lucascastro!~lucas@186.193.178.113.jupiter.com.br, Remote host closed the connection) | |
18:56 | fiesh has left IRC (fiesh!~fiesh@hq.wsoptics.de, Ping timeout: 256 seconds) | |
19:03 | fiesh has joined IRC (fiesh!~fiesh@hq.wsoptics.de) | |
19:15 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154) | |
19:21 | <vagrantc> huh. https://wiki.debian.org/YashAgarwal/GSoCProposal
| |
19:21 | using bittorrent to boot LTSP ... not entirely sure how that would work ... but interesting, at least :)
| |
19:37 | <||cw> seem slike the idea is you PXE boot a small optimized kernel that torrents the main kernel and initrd and bootstraps them
| |
19:38 | guess it could help in a bootstorm situation, but once nfs or nbd are connected they'll be the bottleneck, so you'd need to cluster them too
| |
19:39 | original research paper at https://www.researchgate.net/publication/283121648_BootTorrent_peer-to-peer_fast_network_boot
| |
19:43 | <vagrantc> unless you're booting the whole image into ram
| |
19:44 | which i've often thought would be an interesting approach
| |
19:44 | e.g. each client is also a server
| |
19:55 | Statler|Home has left IRC (Statler|Home!~Georg@p5B30E973.dip0.t-ipconnect.de, Remote host closed the connection) | |
20:09 | Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E973.dip0.t-ipconnect.de) | |
20:30 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection) | |
20:30 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154) | |
20:31 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
20:54 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection) | |
20:55 | <alkisg> Why torrent instead of multicasting?!
| |
20:58 | * vagrantc shrugs | |
20:58 | <vagrantc> ah, torrent would allow clients to boot at different rates
| |
20:59 | multicast would require them to boot at the same time
| |
20:59 | <alkisg> Asynchronous caching :)
| |
20:59 | <vagrantc> exactly
| |
21:38 | <alkisg> (I meant, you can have multicasting with asynchronous caching, there's no need for the extreme overhead of torrents...)
| |
21:38 | * alkisg waves | |
21:38 | <vagrantc> oh
| |
21:50 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 276 seconds) | |
22:13 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
22:16 | ||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, Quit: Do not follow the null pointer, for therein lies ma&^%#___) | |
22:19 | Statler|Home has left IRC (Statler|Home!~Georg@p5B30E973.dip0.t-ipconnect.de, Remote host closed the connection) | |
22:22 | ||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934) | |
22:31 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
23:26 | ||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, Quit: Do not follow the null pointer, for therein lies ma&^%#___) | |
23:32 | ||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934) | |