On 16/12/11 11:00, Bruce Dubbs wrote: > Andrew Benton wrote: >> On Thu, 15 Dec 2011 16:25:17 -0600 >> Bruce Dubbs <[email protected]> wrote: >> >>> Also, the construct is not explained. I think it should be removed. >> >> I agree it should be explained, then people can make an informed >> choice. I don't mind that it's different from the other pages where >> useradd is used. > > I still don't see the value: > > $ sudo useradd -c "D-BUS Message Daemon User" -d /dev/null -u 18 -g > messagebus -s /bin/false messagebus || [ $? == 9 ] > $ sudo useradd -c "D-BUS Message Daemon User" -d /dev/null -u 18 -g > messagebus -s /bin/false messagebus || [ $? == 9 ] > useradd: user 'messagebus' already exists > > In this case it sends a message to stdout. > > There is a paragraph after the useradd. We don't add && to the last > instruction of a segment anywhere in the book the I know of. The only > thing || [ $? == 9 ] does is change the return value of the line from > it's actual value to either a 1 or a 0. Where is this return value used > in the book? > > -- Bruce It's not used used with the book, but outside of the book. The added benefit is using Agile principles in implementing a continuous build process which picks up build problems due to typos, incomplete dependency errors, etc rather quickly by having an auto build mechanism that only relies on the Book alone whithout no human involvement. That off course relies on the instructions to be 100% repeatable. Anyway, that is the type of stuff we have been doing at my place of work over the last 6 months, and the benefits are great. If it gets removed then I don't mind. Consensus rules and all that. Regards, Wayne.
-- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
