On 24 September 2012 18:10, Scott Moser <email address hidden> wrote:
> I suppose this is probably for historical reasons. For all versions of
> our cloud images (hardy+), there was a 'netdev' user in which the 'ubuntu'
> was present (it is added by 'vmbuilder').
But the current stuff uses live-build - my system is derived from the
scripts that builds your cloud images.
And the hook in 030-create-user.chroot disable user creation for Quantal.
if dist_ge "${codename}" quantal; then
echo "User creation on 12.10 is handled by cloud-init."
exit 0
fi
Why have the hooks creating the default groups? Shouldn't they be in
the standard server installation packages so that a debootstrapped
Ubuntu system has the expected /etc/group layout?
On 24 September 2012 18:10, Scott Moser <email address hidden> wrote:
> I suppose this is probably for historical reasons. For all versions of
> our cloud images (hardy+), there was a 'netdev' user in which the 'ubuntu'
> was present (it is added by 'vmbuilder').
But the current stuff uses live-build - my system is derived from the
scripts that builds your cloud images.
And the hook in 030-create- user.chroot disable user creation for Quantal.
if dist_ge "${codename}" quantal; then
echo "User creation on 12.10 is handled by cloud-init."
exit 0
fi
Netdev is created in a 025 default group hook.
echo "Adding admin group..."
addgroup --system --quiet admin
echo "Adding netdev group..."
addgroup --system --quiet netdev
Why have the hooks creating the default groups? Shouldn't they be in
the standard server installation packages so that a debootstrapped
Ubuntu system has the expected /etc/group layout?
--
Neil Wilson