> > it will be "/" only in case the home dir does not exist at login time > as the login program does chdir to the home
That is what the linked page also says, yes. > dir else > you would be locked out of a broken system (damaged partition > mounted to /home, /root folder corrupted on main file system). > This is what I understand, not that you should put "/" in the passwd > files. > I do not see how this backs up the futile "/home/foo" entry when you actually do not create a home directory for "foo" intentionally. Have you read my concerns and comments above? I think it is a mistake to skip those without replying to them one-by-one because I find them valid and that is why I wrote them, but I will reiterate: * you would not know whether a system is broken if you see "/home/foo" in "/etc/passwd", but cannot find the corresponding home folder if you come back to your server 1-2 years later or not even that long, but with many users to keep in mind. * if you create a new home directory with something different than "/home/foo", it would be confusing again. * If we write a usermod alike applet with minimal needs, "/home/foo" even loses its meaning completely, although its meaning is questionable even without that IMHO. Having said that, this is tangential a discussion, and would have deserved its own thread. I personally believe could do a better job than the old gnu tools here by dropping the artificial memory-waster default since it provides no value. If you want to create "/home/foo" later, you ought to aim for a tool that does get the job right for you, rather than manually mkdir'ing and expecting that everything should just work.
_______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
