<noocsharp>
i imagine that it doesn't run when you're not using it
akira01 has quit [Ping timeout: 255 seconds]
claudia has quit [Quit: Leaving]
sad_plan has joined #kisslinux
sad_plan has quit [Read error: Connection reset by peer]
mrlix has quit [Quit: Client closed]
<konimex>
windows 365? OS-as-a-service?
sad_plan has joined #kisslinux
GalaxyNova has quit [Read error: Connection reset by peer]
GalaxyNova has joined #kisslinux
<acheam>
OSAAS
<acheam>
has a good ring to it
<sad_plan>
and what might 'OSAAS' be?
<sad_plan>
os as a service?
<sad_plan>
nvrm
<sad_plan>
has anyone encountered that suddenly one of your firefox profiles is suddenly not able to connect to the internet? mine suddenly does...
<sad_plan>
ah, its one of my extensions appearantly
zenomat has quit [Ping timeout: 256 seconds]
zenomat has joined #kisslinux
zenomat has joined #kisslinux
zenomat has quit [Changing host]
sad_plan has quit [Remote host closed the connection]
<acheam>
wow I didn't expect this much crud on obsd
<acheam>
try to install a browser and it pulls in dbus, avahi, gettext, etc
<acheam>
kiss-bsd is looking more and more likely
sad_plan has joined #kisslinux
<sad_plan>
oh. I though obsd was more minimal than that tbh..
<sad_plan>
in any case, kiss-bsd sounds exciting
<acheam>
also for whatever reason the coil whine is baaaad
<acheam>
could be a coincedanece though
<sad_plan>
kernel adjustment possibly?
<acheam>
also many many dotfiles in ~
<sad_plan>
thats no supprise. but that should be configurable, as its on linux
<noocsharp>
acheam: which browser?
sad_plan has quit [Quit: ]
<acheam>
noocsharp: any of the big ones
<acheam>
I tried chromium, otter, and settled on firefox
<noocsharp>
yeah, i don't think obsd people care too much about reducing dependencies
<noocsharp>
to the degree that kiss does
<necromansy>
as long as its secure yeah they don't mind
sad_plan has joined #kisslinux
<GalaxyNova>
> nobody's making you use it
<GalaxyNova>
We'll se in another 5 years noocsharp xD
<GalaxyNova>
I think it's very likely for actual operating systems to just become chrome bootloaders that connect to a cloud OS
<noocsharp>
that's what people said 5 years ago
<GalaxyNova>
ok
<GalaxyNova>
i said that 5 years ago too lmao
<GalaxyNova>
but this time it's real
<sad_plan>
noocsharp: are you using just the -d flag for sdhcp? I can only get it to start, if im already using dhcpcd, after stopping dhcpcd, and then start sdhcp. if I uninstall dhcpcd, I for some reason cant start sdhcp..
<sad_plan>
wait, maaybe I got it. sdhcp -d -e wpa_supplicant -i wlan0, does that sound about right?
sad_plan has quit [Quit: ]
emmett1 has joined #kisslinux
sad_plan has joined #kisslinux
GalaxyNova has quit [Quit: Whoooooshh]
<sad_plan>
nooppe
<noocsharp>
the man page says -f keeps it in the foreground
<noocsharp>
which is what you want
<sad_plan>
ah, I though the other way around.
sad_plan has quit [Client Quit]
sad_plan has joined #kisslinux
<dilyn>
konimex: hey, try downloading libsodium for me will ya
<sad_plan>
now we're talking. many thanks noocsharp
<noocsharp>
no prob, next time i'd recommend just reading the man page
<noocsharp>
suckless man pages tend to be pretty concise
<sad_plan>
I usually do, but I sometimes struggle to decypher them, if theyre somewhat wierdly formatted. I could only read it in the same format as in the html page, which at first glance didnt really tell me too much.
<sad_plan>
arent they using mandoc or something to open them? mandoc is atleast mentioned on their site as recommended.. but if they use something else, I would obviously fetch that aswell
<konimex>
dilyn: package manager fault, will open an issue to dylan
<dilyn>
i already got it lol
<acheam>
heres a fun quirk: obsd gtk defaults to emacs bindings
<dilyn>
just wanted a sanity check hehe
<dilyn>
we found the bug folx. Everyone who was up in arms over this source file parsing business, rejoice. you have been vindicated
<noocsharp>
sad_plan: if you install the man page in your package, `man sdhcp` should work fine
<noocsharp>
if you have mandoc installed
<noocsharp>
dilyn: that's hilarious
<dilyn>
I was utterly baffled
<noocsharp>
it's so easy to construct tarballs now that break the package manager...
<sad_plan>
I dont belive I was able to open it anyway that way. does it matter if Its installed elsewhere than the makefiles default?
<noocsharp>
where is it installed to?
<sad_plan>
I also used cp install of make install aswell, cause the makefile wasnt as I wanted it..
<sad_plan>
in /usr/share
<sad_plan>
but makefile wans /usr/local/share/man/ iirc
<dilyn>
it would go in /usr/share/man/manX/sdhcp.X
<msk[m]>
rip my dream of making a program called VERSION
kawics11 has quit [Ping timeout: 258 seconds]
<cem>
msk[m]: rip
<micro_O>
cem similar boat with my tools, they are just going to bail on any sources file with VERSION|... all those other strings
<micro_O>
which is kind of a shame because for sources files that actually are plain text and would work, I can no longer be sure
<micro_O>
(downside of the substitution being opt-out by default, instead of opt-in)
<micro_O>
If single '\' character is invalid for url or filepath, and that was used to opt-in to string interpolation, then it would at least give tools something to work with
<cem>
yeah, honestly that change is the single worst thing to happen to the packaging system
<cem>
it just destroys the notion of static, easy-to-parse, easy-to-interact packages
<cem>
i think the best course of action will be to revert it
<cem>
but i doubt it
<acheam>
it wont happen, dylan has made that very clear
<acheam>
but really, its just a sed call away
<acheam>
in ASD, I was using it, but more casually, not going through and changing all the packages at once, but rather just using when creating new packages, or bumping them
<cem>
maybe i should clean up and release crm one of these days :D
<acheam>
sorry, remind me what crm is again?
<acheam>
oh nvm i remember
<cem>
yeah, it's my version update tool
<cem>
I also use macros because updating some packages are annoying, but I believe that the outcome should always be static
michalsieron has quit [Ping timeout: 252 seconds]
<micro_O>
yeah i think its tricky to separate out 'this use case is invalid' from 'this use case is valid, but maybe there are different ways to achieve this same goal'
<micro_O>
one thing i'll do is thing 'is this build-time, or run-time' to decide if something should be a tool for myself to use, versus a feature to be delivered
<micro_O>
it shows up a lot around packaging and releasing (outside of linux package manager context)
<micro_O>
though I appreciate the insistence that VERSION macros are supposed to be opt-in, they are only opt-in for the maintainers of packages. they are strictly necessary for everyone else.
<micro_O>
I think it can also be achieved by some sort of `lint`/`format` tool
<micro_O>
where lint would just display 'hey, i see that in the last commit, you had a version-string-like that matched in both VERSION and SOURCES, but there is no longer a match'
<micro_O>
and `fix` would do something like the current runtime behaviour, at build-time
<micro_O>
anyway, there are 1000x ways to implement this, and I would not be surprised if continued discussion would be wearing down or frustrating dylan
<micro_O>
so like i say every day and then don't actually do, i'll shut up about this
kawics11 has joined #kisslinux
<acheam>
oof 0x0.st is down
<micro_O>
acheam try ix.io as an alternative
<acheam>
i use my own thing
<acheam>
l.armaanb.net
<acheam>
just a shame that 0x0 is down
kawics11 has quit [Ping timeout: 240 seconds]
kawics11 has joined #kisslinux
kawics11 has quit [Ping timeout: 255 seconds]
<acheam>
re: the windows 365 discussion earlier
<acheam>
i've been using remote computing a lot in the last few weeks for some scientific modeling stuff
<acheam>
and its actually not bad at all
<acheam>
i prefer it to running it locally because I don't have to install a bunch of crap on my local machine