lot to love about #netbsd and missing surprisingly little.
-
@lkundrak i'm p sure gnu find works there
@lkundrak otherwise autoconf was for nothing
-
-
@lkundrak i'm p sure gnu find works there
@hipsterelectron gnu versions are in pkgsrc and i ended up with many unix aliases already, even
alias make=gmake
alias sed=gsed
alias awk=gawkfirst is obvious of no fault of bsd, the second two i don't remember why any more (does bsd awk have gsub()??). i'm sure bsd versions are okay, blaming this on years on gnu
-
@hipsterelectron gnu versions are in pkgsrc and i ended up with many unix aliases already, even
alias make=gmake
alias sed=gsed
alias awk=gawkfirst is obvious of no fault of bsd, the second two i don't remember why any more (does bsd awk have gsub()??). i'm sure bsd versions are okay, blaming this on years on gnu
@lkundrak you can also build them to use that g binary prefix
-
@lkundrak you can also build them to use that g binary prefix
@lkundrak blaming gnu always a good strategy although i'm kind of a gnu apologist
-
@lkundrak otherwise autoconf was for nothing
@hipsterelectron it's making things portable*
*to osf/1 on alpha, not a perfectly fine future risc plaform with a perfectly standard modern c compiler
-
@hipsterelectron it's making things portable*
*to osf/1 on alpha, not a perfectly fine future risc plaform with a perfectly standard modern c compiler
@lkundrak i'm a HUGE autoconf apologist
-
@lkundrak i'm a HUGE autoconf apologist
@hipsterelectron sorry to hear, hope you get better
-
lot to love about #netbsd and missing surprisingly little. real annoying things:
find requires a path. "find ." instead of "find", i'm getting it wrong every time.
no "sort -h". how do people sort "du -sh" output? are they content with seeing their file is 173666 blocks big?
anybody knows if patches for these would've been accepted or if they'd be shunned off as gnu-isms?
@lkundrak Haha I come from the BSD, and TIL that you can omit the path in gnu find xD.
-
@lkundrak i'm a HUGE autoconf apologist
@lkundrak i will literally make fixes for things. i'm currently working on an improved help output including ~colors~
-
@hipsterelectron sorry to hear, hope you get better
@lkundrak i fear it may be terminal
-
@lkundrak Haha I come from the BSD, and TIL that you can omit the path in gnu find xD.
@mathieu omg do not get used to it, it's a trap!!
-
@mathieu omg do not get used to it, it's a trap!!
@mathieu it's how gnu vendor locks you
-
@lkundrak i fear it may be terminal
@lkundrak funniest joke i've ever made in my entire life
-
@mathieu it's how gnu vendor locks you
@mathieu do you know research shows that if you learn to ride a reverse bike, your ability to steer a normal bike will get measurably slower
that is how using gnu impairs everybody's ability to use a normal computer
-
@ozzelot oh hail the world of init system neglect
@lkundrak
"si non confectus, non reficiat" -theo de vetinari -
@lkundrak
"si non confectus, non reficiat" -theo de vetinari@lkundrak
(yes, netbsd is the one that theo famously left, i know) -
@lkundrak
(yes, netbsd is the one that theo famously left, i know)@ozzelot the story i remember is that he left the same way kent left
-
lot to love about #netbsd and missing surprisingly little. real annoying things:
find requires a path. "find ." instead of "find", i'm getting it wrong every time.
no "sort -h". how do people sort "du -sh" output? are they content with seeing their file is 173666 blocks big?
anybody knows if patches for these would've been accepted or if they'd be shunned off as gnu-isms?
@lkundrak I didn’t know “sort -h” was a thing! I always use “du -sk”
-
R relay@relay.mycrowd.ca shared this topic
