On 2/20/2018 8:09 PM, Richard Pieri wrote:
> syncoid is exactly what I need.
> Perhaps sanoid, too, but I want to see it running for a while.
Or not what I need. Rather, I couldn't quite get it to do what I want.
It did give me the clues I needed to do it myself which for me is good
enough.
Got t
On Tue, Feb 20, 2018 at 08:09:28PM -0500, Richard Pieri wrote:
> On 2/19/2018 2:43 PM, Dan Ritter wrote:
> > You might want to look at sanoid/syncoid --
> > https://github.com/jimsalterjrs/sanoid/
>
> syncoid is exactly what I need.
> Perhaps sanoid, too, but I want to see it running for a while.
On 2/19/2018 2:43 PM, Dan Ritter wrote:
> You might want to look at sanoid/syncoid --
> https://github.com/jimsalterjrs/sanoid/
syncoid is exactly what I need.
Perhaps sanoid, too, but I want to see it running for a while.
--
Rich P.
___
Discuss mailin
On 2/19/2018 12:10 PM, Richard Pieri wrote:
> send/receive. I also need to get a USB3 cradle because the ASRock board
> doesn't have eSATA.
Annoying. Drove to Microcenter this afternoon and picked up a couple of
USB docks which are prominently labeled "UASP Support".
Neither of them actually supp
On 2/19/2018 2:43 PM, Dan Ritter wrote:
> You might want to look at sanoid/syncoid --
> https://github.com/jimsalterjrs/sanoid/
Interesting.
Certainly worth trying out given that snapshots are cheap.
--
Rich P.
___
Discuss mailing list
Discuss@blu.org
On Mon, Feb 19, 2018 at 12:10:58PM -0500, Richard Pieri wrote:
>
> I need to rework my external backups. The script uses Btrfs snapshots
> and rsync. It needs to be adapted to use ZFS snapshots and zfs
> send/receive. I also need to get a USB3 cradle because the ASRock board
> doesn't have eSATA.
Finished the migration this morning. Some of my thoughts about the process.
Debian 9. While I don't like the direction Debian has gone with the last
few releases it remains the distribution I can most quickly stand up and
configure. The system drive still has plenty of room for some other
distro w
On 2/15/2018 1:52 AM, Greg Rundlett (freephile) wrote:
> So what's the approximate cost for that equipment? Just curious since I
> don't have any clue what stuff goes for since I'm not in the habit of
> building systems.
Most of these prices are Amazon. The Motherboard is NewEgg.
Case: $110
PSU:
So what's the approximate cost for that equipment? Just curious since I
don't have any clue what stuff goes for since I'm not in the habit of
building systems.
Greg Rundlett
https://eQuality-Tech.com
https://freephile.org
On Wed, Feb 14, 2018 at 8:33 PM, Richard Pieri
wrote:
> Finished the ini
Finished the initial build and running Memtest now. Parts:
Case: Fractal Design Node 304. Mostly for the six drive bays in a Mini
ITX form factor.
PSU: Corsair CX 450. Probably more power than I need but better to have
the power and not need it than needing to replace the PSU.
Motherboard: ASRoc
Actually, QNAP is probably one of the worst storage system vendors. They
offer little or no support. They sat on a silent corruption bug until they
were out-ed by a blogger who went public after the company's refusal to
acknowledge the bug:
http://www.sbsfaq.com/?p=4277
I have personally had to d
On 2/5/2018 3:07 PM, Greg Rundlett (freephile) wrote:
> However, they don't mention anything in the release notes yet
> https://www.qnap.com/en/releasenotes/ so I'm unsure if it's "in there".
Safer to assume the patches are not included unless specifically listed.
> They advise:
>
>- Do not
At least QNAP offer to one-click secure your installation with a Let's
Encrypt cert through their SSL management plugin - even though they sell
certs through the the same plugin/admin interface.
(ed. note: TLS/SSL does not prevent Spectre / Meltdown - it's just an
indication that QNAP are not 'cra
I have a QNAP TS-231 (dual bay SMB NAS)
https://static.myqnapcloud.com/device_model/53466f86d6b82f5cd5295b28?r=1517796001
QNAP offered this security advisory on Jan. 8th
https://www.qnap.com/en-us/security-advisory/nas-201801-08
And have released firmware upgrades since then ( 2018/01/30 ) QTS
4
On 2/5/2018 10:30 AM, Joe Polcari wrote:
> I just got an update today which, I think, covers it.
The CVE referenced in the release notes fixes a local privilege
escalation bug in ipesc. The Meltdown/Spectre CVEs are still listed as
"Ongoing" as of this writing:
https://www.synology.com/en-us/supp
Nope - I was wrong
This is the one it addresses CVE-2017-16939
On 2/5/18, 10:30 AM, "Discuss on behalf of Joe Polcari"
wrote:
>I just got an update today which, I think, covers it.
>
>On 2/5/18, 9:33 AM, "discuss-bounces+joe=polcari@blu.org on behalf of
>ma...@mohawksoft.com" of ma...@mohaw
I just got an update today which, I think, covers it.
On 2/5/18, 9:33 AM, "discuss-bounces+joe=polcari@blu.org on behalf of
ma...@mohawksoft.com" wrote:
>This is common across the industry. EMC, Cisco, IBM, and others have said
>basically the same thing. I would dump synology because its cra
This is common across the industry. EMC, Cisco, IBM, and others have said
basically the same thing. I would dump synology because its crap, but not
because of that.
> The Meltdown and Spectre vulnerabilities were publicly disclosed 3
> January.
>
> Synology posted their own security advisory 5 day
The Meltdown and Spectre vulnerabilities were publicly disclosed 3 January.
Synology posted their own security advisory 5 days later on 8 January
listing these vulnerabilities as moderate "because these vulnerabilities
can only be exploited via local malicious programs." As if there were no
ways f
19 matches
Mail list logo