Op 24 jan. 2012, om 18:10 heeft Richard Purdie het volgende geschreven: > The securetty file is machine specific whilst the rest of the shadow recipe > is not. Unfortunately making the recipce machine specific is both inefficient > and also causes dependency problems since parts of the system such as the > useradd > code depend upon it and this introduces a machine specific element to sstate > checksums which should not be machine specific. > > To resolve this, this patch separates out the file into a separate recipe > meaning the machine specific components are isolated.
A word of warning for people with binary feeds: rebuild shadow for all your machines before uploading, otherwise you'll be greeted with error messages about missing securetty packages during upgrade. Opkg itself can't handle the upgrade properly since it will install dependencies first, so it errors out with "/etc/securetty already provided by shadow", so use --force-overwrite. I can't think of a way of doing this change without causing the above problems :( regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
