I'm really new to Linux (and Puppy of course) so I'm struggling a little . .

I have Puppy loaded to HD, in a new partition formated ext2.

Install went well, and Grub is working fine with Puppy and XP.

I have 2 problems:
1) When Puppy loads I get a msge stating that the filesystem is being checked. Seems to scroll very slowly . . . . . When completed everything seems fine.
2) Having saved a pup_save... file the first time I set this up, I followed the instructions in GRUB to save another pup_save.. file in /puppy400. So now I get asked which one to use at boot up! As I don't seem to be able to find /root to delete the first file, I'm a little stumped.

Any help for an ageing ex-windows user most welcome!

Thanks guys

Andy

I have not run puppy. But I can tell you that the ext2 filesystem should be checked from to time. (The need/desirability of checking journaling filesystems like ext3 can and has been debated.) And checking filesystems (from the MS world, think scandisk) can take a while (depending on size, disk speed, etc.). Hopefully this is not done on every boot. (Something like every 20 to 40 boots or 6 months -- whichever comes first -- is common.) It is also normal to check the filesystem if the computer was not shut down properly; i.e. if the partition was not unmounted (or remounted read only) first.

I am not sure about your mention of "/root." I would expect the command you need to delete the first file to be (run as root):

(or whatever the filename actually was ... I just made up "200" )

You should be able to see everything in your root directory (except "hidden" files, which start with a dot) using:

Thanks for your reply - the Filesystem Check seems to happen everytime I load Puppy - which is a bit of a pain!

Think I need to look at what commands are available to me to sort out the other file problem . . . Still a lot to learn!

Andy

Assuming you are using the latest Puppy, your pup_save file (or one of them!) should be in /home/Dingo (could be /mnt/home/Dingo, I can't remember if I've put mine somewhere strange). You can also search for files by using Menu -> Filesystem -> Pfind file finder.

This post makes it sound like that used to be the default action, but that it has been changed. But that post is quite recent (July 15) so maybe the change hasn't made it down to the released version yet. Or perhaps you don't have the latest.

I would quess that it is controlled in a script somewhere, so it might not be difficult to change the behavior yourself. But that might be a bit much to tackle if you are still new to Linux.

Change the ext2 filesystem to ext3 and you won't get a tedious file check each time you boot. I don't remember how to do this, but it worked for me. You might check the Puppy forums for the method, or someone here could tell you. It takes only a single command-line command.

Replace /dev/sda1 with the name of the actual partition.

You can be more specific by also using the -J option. See the tune2fs man page for more info.

When Puppy loads I get a msge stating that the filesystem is being checked. Seems to scroll very slowly . . . . . When completed everything seems fine.

when windows bootup you only see a screen ,hence what ever is happenning is hidden by that screen..but in linux (puppy) what you see is the booting up of linux ,,,showing what is happening during booting ...
this is not a problem

It is not a problem per se. But if the filesystem check (fsck) takes very long, occurs on every boot, and if you boot frequently, it can be annoying. This is what I understood to be the OP's complaint. Except after improper shutdowns, it used to be common for Linux distros to only do a filesystem check every 20 something or every 30 something boots (or every 6 months, whichever came first). Now, with journaling file systems, I think some distros, by default, don't check at all at boot time. (It can and has been debated whether that is a good thing).

It also seems to be becoming fashionable with certain Linux distros to hide the boot messages by default, just like MS Windows does. Personally, I like to see the messages scroll by. But then, I also like the command line.




Now that I am revisiting the issue of file system checks, it occurs to me that Puppy might be announcing that it is going to do a filesystem check and then very quickly announce that the filesystem is "clean." If this happens, then it is actually skipping the filesystem check because the filesystem was properly "unmounted" at the previous shutdown and it is not yet time to check it. The fsck program itself determines whether it is time to check.