Btw, managed to f**k up everything, by trying to increase the savefile by 1 gb, then doing it again without fixing it during boot. (yeah, read too late about that bug )

The savefile became 3 gb but puppy used it as if it was still 1 gb, and there is no way I could fix it. Tried to fix it from a Lucid puppy I had around, and then from the lighthouse CD, and the only thing I managed to do is screwing up the installation. So I decided to relax and reinstall.

Saved the only thing worth saving (the virtual disk of Virtual Box where I installed Windows XP, which would be a true PITA to reinstall-redownload patches) and I'm ready to begin.

A last question, is there a way to save your stuff without using the savefile? Sounds incredibly dumb to have a ext3 filesystem savefile in a filesystem partition that is already ext3.

A last question, is there a way to save your stuff without using the savefile? Sounds incredibly dumb to have a ext3 filesystem savefile in a filesystem partition that is already ext3.

You can save most of your stuff outside the save file.

Configuration data that automatically stores within the linux filesystem will go in the save file.

You can save external data files outside of the save file as you wish.

If there is a configuration setting you can also save other automatically generated files outside the save file. The first thing most users find is that the browser temporary file cache starts grabbing lots of save file space. The solution is to set the browser conguration so that the temporary file space is on your hd filesystem rather than the linux filesystem.

In order to save stuff outside the save file you need to have an understanding of mounting disk partitions because you cannot save to the partition until it is mounted. Secondly you need to know what your partitions are known as to Puppy Linux when they are mounted.

You should find that the partition with the sfs file on it is already mounted and is known as /mnt/home.

You can mount other partitions by clicking the desktop icon for the partition.

If I remember rightly the first primary partition of the first sata/ide hard disk is known as /mnt/sda1 when mounted.

The second primary partition is /mnt/sda2

The first logical partition in an extended partition is known as /mnt/sda5

The first primary partition on the SECOND sata/ide hard disk is known as /mnt/sdb1

When you click on the disk icon to mount it then the filesystem will open as well and you can see what it is known as.

Hope the pattern is understood now. When saving a file just save to the appropriate directory.
e.g to save to the document directory of the second primary partition of the first sata/ide hard disk then save to:
/mnt/sda2/document

Of course, if you did a full install rather than a frugal install you wouldn't have to worry about save files and all this. One of the advantages of a full install. However, that is not a recommendation for a full install. You do what is best for you. I prefer frugals myself.

These questions are becoming Puppy generic rather than specific to Lighthouse Pup. I would suggest if you have further questions like this you start a thread in the Beginners Forum so that we can leave this thread to discuss Lighthouse specifically.

Saved the only thing worth saving (the virtual disk of Virtual Box where I installed Windows XP, which would be a true PITA to reinstall-redownload patches) and I'm ready to begin.

A last question, is there a way to save your stuff without using the savefile? Sounds incredibly dumb to have a ext3 filesystem savefile in a filesystem partition that is already ext3.

ICPUG's reply is right on the mark. /mnt/home is your friend--with as much space as that partition has, and outside of the save file.

I would add that VirtualBox is especially prone to filling up the save file, (OS installations can be huge) as you've found. What I do is close VirtualBox, move /root/.VirtualBox to, or make a folder, .VirtualBox on another partition or within /mnt/home. Then in ROX-Filer I drag and drop it to /root and choose 'Link (absolute)' when prompted. That way VB will work with /root/.VirtualBox as before, even though it is actually on another partition.

In Lighthouse, you can also do that by pasting this into a terminal:

Code:

frugal-symlink /root/.VirtualBox .VirtualBox

(There is a space before the last .VirtualBox.) That method will put the large .vdi disk images and all VB settings into a folder at /mnt/home/LHP_503_Programs/.VirtualBox

The same method can be used for browsers e.g., Firefox with /root/.mozilla or Wine with /root/.wine

I am having intermittent problems connecting a variety of Dell laptops via wireless.
These have Dell Wireless DW1490 pci cards in them.
I can successfully connect maybe 1 time in 20.

Frisbee tries hard but does not succeed.
The network connection wizard does not work either, can't even see the wlan.
Older puppies like 4.3.1 do work.

Is there some way to use Barry's Simple Network Setup?
Or could it be a kernel upgrade problem?
I was able to connect with an earlier Lighthouse which I have since deleted.
I've searched all over the forum and tried various pieces parts to no avail.
Mind you, I love Lighthouse too much to give up.
I went so far as to drop a CAT5 cable from the attic to direct connect.

I have attached both working and nonworking pnetworkdiag files.
Perhaps someone can point me to the error of my ways.

EDIT
It may be that I have a hardware initialization problem tho the wireless card is known good and works under Windows and Pup Server 4.3.5
Plus I have this problem on at least 4 similar Dell laptops.

This is the boot error message I usually get.
I was finally able to trap it with ctrl-S during boot up:

Looks like the card is not getting initialized.
The advice I found in /var/logs/messages is to flash the firmware on the wireless card from linuxwireless.org
But I've never tried this before.
I'm not sure if I am up to doing this.

