pup_save.3fs on NTFS?

[John Doe]

http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm will read an ext3 partion really well from windows. I've haven't had a single problem yet.

I'm actually going to wipe out my fat32 and ext3 partion (on the shrunken NTFS drive I created) and make them one ext3 partion so I can have more space to run Unleashed.

[gpk]

Given that FAT32 works fine with Win and Linux, why bother with ext (or NTFS for that matter)?

[raffy]

Ext2/3 - It is the filesystem needed to do a full HD install (option2) to hard disk. (Am not sure if Ext2 is still used in HD install for Puppy2, perhaps not anymore.)

Although, if the PC/laptop has a CD drive that works, it is better to use the live CD and retain the (potentially virus-prone) FAT32.

In both cases (FAT32 or Ext2), the live CD will save its pupsave.3fs file to the partition, so maybe leave the decision to the user.

The use of live CD eases upgrading to new Puppy versions.

[edoc]

Ext2/3 - It is the filesystem needed to do a full HD install (option2) to hard disk. (Am not sure if Ext2 is still used in HD install for Puppy2, perhaps not anymore.)

Although, if the PC/laptop has a CD drive that works, it is better to use the live CD and retain the (potentially virus-prone) FAT32.

In both cases (FAT32 or Ext2), the live CD will save its pupsave.3fs file to the partition, so maybe leave the decision to the user.

The use of live CD eases upgrading to new Puppy versions.

Here are my reasons for using a HDD install. Perhaps someone can show where I am
wrong?

1. Booting from CD is slower than from HDD.
2. Booting from CD requires an undamaged CD and a properly functioning CD drive.
3. Configuring things to save files and settings across multiple apps can be a pain.
4. CD-RW drives are not always available so saving to the CD is not always practical.
5. As of 2.0x I understand that updates will no longer be as challenging as it has been.

WDYT? doc

[raffy]

Hmm, let me try these reassurances:

2 - functioning CD and drive - a must requirement, so can't be argued

3 & 5 - these go together; configuring and updating the installation are always taken care of by the most recent release. in whatever way Puppy is installed, config can be changed to the user's preferences.

1 - booting via CD can be made faster by copying pupxxx.fs to the hard disk, beside the pupsave.3fs.

And as to the use of CD-RW, it is an entirely different option from the one being discussed - no need for hard disk when using multisession CD. More RAM may be needed, though.

My $0.02

[edoc]

Hmm, let me try these reassurances:
2 - functioning CD and drive - a must requirement, so can't be argued
3 & 5 - these go together; configuring and updating the installation are always taken care of by the most recent release. in whatever way Puppy is installed, config can be changed to the user's preferences.
1 - booting via CD can be made faster by copying pupxxx.fs to the hard disk, beside the pupsave.3fs.
And as to the use of CD-RW, it is an entirely different option from the one being discussed - no need for hard disk when using multisession CD. More RAM may be needed, though.
My $0.02

I appreciate the clarifications.

Apart from my personal preferences I am assisting with the configuration of a 5 laptop
Puppy system. The users will be moving about, the environment not highly controlled,
and the users both adults and children.

My concern with a cd-boot system is that they could easily find themselves in a remote
location with one of the laptops and have misplaced the cd, gotten debris into the CD
drive, damaged the cd, or otherwise suffered the predictable fate of multi-part moving
devices using exposed-surface removable media.

Given that the Puppy 2.0x series reportedly resolves the update complexity (not that once
set up they are likely to fuss with upgrades for a while) it would seem that retaining their
complete Puppy install on their HDD removes one level of complexity for them.

WDYT? doc

[raffy]

You're right, and can extend the HD install to possibly CF (compact flash) drive used as IDE, which is shock-proof

[edoc]

You're right, and can extend the HD install to possibly CF (compact flash) drive used as IDE, which is shock-proof

We did discuss the possibility of using a USB stick or a CF/SD card.

The challenge is that they are headed into full time missions for several years and funds
are limited. The laptops come with a HDD and they will use a single large external HDD
NAS (networked) for their backups because of the less costly CD's vs CF/SD sticks. But
the backup box will stay at their home base and be in a cleaner environment.

Knowing where they will be and what they will be exposed to they need portability, Linux
to resist spam and viruses, and a good backup system.

Thanks! doc

[edoc]

I could still use some very basic guidance re. dual booting WinXP and Puppy 2.xx

Is this an OK procedure?

1. Run gparted and reduce the existing partition by .5 - 1 gig and make that ext2 or ext3?

2. Run the Puppy Universal Installer and load Puppy to the new ext2/3

Yes, no, maybe, wait for 2.02?

If I want to be able to access files between the WinXP and Puppy sides I guess I need to
backup the current WinXP side, wipe the disk and partition with something other than the
default WinXP NTFS?

Do I have to use the security-challenged FAT/32 or will WinXP run under ext2/3?

This is not for my pc as I do not run WinXP on anything.

Thanks! doc

[John Doe]

Given that FAT32 works fine with Win and Linux, why bother with ext (or NTFS for that matter)?

Unleashed will only run under Ext and I want to use Unleashed.

[Locodarwin]

edoc,

You said:

If I want to be able to access files between the WinXP and Puppy sides I guess I need to
backup the current WinXP side, wipe the disk and partition with something other than the
default WinXP NTFS?

If you have access to Partition Magic, you can use it to convert an NTFS volume to FAT32 without reformatting/wiping it. Backing up the partition you want to convert first is a good idea, of course.

-S