Im not cloning the system yet (not entirely). I only cloned them to get the basic setup across 3 sbcs in my lab environment rather then install each one individually (was faster at the time and I was able to resolve the issue by removing the rules files and letting the system regen them).
I just need to make sure that this incremental nameing issue is resolved before I get too much deeper in the development. But thanks for the comments anyway. On Tue, Aug 30, 2011 at 07:46, <[email protected]> wrote: > John, > > First rule of embedded systems design: DO NOT switch O/S or runtime levels > until you're sure the new one works. > > As for your specific problem, you shouldn't be cloning images from a > working system since it is going to have all of the configuration > information for that system. Build an image on disk, then clone that. > Tweak that image to have the changes you need to deploy. It's much cleaner > and less prone to errors that way. > -- > Julie Haugh > Senior Design Engineer > greenHouse Computers, LLC // jfh at greenhousepc.com // greenHousePC on > Skype > > > -------- Original Message -------- > Subject: [Voyage-linux] Re: UDEV Rules, hardware Mac addresses > From: John Schultz <[email protected]> > Date: Tue, August 30, 2011 1:50 am > To: "Kim-man 'Punky' TSE" <[email protected]> > Cc: voyage linux Mailing List <[email protected]>, Tim Thayne > <[email protected]> > > > My system only contains a link to pcmcia.rules titles 85-pcmcia.rules and > mount-usb.rules. > > The thing I do not understand is that 0.6.5 dated March 2011 contained > about 5 different files (unfortunately I have deleted these images because > 0.7.5 has been released and I try to keep all my systems at the same > version). > > The biggest issue with this is that we are following > http://www.pcengines.info/forums/?page=post&id=799918CD-66C8-40F6-A60B-26A05A078D08&fid=DC038CE7-688B-4FD7-A449-014010E444D1because > we were or still are (need to resolve this udev issue first) having > issues where the ath9k driver would un-associate after an indeterminate > amount of time. > > > The above example is just one of several plaiging this project that has to > be resolved in order for us to use Voyage. > > On Tue, Aug 30, 2011 at 00:41, Kim-man 'Punky' TSE > <[email protected]>wrote: > >> Hi John, >> >> >> On 8/30/2011 2:33 PM, John Schultz wrote: >> >>> The problem is that when I take this cf card or image it to another SBC, >>> the names of the interfaces shift. This needs NOT to happen and the only way >>> I know around it, is to delete the rules files and have the system recreate >>> them. >>> >> >From what I understand, removal of >> >/lib/udev/rules.d/75-**persistent-net-generator.rules >> is supposed to allow you to migrate the CF to other board without shifting >> the interface naming. >> >> But does your system still contain /lib/udev/rules.d/75-** >> persistent-net-generator.**rules? >> >> >> -- >> Regards, >> Kim-man "Punky" Tse >> >> * Open Source Embedded Solutions and Systems >> - Voyage Linux (http://linux.voyage.hk) >> - Voyage ONE >> (http://linux.voyage.hk/**voyage-one<http://linux.voyage.hk/voyage-one> >> ) >> - Voyage MPD >> (http://linux.voyage.hk/**voyage-mpd<http://linux.voyage.hk/voyage-mpd> >> ) >> * Voyage Store (http://store.voyage.hk) >> >> >> > ------------------------------ > _______________________________________________ > Voyage-linux mailing list > [email protected] > http://list.voyage.hk/mailman/listinfo/voyage-linux > >
_______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
