Hey all,
I'm trying to copy configuration files from my old CentOS 6.6 32 bit
machine to my new CentOS 6.6 64 bit machine.
On my 32 bit machine:
[mlapier@mushroom ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:DB:E5:4E:9F
inet addr:192.168.15.105
When I issue this command on my new 64 bit machine, 192.168.15.101:
scp -pr mlapier(a)192.168.15.105: /home/mlapier/.thunderbird
/home/mlapier/.thunderbird
It copies all directories and files in 192.168.15.105: /home/mlapier/ to
192.168.15.101: /home/mlapier. I don't want all that, I just want the
.thunderbird folder and all it's contents.
The user and group account numbers match on the two machines for this
user so that's not the issue.
When I RTFM this is what I thought it said to do. I'm I misreading the
FM or is something weird going on here?
--
_
°v°
/(_)\
^ ^ Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/
****
On Sat, Feb 28, 2015 at 5:14 PM, Chris Murphy <lists(a)colorremedies.com> wrote:
> "Drives, and hardware RAID cards are subject to firmware bugs, just as
> we have software bugs in the kernel." makes no assessment of how
> common such bugs are relative to each other.
I don't want to underestimate the value of good hardware RAID with
BBWC implementations when it comes to avoiding problems that aren't
bugs, but are "just the way things are." For example unclean
shutdowns, and especially unclean shutdowns along with a device
failure.
There's a metric ton of really useful information in the man 4 md page
that most people probably aren't aware of because they usually read
the mdadm page.
http://linux.die.net/man/4/md
Relevant in this case is the Unclean Shutdown section. It's completely
rational for people to think, hmmm, maybe I'd rather get a hardware
RAID card that supports BBWC to avoid some of these problems? Plus
then you get to use no barriers, resyncs and degraded operation can
have much lower performance penalty, etc.
--
Chris Murphy