00:08:06pabs quits [Read error: Connection reset by peer]
00:08:45pabs (pabs) joins
00:09:41fireonlive is kicked by @OrIdow6 [as requested]
00:09:55fireonlive (fireonlive) joins
00:09:56<fireonlive>:P
00:10:39<@OrIdow6>(Took me a bit to figure out how to get the command right)
00:10:58<Notrealname1234>Got shut down
00:11:15<Notrealname1234>and stop being sussy fireonlive
00:17:50Notrealname1234 quits [Client Quit]
00:51:09Arcorann (Arcorann) joins
01:10:22etnguyen03 quits [Client Quit]
01:11:04etnguyen03 (etnguyen03) joins
01:12:10<fireonlive>take the middle of my name and reverse it
01:15:51<TheTechRobo>no
01:46:27<fireonlive>Mozilla Corporation Org Changes to Accelerate our Path to the Future https://blog.mozilla.org/en/mozilla/mozilla-corporation-org-changes-to-accelerate-our-path-to-the-future/
01:47:33<fireonlive>https://x.com/dixie3flatline/status/1794407971939832188?s=12 lmao
01:48:36NotGLaDOS quits [Quit: No Ping reply in 180 seconds.]
01:49:52NotGLaDOS joins
01:54:14etnguyen03 quits [Client Quit]
01:54:55etnguyen03 (etnguyen03) joins
02:20:06etnguyen03 quits [Client Quit]
02:20:47etnguyen03 (etnguyen03) joins
02:49:45<nukke>https://www.bleepingcomputer.com/news/security/high-severity-gitlab-flaw-lets-attackers-take-over-accounts/
03:29:51<nicolas17>not again
03:41:04<steering>>The security flaw (tracked as CVE-2024-4835) is an XSS weakness in the VS code editor (Web IDE) that lets threat actors steal restricted information using maliciously crafted pages.
03:41:15<steering>because everyone wants a halfbaked IDE in their web browser
03:41:31<steering>(I haven't actually tried it but I can only imagine it's painful)
03:57:47<fireonlive>steering: ima make you use nothing but vscode for 2 weeks
04:44:22shgaqnyrjp_ is now known as shgaqnyrjp
04:54:14etnguyen03 quits [Client Quit]
04:54:55etnguyen03 (etnguyen03) joins
05:10:51etnguyen03 quits [Remote host closed the connection]
05:43:09BlueMaxima quits [Read error: Connection reset by peer]
06:06:52nulldata quits [Ping timeout: 265 seconds]
06:10:54nulldata (nulldata) joins
07:29:34shgaqnyrjp quits [Remote host closed the connection]
07:30:47shgaqnyrjp (shgaqnyrjp) joins
09:00:04Bleo182600722719 quits [Client Quit]
09:01:32Bleo182600722719 joins
09:10:47Dango360 quits [Read error: Connection reset by peer]
09:14:20Dango360 (Dango360) joins
09:34:36Dango360 quits [Read error: Connection reset by peer]
09:37:52Dango360 (Dango360) joins
10:24:26Dango360 quits [Client Quit]
10:27:18Dango360 (Dango360) joins
10:42:51BearFortress joins
10:46:43BearFortress_ quits [Ping timeout: 265 seconds]
10:53:29Barto quits [Ping timeout: 265 seconds]
10:53:45Barto (Barto) joins
11:03:58nulldata quits [Ping timeout: 255 seconds]
11:52:37sludge quits [Remote host closed the connection]
11:52:39katocala quits [Remote host closed the connection]
11:52:42sludge joins
11:52:49katocala joins
12:27:53etnguyen03 (etnguyen03) joins
12:39:03<TheTechRobo>I'm out of inodes on an ext4 filesystem, but there's plenty of free space. I'd like to tar up the files onto that same filesystem as I'm running out of space on the server in general. If I delete one file, can I make a tarball of arbitrary size?
12:43:16etnguyen03 quits [Client Quit]
12:43:57etnguyen03 (etnguyen03) joins
13:37:36nulldata (nulldata) joins
13:51:22Arcorann quits [Ping timeout: 255 seconds]
14:23:46nulldata quits [Ping timeout: 255 seconds]
14:42:26nulldata (nulldata) joins
14:44:47nulldata quits [Client Quit]
14:45:31nulldata (nulldata) joins
14:55:55eroc19901 quits [Quit: The Lounge - https://thelounge.chat]
14:56:23eroc1990 (eroc1990) joins
14:57:34LeGoupil joins
15:21:22f_ quits [Ping timeout: 255 seconds]
15:24:25<nukke>TheTechRobo: I'm confused about that question. You mean delete the original file(s) after tar'ing them?
15:25:23<nukke>If so, yes, you will recover inodes after the fact. I actually worked on this exact issue at work this week. We have a server with millions and millions of individual CSV files, and new ones get dumped periodically by the thousands
15:25:58<nukke>A simple script to tar them and delete the originals will do the trick.
15:26:15<nukke>Of course, if you untar you will lose inodes again
15:26:48<TheTechRobo>nukke: Yes, but as I'm out of inodes, I can't create the tarball. If I delete one singular file off the filesystem, giving me one free inode, is that one inode enough to tar up everything, or do large files take up multiple inodes?
15:27:01<TheTechRobo>I unfortunately don't know very much about filesystems
15:28:07Notrealname1234 (Notrealname1234) joins
15:28:37<nukke>If you delete ONE file and then tar one more file, you can get a snowball effect
15:29:00<nukke>Taring one file will likely not need more than however many inodes get freed from deleting one
15:29:48<nukke>Depending on what the files are, you could cat multiple files into one
15:30:02<nukke>If it's text files, for example, condense multiple into one
15:32:44<thuban>eh? the point of the tar would already be to merge multiple files into one
15:34:21<thuban>TheTechRobo: i don't have any _specific_ knowledge of ext4, but i believe that a single file has a single inode regardless of size
15:34:53<TheTechRobo>thuban: Alright
15:37:17<nukke>thuban: cat'ing would make deleting one file unnecessary
15:37:36<nukke>So if you don't wanna lose ANY files, just merge two into one
15:38:40<thuban>ah, i guess. you'd need sponge or equivalent though
15:39:34<TheTechRobo>Fortunately I did have a few files on there I don't need
15:43:07Notrealname1234 quits [Client Quit]
16:00:24nicolas17 quits [Ping timeout: 265 seconds]
16:00:56nicolas17 joins
16:11:52Notrealname1234 (Notrealname1234) joins
16:16:56Notrealname1234 quits [Client Quit]
16:47:32Notrealname1234 (Notrealname1234) joins
16:50:45Notrealname1234 quits [Client Quit]
17:55:15qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
18:10:35etnguyen03 quits [Client Quit]
18:11:17etnguyen03 (etnguyen03) joins
18:24:52f_ (funderscore) joins
18:48:56etnguyen03 quits [Client Quit]
18:49:37etnguyen03 (etnguyen03) joins
19:01:00BearFortress_ joins
19:05:31BearFortress quits [Ping timeout: 265 seconds]
19:25:13matoro joins
19:27:09<nulldata>https://phys.org/news/2024-05-boeing-wont-leaky-starliner-flying.html
19:41:28<nulldata>https://www.foxbusiness.com/economy/american-airlines-passengers-miami-stuck-sweltering-boeing-plane-travelers
20:13:54etnguyen03 quits [Client Quit]
20:14:36etnguyen03 (etnguyen03) joins
20:22:18LeGoupil quits [Client Quit]
20:28:17PredatorIWD quits [Read error: Connection reset by peer]
20:33:18qwertyasdfuiopghjkl quits [Client Quit]
20:33:46PredatorIWD joins
21:35:58<nukke>It's been _ days since the last Boeing and/or Gitlab and/or Microsoft incident
21:36:18<@JAA>TIL GitLab uses VS Code.
21:36:36<@JAA>Also yeah, time to reset the 'days since serious GitLab vuln' counter.
21:37:14<nukke>I remember reading an interview or announcement about the upcoming 18.0 release and how they were patching some big vulns
21:37:29<nukke>That was like 2-3 weeks ago
21:38:02<@JAA>Let's not forget Ivanti & Co. :-)
21:39:04<nukke>Also this one https://cybersocialhub.com/csh/vmware-abused-in-recent-mitre-hack-for-persistence-evasion/
21:39:16<@JAA>TheTechRobo: I wouldn't be surprised if the answer to that question was 'it depends'. There are multiple implementations of the tar command, and they might differ in how they do tempfiles etc.
21:39:26<nukke>Hackers broke into MITRE and ran their own VMs on their esxi hosts lol
21:39:32<@JAA>But the output file would only consume a single inode, yeah.
21:39:49<@JAA>Ooh, yeah :-)
21:39:55<@JAA><this_is_fine.png>
21:40:57<nukke>Ohh that's the ivanti one
21:41:10<nukke>🤦
21:43:12<@JAA>Ah right
21:52:24qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
22:21:38etnguyen03 quits [Client Quit]
22:22:19etnguyen03 (etnguyen03) joins
22:26:39Notrealname1234 (Notrealname1234) joins
22:27:46Notrealname1234 quits [Client Quit]
23:11:58<@JAA>TIL ALTCHA: https://altcha.org/
23:13:58<@JAA>nicolas17: And https://github.com/altcha-org/altcha/issues/28 made me think of your comment about breakage on Discourse.
23:20:37etnguyen03 quits [Client Quit]
23:21:18etnguyen03 (etnguyen03) joins
23:36:35muklumsum joins
23:40:25muklumsum_ quits [Ping timeout: 255 seconds]
23:49:50<kpcyrd>seeking Nix help: https://github.com/kpcyrd/what-the-src/issues/12#issuecomment-2132435470