jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
SiFuh has quit [Ping timeout: 260 seconds]
SiFuh has joined #crux-devel
farkuhar has joined #crux-devel
SiFuh has quit [Ping timeout: 260 seconds]
SiFuh has joined #crux-devel
SiFuh has quit [Ping timeout: 268 seconds]
SiFuh has joined #crux-devel
<jaeger> I've been pulled all over the place in terms of projects and workload lately, very distracting. What's still outstanding for 3.7?
<jaeger> At least one thing is that we still need to merge the sandbox documentation into the new handbook if folks are happy with it
<farkuhar> It would be nice to decide whether we're keeping our custom login.defs, or adopting the upstream defaults that come with the shadow project. According to SiFuh's logs, ten years ago jue was fine with using the upstream settings, but we're still deploying (with slight modifications) the defaults we inherited from jw.
<jaeger> I prefer upstream defaults in most cases
<farkuhar> I believe at least SiFuh and ivandi made the conscious choice to follow more closely the upstream settings in their own login.defs. But we need more core maintainers to weigh in, before making any changes to the shadow port.
<SiFuh> I follow the default groups file from CRUX and the default login.defs from shadow
<SiFuh> Heavily opposed to changing the default group file
<farkuhar> just for laughs, you could add the line "haters::1000" to /etc/group, leave our custom login.defs in place, and see who's the first to complain that their normal user has 'haters' as the primary group.
<SiFuh> That won't work. They will end up with group 1001
<SiFuh> Unless it is an old home directory from a previous distro (Not CRUX)
<SiFuh> lusers::1000 if you wish to take a trip down memory lane
<farkuhar> SiFuh: i tried it just now on a clean CRUX 3.7 system, and it works just as i predicted. Only by consciously changing login.defs (the one that gets copied from our ports tree) can you force useradd to avoid falling back on gid 1000, in the absence of a '-g' flag on the command line.
<dlcusa> jaeger, using rc3, lsusb misses libatomic.so.1
<jaeger> yep, already fixed that one for rc4
<dlcusa> Great!
<SiFuh> farkuhar: Heh, as I am the man page said. Don't mess witht he groups file. Just modify the login.defs, everything will work fine and dandy.
<beerman> i am not missing anything and i am fine with following along with upstreams login.defs more closely.
<beerman> jue said he is fine with 3.7 as is and whats it out as soon as possible
<beerman> we might want to wait for glibc, there is a patch soon for dhcpcd and everything else seems to work for me
<farkuhar> SiFuh: the whole point of this discussion is to save new users the trouble of reverting our 16-year-old customizations of login.defs! If we just installed the defaults provided by upstream, they would have useradd "working fine and dandy" without needing to modify anything.
<SiFuh> Basically what I have been saying for the last week
<SiFuh> Leave CRUX default groups alone and just use the 'upstream' login.defs from the shadow
<SiFuh> It is kind of funny how this conversation is actually over 10 years old :-P
<farkuhar> SiFuh: in case it wasn't obvious from the prefatory comment "just for laughs", i wasn't seriously proposing to change /etc/group, i just wanted to illustrate a silly side-effect that could be accomplished if we insisted on retaining the custom login.defs
<stenur> gcc, but that is a regular update