I can say, however, that I've reunited with an "old friend" who is still in great shape.
Uncategorized
14
Posts
6
Posters
11
Views
-
I can say, however, that I've reunited with an "old friend" who is still in great shape. Before I get dozens of replies about it being insecure: in theory, it is, but it's not accessible from the outside. It's isolated within its own network and is only able to connect and fetch backups for 'extreme disaster recovery' (only at specific times, restricted by specific firewall rules). It served its purpose today, and tomorrow, it might be even more useful.
18:33:01 up 3188 days, 4:47, 1 user, load average: 5.09, 4.73, 4.74
Debian, Btrfs, and zero internal dust.
It's kept in a sterile, extremely protected room. -
I can say, however, that I've reunited with an "old friend" who is still in great shape. Before I get dozens of replies about it being insecure: in theory, it is, but it's not accessible from the outside. It's isolated within its own network and is only able to connect and fetch backups for 'extreme disaster recovery' (only at specific times, restricted by specific firewall rules). It served its purpose today, and tomorrow, it might be even more useful.
18:33:01 up 3188 days, 4:47, 1 user, load average: 5.09, 4.73, 4.74
Debian, Btrfs, and zero internal dust.
It's kept in a sterile, extremely protected room.@stefano Btrfs existed in a Debian release 3318 days ago? I'm getting old -
I can say, however, that I've reunited with an "old friend" who is still in great shape. Before I get dozens of replies about it being insecure: in theory, it is, but it's not accessible from the outside. It's isolated within its own network and is only able to connect and fetch backups for 'extreme disaster recovery' (only at specific times, restricted by specific firewall rules). It served its purpose today, and tomorrow, it might be even more useful.
18:33:01 up 3188 days, 4:47, 1 user, load average: 5.09, 4.73, 4.74
Debian, Btrfs, and zero internal dust.
It's kept in a sterile, extremely protected room.@stefano
Old enough to go to school 😅 -
I can say, however, that I've reunited with an "old friend" who is still in great shape. Before I get dozens of replies about it being insecure: in theory, it is, but it's not accessible from the outside. It's isolated within its own network and is only able to connect and fetch backups for 'extreme disaster recovery' (only at specific times, restricted by specific firewall rules). It served its purpose today, and tomorrow, it might be even more useful.
18:33:01 up 3188 days, 4:47, 1 user, load average: 5.09, 4.73, 4.74
Debian, Btrfs, and zero internal dust.
It's kept in a sterile, extremely protected room.@stefano sooo, running since April 1017, that's Debian Jessie (8) if stable.. right?
-
@stefano sooo, running since April 1017, that's Debian Jessie (8) if stable.. right?
@peterk yes, it is 😉
deb http://archive.debian.org/debian jessie main contrib non-free
-
@stefano
Old enough to go to school 😅@toromtomtom and, considering the clean dmesg, with great results!
-
@stefano Btrfs existed in a Debian release 3318 days ago? I'm getting old
@feld yes, I'm old, too...
-
@peterk yes, it is 😉
deb http://archive.debian.org/debian jessie main contrib non-free
@stefano end of ELTS was in June 2025.. I think it's time.. 🙂
-
@stefano end of ELTS was in June 2025.. I think it's time.. 🙂
@peterk I think it will stay that way until it will break. They don't want/can't touch it at the moment.
-
I can say, however, that I've reunited with an "old friend" who is still in great shape. Before I get dozens of replies about it being insecure: in theory, it is, but it's not accessible from the outside. It's isolated within its own network and is only able to connect and fetch backups for 'extreme disaster recovery' (only at specific times, restricted by specific firewall rules). It served its purpose today, and tomorrow, it might be even more useful.
18:33:01 up 3188 days, 4:47, 1 user, load average: 5.09, 4.73, 4.74
Debian, Btrfs, and zero internal dust.
It's kept in a sterile, extremely protected room.OMG after all these years and switching to *BSD you still remember how it works 😆
-
I can say, however, that I've reunited with an "old friend" who is still in great shape. Before I get dozens of replies about it being insecure: in theory, it is, but it's not accessible from the outside. It's isolated within its own network and is only able to connect and fetch backups for 'extreme disaster recovery' (only at specific times, restricted by specific firewall rules). It served its purpose today, and tomorrow, it might be even more useful.
18:33:01 up 3188 days, 4:47, 1 user, load average: 5.09, 4.73, 4.74
Debian, Btrfs, and zero internal dust.
It's kept in a sterile, extremely protected room.@stefano Wow..... just wow.
I have never come even close to this record on anything, EXCEPT a Livingston Portmaster 3 series.
The last dialup bank we decommed at $weDropPackets, pm3-4, had an uptime of over 4,000 days.
We had FreeBSD servers with uptimes approaching 1,000 days, but nothing even close to this.
And, I'm not going to lie, when I took the reigns in 2004..... long uptimes on devices that still had regular security patches went away. We went from the culture of almost never patching to a culture of _always_ patching unless we couldn't.
Drove the owner nuts.
When I took over, we had FreeBSD 5, 4, and 3 servers in production. By the time FreeBSD 6 came out, that was all we had.
But hot damn, those Cisco 7507s and Livingston Portmasters had some insane uptimes.
-
OMG after all these years and switching to *BSD you still remember how it works 😆
@Glop_glop_pasGlop I've never abandoned Linux, as I have never abandoned the BSDs. I've used all of them over the years 🙂
-
@stefano Wow..... just wow.
I have never come even close to this record on anything, EXCEPT a Livingston Portmaster 3 series.
The last dialup bank we decommed at $weDropPackets, pm3-4, had an uptime of over 4,000 days.
We had FreeBSD servers with uptimes approaching 1,000 days, but nothing even close to this.
And, I'm not going to lie, when I took the reigns in 2004..... long uptimes on devices that still had regular security patches went away. We went from the culture of almost never patching to a culture of _always_ patching unless we couldn't.
Drove the owner nuts.
When I took over, we had FreeBSD 5, 4, and 3 servers in production. By the time FreeBSD 6 came out, that was all we had.
But hot damn, those Cisco 7507s and Livingston Portmasters had some insane uptimes.
@nuintari It was 2006, I think (or 2007 at the latest), and I went with a colleague to a company - the same one that, incidentally, gave us some decommissioned Digital AlphaStations. They showed me a machine (not connected to the network, obviously) that they were still using for payroll. I couldn't quite tell what it was exactly, but it was some kind of Unix system and it had been rebooted for the last time... in 1986.
I believe it’s the longest uptime I’ve ever seen. -
@nuintari It was 2006, I think (or 2007 at the latest), and I went with a colleague to a company - the same one that, incidentally, gave us some decommissioned Digital AlphaStations. They showed me a machine (not connected to the network, obviously) that they were still using for payroll. I couldn't quite tell what it was exactly, but it was some kind of Unix system and it had been rebooted for the last time... in 1986.
I believe it’s the longest uptime I’ve ever seen.@stefano When I was still working at $weDropPackets, we had an intern who had never seen..... anything.
We installed new service on a network, and, instead of looking at the existing network, he just dropped in a router on 192.168.0.1/24.
Problem is, they had an AS/400 on that address, and their previous provider had used .254 as the gateway/dhcp server.
It turns out, AS/400s do not handle ARP conflicts well, at all.
Had to get the vendor on the horn, because I am not an IBM person. He was very nasty, "I don't understand why anyone did this, why did this happen?"
Dude, we hired an 18 year old, and he was an idiot..... get over it and help me fix this shit.
That was the day I learned that nearly all IBM mainframe commands begin with the letter W for some reason.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@wcbdata we're larger than you think! 😜
-
Coming soon. Too soon. Well… already here.
-
@andypiper I read this as "choose a thousand small communists..." and yep, it still holds up that way. 👍
-
Choose #Monsterdon. Choose #SilentSunday. Choose #CatsOfMastodon. Choose #BelieveInFilm. Choose #Mosstodon. Choose optionality. Choose respect.
-
@OliviaVespera YES! If you have any examples feel free to share them with me... I'll add them to my resistance / inspiration mood board 😊
-
-
Choose creativity. Choose interoperability instead of being walled in or caged. Choose joy. Choose The Indie Beat!
-
@andypiper Choose a network that doesn’t try to make you dependent, but leaves the door open when you need a break.
Choose conversation over conflict.
Choose slow social instead of doomscrolling.
Choose people, not brands.
Choose Fediverse.
Because maybe the internet isn’t broken — maybe it just needs to belong to us again.
