While I will concede that the new addition of /etc/issue is indeed a exceptional looking art, /etc/issue and /etc/motd I consider to be cruft files. If you're on a single user system, its not hard to make your own, and if you're on a multi-user system, you'll be at the mercy of the sysadmin anyway. IMHO this addition to baselayout would've been better placed by adding to the linux_logo package, or the Welcome2L package, where the rest of the issue files appear to reside.
I've heard from numerous people who think it was a very worthwhile contribution. Anyone with their own will obviously want to discard it in etc-update. (Err, why would you have root if you weren't the sysadmin?)
I don't claim it to be not worthwhile, quite the contrary. I applaud the nice piece of art that it is. I just merely think it could be better placed in the packages I noted. I don't doubt that it was well received by those who noticed, but I bet thrice as many people never noticed it didnt exist. I just ask that it go where all the other /etc/issues are.
I thought about it,but Im not sure what the root reference is for. What I said was that if you're the only user, hey no prob to fix it. If your on a multi-user system and you're not the sysadmin, you're screwed anyway. My major bitch about it is that all of a sudden, I have an issue file blasting on 11 vcs, where there was sweet black before. Doesn't anyone recall Debian's issue and motd files? Like herpes they were, no matter how many times they got deleted they came back.Also someone else oviously thought it was worthwhile long ago, and submitted the Welcome2L package which has about 20 issue files.All Im saying Id like to see it in a package Im not _required_ to have:)
*** Bug 20838 has been marked as a duplicate of this bug. ***
Made it plain text for 1.8.6.8.
