| 2006-10-10 07:16:38 |
Steven McCoy |
bug |
|
|
added bug |
| 2006-10-10 07:20:07 |
Steven McCoy |
xorg: statusexplanation |
|
|
|
| 2006-10-10 07:23:37 |
Steven McCoy |
description |
In both Dapper and Edgy the ltsp-build-client script exits immediately after debootstrap has finished. In Dapper I have to comment out debootstrap and re-run to finish, and in Edgy I have to move the file 010-debootstrap out of the /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu directory and re-run.
My install steps are here:
http://developer.novell.com/wiki/index.php/Edgy/HOWTO:_Install_MueKow_on_Ubuntu |
In both Dapper and Edgy the ltsp-build-client script exits immediately after debootstrap has finished. In Dapper I have to comment out debootstrap and re-run to finish, and in Edgy I have to move the file 010-debootstrap out of the /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu directory and re-run.
My install steps are here:
http://developer.novell.com/wiki/index.php/Edgy/HOWTO:_Install_MueKow_on_Ubuntu
console output:
…
I: Configuring pcmciautils...
I: Configuring console-setup...
I: Configuring console-tools...
I: Configuring ubuntu-minimal...
I: Base system installed successfully.
error: LTSP client installation ended abnormally |
|
| 2006-10-10 08:57:21 |
Oliver Grawert |
title |
ltsp-build-client exits after debootstrap |
ltsp-build-client needs to handle proxy settings for apt in the chroot |
|
| 2006-10-10 09:02:36 |
Oliver Grawert |
ltsp: assignee |
|
ogra |
|
| 2006-10-10 09:02:36 |
Oliver Grawert |
ltsp: statusexplanation |
|
could you attach the output of an ltsp-build-client --debug run from that machine (with this proxy setup) ? |
|
| 2006-10-10 10:59:28 |
Steven McCoy |
bug |
|
|
added attachment 'ltsp-build.debug.log' (ltsp-build-client --debug) |
| 2006-10-10 16:26:07 |
Steven McCoy |
description |
In both Dapper and Edgy the ltsp-build-client script exits immediately after debootstrap has finished. In Dapper I have to comment out debootstrap and re-run to finish, and in Edgy I have to move the file 010-debootstrap out of the /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu directory and re-run.
My install steps are here:
http://developer.novell.com/wiki/index.php/Edgy/HOWTO:_Install_MueKow_on_Ubuntu
console output:
…
I: Configuring pcmciautils...
I: Configuring console-setup...
I: Configuring console-tools...
I: Configuring ubuntu-minimal...
I: Base system installed successfully.
error: LTSP client installation ended abnormally |
In both Dapper and Edgy the ltsp-build-client script exits immediately after debootstrap has finished. In Dapper I have to comment out debootstrap and re-run to finish, and in Edgy I have to move the file 010-debootstrap out of the /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu directory and re-run.
My install steps are here:
http://developer.novell.com/wiki/index.php/Edgy/HOWTO:_Install_MueKow_on_Ubuntu
console output:
…
I: Configuring pcmciautils...
I: Configuring console-setup...
I: Configuring console-tools...
I: Configuring ubuntu-minimal...
I: Base system installed successfully.
error: LTSP client installation ended abnormally
The LTSP server is running NFS root from FreeBSD (FreeNAS). |
|
| 2006-10-11 02:56:46 |
Steven McCoy |
bug |
|
|
assigned to debootstrap (Ubuntu) |
| 2006-10-11 02:57:39 |
Steven McCoy |
bug |
|
|
assigned to coreutils (Ubuntu) |
| 2006-10-11 22:54:27 |
Steven McCoy |
title |
ltsp-build-client needs to handle proxy settings for apt in the chroot |
debootstrap fails to remove own log file on NFS |
|
| 2006-10-11 23:02:52 |
Steven McCoy |
bug |
|
|
added attachment 'debootstrap.nfs.patch' (debootstrap fix for NFS log) |
| 2006-10-12 08:29:19 |
Colin Watson |
coreutils: status |
Unconfirmed |
Rejected |
|
| 2006-10-12 08:29:19 |
Colin Watson |
coreutils: statusexplanation |
|
This isn't a coreutils bug; it genuinely can't remove all the files (counting the NFS dotfile) and therefore can't do the rmdir(). If anywhere, the bug is that the NFS server is implementing access to still-open unlink()ed files by means of a dotfile in the same directory as the link, which means you can't do unlink() and then rmdir() without closing any fds you have open on the file as well.
This suggests a different workaround in debootstrap; I'll post a suggested patch shortly. |
|
| 2006-10-12 08:39:16 |
Oliver Grawert |
ltsp: status |
Unconfirmed |
Rejected |
|
| 2006-10-12 08:39:16 |
Oliver Grawert |
ltsp: statusexplanation |
could you attach the output of an ltsp-build-client --debug run from that machine (with this proxy setup) ? |
|
|
| 2006-10-12 08:41:44 |
Colin Watson |
debootstrap: status |
Unconfirmed |
Fix Released |
|
| 2006-10-12 08:41:44 |
Colin Watson |
debootstrap: assignee |
|
kamion |
|
| 2006-10-12 08:41:44 |
Colin Watson |
debootstrap: statusexplanation |
|
debootstrap (0.3.3.0ubuntu7) edgy; urgency=low
* When removing $TARGET/debootstrap, debootstrap.log is still open as
stdout/stderr and needs to remain so, but after unlinking it some NFS
servers implement this by a temporary file in the same directory, which
makes it impossible to rmdir that directory. Moving it instead works
around the problem (thanks, Steven McCoy; closes: Malone #65003).
-- Colin Watson <cjwatson@ubuntu.com> Thu, 12 Oct 2006 09:40:44 +0100 |
|
