Page 30 of 49 [730 Posts]   Goto page: Previous 1, 2, 3, ..., 28, 29, 30, 31, 32, ..., 47, 48, 49 Next
Author Message
RSH
PostPosted: Sat 12 May 2012, 00:05    Post subject:

LazY Puppy Info Center

Sorry for the delay to upload the new LazY Puppy 2.0.1. I am sure LazY Puppy LazY Remaster Suite is worth waiting a little longer.

LazY Puppy LazY Remaster Suite - Part 3

New Options:

- automatically Install of Programs (no database entry)
- installing images to /usr/share/backgrounds
- installing sounds to /usr/share/audio
- installing icons (png) to /usr/share/pixmaps
- installing icons (xpm) to /usr/local/lib/X11/mini-icons

- remove symbolic links (empty the directories)



I am now back to the basic work and will hopefully upload the new LazY Puppy 2.0.1 on Sunday 13. May 2012

RSH
RSH
PostPosted: Thu 10 May 2012, 10:24    Post subject:

LazY Puppy Info Center

Finally introducing:

LazY Puppy 2.0.1 Remaster Suite

Basic options (tab 1):

- specify ISO-Name before remastering starts
- specify des ISO-Label before remastering starts

- Option to remaster without possibility to edit /tmp/root and/or /tmp/etc (remaster likely in one step)
- Option to remaster standard (shows all OK- & Cancel-GUIs)
- Option to remaster standard customize (like customizing automatically /tmp/etc)
- Option to remaster full customize (removes /tmp/root and /tmp/etc and copies /root and /etc completely to /tmp (might work only in this (your used) remaster pc)

- Option to choose creating ISO and/or burn CD/DVD



Extended options (tab 2):

from /etc

- keep file: codepage
- keep file: desktop_icon_theme
- keep file: hostname
- keep file: hosts
- keep file: keymap
- keep file: profile
- keep file: localtime
- keep file: PuppyBackgroundPicture
- keep file: windowmanager
- keep file: .numlock_set_on

from /root and sub dirs

- updating directory: .my-sfs-scripts
- updating directory: .my-sfs-lists
- updating directory: FbPanel
- updating directory: Openbox
- updating directory: IceWM
- updating directory: JWM
- updating directory: my-documents
- updating directory: Startup

- updating several desktop settings

from /etc

- keep changes in DISTRO_SPECS

- plus: button (option) to unload unwanted sfs files before remastering



Currently doing this post from a new remaster used the LazY Puppy 2.0.1 Remaster Suite! Very Happy Cool
RSH
PostPosted: Tue 08 May 2012, 17:17    Post subject:

LazY Puppy Info Center

Hi.

Introducing LazY Puppy 2.0.1 LazY Remaster, no Smart Remaster, no Quick Remaster. Very Happy

Currently i am doing the last programming steps and some localisations (German) on LazY Puppy 2.0.1. My last big work has been a shell to the puppy remaster function, which gives some comfortably options to remaster the LazY Puppy 2.0.1.

Here some options:

- specify ISO-Name before remastering starts
- specify des ISO-Label before remastering starts

- Option to remaster without possibility to edit /tmp/root and/or /tmp/etc (remaster likely in one step)
- Option to remaster standard (shows all OK- & Cancel-GUIs)
- Option to remaster standard customize (like customizing automatically /tmp/etc)
- Option to remaster full customize (removes /tmp/root and /tmp/etc and copies /root and /etc completely to /tmp (might work only in this (your used) remaster pc)

- Option to choose creating ISO and/or burn CD/DVD

All of these options can be set before the remaster starts.

Tomorrow hopefully finished the programming work and then need one more day to create and test the new LazY Puppy 2.0.1 sfs files (some new programs inside the sfs suites and also available as single apps (sfs)).

So, hopefully i can upload all files on Friday, 11th of Mai 2012.

RSH
RSH
PostPosted: Mon 30 Apr 2012, 07:50    Post subject:

LazY Puppy Info Center

Thanks for posting your files, sunburnt.

---

Introducing the LazY Puppy Run-Scripts:

- LazY Puppy 2.0.1 does not need to load any SFS in front of starting any application inside the sfs
- Just click the menu entry or the run-script of the application and if the SFS is not loaded, it will be loaded automatically
- Does the SFS need any other SFS, it loads the dependent SFS automatically (Lazarus loads autom. the devx)
- Is the sfs not available at LazY Puppy install-directory it will be downloaded automatically (no browser needed)
- After all needed SFS files are loaded, the program runs

This is made using run-scripts. These run-scripts can be created by right-click action on any unmounted/unloaded SFS (converted to LazY Puppy Format) - no matter if in /mnt/home or /mnt/sda3 and it is all really quick and easy to handle.

Here is a video: http://www.mediafire.com/?fyr7qmhfl853ccn it shows: the menu (no wine loaded), removing of wine from usb, trying to start foobar using the run-script, trying to load wine, downloading wine and then loading the sfs and running foobar - all after a single left-click on the run-script. LazY Puppy 2.0.1 will have all the menu entries of all LazYY Puppy SFS programs and these entries do call the related run-script (also all built in).

---

Note: do not download the currently available LP2_Wine.sfs at smokey01.com - this is not the original file. It is just for my testings. You must not use this with LazY Puppy 2.0.1.
sunburnt
PostPosted: Sun 29 Apr 2012, 22:27    Post subject:

Okay... My Sunday of effort here.
A GtkDialog auto. menu of Tiny Core`s SCM app. files.

This is a link to my scm_kit post:
http://murga-linux.com/puppy/viewtopic.php?p=624016#624016[/url]
sunburnt
PostPosted: Sun 29 Apr 2012, 14:55    Post subject:

RHS; And everyone. I have looked into Tiny Core Linux`s SCM files.
These are TC`s version of SqApp files, and there are a lot of them.

They seem to work fine in Puppy, I think this has been done already.
I`m not very good at compiling apps, so this is an easy way to go.

SCM files seem to be single app. only, SqApp files can have many apps.
Groups of like apps. go well in one Sq. file, media, server, office, etc.
SCM files can have more than one app., but how to tell what`s in it?
The /bin dir. in some scm files is cluttered with files, making it hard to
find the real run files. So then a sort of manifest file is needed to fix it.

SCM files also seem to have no dynamic "mount/umount" at run time.

I`m going to rewrite my auto. menu to use them, I`ll let you know...
Quote:
Make the dirs. "/apps" and "/mnt/(Partition for Files)/SCM"
Download SCMs and move to "/mnt/(Partition for Files)/SCM"
Make dir. "/apps/(SCM file name, NO extention)
Do: mount -o loop /(Path)/(SCM File) /apps/(SCM mnt. dir.)
Exec. the app`s run script in /bin.

Here`s a link to TC`s repository of SCM files:
http://distro.ibiblio.org/tinycorelinux/4.x/x86/scm/
.
RSH
PostPosted: Sat 28 Apr 2012, 14:29    Post subject:

LazY Puppy Info Center

sunburnt wrote:
I only have built Mahjongg and Dead Meat music player Sq.Apps.

I can post my files for you to examine if you like...

Sorry for late reply - i am just so busy. Yes, please do post your files.

I plan to upload all files of the new LazY Puppy 2.0.1 within the next week.

After release of LazY Puppy 2.0.1 i do plan a break of active develpoment for several weeks (except needed bug fixing).

More Information here


RSH
sunburnt
PostPosted: Mon 23 Apr 2012, 15:53    Post subject:

That`s great! I`ve been wanting a boot setup for Weeners.
I don`t use it myself but many friends and family still do.

I think there`s a simple way to have code setup a Grub4dos menu with found Puppies.
Then as you say, a change to the PC`s hardware wont break the boot setup.
I`ve changed drives as we all have and had the PC be unbootable. USB time...
At least a default search profile at the bottom to find one Puppy would be good.
minesadorada
PostPosted: Mon 23 Apr 2012, 05:20    Post subject:

sunburnt wrote:
minesadorada`s "find" for making boot menus sounds great!
Does it make a menu of all found bootable O.Ss.?


It doesn't make a menu. It just searches all available hard disk partitions for the frugal subdirectory. I have 7 hard disks on my system some with multiple partitions, and it's easy to forget which (hdn,n) each installaton is on. Besides, I don't want menu.lst to break if I change my system disk setup.

This Grub4DOS code can find Windows if it exists on a bootable partition:
Code:

# Windows
# this entry searches Windows on the HDD and boot it up
 title Windows
   errorcheck off
   find --set-root --ignore-floppies --ignore-cd  /bootmgr
   chainloader /bootmgr
   find --set-root --ignore-floppies --ignore-cd  /ntldr
   chainloader /ntldr
   find --set-root --ignore-floppies --ignore-cd   /io.sys
   chainloader /io.sys
   errorcheck on
sunburnt
PostPosted: Sun 22 Apr 2012, 15:25    Post subject:

Sorry about the delayed reply, my main PC just died crippling me.

Sq.Apps are configured with: --prefix ( Path to Mount Point )
This sets the path where the app. is installed to, and also
where the app. expects to find it`s dependencies at.
App. C code has RPATH and CPATH that is set by this.
Anyone experienced in compiling should have no trouble with it.

Static built packages are more robust and run on more Linuxes.
Sure they`re bigger but media apps. are really library picky.
So the more that`s compiled in the greater chance it`ll work.

I only have built Mahjongg and Dead Meat music player Sq.Apps.

I can post my files for you to examine if you like...


minesadorada`s "find" for booting Puppy sounds great!
Does it make a menu of all found bootable O.Ss.?
minesadorada
PostPosted: Sun 22 Apr 2012, 02:33    Post subject:

RSH wrote:

Yes, this is almost exactly what i plan to do. But i want to go one step beyond that point. Currently i am able to do some work on this for the use with my own syslinux bootloader and also for Grub4DOS. I would like to make this also for Grub and/or Grub2 but i do not know how these boot menu entries have to look.

What do you use for booting LazY Puppy or other Puppies? Can you give an example for Grub and/or Grub2?


I use Grub4Dos, with its simple menu.lst. I don't specify the partition, but use the 'find --setroot' command, which searches the available partitions:
Code:
find --set-root --ignore-floppies /lazypuppy528/initrd.gz
kernel /lazypuppy528/vmlinuz pmedia=atahd psubdir=lazypuppy528 pfix=fsck acpi=off
initrd /lazypuppy528/initrd.gz


I have used grub(2) and it is more powerful, but as I recall, you have to edit a copy of the menu.lst (or the custom40 list), then run the update facility which copies the changes to the real menu.lst.

For Puppy installs, grub(2) seems like overkill.

I like your boot wallpaper. I never managed to get graphics to work in my grub4dos setup.
RSH
PostPosted: Sat 21 Apr 2012, 23:56    Post subject:

sunburnt wrote:
Hi RSH; Have you considered using Squash Apps. instead of SFS files?
They are mounted but not unioned, so less complexity and cpu overhead.
They`ve been used in Puppy before, and Tiny Core Linux uses them too.
The Sq.App. package build and compile is almost the same as normal.

Pets and other legacy loose file packages take up Save file space.
They can get viruses and be corrupted, Squash file packages can`t.
If all app. packages are Squash file types then no union FS is needed.

I have a Sq.App. menu written in BaCon that mounts and runs the Sq.App.
when it`s clicked, and unmounts it when the Sq.App. is exited.
I need to write a menu right-click to remove the Sq.app. and it`s config. files.

I did never hear of Squash Apps and my experience to compile sources is less than less (and unfortunately almost unsuccessful). Do you have a link to a working .pet of Squash Apps and/or some information, where to find, how to use, how to make own squash apps etc.pp.?
RSH
PostPosted: Sat 21 Apr 2012, 23:46    Post subject:

minesadorada wrote:
When you release Lazy Puppy 2.1, can you include a sample menu.lst as a textfile (perhaps in the 'guides' section)?

This will make it easy for a user to copy/paste all the sfs load options into a frugal install menu.lst rather than having to (mis)type them.

Looking forward to Lazy Puppy 2.1 Smile

Yes, this is almost exactly what i plan to do. But i want to go one step beyond that point. Currently i am able to do some work on this for the use with my own syslinux bootloader and also for Grub4DOS. I would like to make this also for Grub and/or Grub2 but i do not know how these boot menu entries have to look.

What do you use for booting LazY Puppy or other Puppies? Can you give an example for Grub and/or Grub2?
sunburnt
PostPosted: Sat 21 Apr 2012, 02:27    Post subject:

Hi RSH; Have you considered using Squash Apps. instead of SFS files?
They are mounted but not unioned, so less complexity and cpu overhead.
They`ve been used in Puppy before, and Tiny Core Linux uses them too.
The Sq.App. package build and compile is almost the same as normal.

Pets and other legacy loose file packages take up Save file space.
They can get viruses and be corrupted, Squash file packages can`t.
If all app. packages are Squash file types then no union FS is needed.

I have a Sq.App. menu written in BaCon that mounts and runs the Sq.App.
when it`s clicked, and unmounts it when the Sq.App. is exited.
I need to write a menu right-click to remove the Sq.app. and it`s config. files.
minesadorada
PostPosted: Fri 20 Apr 2012, 13:10    Post subject:

When you release Lazy Puppy 2.1, can you include a sample menu.lst as a textfile (perhaps in the 'guides' section)?

This will make it easy for a user to copy/paste all the sfs load options into a frugal install menu.lst rather than having to (mis)type them.

Looking forward to Lazy Puppy 2.1 Smile
Display posts from previous:   Sort by:   
Page 30 of 49 [730 Posts]   Goto page: Previous 1, 2, 3, ..., 28, 29, 30, 31, 32, ..., 47, 48, 49 Next

Powered by phpBB © 2001, 2005 phpBB Group