remaster ubuntu alternate
Colin Law
clanlaw at googlemail.com
Tue Jul 3 08:53:20 UTC 2012
On 3 July 2012 09:34, Oliver Grawert <ogra at ubuntu.com> wrote:
> hi,
> Am Dienstag, den 03.07.2012, 07:32 +0100 schrieb Colin Law:
>> > and the other thing, when you copy the disk to another machine, you need to
>> > delete the network rules(rm /etc/udev/rules.d/70-persisten.net.rules) and
>> > many others
>>
>> If that is correct then how is it that I can take a disk from one
>> machine and move it to another and it works ok, without having to
>> touch that file?
> depends what kind of disk ;)
> if you move the disk around, the device name assigned in that file
> (usually eth0) is simply blocked, udev just assigns a different device
> name (i.e. eth1) and moves on...
>
> in desktop installs where network-manager cares and does not use any
> device name specific settings for the network, moving the disk wont do
> any harm, NM will just handle everything automatically with the new
> device name ....
>
> but if you have a server install ... with a fixed IP setup
> in /etc/network/interfaces that is assigned to the device name, it will
> break without manual fixing ....
Understood. Is it in fact the fixed IP that causes the issue rather
than whether it is desktop or server? If I have a desktop with fixed
IP and clone that disk to another machine then I would have to change
the IP in the destination machine. In fact I do use fixed IPs on my
machines as I find ssh with keys gets annoyed when it finds the IP for
a_machine.local has changed.
Thanks
Colin
>
> /etc/udev/rules.d/70-persisten.net.rules gives you a hint at the top of
> the file how to re-generate it if you run into probs with the hardcoded
> value though :)
>
> ciao
> oli
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
More information about the ubuntu-users
mailing list