Re: [Voyage-linux] Voyage 0.10: Ethernet bug when moving CF-disks to other boards discovered

I don't think that this is a bug. Those rules keep your Ethernet port names consistent over time. In my cloning notes I have a step to delete the appropriate lines before moving the disk / CF card to a new system. I would have expected a new line for eth1 to be added to the file, which is not

Re: [Voyage-linux] Voyage 0.10.0 on ALIX wants to fsck :-) - does that make sense?

do this: remountro e2fsck /dev/sda1 2016-11-26 14:04 GMT+01:00 Andreas Delleske : > Hi all, > > after having successfully installed Voage Linux 0.10.0 on a Compact > Flash disk for an ALIX board, the startup messages are reminding me to > use fsck as the data structure

[Voyage-linux] Voyage 0.10.0 on ALIX wants to fsck :-) - does that make sense?

Hi all, after having successfully installed Voage Linux 0.10.0 on a Compact Flash disk for an ALIX board, the startup messages are reminding me to use fsck as the data structure would be OK yet they recommend using fsck: Nov 24 15:10:58 xxx vmunix: [ 12.260186] EXT2-fs (sda1): warning:

[Voyage-linux] Voyage 0.10: Ethernet bug when moving CF-disks to other boards discovered

Hi list, I guess I have discovered a bug: With an Alix board and Voyage Linux 0.10.0, I prepared a Compact Flash with the usual script. It started fine, I got ssh access etc., DHCP was working, Ethernet.. Then when I stopped the machine (orderly shutdown) and plugged the CF-card into another

Re: [Voyage-linux] Voyage 0.10: Ethernet bug when moving CF-disks to other boards discovered

Hi Andreas - I have checked my notes and this has been "an issue" going back to at least SuSE Linux (a fine German product) in 2006. So, it is not Voyage-linux specific, but maybe Debian related. Here is at least one good reason for this: suppose you have a server running in a data center and you

Re: [Voyage-linux] Voyage 0.10: Ethernet bug when moving CF-disks to other boards discovered

Hi Jon, > I don't think that this is a bug. Those rules keep your Ethernet port names > consistent over time. In my cloning notes I have a step to delete the > appropriate lines before moving the disk / CF card to a new system. Objection, your honour :) At least when we chose DHCP I guess