[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi] Missing system directories in chroot [Was: Creating a chroot for c
From: |
Greg Chicares |
Subject: |
[lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi] |
Date: |
Thu, 15 Sep 2016 15:46:32 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0 |
On 2016-09-08 22:06, Vadim Zeitlin wrote:
> On Fri, 2 Sep 2016 01:31:12 +0000 Greg Chicares <address@hidden> wrote:
[...]
> GC> During 'debootstrap', I see messages like this:
> GC> # E: Can not write log (Is /dev/pts mounted?)
> GC> # [FAIL] Can't start system message bus - /proc is not mounted ...
> failed!
> GC> and I just ignore them, because the chroot seems to work perfectly.
> GC> What negative consequences could this have?
To explore the consequences, I tried installing google-chrome-stable in
a minimal chroot (created as described in the original message thread).
As root in the chroot, I installed the package with apt-get, in exactly
the same way that I (successfully) installed it on the spousal machine
(not in a chroot). Installation seemed to work, but the program could
not be started because the chroot lacks /proc and /dev :
$/usr/bin/google-chrome-stable
/usr/bin/google-chrome-stable: line 45: /dev/fd/62: No such file or directory
/usr/bin/google-chrome-stable: line 46: /dev/fd/62: No such file or directory
/proc/cpuinfo: No such file or directory
[0914/222359:ERROR:icu_util.cc(173)] Invalid file descriptor to ICU data
received.
zsh: abort /usr/bin/google-chrome-stable
> I don't know because I don't see them, probably because I updated my last
> Wheezy system to Jessie by now. I probably could install a Wheezy chroot
> and try creating a Jessie chroot from it, but this is starting getting
> seriously metaphysical, so let me just give two advices without bothering
> practically checking them:
>
> 1. As I said before, I think you do need to mount /dev/pts because many
> programs risk to fail mysteriously if PTYs don't work. This can be done
> manually using "mount -o bind -t devpts /dev/pts devpts".
Here's where I get lost. I'm assuming this must be done after entering
the chroot:
$schroot --chroot=chrome
$mount -o bind -t devpts /dev/pts devpts
mount: only root can use "--options" option
Okay, so I exit the chroot, reenter it as root, and try mounting again:
$schroot --chroot=chrome --user=root --directory=/
# mount -o bind -t devpts /dev/pts devpts
mount: mount point devpts does not exist
# cat /etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM
# mount
mount: failed to read mtab: No such file or directory
# ls /dev/
console loop0 loop5 port ram1 ram14 ram4 ram9 stdout zero
core loop1 loop6 ptmx ram10 ram15 ram5 random tty
fd loop2 loop7 pts ram11 ram16 ram6 shm tty0
full loop3 mem ram ram12 ram2 ram7 stderr urandom
kmem loop4 null ram0 ram13 ram3 ram8 stdin xconsole
Do I need to install udev first?
> GC> The '~/.zshrc' created by the quasi-script suggests running
> GC> update-locale LANG=en_US.UTF-8 LC_TIME=en_DK.UTF-8 LC_COLLATE=C.UTF-8
>
> I have no idea where is this coming from, especially DK for the time
> format. I just use "LC_ALL=C.UTF-8" and set "LANG" to the same value.
Thanks, I'll try that. BTW, en_DK for LC_TIME is a workaround to make
icedove (thunderbird) use a ISO8601 date format (because 2013-11-12 is
sensible, while 11/12/2013 is not). The DK trick is even mentioned in
the Arch Linux documentation:
https://wiki.archlinux.org/index.php/locale
- [lmi] Creating a chroot for cross-building lmi, Greg Chicares, 2016/09/01
- Re: [lmi] Creating a chroot for cross-building lmi, Vadim Zeitlin, 2016/09/08
- [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi],
Greg Chicares <=
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Vadim Zeitlin, 2016/09/15
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Greg Chicares, 2016/09/15
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Vadim Zeitlin, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Greg Chicares, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Vadim Zeitlin, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Greg Chicares, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Vadim Zeitlin, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Greg Chicares, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Vadim Zeitlin, 2016/09/16
- Re: [lmi] Missing system directories in chroot [Was: Creating a chroot for cross-building lmi], Greg Chicares, 2016/09/22