Re: Replacing a new HD
On Thu, 2002-06-20 at 17:21, csj wrote:
> On 20 Jun 2002 04:56:41 -0500
> Ron Johnson <ron.l.johnson@cox.net> wrote:
>
> > If I copy /boot to /new/boot on /dev/hdc1, and / to /new/treeroot
> > on /dev/hdc2, then symlinks like /vmlinuz which are now
> > /new/treeroot/vmlinuz still point back to /dev/hda1 instead of
> > automagically pointing to /dev/hdb1.
>
> Why should vmlinuz point back to hda1? It should point back to a file,
> not a device.
But files don't exist out in the ether, they exist on devices. I
presumed you would understand the general thrust of the paragraph.
Of course, I meant that it still points back to /boot, but /boot is
/dev/hda1... Sometimes being algorithmically specific clutters up
the meaning.
cp may break the link, but tar does not.
--
+-------------------------------------------------------------+
| Ron Johnson, Jr. Home: ron.l.johnson@cox.net |
| Jefferson, LA USA http://ronandheather.dhs.org:81 |
| |
| "Object-oriented programming is an exceptionally bad idea |
| which could only have originated in California." |
| --Edsger Dijkstra |
+-------------------------------------------------------------+
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: