Puppy Linux Discussion Forum

[01micko]

here's mine..

[8-bit]

When I start Lucid 5.1, right after loading drivers to access drives is displayed, I see a file system check of the partition I am booting from as well as a file system check of the pupsave file.
I do not have e2fsck as an option on my kernel line in menu.lst and it seems that Lucid 510 is the only version I have installed frugally that does this check on starting.
So is it built in or can it be disabled?

Also, am I the only one seeing this file system check on booting to Lucid 510?

[norman]

[inoxidabile]

Dear All,
I'm a not skilled Puppy user … I apologize for the question, maybe due to my low know-how and please pardon if this is not the right place for the following topic.

I use Puppy since its 3.01 version and thanks to it, I'm still able to work on an old pc (notebook Dell Latitude - 650MHz - 512M RAM).

After some test with the Lucid 5.1 / Live CD , I decided to install it on HD as fresh install (delete all the previous things) as frugal type.

The problem is this: in a simple Live mode I had (of course) a lot of available RAM, but after the install it becomes about 430M.
Moreover, with just few more packet added (Firefox, Dia, AisleRiot game) and no other activities, it dropped down to 343M.

The version I used before was ChoicePup, with a lot of sfs loaded (Koffice, Opera, FoxitReader and so on), but the amout of available RAM was about 385M.

Could anyone kindly tell me some more info about? Maybe there are some tricks to do or some particular actions.

Oh, an other thing: the chrome browser doesn't run at all, it's not a problem for me because I use Firefox and surely it's yet known, but...

Thanks in advance to everyone for any suggestion (and patience!)

Best Regards,

Inoxidabile

[Tasgarth]

hi,
startmount and 'free space on drives' :
It's strange, they show non-identical numbers (luci 217)

Cheers,

[01micko]

Tasgarth,

Run Startmount and while the GUI is open hover over the drive icons on the desktop.. you will find they are identical and correct. There is a small bug in Partview with the calculations I believe.

_____________

8bit

I reckon your machine is not shutting down cleanly with lupu for some reason. Try exiting from X first then at the prompt run poweroff. That way we will know if it is an X problem or hardware.

Cheers

[8-bit]

01micko,
The file system check in both 500 and 510 appear to be an unclean shutdown with my extended 2 partition.
I booted from a CD of Lucid 510 with pfix=ram and did a file system check of the ext2 partition with a -y parameter and then rebooted to Lucid 510 on the hard drive.
That boot booted without the file system check coming up.
But....
Upon rebooting to Lucid 510 again, the file system check came up.
So I assume that the partition is not being unmounted cleanly even though the pupsave is.

The message I got twice in a row on doing the file system check while booting from the CD was that the partition was shown to have been mounted in the future.
That was the only error message that was displayed.
And as far as I know, I had the time and date set to my area and time zone as local time.
Also, even though that was the only error showing up, a forced file system check of the 40 gig partition takes a little while and really slows up the boot process.

Any suggestions?

[01micko]

[8-bit]

When one has created an ext2 partition, the pupsave file creation defaults to ext2.
I still think it has something to do with the locale, timezone, time and date setup messing up.
So should I try "The complete Experience" option and try setting it again with it?
Anyway I am going to try and let you know.
Both LightHouse and Puppy 431 SCSI do not do a file system check when I boot to them so it must be specific to Lucid.

[8-bit]

01micko,

I am back after booting from CD, making sure I set the locale, timezone, local using hardware clock and rebooting Lucid 510 twice.
Both times, it proceded to do a file system check.
Also, I ran a file system check while I was at the desktop on the CD boot and the only error I got was that the file system (partition) was not unmounted cleanly.
So again I am at a loss.
As to making it an ext3 partition, I have so many puppy versions and data on that partition, I am not ready to do a deletion and reformat of it.
So I guess I will have live with a bootup file system check until I can figure this out.

[paulhomebus]

8-bit... sounds serious... backup all important stuff on that drive.
I knocked over my computer one day and sure enough I had lost the biggest drive I had.... a 250Gb.

Your system checking the disk could be a symptom of that drive starting to fail.

Just a heads up
Paul

[weffy]

01micko,

You're right, there is a gtk dialog error.

# /usr/local/Startmount/Startmount
/usr/local/Startmount/Startmount: line 110: kill: (1516) - No such process


ok

** ERROR **: gtkdialog: Error in line 62, near token '</default>': syntax error

aborting...
/usr/local/Startmount/Startmount: line 430: 1683 Aborted gtkdialog3 -p STARTMOUNT -c
#


Jeff

Edit: BTW the tiny partition is an extended partition.

[weffy]

01micko,

/usr/local/Startmount/Startmount

line 62: do
line 110: kill `ps | grep PROGRESS | awk '{print $1}'`
line 430: gtkdialog3 -p STARTMOUNT -c

[tasmod]

weffy,
those do not 'ring' right.

Try loading the attached pet and try again.

[tasmod]

Had me for a minute, line 62 doesn't refer to the 'normal' line number but gtkdialog and I suspect it's refering to the startfunc script tag </default>