0.6.2 was the first official release on the 0.6.x branch. There were some issues with an older version of unionfs on pre 0.6.2 builds. Then can be manually fixed, but you will need to do the following steps:
cd /oldroot/mnt/asturw/lib/ rm -rf modules Then reboot. The bug in the older unionfs code copied modules that were loaded to the unionfs partition. The modules are older and as a result will not load with the kernel from 0.6.2. Since the module isn't loading, the device isn't there (which is why ifconfig complains). That has been fixed in 0.6.2 and won't cause a problem on future upgrades. Darrick Tom Chadwin wrote: > I finally got on-site to retrieve the box which I tried to upgrade > remotely from 0.6.1 to 0.6.2. The ethernet ports seem to have been > knocked out. I see this during boot, just after the TDM410P messages: > > ifconfig: SIOCSIFADDR: No such device > route: SIOCADDRT: No such device > ifconfig: SIOCSIFADDR: No such device > route: SIOCADDRT: No such device > > After boot, ifconfig only gives me the loopback interface. > > Can anyone help me fix this? > > Thanks > > Tom > > >> It's more likely that what Tom is seeing is due to a missing filesystem >> label on one of his partitions (either ASTURW or ASTKD). >> Without seeing the console, we can only speculate. If the original >> install on that box was prior to 0.6.1, the filesystem labels may be missing. > >>>> Currently 0.6.1. Is a remote upgrade possible, and if so, what's the >> process? >>> OK, I followed the directions here: >>> >>> http://www.astlinux.org/node/38 >>> >>> Unfortunately, I did this remotely via SSH, and the box has not come >>> back up, as far as I can see. However, two others which I have >>> physically here, I did via the serial port, and they have upgraded >>> flawlessly to 0.6.2. Any ideas what might have caused the problem? Is >>> a remote upgrade not recommended? >>> >>> With the boxes which have upgraded from 0.6.1 to 0.6.2, is copying >>> the new files to /oldroot/cdrom/os really all one must do? Is rc.conf >>> identical in both versions? >>> >>> Thanks >>> >>> Tom >>> >> rc.conf has changed, as has /etc/arno-iptables-firewall/ ... and no >> doubt others. >> >> What I do is this. >> >> I copy up the new image. >> >> The I do: >> >> mkdir /tmp/new >> mount -o loop,ro /oldroot/cdrom/os.new/astlinux-trunk-XXXX.run >> /tmp/new diff -ur /stat /tmp/new/stat >> >> and make note of the changes... Files that I've not modified, I can >> just copy over... files that I have modified, I get diffs of, and try >> to apply a patch... otherwise, the rejected patch hunks I end up >> editing by hand. >> >> -Philip > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.