libera/#devuan-dev/ Monday, 2023-09-18

* joerg just muses if #!/bin/sh is now #!/usr/bin/sh00:50
rrqanyone knows how to stop bash from omitting failed commands from the history?05:50
DelTomixrrq: never noticed bash doing that here before ? maybe check .bashrc for a trap on ERR or maybe something buried in the prompt or $PS1 ?? unless maybe something new in $HISTIGNORE ?07:00
rrqprobably me confusing myself :)07:01
DelTomixI can relate :)07:07
friedhelmjoin #openSUSE-buildservice10:49
bb|hcbrrq: bash omits commands that start with space11:27
bb|hcbAnd there is a setting about that, but I forgot the name11:27
rrqyeah I feel like I've had several cases where it omits a command that fails ... I can see it in the terminal but up-arrow doesn't recall it11:29
rrqand then, after 1-2 other commands it's again available with some up-arrows11:30
rrqbut this happens so occasionally that I haven't really focussed on it; it may have been be jumping around to some ather terminal .. often some handful or two terminals in progress...11:32
rrqthis time it bugged me enough to drop a line to see if anyone else here had a similar observation11:32
joergI *think* the commandline content is added to the history buffer *before* it's getting executed, so bash would need to actively *remove* / delete that last record from the history in case of $failure (return code != 0 ?)12:36
joergrrq:  man 1P fc|less -j11 '+/shall be entered at the end of the history list and then re-executed by sh'  ;#  ;-)13:43
DelTomixYeah the setting to omit from history is $HISTCONTROL - which can be "ignorespace" (commands with leading spaces), "ignoredups"(successive identical commands), or "ignoreboth"13:44
DelTomixwith $HISTIGNORE you can ignore based on pattern matches13:50
joergwow, TIL14:09
joergleading whitespace tricked me a few times. it's not in history so you malso can't recall it with (usually) arrow-up to remove the leading space :-)14:10
joerg-m14:10
joergneeds literal c&p from the terminal14:11
sachyleading space is great so you dont have .history filled with everyday garbage - just important commands14:20
masonRandomly, even if, for example, dash installs /usr/bin/sh (or /usr/bin/dash with a /usr/bin/sh symlink) this will still break dpkg -S unless PATHs stop using /bin before /usr/bin, as an example of something packages themselves moving the files won't address.16:02
joergthe webpaqe https://subdivi.de/~helmut/dep17.html Helmut set up seems to very thoroughly cover all implications.16:20
joergnice analysis of the situation and the plans to proceed16:22
masonHe's doing quite a bit of work, yes.16:34
masonNote the first paragraph in "proposal" though. They're not getting buy-in from the dpkg folks because they note a distinct set of issues: https://wiki.debian.org/Teams/Dpkg/MergedUsr16:37
joerg>>This can reduce the overhead of distinct directories and where to put what<< *cough*. This is the justification for messing up FHS? Sounds like a poor deal17:01
bb|hcbIt IS a poor deal. Some people pushed that in, leaving for others to clean the mess17:09
bb|hcbLast couple of months helmut is the one who is working hard to clean that mess.17:11
bb|hcbIMHO it would be much easier to revert the decision but politics+hubris are in the way17:11
sachypublic? no. RH with its tremendous power to break things.17:15
DelTomixexactly bb|hcb17:20
DelTomixI'm pretty sure he also understands its a poor idea, in great detail judging by his work.17:24
joerg:nod:17:31
DelTomixonefang's earlier comment "onefang wonders why that would be a thing in the first place?" regarding bb|hcb's point "there are races when a package installs /bin/foo and another replaces it with /usr/bin/foo..." made me think maybe we are feeding the wrong end of the donkey, and rrq is absolutely correct about "as long as files are named via their installation path there's no issue." however,17:36
DelTomixthere's going to be a transition where its a mess, and so maybe helmut's idea of having a tool to find and identify the issues can help save work wading through that mess17:36
DelTomix...but most of that is still going to have to be on the Debian side17:41
ksx4systemhello :) what happens if you try to replace sysvinit with something that's not (yet) available in Devuan repository?18:58
ksx4systemas far as I can see Google revived upstart and it's consequently updated18:58
ksx4systemI'm seriously considering porting it to Devuan18:58
bgstack15ksx4system: You are welcome to experiment and let us know the results! I don't recall how upstart was better/different, but we do advertise init diversity!20:10
bgstack15I didn't hate CentOS 6 because of its init, let me say.20:11
bb|hcbDelTomix: The transition is already in progress... :(20:47
ksx4systembgstack15, I liked it because it didn't mess with /etc/init.d scripts (same as for sysvinit) and OS booted a little faster on shit hardware21:19
ksx4system(not much of a difference on then decent hw)21:20
sachyanyone here planning to attend LinuxDays 2023 (Prague, 2023-10-08 https://www.linuxdays.cz/2023/) ? At our hackerspace boot Im goint to provide also some Devuan propaganda :)21:57
sachy*going21:57

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!