Uptime

damgar · 07-11-2012, 09:43 PM

Quote:

Originally Posted by Col-Panic

Firewall - router machine with ten 1 gbps ports, with a couple of different 802.1Q bonded interfaces:

Code:

blackhole:~# cat /etc/slackware-version; uname -a; uptime
Slackware 11.0.0 (x86_64)
Linux blackhole 2.6.19.2-grsec #3 Sat Apr 28 20:37:38 PDT 2007 x86_64 x86_64 x86_64 GNU/Linux
 10:44:39 up 1461 days,  4:05,  5 users,  load average: 0.00, 0.00, 0.00

It's been a great box. So much more versatile than some of the Cisco PIX and ASA units that we also have in service here.

It's a 64 bit version of Slackware 11?

kingbeowulf · 07-12-2012, 01:19 AM

Quote:

Originally Posted by damgar

It's a 64 bit version of Slackware 11?

I was wondering about Col-Panic's box too. Back then, I was running Slackware 11 on some PIII laptops and my AMD64 was running SLAMD64 11 so I could play with x86_64.

Col-Panic · 07-12-2012, 10:57 AM

Quote:

Originally Posted by kingbeowulf

Quote:

Originally Posted by damgar

It's a 64 bit version of Slackware 11?

I was wondering about Col-Panic's box too. Back then, I was running Slackware 11 on some PIII laptops and my AMD64 was running SLAMD64 11 so I could play with x86_64.

Yes, this one is a Slamd64 machine with a Xeon proc. Slamd64 11.0 reported itself as "Slackware 11.0.0 (x86_64)," whereas Fred changed it on subsequent versions to have an /etc/slamd64-version file that didn't call itself Slackware.

fskmh · 07-12-2012, 06:38 PM

Quote:

Originally Posted by Col-Panic

Yes, this one is a Slamd64 machine with a Xeon proc. Slamd64 11.0 reported itself as "Slackware 11.0.0 (x86_64)," whereas Fred changed it on subsequent versions to have an /etc/slamd64-version file that didn't call itself Slackware.

I have a couple of old Opterons still running that. Fred did some good work on Slamd64.

Here's another one:

Code:

fskmh@fskbhe2:~> cat /etc/slamd64-version; uname -a; uptime
Slamd64 12.1.0
Linux fskbhe2 2.6.26.6-dazuko-grsec #2 SMP Fri Oct 31 18:42:08 SAST 2008 x86_64 x86_64 x86_64 GNU/Linux
 01:25:31 up 307 days, 10:56,  3 users,  load average: 3.00, 2.67, 3.02

This is a campus intranet machine but it is firewalled and I keep everything up-to-date manually (httpd, php, ftpd, sshd etc).

Col-Panic · 07-13-2012, 02:51 PM

Quote:

Originally Posted by fskmh

Fred did some good work on Slamd64.

Yes, he did! A lot of folks are indebted to him for his contributions to Slackware 64.

Quote:

Originally Posted by fskmh

Here's another one:

Code:

fskmh@fskbhe2:~> cat /etc/slamd64-version; uname -a; uptime
Slamd64 12.1.0
Linux fskbhe2 2.6.26.6-dazuko-grsec #2 SMP Fri Oct 31 18:42:08 SAST 2008 x86_64 x86_64 x86_64 GNU/Linux
 01:25:31 up 307 days, 10:56,  3 users,  load average: 3.00, 2.67, 3.02

Sweet, another grsecurity-enhanced Slamd64 machine!

wargus · 07-15-2012, 10:46 AM

Quote:

Originally Posted by Col-Panic

Sweet, another grsecurity-enhanced Slamd64 machine!

Yes I wonder a bit now as I found grsecurity through an "incident" since most of people are talking about SELinux and it's spread much wider, but it also is regularly exploited by Spender (the GRSec maintainer) to show that it's quite for nothing

Are people just silently using grsecurity and don't talk about it? (Maybe because it's that simple and easy to use)

damgar · 07-15-2012, 09:51 PM

Code:

 20:49:27 up 35 min,  5 users,  load average: 2.17, 1.59, 1.13

I ran in circles for 3 days to get those 35 minutes! Stupid DIMM slot failed, causing the disk to fail, causing me to believe in gremlins! lol