On Thursday 09 May 2013 20:00:01 Paul Boddie wrote:And just adding to the noise even more - sorry about this! - I discovered that
> Just following up to myself, having attempted to repeat my previous
> experiments with wheezy-grip...
I had failed to follow my own instructions properly...
I no longer experience this problem.
> On Thursday 09 May 2013 18:06:52 Paul Boddie wrote:
> > On Thursday 09 May 2013 17:09:39 mind entropy wrote:
> > > Now I get the following error:
> > >
> > > login: PAM Failure, aborting: Critical error - immediate abort
> After completing the initial package configuration of a multistrapped
> system and having made an attempt to remove the root password (which may or
> may not have done anything, but there isn't a root password afterwards,
> anyway), I then cannot set a root password and get the following error:
> passwd: Authentication token manipulation error
> passwd: password unchanged
I found that even though multistrap elevates its privileges using sudo, the
resulting filesystem hierarchy preserves the original user's permissions.
Consequently, the booted system didn't like various files having the wrong
uid. I may have discovered this previously and had noted in my own
instructions that multistrap needs to be run as root or using sudo (unless
anyone can advise me differently), but this time I assumed that when
multistrap invoked sudo everything would end up being owned by root.
This is now gone, too.
> There are also odd things like trying to ping another host while logged in
> as the root user and getting the following error:
> ping: ping must run as root
> (That said, I'm not completely sure that the kernel is as happy as it was
> under Squeeze.)
This is also gone as well.
> Trying to add a new user with adduser gets the following error when setting
> a password:
> chfn: PAM: Authentication failure
> adduser: `/usr/bin/chfn paulb' returned error code 1. Exiting.
> Upon rebooting and attempting to log in, I get the previously stated error
> message flashed up briefly on the display after trying to log in as root or
> my perhaps unsuccessfully created user:
> Unable to determine your tty name
So this was just me not following instructions written down a few months
> I'm using the same kernel as before, which is a mipsel 3.3.8 Linux kernel
> built using the OpenWrt toolchain. So perhaps there's some incompatibility
> between kernel and user space.
However, it does potentially inform the discussion because I can now verify
that an Emdebian wheezy-grip installation will work with the device
configuration previously mentioned, and I can remind myself and others that
the ownership of the multistrapped filesystem hierarchy has to be checked
before it gets transferred to the target system. ;-)
Archive: firstname.lastname@example.org" target="_blank">http://email@example.com
To UNSUBSCRIBE, email to debian-embedded-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org