On Jan 10, 2008, at 3:38 PM, Mark Post wrote:
On Thu, Jan 10, 2008 at 4:23 PM, in message
<OF1A84D61D.03725F25-ON852573CC.0074D311-852573CC.
[EMAIL PROTECTED]>, Alan
Altmark <[EMAIL PROTECTED]> wrote:
-snip-
But that doesn't mean you can't fix a Linux configuration. Just use
another guest that DOES have its network connections up. Take the
problem
Linux offline (FORCE, shutdown). Then have the Good Linux LINK to
the
target Linux's disk and mount it. Then you can edit (with all needed
tools) the Linux configuration. When done, unmount, DETACH the
disk, and
start up the Problem Linux again.
Definitely not something you want to do before other avenues have
failed. Ouch.
Also: if the problem volume is actually an LVM, and the vgname/lvnames
are the SAME as on your rescue system, you will be really sorry.
Which is why your rescue system OUGHT to be a one-volume, no live LVM,
sort of system.
Adam
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
