Booting 2.10 and pup_save on NTFS: what happened?

[Béèm]

Having seen 2.10 gold was out a couple of days ago, I felt (over?) enthousiastic to use it.
So I booted from the 2.10 iso.

First surprise, it loaded a pup_save from hda5 (ntfs), as I forgot I moved it to there to save room on hda6 (vfat)
So I cut the power to prevent from writing to hda 5 (ntfs), booted from XP and renamed the pup_save.

Booted again from the 2.10.
My regular pup_save (from 2.02) on hda6 was found and used.
I got all kind of messages and also the warning that files were written to /tmp/versioncleanup.
To my surprise, I was in jwm and not KDE but then I remembered it was still xxx_202.sfs. So kind of normal.

I saved the /tmp/versioncleanup to a save place, but had errors specialy when copying bin.

I tried to start the internet connection, but had errors saying usr couldn't be accessed due to permission problems. I thought usr was in root, but appears to be in users now.

Fearing more problems and corruption of my good 1.3GB pup_save file I cut power again, hoping nothig was written to the pup_save file yet.

I then booted from the 2.02 and tried to connect to the internet.
(In the meantime I renamed the kdexxx_202.sfs) and but xwm didn't start.

I then stated 2.02 again but with pfix=ram in order to report the problems.
The connection to internet seemed to be ok, the previous configuration seemed to be found, but I couldn't load any page.
I added the IP of one of the ISP nameservers to the RP configuration, but still no luck.

So I am forced to go to XP to report the problem.

Now the big question is?
How can I correct if even booting the 2.02 with pfix=ram doesn't permit to work on internet.
Also how can I get back my pup_save info (being short on room I wasn't able to make a copy of the 1.3 GB pup_save file)

[Béèm]

To be certain, after renaming the 1.3GB pup_safe file (in XP), I rebooted 2.02
So still only in RAM.
Configured Roaring Pinguin and connected to internet.
Same problem, whatever URL I try I get the page not found error.

Another problem is, that I can't display my hda6 (vfat) in ROX.
The window comes briefly and then disappears.
Strange.

[Béèm]

Additional questio.
On the hda 5 (ntfs) I found a file dev_save of 4 bytes.
The creation time is about the time I did my first boot of 2.10

What is the purpose of this file?

[Béèm]

Ok then.
Trying again with the pup_save of 512MB, which had been used once in 2.02
After having the same problem with the page load error, a dns resolving problem, I looked again in the Roaring Pinguin config.
On the last tab I saw the firewall was at masquerade.
Don't know how it was set so.
Changed to firewall none and I can load pages now.

Before doing anymore stupid things, are there precautions to take if I want to use the 1.3GB pup_save file from 2.02?

[GuestToo]

i think RP's standalone firewall will work if the execute permissions for the file are set ... it will work for cable or dialup too

just thought i would mention it

[Béèm]

Where can I check this execute permission?

[GuestToo]

type: chmod +x /etc/ppp/firewall-standalone

then i think you can select Standalone Firewall in the Roaring Penguin options, and it will work.

you can test it at, for example, www.grc.com

or you can put

/etc/ppp/firewall-standalone

in /etc/rc.d/rc.local

it is just a simple firewall ... there is no configuration for opening ports, etc etc

[Béèm]

Thank you GuestToo.
From the moment I did put stand-alone or none in the options tab of RP-PPPoE I could load pages.