GalaxyNova has quit [Remote host closed the connection]
<testuser[m]>
GalaxyNova: hi
rohan has quit [Ping timeout: 248 seconds]
rohan has joined #kisslinux
<virutalmachineus>
hi
<wael_>
rohan: have a system logger
rohan has quit [Ping timeout: 248 seconds]
rohan has joined #kisslinux
phinxy has joined #kisslinux
travankor has joined #kisslinux
travankor has quit [Remote host closed the connection]
travankor has joined #kisslinux
<midfavila>
there's a kernel parameter you can set to change the minimum urgency level required before debug messages are printed to the console, rohan
<midfavila>
i can't quite recall which, though...
<wael_>
loglevel=4
<wael_>
or quiet
<midfavila>
yeah so there you go
<midfavila>
no system logger necessary
<wael_>
doesn't it print to stdout and not kernel log
<midfavila>
iwd spams both in my experience
<midfavila>
you can also just direct stdout to null or something
<testuser[m]>
so bad
<testuser[m]>
make logger
* midfavila
shrugs?
midfavila has quit [Remote host closed the connection]
<testuser[m]>
It's not in GNU's interest to break my program, but it's also not not in GNU's interest to break my program. GNU wants us to write programs for GNU. A proliferation of programs that only work under GNU makes it more attractive to install GNU, and less attractive to install alternatives.
phinxy has quit [Quit: WeeChat 3.5-dev]
phinxy has joined #kisslinux
<testuser[m]>
phoebos: any idea why man3 is not installed in man-pages? it doesn't conflict with anything
<phoebos>
i have no objection to adding them but i'm guessing that's what dylan was thinking
midfavila has joined #kisslinux
midfavila has quit [Client Quit]
phoebos[m] has quit [Quit: You have been kicked for being idle]
midfavila has joined #kisslinux
<testuser[m]>
_<PID>_GNU_nonoption_argv_flags_ This variable was used by bash(1) 2.0 to communicate to glibc which arguments are the results of wildcard expansion and so should not be considered as options. This behavior was removed in bash(1) version 2.01, but the support remains in glibc.
<midfavila>
^lectures to accompany SIT's APUE course
<midfavila>
figured you guys might find them useful
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 260 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 246 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 264 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
phinxy has quit [Quit: WeeChat 3.5-dev]
phinxy has joined #kisslinux
rohan has quit [Ping timeout: 252 seconds]
rohan has joined #kisslinux
chomwitt has quit [Ping timeout: 268 seconds]
rohan has quit [Ping timeout: 260 seconds]
rohan has joined #kisslinux
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
GalaxyNova has joined #kisslinux
<GalaxyNova>
standards are actuallly pretty bad
<midfavila>
that's actually a stupid take.
<GalaxyNova>
well somewhat
<GalaxyNova>
my statement was a bit exagerated
<GalaxyNova>
standardization isn't inherently bad
<GalaxyNova>
but most of the standards we have today are filled with decades worth of cruft and historical garbage that is kept around only for compatibility with older versions of the standards
<GalaxyNova>
over time this causes standards to become larger and larger
<midfavila>
legacy compatability is one of the main advantages of standards
<midfavila>
compatibility*
<midfavila>
obviously if you look at stuff like what GNU does, where they throw out new ideas every five minutes and then deprecate them in another five, that causes issues
<midfavila>
but idk, you look at, say, POSIX - sure, there are a handful of functions kept around for legacy support exclusively, but it's trivial to just... ignore those, or rewrite programs that use them
<GalaxyNova>
you can say that for anything
<midfavila>
yes, that's... kind of the point
<midfavila>
your statement can be applied to anything, but so can its inverse
<GalaxyNova>
well, there's a reason people use C over something like C++
<GalaxyNova>
when they could easily just ignore the features C++ gives them that they don't need
<GalaxyNova>
but the point is that it dirties the whole ecosystem
<midfavila>
sure, if you're a compiler writer (in the case of C++)
<midfavila>
so... don't write C++ compilers, or only implement a subset of it
<midfavila>
just because some standards are handled poorly doesn't mean all standards are, or even most
<GalaxyNova>
legacy compatibility isn't as important as people make it out to be
<GalaxyNova>
compatibility layers are a thing
<midfavila>
you uh
<midfavila>
you *realize* compat layers implement part or all of the abstract spec you're trashing,
<midfavila>
*in addition* to a bunch of other shit to translate it to underlying system calls?
<midfavila>
anyway, "legacy support" is critical
<midfavila>
it implies that the standard gives you time to actually use it
<GalaxyNova>
it's still better than trashing the base OS
rohan has quit [Ping timeout: 268 seconds]
<midfavila>
it's literally worse
rohan has joined #kisslinux
<midfavila>
if you're going to implement the standard anyway, and you're going to use it in a large number of system programs (or even a moderate amount), you should just... implement the standard
<GalaxyNova>
most people that use OSS software don't have a use for legacy compatibility, so they won't need the compatibility layer
<GalaxyNova>
since most software is just recompiled or patched when the OS breaks compatibility
<GalaxyNova>
and also standards like POSIX and ISO C are not free
<midfavila>
if the standards that those programs adhere to change, because "muh legacy", then you need to rewrite the programs
<midfavila>
end result? you spend a fuckton of wasted time rewriting things every time the standards change
<midfavila>
and I fail to see what you mean by "free" in that context