public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rearranging hard drives and data.
Date: Sat, 19 Dec 2020 22:31:38 +0100	[thread overview]
Message-ID: <20201219213138.lfouqtqile2fwfgz@grusum.endjinn.de> (raw)
In-Reply-To: <545fb66a-3d02-3daf-1ccb-7ad12b015f51@youngman.org.uk>

Hello,

On Sat, 19 Dec 2020, antlists wrote:
>On 19/12/2020 18:49, David Haller wrote:
>> -dnh, the MoBo though is quite a fine piece with 8 SATA + 2 eSATA
>>      ports onboard:)  I'm gonna miss eSATA in newer HW:(  Hot-plug
>>      almost like USB but full SATA feature set and speed (e.g. SMART).
>
>Buy add-in sata cards. The ones I've been looking at are two-port cards, with
>two internal and two external (jumper-selected) connectors.

I already got one. Yes, I'd pitch MoBo w/many SATA vs. MoBo w/fewer
SATA plus AddIn, but PCI(e) slots are also limited and >=2 port cards
get expensive rather quick, say a card with >= 4 internal and
_extra_[0] 1-2 eSATA ... So, I'll rather have a MoBo with lots of SATA
+ addin than MoBo plus tons of addin cards...

My MoBo has the AMD 710 "Southbridge" with 6 int. SATA2/3G [1] ports,
a MV9128 with 2 int. SATA3/6G ports and a JMB362 with 2 ext. eSATA2/3G
ports. Try to find _anything_ even remotely resembling that (with any
SATA rev) ;) My guess is, with most MoBos you'd need two 4-port addin
cards even for that. And my MoBo was not even expensive, just ~80 EUR
in 04/2010. BTW: GA-770TA-UD3, hosting a AMD Athlon II X2 250 for then
~65 EUR :) Still running as champs :))

Again: find me a MoBo + Addin Card(s) Combo with: >= 9 internal SATA
ports, >=1 eSATA ports (dedicated, not switched with one of the
internal ones!). An IDE port would be a nice extra.

Were it not for gentoo and large stuff needing 6+ hours to compile,
the occasional reencoding of a video[3], and some fucking websites
which take ages to load (which was one reason for me to update 10
years ago from my then Athlon 500[2])... *ELIDED* those *ELIDED*
webdevs *ELIDED* - sideways - *ELIDED* that *ELIDED* *ELIDED* so
called webpages that gobble CPU as if there's no tomorrow! And
*ELIDED* I know, I built webpages that (besides larger pictures) load
snappy over a 4kB/56kBit/s modem in fractions of a second (no wonder,
being typically <0.5KB in size and no JS or other crud, there's a lot
you can fit in 1 KB :).

What was I saying, ahh, yes: ... I'd not even consider upgrading.

Well, more RAM would be nice by now, what with those *ELIDED* browsers
and *ELIDED* Java-Apps gobbling RAM as if there's TiBs of it for
free... *ARGHHHH*&&RAS*()#@*{!@_)(@I*CONNECTION RESET BY BEER*

-dnh

[0] i.e. working in parallel to the internal ports

[1] SATA2 was still normal then

[2] yep, the original, slowest Athlon ever sold, sufficed for me for
    many many years, along with an even older Matrox Mystique (the
    original 150MHz RAMDAC but as the beefy 4MB SGRAM version)

[3] BTW: it's astonishing how inefficient some streamed videos are
    encoded, just today I crunched down one from 2.9GiB to about
    639MiB. Albeit, I scaled down from 720p to 576p, but do the maths.

    I regularly get to <50% of the size of the original without any
    scaling, and all without any visible loss (x264 with crf=23:nr=750,
    that codec-internal noise reduction alone can get you ~10% less
    size ;) Well, it's what you get when you don't know about codecs
    or you just run HW-encoders at defaults, I guess...

-- 
"That time in Seattle... was a nightmare.  I came out of it dead broke,
without a house, without anything except a girlfriend and a knowledge of
UNIX."  "Well, that's something," Avi says.  "Normally those two are
mutually exclusive."                    --Neal Stephenson, "Cryptonomicon"


  reply	other threads:[~2020-12-19 21:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 13:02 [gentoo-user] Rearranging hard drives and data Dale
2020-12-19 13:47 ` bobwxc
2020-12-19 16:51 ` David Haller
2020-12-19 17:28   ` Dale
2020-12-19 18:37   ` antlists
2020-12-19 18:49     ` David Haller
2020-12-19 20:10       ` antlists
2020-12-19 21:31         ` David Haller [this message]
2020-12-19 23:21           ` Wols Lists
2020-12-19 17:06 ` Neil Bothwick
2020-12-19 17:32   ` Dale
2020-12-19 17:48     ` Neil Bothwick
2020-12-19 17:54       ` Dale
2020-12-19 21:48         ` Neil Bothwick
2020-12-20  1:02           ` Dale
2020-12-19 18:55     ` antlists
2020-12-19 19:19       ` Dale
2020-12-20  1:06 ` Frank Steinmetzger
2020-12-20  3:01   ` Dale
2020-12-20 14:21     ` Frank Steinmetzger
2020-12-20 22:37       ` Dale
2020-12-20 10:03   ` antlists
2020-12-20 13:20     ` Frank Steinmetzger
2020-12-20 13:39       ` Mark Knecht
2020-12-21  0:33       ` antlists
2020-12-21  0:20 ` Dale
2020-12-21  2:52   ` William Kenworthy
2020-12-21  9:19     ` Dale
2020-12-21 11:26       ` Frank Steinmetzger
2020-12-25  9:41         ` Dale
2020-12-21 10:48   ` Frank Steinmetzger
2020-12-21 12:53     ` Dale
2020-12-22  0:12       ` antlists
2020-12-24 16:38         ` Dale
2020-12-24 20:33           ` Frank Steinmetzger
2020-12-25  9:15             ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201219213138.lfouqtqile2fwfgz@grusum.endjinn.de \
    --to=gentoo@dhaller.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox