00:09:00fuzzy8021 quits [Remote host closed the connection]
00:09:00qwertyasdfuiopghjkl_ quits [Client Quit]
00:09:59fuzzy8021 (fuzzy8021) joins
00:22:33fuzzy8021 quits [Killed (NickServ (GHOST command used by fuzzy802!~fuzzy8021@173.224.25.67))]
00:23:27fuzzy8021 (fuzzy8021) joins
00:23:49Meli quits [Client Quit]
00:24:03Meli (Meli) joins
00:24:12qwertyasdfuiopghjkl_ joins
00:37:18Meli quits [Killed (NickServ (GHOST command used by Meli-sama))]
00:37:24Meli (Meli) joins
00:39:23qwertyasdfuiopghjkl_ quits [Remote host closed the connection]
01:09:35qwertyasdfuiopghjkl_ joins
03:11:25qwertyasdfuiopghjkl_ quits [Remote host closed the connection]
03:53:03qwertyasdfuiopghjkl_ joins
03:53:21qwertyasdfuiopghjkl_ is now known as qwertyasdfuiopghjkl
05:11:52mrfooooo0 joins
05:24:49mrfooooo06 joins
05:25:31mrfooooo0 quits [Client Quit]
05:25:31qwertyasdfuiopghjkl quits [Client Quit]
05:25:31mrfooooo06 is now known as mrfooooo0
05:36:39Meli quits [Ping timeout: 276 seconds]
05:43:07Meli (Meli) joins
05:44:07<kurusii>well, /root/startup.sh has a comment indicating 'versions 3.0 and 3.1 of the VM image use a file at...' so i must be on 3.1 at most, but for reference 'years' is at least five, but i see the docker image is updated on each boot, or at least from what i can glean from the scripts in /root. i've nothing but a getty on tty2 so i suppose 3.1?
05:44:50eroc1990 quits [Quit: The Lounge - https://thelounge.chat]
05:45:00<kurusii>sounds to me, though, that as long as the docker image is continuously updated, it's still "useful," and an upgrade to the host OS/appliance version would just bring some quality-of-life things to the host OS, correct?
05:46:09<kurusii>if that is the case, i'm not too worried. i was just looking at the VM on a whim and was wondering if it ever needed to be upgraded itself. it's clear from the webui that (some) projects are actually performing work, so i guess that answers my question.
05:46:24<kurusii>thanks for the help, and i admire your mission.
05:51:01eroc1990 (eroc1990) joins
06:13:38@JAA quits [Ping timeout: 265 seconds]
06:13:55JAA (JAA) joins
06:13:55@ChanServ sets mode: +o JAA
06:18:41AlsoJAA (JAA) joins
06:18:41@ChanServ sets mode: +o AlsoJAA
06:31:21qwertyasdfuiopghjkl_ joins
06:38:24qwertyasdfuiopghjkl_ is now known as qwertyasdfuiopghjkl
07:54:58yawkat (yawkat) joins
08:56:44qwertyasdfuiopghjkl quits [Client Quit]
11:56:31qwertyasdfuiopghjkl_ joins
11:57:47qwertyasdfuiopghjkl_ is now known as qwertyasdfuiopghjkl
12:03:41mrfooooo0 quits [Ping timeout: 268 seconds]
12:48:23tzt quits [Read error: Connection reset by peer]
12:51:40Sluggs joins
13:22:12mut4ntm0nkey quits [Remote host closed the connection]
13:22:43mut4ntm0nkey (mutantmonkey) joins
13:35:34Meli quits [Ping timeout: 268 seconds]
13:38:17Meli (Meli) joins
13:42:58mrfooooo0 joins
14:01:14qwertyasdfuiopghjkl quits [Client Quit]
15:47:59mrfooooo0 quits [Ping timeout: 265 seconds]
16:28:44mrfooooo0 joins
16:29:47mrfooooo0 quits [Remote host closed the connection]
17:24:21Iki1 quits [Ping timeout: 268 seconds]
18:35:53Meli quits [Ping timeout: 268 seconds]
18:38:19Meli (Meli) joins
20:28:15yano1 is now known as yano
21:06:49eroc1990 quits [Client Quit]
22:03:40tzt (tzt) joins
22:20:55eroc1990 (eroc1990) joins
22:27:54eroc1990 quits [Client Quit]
22:36:15eroc1990 (eroc1990) joins