*** This bug is a duplicate of bug 347957 ***
https://bugs.launchpad.net/bugs/347957
This bug was fixed in the package ltsp - 5.1.74-0ubuntu1
---
ltsp (5.1.74-0ubuntu1) karmic; urgency=low
* new upstream version (5.1.74)
* ltsp-localapps: Make it work correctly when the serv
*** This bug is a duplicate of bug 347957 ***
https://bugs.launchpad.net/bugs/347957
This is the same bug as 347957 previously reported.
** This bug has been marked a duplicate of bug 347957
jaunty ltsp client creates /etc/resolv.conf with 000 permissions
--
jaunty /etc/resolv.conf in ch
Sorry, here is /etc/resolv.conf file after installation.
admin-lt...@ubuntu-ltsp5:~$ ssh r...@192.168.1.200
The authenticity of host '192.168.1.200 (192.168.1.200)' can't be established.
RSA key fingerprint is ce:2b:fb:ee:ee:b8:41:38:de:23:4e:46:f3:54:2c:7c.
Are you sure you want to continue conn
Fresh RC i386 install with one nic.
admin-lt...@ubuntu-ltsp5:~$ ssh r...@192.168.1.200
r...@192.168.1.200's password:
r...@ltsp200:~# cat /etc/resolv.conf
search ubuntu-ltsp5
nameserver 192.168.1.1
r...@ltsp200:~# ls -al /etc/resolv.conf
-- 1 root root 43 2009-04-18 22:00 /etc/resolv.con
the touch command should probably try to touch a file from the bindfiles
variable instead of trying to touch /
--
jaunty /etc/resolv.conf in chroot has permission-rights 000
https://bugs.launchpad.net/bugs/348305
You received this bug notification because you are a member of Ubuntu
Bugs, which is
in the ltsp-setup initscript i see:
if [ -z "$root_write_method" ]; then
touch / 2> /dev/null || root_write_method="bind_mounts"
fi
[ "$root_write_method" = "bind_mounts" ] && bind_mounts
...
can somebody seeing the issue attach the output if "cat /proc/mounts"
while this is a working workaround, the cause why the file is created
with 000 permissions at all still isnt clear, it would be helpful to dig
deeper here to find the actual bug and fix.
afaik the initscript only creates a resolv.conf if DNS_SERVER and
SEARCH_DOMAIN are set in lts.conf, the creati
Here is a fix.
This one is for server with one nic. This works also with two nics
(forward & nat). I tested it, too.
1.
admin-lt...@ubuntu-ltsp5:~$ cat /opt/ltsp/i386/etc/init.d/chmod-resolv.sh
#! /bin/sh
chmod 644 /etc/resolv.conf
admin-lt...@ubuntu-ltsp5:~$
2.
admin-lt...@ubuntu-ltsp5:~$
I can confirm this. After using these lines in lts.conf file, root can ping
with names in chroot, but user can't use Konqueror with names. After changing
mode to 644 user can use Konqueror with names. Here are my notes in mailing
list:
https://lists.ubuntu.com/archives/edubuntu-users/2009-Apri
(server) sudo chroot /opt/ltsp/i386
ls -al /etc/resolv.conf
-> permission rights rw- r - r
(ltspclient) xterm(<-localapp p...@ltsp)
ls -al /etc/resolv.conf
-> permission rights --- --- ---
comment: Something changes the permission rights after starting the
client (ltsp-update-image was m
10 matches
Mail list logo
