Page 12 of 13
Re: Post #1 Fd64-600a2 request quick how-to frugal & grub menu
Posted: Thu 07 Jun 2012, 08:56
by jamesbond
openwell3 wrote:Hi,
I have failed trying to do frugal install.
New boot options, new homogenus frugal, new grub stuff difficult.
My request may help many users-
Can you edit post#1 to add-
1. Frugal install of "600" steps
2. Then, grub menu.lst example(s)
Seems everything is different, and I know others are having trouble too.
Thread seems to refer to FAQ, but cluttered with too many specific problems. No offense to Jim1911 or others.
I want to keep frugal install "521" on sda3 and do frugal install of "600a2" on sda6
Many thanks,
Openwell
I don't think anyone has answered this before. Assuming you already have grub installed somewhere and comfortable to edit menu.lst yourself, the easiest way to do it is to copy vmlinuz and initrd from Fatdog iso to the root directory of sda6, and add this to your menu.lst:
Code: Select all
title Fatdog 600
root (hd0,5)
kernel /vmlinuz
initrd /initrd
Good luck.
PS: The FAQ link is already on the first post.
Posted: Sat 09 Jun 2012, 06:21
by mavrothal
Tried alpha2 briefly on a manual frugal install and found no way to get sfs loader to load the devx.
I guess this is answered somewhere in the pervious 14 pages. Would someone point me to it please (and maybe add it to the top or Q&A post).
Another strange thing is that although vmlinuz/initrd were in the /FatDog folder of the boot device, the savefile went to the root of the device with no option to change that.
That makes it a bit messy when FatDog is installed along few other puppies in a partition.
Posted: Sat 09 Jun 2012, 08:50
by jamesbond
Hi,
mavrothal wrote:Tried alpha2 briefly on a manual frugal install and found no way to get sfs loader to load the devx.
I guess this is answered somewhere in the pervious 14 pages. Would someone point me to it please (and maybe add it to the top or Q&A post).
I can't remember whether it is in System or Setup menu, but there is a "System SFS Loader" that enables you to any sfs that you need. The SFS loader can load SFS from anywhere (by default from /mnt/home) - just choose the folder that contains the SFS, then click "refresh". If you want to load the SFS at every boot, click "load permanently" before loading it.
Another strange thing is that although vmlinuz/initrd were in the /FatDog folder of the boot device, the savefile went to the root of the device with no option to change that.
That makes it a bit messy when FatDog is installed along few other puppies in a partition.
You can put the savefile anywhere. By default Fatdog only tries to look at the root of the partition to make it faster. But if you know exactly where is the savefile, you can put the "savefile" boot parameter as follows:
savefile=direct:device:sda6:/path/to/savefile.
- direct means directly use savefile (not using RAM layer) - just like standard puppy PUPMODE=12
- device means you want to specify the device name
- sda6 is - well - that's your partition
- /path/to/savefile
For for possibilities on the savefile, you can read the boot-options FAQ specified in the 1st (or 2nd) post.
When running without any savefile (savefile=none), during shutdown you will be asked to create a savefile. This savefile doesn't have to be in the root partition, it can be elsewhere too. Just type the full path as needed (don't worry if the subdirectory doesn't exist yet; the savefile creation tool will create it for you).
cheers!
Posted: Sat 09 Jun 2012, 11:04
by mavrothal
jamesbond wrote:Hi,
mavrothal wrote:Tried alpha2 briefly on a manual frugal install and found no way to get sfs loader to load the devx.
I guess this is answered somewhere in the pervious 14 pages. Would someone point me to it please (and maybe add it to the top or Q&A post).
I can't remember whether it is in System or Setup menu, but there is a "System SFS Loader" that enables you to any sfs that you need. The SFS loader can load SFS from anywhere (by default from /mnt/home) - just choose the folder that contains the SFS, then click "refresh". If you want to load the SFS at every boot, click "load permanently" before loading it.
That's exactly what I was trying to no avail. From terminal, it spits no errors but no SFS loaded ever and PUPSTATE/BOOTCONFIG agrees with that.
BTW I did not see any load button. Just select, click load permanently and "done" is enough?
I do not know if it is relevant but I'm booting with grub4dos and its standard configuration (just editing the menu list as needed).
Also this is running on a VM (Paralles) with all the other puppies. The VM runs 64bit distros (Fedora, Ubuntu) just fine.
Posted: Sat 09 Jun 2012, 11:36
by rcrsn51
mavrothal wrote:Tried alpha2 briefly on a manual frugal install and found no way to get sfs loader to load the devx.
1. Setup > System SFS Loader
2. Click the Folder icon.
3. Browse to the folder containing your SFS. Note that you are selecting the folder, not the actual SFS file.
4. Click the Refresh button.
5. Select your SFS from the list.
6. Click Load.
7. Click Done.
Posted: Sat 09 Jun 2012, 11:52
by mavrothal
rcrsn51 wrote:
6. Click Load.
(is hard to defend this, but let's "blame" the UI that is not very helpful after an 18h day
)
Posted: Sat 09 Jun 2012, 16:43
by mavrothal
I was cross compiling an ARMv7 kernel in FatDog 600a2 and my cross compiler needed mpc, a small math library.
So here is the pet compiled in FD from the T2 source, for your devx
Latter Hmm, the original pet (~33kb) was generated by "new2dir make install > dir2pet" and from what I see had no so libs only the dev lib.
The so libs where installed in FatDog directly!
When I realized it, I untared the original pet included the so libs and run dir2pet but dir2pet failed with
Code: Select all
** ERROR **: gtkdialog: Error in line 16, near token '</default>': syntax error
aborting...
Aborted creation of PET package
It would appear that it does not like the DEF_version variable (ie pet version) and quits
I'll see about that but till then here is the correct pet that includes both libpmc.so and .a using the slacko dir2pet
Posted: Sun 10 Jun 2012, 16:46
by WillM
This is lxpanel-0.5.9, and its dependencies, menu-data and menu-cache.
These pets do overwrite some system files.
add'l pets for FD600a2
Posted: Sun 10 Jun 2012, 18:55
by openwell3
Pet for Transmission:
Transmission is very old version, no longer supports blocklists.
Pet for Frisbee.
Had to use network wizard, instead of wpa.
Lost my tray icon for wifi, but can connect OK.
Like frisbee very well.
Pets for them would be appreciated, may need instructions to disable other stuff to use them.
Many thanks to anybody who can help.
Posted: Mon 11 Jun 2012, 03:12
by jamesbond
mavrothal wrote:rcrsn51 wrote:
6. Click Load.
(is hard to defend this, but let's "blame" the UI that is not very helpful after an 18h day
)
I'm open to suggestion to improve the GUI.
The System SFS Loader is a "legacy" application and was coded in gtkdialog; I now do most of the GUI in gtk-server which is leap-and-bounds more flexible.
Btw - thanks for hosting a mirror for Fatdog
Posted: Mon 11 Jun 2012, 03:23
by jamesbond
mavrothal wrote:I was cross compiling an ARMv7 kernel in FatDog 600a2 and my cross compiler needed mpc, a small math library.
So here is the pet compiled in FD from the T2 source, for your devx
Latter Hmm, the original pet (~33kb) was generated by "new2dir make install > dir2pet" and from what I see had no so libs only the dev lib.
The so libs where installed in FatDog directly!
If you get the mpc libs from T2 compile (t2-packs), it only has the static library (libmpc.a). It does not come with the dynamic library (libmpc.so) - the idea being, the file is so small so that it is expected to be included in the executables that use it; when those executables are built. That is how T2 built the mpc.
Personally, I used to have tons of these small .so libs everywhere but following technosaurus suggestions; I'm trying to use the static libraries when those libraries are only used by one or two apps.
When I realized it, I untared the original pet included the so libs and run dir2pet but dir2pet failed with
Code: Select all
** ERROR **: gtkdialog: Error in line 16, near token '</default>': syntax error
aborting...
Aborted creation of PET package
It would appear that it does not like the DEF_version variable (ie pet version) and quits
The dir2pet in Fatdog is of "heritage" quality - with all bugs etc
I have been biten more than once. Whenever it get screwed, however, deleting the pet.specs always automagically cure the disease
I'm a bit wary of including newer version of the tools because I someome reckon that the package-database format (the field descriptions inside pet.specs) have changed a couple of times, since puppy4? Hmmm
Plus, kirk has hacked dir2pet to produce xz-compressed files by default.
Re: add'l pets for FD600a2
Posted: Mon 11 Jun 2012, 03:29
by jamesbond
openwell3 wrote:Pet for Transmission:
Transmission is very old version, no longer supports blocklists.
It is old, true, but it does support blocklist. You just have to install the blocklist it manually.
Pet for Frisbee.
Had to use network wizard, instead of wpa.
Lost my tray icon for wifi, but can connect OK.
Like frisbee very well.
Anyone interested in Frisbee can lift it up from 521; but please note that Frisbee requires a special patched version of dhcpcd which isn't in 600.
Posted: Tue 12 Jun 2012, 09:45
by 01micko
Posted: Tue 12 Jun 2012, 11:47
by jamesbond
WillM wrote:This is lxpanel-0.5.9, and its dependencies, menu-data and menu-cache.
These pets do overwrite some system files.
Thanks Will.
Three questions:
1. Is this patched or unpatched lxpanel? The one in 600 is patched for puppy's menu hierarchy (among other things).
2. Is it stable? The last time I tried to compile newer lxpanel (a couple of years ago) was when it reached 0.5 and it crashed immediately at start-up.
3. How does the menu system work? Does it auto-refresh its menus based on the desktop files in /usr/share/applications, or do we need to run something equivalent to fixmenus?
cheers!
Posted: Tue 12 Jun 2012, 11:56
by jamesbond
01micko wrote:Since we have imlib2 available, I thought I'd compile
feh console image viewer. It's a very cool tool!
I was thinking to do the same, but you beat me to it
Would be a fine addition to the pet repo. Thank you.
...it requires "giblib" (I added lib prefix so it's called "libgiblib" [say that 3 times fast!])
Arrgh, I twisted my tongue
cheers!
Posted: Tue 12 Jun 2012, 12:42
by 01micko
I made an sfs of SRWare..
Iron
http://www.smokey01.com/01micko/fatdog6 ... x86_64.sfs 35MB (includes gconf and dbus_glib, so that's why it's an sfs
plus it's pretty big, even with xz comp)
Checksum: e1eae2da9f98dbbed67828fb4faf52b3 iron-19.1100.0-x86_64.sfs
It's not compiled by me, it's the generic version from their site. Also, I had problems compiling gconf from t2 source so I used slackware's 64 bit version. Dbus_glib is from FDPM. It should run as user "spot" if you are user root, but I have an alternate starter script in there allowing running as root.. we all know iron/chrome/chromium hate that! It uses
iguleder's library compiled on FD. So, if you need to run it as root all the time you can edit the iron.desktop file and set the exec as
iron-root.
Have fun! (let me know if it works for you)
FOOTNOTE: newcomers to chrome based browsers.. careful.. the cache fills up quick so watch your save file!
new pets for fd64-a2
Posted: Tue 12 Jun 2012, 16:05
by openwell3
Anyone with skills, compile and make avail these:
Can you make Transmission pet, newer ver.
& Frisbee pet ?
Developers are happy with status quo on these 2 programs.
wish no more, enough said, they make a very good base program.
suggested manual iblock install and copy frisbee fd64-521, except still needs a patch for dhcp???
I am sure others would benefit too.
I can not be the only one using transmission and enjoys frisbee.
Many thanks,
Openwell
Posted: Tue 12 Jun 2012, 22:44
by WillM
jamesbond wrote
Three questions:
1. Is this patched or unpatched lxpanel? The one in 600 is patched for puppy's menu hierarchy (among other things).
2. Is it stable? The last time I tried to compile newer lxpanel (a couple of years ago) was when it reached 0.5 and it crashed immediately at start-up.
3. How does the menu system work? Does it auto-refresh its menus based on the desktop files in /usr/share/applications, or do we need to run something equivalent to fixmenus?
1. This does use the Puppy Linux hierarchy. That is the job of menu-data, which places an application menu in /etc/xdg/menus.
The application menu came from Lighthouse Pup 64, with a few changes to add Faenza icons to the main menu.
2. lxpanel-0.5.9 was recently released with a lot of bug fixes.This pet has been very stable for me, although I don't have a laptop to check the battery plugin. The pager has never hang up on one desktop, like it did in version 0.5.8. I left out one plugin,wnckpager, because it was not stable.
3. menu-cache reads /usr/share/applications and /usr/share/desktop-directories, so it does update, and maintains a cache file in ~/.cache/menus. I don't think the fixmenus script is needed.
These probably should have been wrapped up into one .pet
Last and most important, thank you and kirk for Fatdog64-600. I really enjoy using.
Posted: Wed 13 Jun 2012, 07:39
by jamesbond
Thank you Will.
I have merged your three pets into one (lxpanel-0.5.9-all.pet) and upload it to the pet repo. It looks cool
. I also moved the /root/.config/lxpanel to /usr/share/lxpanel so that it is applicable to all users.
cheers!
Posted: Wed 13 Jun 2012, 08:08
by jamesbond
01micko wrote:I made an sfs of SRWare..
Iron
http://www.smokey01.com/01micko/fatdog6 ... x86_64.sfs 35MB (includes gconf and dbus_glib, so that's why it's an sfs
plus it's pretty big, even with xz comp)
Checksum: e1eae2da9f98dbbed67828fb4faf52b3 iron-19.1100.0-x86_64.sfs
It's not compiled by me, it's the generic version from their site. Also, I had problems compiling gconf from t2 source so I used slackware's 64 bit version. Dbus_glib is from FDPM. It should run as user "spot" if you are user root, but I have an alternate starter script in there allowing running as root.. we all know iron/chrome/chromium hate that! It uses
iguleder's library compiled on FD. So, if you need to run it as root all the time you can edit the iron.desktop file and set the exec as
iron-root.
Have fun! (let me know if it works for you)
FOOTNOTE: newcomers to chrome based browsers.. careful.. the cache fills up quick so watch your save file!
Thank you Mick.
I uploaded this to the SFS section in Fatdog's repository here:
http://distro.ibiblio.org/pub/linux/dis ... atdog/sfs/.
Unfortunately Fatdog is still a bit lacking in its SFS management, so it won't be visible from anywhere unless one knows where to find it.