Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177586

Re: HELP! Re: How to fix I/O errors?

Show all headers | View raw

On Wednesday, February 08, 2017 06:37:55 PM Marc Shapiro wrote:
> On 02/08/2017 03:06 PM, Ric Moore wrote:
> > On 02/08/2017 04:38 PM, Marc Shapiro wrote:
> > Careful there, I would not copy any of the /home/username/dot-files or
> > dot directories over, except like .mozilla and .thunderbird, so you
> > don't carry over some old and crufty setting that might have been
> > problematic. To spare you nightmares like this one, I use the /opt
> > directory on a separate partition for all of my personal data.
> > So, I use /opt/ric/Documents and in my brand-new /home/ric directory I
> > delete the newly created Documents directory and then link (ln -s
> > /opt/ric/Documents Documents) and do the same with the other familiar
> > home directories like Videos, Music, Downloads, everything except
> > Desktop. If something goes ape, systemk-wise, you can do a fresh
> > install of / (root) directory and leave /opt alone. I've done this
> > since the old Caldera days. Nary a burp in the barrel! Ric

Why not make your own top level directory, i.e. /ric (with Documents and 
such)--that's what I do.

> I don't usually go quite that far, but photos, videos, and virtual disks
> are all in /usr/local/  which I will also need to copy over.  

Same comment as above--why not make your own top level directory for that 
stuff.  (Reading the File Hierarchy Standard (FHS), I don't think that is quite 
the intent of /usr/local--and could make some things inconvenient at one time 
or another...)

> You say to
> avoid copying   except .mozilla and .thunderbird.  I have 117 such
> dot-files and dot-directories.  Are you saying only to leave .mozilla
> and .thunderbird and have everything else rebuild when it is next used.
> Admittedly, that will get rid of some cruft, but how should I determine
> if there are others that I should keep?
> 
> 
> I tried to format the new drive using st (Seagate Tools).  It said that
> it would remove all data, which is expected, but nothing was removed!
> It also took less than a minute.  Should I be using /dev/sda in the
> command line instead of /dev/sg0 (which is how st -l lists the drive?
> 
> 
> Marc
> 
> 
> 
> Marc

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

HELP! Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-08 08:40 +0100
  Re: HELP! Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-08 19:00 +0100
  Re: HELP! Re: How to fix I/O errors? Ric Moore <wayward4now@gmail.com> - 2017-02-09 00:10 +0100
    Re: HELP! Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-09 00:40 +0100
      Re: HELP! Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-09 01:00 +0100
        Re: HELP! Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-09 02:40 +0100
          Re: HELP! Re: How to fix I/O errors? (SOLVED) Marc Shapiro <marcnshap@gmail.com> - 2017-02-11 08:40 +0100
            Re: HELP! Re: How to fix I/O errors? (SOLVED) David Christensen <dpchrist@holgerdanske.com> - 2017-02-11 23:30 +0100
      Re: HELP! Re: How to fix I/O errors? rhkramer@gmail.com - 2017-02-09 03:00 +0100
    Re: HELP! Re: How to fix I/O errors? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-02-09 14:20 +0100
      Re: HELP! Re: How to fix I/O errors? Ric Moore <wayward4now@gmail.com> - 2017-02-09 18:10 +0100
        Re: HELP! Re: How to fix I/O errors? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-02-09 18:20 +0100
          Re: HELP! Re: How to fix I/O errors? Ric Moore <wayward4now@gmail.com> - 2017-02-10 18:50 +0100

csiph-web