% wrote:
Mike Easter wrote:
Mike Easter wrote OT in another thread:i don't have any stuff to save
In a discussion on reddit on this topic, one of the 'sages' had the
opinion that what we are talking about is the 'wrong approach' for
those of us who are taking care of our own systems rather than being
a tech trying to rescue someone else's.
That sage recommended wise planning w/ such as timeshift on linux and
appropriate regular backups, so that there is no need to pull out the
hammer and chisels to try to fix something.
There is a worthwhile discussion in the LM forum (somewhat) comparing
timeshift w/ clonezilla, which are two different 'things' in terms of
restoration and 'convenience' or speed.
https://forums.linuxmint.com/viewtopic.php?t=276749
(Solved ) timeshift vs Clonezilla
particularly:
https://forums.linuxmint.com/viewtopic.php?p=1520322#p1520322
Of course, the 'broad' question/answer of 'how should I backup my
'stuff' to prepare for some failure' is quite complicated, and not
nearly as 'simple' as timeshift vs clone, and needs to be done
'personally' w/ insight to what you have an how you need to keep it.
Personally, I don't do a very good job of it; 'I could do better'.
I give all the Linux fuckwits shit on youtube. If you ever want to be
tempted to take a baseball bat to your computer and monitor there's no
surer way than put Linux on it.
On Wed, 16 Jul 2025 09:41:25 -0400, Tony wrote:
% wrote:the 'sages' had the >>>> opinion that what we are
Mike Easter wrote:
Mike Easter wrote OT in another thread:
In a discussion on reddit on this topic, one of
talking about is the 'wrong approach' for >>>> those
of us who are taking care of our own systems rather
than being >>>> a tech trying to rescue someone
else's.
timeshift on linux and >>>> appropriate regularThat sage recommended wise planning w/ such as
backups, so that there is no need to pull out the
hammer and chisels to try to fix something.
(somewhat) comparing >>> timeshift w/ clonezilla,There is a worthwhile discussion in the LM forum
which are two different 'things' in terms of >>>
restoration and 'convenience' or speed.
https://forums.linuxmint.com/viewtopic.php?t=276749
(Solved ) timeshift vs Clonezilla
particularly:
should I backup my >>> 'stuff' to prepare for someOf course, the 'broad' question/answer of 'how
failure' is quite complicated, and not >>> nearly as
'simple' as timeshift vs clone, and needs to be done
you need to keep it.'personally' w/ insight to what you have an how
could do better'.Personally, I don't do a very good job of it; 'I
i don't have any stuff to save
I give all the Linux fuckwits shit on youtube. If
you ever want to be tempted to take a baseball bat
to your computer and monitor there's no surer way
than put Linux on it.
I've been running Linux since 1992. It's always been
the better choice...for me, and all our tens, then
hundreds, then thousands of customers.
There was another company we competed with in the
90's, which was married to Solaris. Buddy, did they
back the wrong horse(!). They aren't around anymore.
The company I worked for way back when originally settled on IBM
Token Ring. They also went full steam with Novell Netware. Not
surprising that they eventually went out of business. Choosing one
loser after another is not good business sense.
On 20 Jul 2025 23:44:14 GMT, Tegenaria wrote:
The company I worked for way back when originally settled on IBM
Token Ring. They also went full steam with Novell Netware. Not
surprising that they eventually went out of business. Choosing one
loser after another is not good business sense.
Hindsight is 6/6, don’t they say.
Novell NetWare was the dominant file/print-server platform from the latter 1980s right into about the mid-1990s.
It took Microsoft many years of
effort to push it out of that market.
Your company was far from alone in
betting on that particular horse.
It’s true token-ring started to look a bit long in the tooth by the latter 1980s. It was only true-blue IBM shops that stuck with it, and continued
to believe the FUD about colliding Ethernet frames being some kind of performance-killer.
Not to mention the typical IBM prices for their
proprietary technology.
On Mon, 21 Jul 2025 09:11:17 +0100, T i m wrote:
On 21/07/2025 06:47, Lawrence D'Oliveiro wrote:
It’s true token-ring started to look a bit long in the tooth by the
latter 1980s. It was only true-blue IBM shops that stuck with it, and
continued to believe the FUD about colliding Ethernet frames being some
kind of performance-killer.
But it was the case (CSMA/CD), long before 100% wire speed saturation?
I recall a colleague describing a demo by Sun Microsystems, done sometime
in the late 1980s, involving two pairs of their Unix workstations doing simultaneous data transfers. Apparently they were able to get to a
combined 98% bandwidth usage (i.e. useful data transferred, less
collisions). The idea between having two pairs was to demonstrate that the potential for collisions between the members of each pair was not as bad
as some had made out.
This would have been on 10Mb/s Ethernet, and it would have been on “thin- wire” cabling (coaxial cable with BNC connectors daisy-chained, collisions and all). UTP and star topologies came later.
On 21/07/2025 06:47, Lawrence D'Oliveiro wrote:
It’s true token-ring started to look a bit long in the tooth by the
latter 1980s. It was only true-blue IBM shops that stuck with it, and
continued to believe the FUD about colliding Ethernet frames being some
kind of performance-killer.
But it was the case (CSMA/CD), long before 100% wire speed saturation?
Hindsight is 6/6, don’t they say.
I recall a colleague describing a demo by Sun Microsystems, done sometime
in the late 1980s, involving two pairs of their Unix workstations doing >simultaneous data transfers. Apparently they were able to get to a
combined 98% bandwidth usage (i.e. useful data transferred, less
collisions). The idea between having two pairs was to demonstrate that the >potential for collisions between the members of each pair was not as bad
as some had made out.
This would have been on 10Mb/s Ethernet, and it would have been on thin- >wire cabling (coaxial cable with BNC connectors daisy-chained, collisions >and all). UTP and star topologies came later.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 35:47:27 |
| Calls: | 10,392 |
| Calls today: | 3 |
| Files: | 14,064 |
| Messages: | 6,417,151 |