RE: [**EXTERNAL**] HOME variable in init/init.c
>I would expect it to be "/root" considering that USER has been set to "root"... Who says there has to _be_ a "/root" directory? -- Jim ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
Re: HOME variable in init/init.c
On Sat, 15 Sep 2018 18:36:27 +0300 Asaf Kahlon wrote: > I would like to know why HOME was set to "/" at init/init.c (the > comment above the code just says "Make sure environs is set to > something sane")? I would expect it to be "/root" considering that > USER has been set to "root"... I don't know for sure, but I am guessing it is because busybox is quite often used in embedded environments. The "/" directory is the only one that is guaranteed to exist. Cheers, Sean ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
HOME variable in init/init.c
Hello, I would like to know why HOME was set to "/" at init/init.c (the comment above the code just says "Make sure environs is set to something sane")? I would expect it to be "/root" considering that USER has been set to "root"... It can lead to different behaviors when running a daemon process as init script compared to run it manually (e.g with a Python script which runs expanduser). It would be nice if someone can explain why this value was chosen (or whether it's OK to send a patch to change it). Thanks! ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
