code logs -> 2024 -> Tue, 23 Apr 2024< code.20240422.log - code.20240424.log >
--- Log opened Tue Apr 23 00:00:32 2024
--- Day changed Tue Apr 23 2024
00:00
<&[R]>
Ciphers*
00:10
<@macdjord>
Good news: Found an article listing exactly the information I'm after: n never use' category.
00:10
<@macdjord>
<macdjord> Suggesting that warning is either outdated or more serious than it sounds.
00:10
<@macdjord>
Erg.
00:11
<@macdjord>
Good news: Found an article listing exactly the information I'm after: https://blog.stribik.technology/2015/01/04/secure-secure-shell.html
00:11
<@macdjord>
Bad new: It's over 9 years old; I'll need to find something fresher.
00:39
<@macdjord>
Huh. Looks like that post, while *originally* from 2015, has been updated as recently as late 2023. So it should still be a good resource.
00:44
<&[R]>
\o/
01:17
<&McMartin>
I grew up with DOS and picked up Linux pretty much immediately, though I didn't have anything worth _doing_ with it for another seven years
04:58 Degi_ [Degi@Nightstar-r3bk2i.pool.telefonica.de] has joined #code
05:00 Degi [Degi@Nightstar-5f38oe.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
05:00 Degi_ is now known as Degi
05:50
< bluefoxx>
ToxicFrog: It's not an issue of capacity to open them from the CLI why I install winrar, as much as GUI workflows when I'm outside of a CLI; oftentimes I just need to quickly remember the contents of an archive or extract one specific file, and that's tragically simpler for me in the GUI winrar offers than even some of the native linux offerings like peazip as one example
05:54
< bluefoxx>
[R]: I've used DOS in as much as I've run W98 in the distant past, and occasional use for low level boot tools, but never had a chance to experience it as a primary OS interface
05:54
< bluefoxx>
was thoroughly obsolete by the time I had any computer I could call my own
05:55
< bluefoxx>
I grew up using a macintosh clone who's GUI spat out the most useful question "Are you mocking me?" instead of any useful error messages I could have learned from, else I might have ever learned to do more than launch games from CDs on it
05:56
< bluefoxx>
I had some fun in high school mucking around on Windows XP systems but I didn't really learn much other than basic system adminstration level stuff
05:59
< bluefoxx>
There was a brief stint I had with installing Turbolinux on an old PII laptop, which I managed to stumble through without instruction, but when it dumped me at a root shell prompt I was utterly lost for guidance
05:59
< bluefoxx>
I didn't even know about man pages
06:02 Vornicus [Vorn@Nightstar-tai.093.243.23.IP] has joined #code
06:02 mode/#code [+qo Vornicus Vornicus] by ChanServ
07:10 macdjord [macdjord@Nightstar-igge6l.dsl.bell.ca] has quit [[NS] Quit: Deep inside, every housecat believes themself to be just a temporarily embarrassed tiger.]
07:16 macdjord [macdjord@Nightstar-igge6l.dsl.bell.ca] has joined #code
07:16 mode/#code [+o macdjord] by ChanServ
13:58
<&[R]>
Oof@man pages
14:23
<@celticminstrel>
> was thoroughly obsolete by the time I had any computer I could call my own
14:23
<@celticminstrel>
Similar. The first Windows computer I could use (mostly) whenever I wanted was around '95… but I already had my personal Mac by then, so I used that more.
14:24
<&ToxicFrog>
bluefoxx: I think you've missed my point -- having the command line tools installed enables RAR support for GUI tools like Ark. Although these days they might not even need that and just use libarchive.
14:59
<&[R]>
Do note that rar support in libarchive is newish
15:00
<&[R]>
So there could have been libarchive GUIs that needed the rar CLI stuff to support rar in the past
15:04
<&[R]>
Hmm, apparently "newish" is 2011
15:04
<&[R]>
RAR*5* support was added in 2019 which might be what confused me
15:04
<&[R]>
Sorry for the misinfo
15:05
<&[R]>
Alternatively, they could have used the rar cli for rar5 support
15:05
<&[R]>
libarchive cannot /write/ RARs though
15:07 [R] [rms@Nightstar-d7h8ki.org] has quit [Connection closed]
15:08 [R] [rms@Nightstar-d7h8ki.org] has joined #code
15:08 mode/#code [+ao [R] [R]] by ChanServ
16:31
<&[R]>
YIL: make can change the shell it uses; TIL: it's per-make-process D:
16:31
<&[R]>
(mk can have it per-rule)
17:33 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code
18:36
<@celticminstrel>
…can't you just write eg `sh -e stuff` or whatever?
18:36
<@celticminstrel>
Or -c maybe, I forget
18:40
<&[R]>
Sure, yes. But that's inconvenient
18:41
<&[R]>
I was mostly looking into it because the Makefile wasn't setting PATH correctly, found out that was a bug that was fixed in 4.4, which is why some systems (the ones with 4.3) would spew errors, but others (the ones with 4.4) worked fine
18:41
<@celticminstrel>
How many lines do youhave per rule?
18:41
<&[R]>
1-3 generally, do have a 9-ish line rule
18:42
<&[R]>
But I can properly stuff into $(CURDIR)/bin and have it run
22:27
< FLHerne>
I should trigger a chain of bugs that deletes my kernel and then crashes the system more often
22:27
< FLHerne>
but not too much
22:28
< FLHerne>
it makes me nostalgic for being like 14 when installing and then horribly breaking Linux on everything was my primary hobby :p
22:37
< FLHerne>
would be really annoying at the wrong time
22:37
< FLHerne>
but at, say, 8pm while not doing anything particularly important it's quite a good puzzle to spend a couple of hours on
23:04
<&[R]>
Get into ReactOS?
23:44 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
23:56 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
--- Log closed Wed Apr 24 00:00:42 2024
code logs -> 2024 -> Tue, 23 Apr 2024< code.20240422.log - code.20240424.log >

[ Latest log file ]