Hello!
I remastered puppy 2.14 to cd as backup with all of my specific computer's configurations (simple copy option). Unfortunately I had to use this backup to reinstall to usb drive and then switch computers.
The original computer has eth0, while the new only has eth1 (wireless). Now every time I reboot, puppy looks for a non-existant eth0 even though I run the ethernet/network wizard and succesfully configure/save wireless before shutdown.
Possibly this is because the original settings are on pup_214.sfs and the new ones on pup_save.2fs. I am afraid that even if i deleted eth0 (but I dont know how to) eth1 would not start up at boot.
Any Ideas?
thanks,
orbisvicis
what remastering does to your ethernet configuration
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
Re: what remastering does to your ethernet configuration
You got it right, you remastered with your settings, now your settings are on the sfs file. When remastering you have the option to delete Hardware specific files so those files are not included in the remastered sfs file. The thing is that with the unionfs, if you delete a file that is in the sfs file, it should mask it on the 2fs file system. If you are using a pup_save.2fs, try deleting the file /etc/eth0mode and when you reboot, that device should not be tested. If you save your wireless configuration, there must be a /etc/eth1mode and a /etc/eth1wireless.
Deleting the /etc/eth0mode will not affect in any way the eth1 connection.
So you will end up with the following
- /etc/eth0mode in the sfs file
- a masking file in the 2fs file system that indicates that /etc/eth0mode has been deleted
- /etc/eth1mode and /etc/eth1wireless in the 2fs
Deleting the /etc/eth0mode will not affect in any way the eth1 connection.
So you will end up with the following
- /etc/eth0mode in the sfs file
- a masking file in the 2fs file system that indicates that /etc/eth0mode has been deleted
- /etc/eth1mode and /etc/eth1wireless in the 2fs
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
- bostonvaulter
- Posts: 269
- Joined: Wed 27 Sep 2006, 03:41
Sorry, I didn't understand the question: What capability?bostonvaulter wrote:do you think it would be possible to add that capability to the network wizard if it works?
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
- bostonvaulter
- Posts: 269
- Joined: Wed 27 Sep 2006, 03:41
The capability to delete the old way of connecting, in this case eth0. So that the next time they boot up it connects to their wireless instead of looking for eth0 again.rarsa wrote:Sorry, I didn't understand the question: What capability?
Jason
[img]http://img.photobucket.com/albums/v212/BostonVaulter/avatar/puppybar.png[/img]
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
Unfortunately, this does not work
eth0mode in /etc re-appears after boot. So do dhcpcd-eth0.chache, dhcpcd-eth0.info and dhcpcd-eth0.pid in /etc/dhcpc
However, files in /root were successfully deleted.
strange
I am using puppy 2.14, I think that version got rid of .wh files: is there then a text file located in the drive that lists all deleted files; that I can manually edit?
thanks,
orbisvicis
eth0mode in /etc re-appears after boot. So do dhcpcd-eth0.chache, dhcpcd-eth0.info and dhcpcd-eth0.pid in /etc/dhcpc
However, files in /root were successfully deleted.
strange
I am using puppy 2.14, I think that version got rid of .wh files: is there then a text file located in the drive that lists all deleted files; that I can manually edit?
thanks,
orbisvicis