EDIT2
For work I got a refurbed Dell D631 with a different Dell Wireless PCI card which is not even seen by the OS, though it works in XP and PupServer.
I ran thru all the Lighthouse AutoProbe drivers but still can't connect wirelessly.
So I think it's a driver and/or firmware problem.
Solution: I added a switch to the CAT5 I dropped from the attic. My wife is less than thrilled at my klugery.

Hi i am in the process of creating a puplet. i am wanting to know how you have added up to 40 sfs to load on startup. i would like to do something similar to this. you seem to be the only puppy based os with this ability.

can you also let me know if you do not want to give this information away.or send me a message via the forums if you prefer. .

...
What I do is close VirtualBox, move /root/.VirtualBox to, or make a folder, .VirtualBox on another partition or within /mnt/home. Then in ROX-Filer I drag and drop it to /root and choose 'Link (absolute)' when prompted. That way VB will work with /root/.VirtualBox as before, even though it is actually on another partition.
...

Hope that helps,
TaZoC

I got lost in your procedure above.

Where do you move /root/.VirtualBox to?

Which folder is being dragged and where precisely
in /root is it being dropped?

Any procedure for redirecting storage area from
within ROX is valuable to me - I'd prefer not to use
the console unless it is absolutely necessary.

Which folder is being dragged and where precisely
in /root is it being dropped?

Any procedure for redirecting storage area from
within ROX is valuable to me - I'd prefer not to use
the console unless it is absolutely necessary.

Can you clarify please? Many thanks in advance!

Assuming you are going to use /mnt/home as your storage area:

1) MOVE the folder /root/.VirtualBox to /mnt/home

When you have done that the folder .VirtualBox should now be in /mnt/home and NOT /root. That is, there exists a folder /mnt/home/.VirtualBox but /root/.VirtualBox no longer exists.

2) Now drag the newly created folder .VirtualBox, which is in /mnt/home, back to /root, (not a subdirectory of root), BUT when prompted choose 'Link (absolute)'

When you have done that the folder .VirtualBox will still be in /mnt/home but .VirtualBox will now be back in /root again as a Link.

Virtual box still saves to /root/.VirtualBox but as this is now a link and not a folder it really stores to the folder that is linked to, /mnt/home/.VirtualBox. This means all storage from VirtualBox is outside the save file and in the /mnt/home partition.

Hi i am in the process of creating a puplet. i am wanting to know how you have added up to 40 sfs to load on startup. i would like to do something similar to this. you seem to be the only puppy based os with this ability.

can you also let me know if you do not want to give this information away.or send me a message via the forums if you prefer. .

The mods are not easy--need to extract the init script from initrd.gz, edit the script as Leon did, add loop device nodes in /dev and directories up to /pup_ro42, then rebuild the new initrd.gz and test. Also, the main file might need similar nodes and directories as well as tweaking of /usr/sbin/bootmanager.

Greetings. I've done a frugal install of Lighthouse 5.0.3g on my 8-yr-old desktop PC and like it very much;almost worked out-of-the-box.
Now I intend to frugal install it on my Acer Travelmate TM630 notebook(since 2002), cpu Pentium 4 1.6Ghz,ALI chipset motherboard, 512MB ram, onboard NVidia Geforce2Go graphics using shared memory 16MB, 80GB harddisk, cardbus wireless adapter model DLink DWL-G630 (based on RT61.sys or RT2500). Based on this specs,I wonder if this version of Lighthouse Puppy will work. Hope someone can advise me as I've tried other puppies,eg Slacko 5.3,Wary 5.2.2,Brunopuppy(based on 431) - each of them seems to give me some problem ,such as touchpad no tapping,mouse hanged for no reason,wireless connection problem,Youtube video crappy(hardware limitation?). Even without these problems, Lighthouse Puppy is still my first choice but am reluctant to go through the hassle if it is sure not to work as I've already spent a lot of time trying to get those other puppies to work without much success,not for want of effort. Pardon me if I've posted the query in the wrong thread.
At last,I made another livecd to test it on the notebk(OS WinXP),only xvesa works and the touchpad no tapping problem. Is there a way to resolve the touchpad problem and tweak xorg for better youtube video performance?

Dave S gave this advice in using Flsynclient which is the
software that controls the touch pad.

Quote:

Go into /root/ in your filemanager. set it to show hidden files. Load the file .flsynclient into a text editor (right click, select 'open as text') Look for the entry 'clickfinger3=' and set the value to '1', so : clickfinger3= 1

I found this advice on this page. It also describes how to turn off
the touch pad.

The problem is Flsynclient doesn't run in xvesa. I'm been hoping to get xorg NVidia driver working for my notebook NV11 Geforce 2 Go graphics chipset using 16MB onboard memory. Xorg probing correctly identifies my graphics as 'nv" but my external LCD monitor screen,in place of my faulty notebook screen, is garbled unless I switch to xvesa. Is there a workaround for me? I've posted for help before and am still waiting for some kind soul to assist me.
So far,Puppy Linux has been a happy and exciting discovery for me, even more than Ubuntu which I've tried without satisfactory results for my older PC hardware. Now,I use Puppy exclusively for my old PCs,in particular Lighthouse which,unfortunately,is too much for this notebook to handle but it works beautifully in one of my older desktop PC with slightly better hardware. Keep up the great work!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum