|00:59||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|06:03||RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)|
In case anyone's using it, I updated https://github.com/alkisg/liveusb with the latest ipxe.lkrn and ipxe.efi, and I added the ability to boot many linux distributions by just dropping .iso files
|11:12||adrianorg has joined IRC (firstname.lastname@example.org)|
|11:15||adrianor1 has left IRC (email@example.com, Ping timeout: 264 seconds)|
|12:35||markit has joined IRC (firstname.lastname@example.org)|
|13:28||mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 264 seconds)|
|13:39||nikoh77 has joined IRC (email@example.com)|
|13:42||mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)|
alkisg: i mouted nfs share but now i can't enter/oper dir because i don't have rights; can i mount like nikoh user or can i define a specific i p that can mount with nikoh user? I already see /etc/export but it seem all commented lines....
nikoh77: you should have /etc/exports.d/ltsp-nfs.exports
if you modified it, you have to "exportfs -a" and restart nfs services
nikoh77: you must have the correct line also in ltsp.conf UNCOMMENTED
(should be something like FSTAB_HOME="server:/home /home nfs defaults,nolock 0 0")
markit: ok, i try, thanks ;-)
nikoh77: I've not read what you are trying to do, I entered the chat late... I suppose you are configuring normal ltsp under ubuntu (I use Kubuntu) 20.04 or 18.04 (never tried there)
markit: my ltsp (new version) is installed and working (fine). there is 1 extra mount (nfs share) and i would mount thi share on external mac os (not a ltsp client)
i can mount but i can open and see folder content
oh, I see, just for test create a dir and assign 777 permission, also to files under it and see if it works
chmod -R 777 newdir
(or something like that)
|13:58||Guest90732 has joined IRC (Guest90732firstname.lastname@example.org)|
ok, i see that line on ltsp.conf but this share is "created" on the fly for clients right? how i can config real share on the server?
if i change rights it work but i cant
markit: there is a way to mount from a specific pc like a specific user?
nikoh77: nfs does user and id mapping, so the easiest way would be to use the same id/name in the mac user
Otherwise, there's "all_squash" and "anon_uid" and "anon_gid", run `man exports` to see the nfs man page
Hi, I'm using the new ltsp (2019) quite some time on Debian buster - recently, (when starting the client and after 'ltsp image /') I get the following error message: "nfs: server 192.168.67.1 not responding, still trying". I'm using a dual NIC server (NAT=1). Is there any known problem around ...
Guest90732: the ltsp version has stayed the same for months, right?
dpkg shows 20.04-1~ubuntu18.04.1
apt-get upgrade has probably renewed ltsp some days ago ...
Does this happen all the time? always?
the "not responding"
yes, I treid now several ( > 6) times
I recently install jitsi but have excluded this via: RM_SYSTEM_SERVICES="dnsmasq nbd-server netfilter-persistent jitsi-videobridge2 jicofo prosody"
|15:19||nikoh77 has left IRC (email@example.com, )|
What does `showmount -e localhost` show on the server?
Export list for localhost: /srv/tftp/ltsp * /srv/ltsp
I just tried again to boot the client: now I get the following message: Dependency faild for Raise network interfaces.
I will check the cables ...
The "not responding" would probably be because of the cabling,
but the dependency failed might be due to jitsi; does it complete boot after a while?
You may also use epoptes and right click > open root terminal > run systemctl status, to see what's wrong with services
On the first client I still get "not responding" - the new error message was from a second client.
Try to boot the first client with a live usb, and see if you can mount nfs from it
Btw: sudo ltsp image -r /
This reverts to the previous image version
In case you think it's related to the image; I don't think so
Btw is the first client trying to mount from the correct server ip?
Hmm 2 nic, it should be...
yes, 192.168.67.1 is the correct IP
I will try with the live usb ... may take some time
I just tried the 2nd client with the same cabeling but still get a different error message ...
What message, about the raise network interfaces?
And does it boot after a while?
Or does it stay there forever?
no, it stays for ever ...
OK maybe something that you installed breaks networking. Do you have a VM client that you could share its screen with me, to test things? But not now, in a couple of hours when I'll be back..
now client2 also shows "nfs: server 192.168.67.1 not responding" ...
I'll try a restart of the server ... which means that I will be disconnected for some time ... see you later
|15:48||Guest90732 has left IRC (Guest90732firstname.lastname@example.org)|
|17:22||woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 258 seconds)|
|17:23||woernie has joined IRC (email@example.com)|
|17:31||woernie has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|19:26||nikoh77 has joined IRC (email@example.com)|
|19:26||nikoh77 has left IRC (firstname.lastname@example.org, Client Quit)|
|19:37||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|20:24||RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)|
|21:00||markit has left IRC (email@example.com, )|