LxPupSc


LxPupSc is a somewhat different pup....

As default, the desktop environment is LXDE (openbox, lxpanel, pcmanfm) rather than the more usual puppy jwm and rox (although these are still part of the build and there is a desktop switcher to activate them if you prefer).

LxPupSc is a 100% woof-ce 32-bit build but it does have a unique characteristic in that it is built from multiple sources as follows:
- Slackware base components come from Slackware-14.2 (a.k.a Slackware-Current)
- LXDE components come from Arch Linux
- Puppy pets are a mixture of Slacko-14.2 plus specific pet-builds when recompilation is needed for Slackware-Current library compatibility

Plus there are also a bunch of fix-pets, packages-templates, woof-ce patches etc. to get it all to hang together. (What properly goes where is still a bit of a black-art for me and I suspect some rationalisation could be done here!)

The kernel is a woof-ce kernel-kit build.

Thanks are due to many people whose more original work has been plagiarised ruthlessly:
- Jejy69 for the original LxPup way back in 2013 and particularly the menu configuration
- 01Micko for the Slacko-6.3 configuration used as a starting point and for much advice along the way and the pet-build system
- Stemsee for the kernel config
- Iguleder, 01Micko, and pemasu for the kernel-kit
- Mavrothal for testing and fixes (particularly the ppm/dependencies fix) and woof-ce advice and help
- Marv, Billtoo, ETP, radky, rcrsn51, gcmartin and many others for testing and helpful suggestions on the forum thread (apologies to anybody not mentioned)
- Smokey01 for the repository

Along the way, testing has identified some things that have found their way back into woof-ce for the benefit of future puppies (e.g. the sns/firewall-ng fixes).

In using woof-ce I have got a list of "enhancements" that I'd like to see:
- better support for incremental builds (1download to produce a list of changed packages downloaded; 2createpackages to loop to build that list)
- better integration of rootfs-packages and DISTRO_PKGS_SPECS- so that you don't have to tick choices in 3builddidtro-Z (e.g. have yes/no/woof as options)
(an interim change would be to make all rootfs-package chosen by default so you only have to unselect unwanted ones....)
- 3builddistro-Z to have better unattended operation - replace terminal questions scattered through script with a config file so you can start the build and go away and forget about it

The version of LxPupSc at the time of writing is 16.08.1 (hosted on SourceForge)
The forum thread
The repository
LxPup Reviews

Cheers
PeeBee
August 2016

Obligatory screenie:


Posted on 8 Aug 2016, 08:22 by peebee - Categories: Puppy Woof-CE
Comments - Edit - Delete


Booting Slacko 6.3 on UEFI


Booting UEFI difficult? Nah. Not at all. Let's do this for Slacko 6.3 (32-bit).

1. Make sure you have UEFI machine. Machines that comes with Win8 or recent usually okay.
2. Get a blank flash drive. Format it as FAT32.
3. Grab a copy of Slacko 6.3 ISO
4. Grab a copy of Grub2 UEFI bootloader, from here: http://distro.ibiblio.org/fatdog/packages/700/grub2-efi64-2.00-x86_64-1.txz.
This is for 64-bit machine, if yours is 32-bit (extremely rare) then get http://distro.ibiblio.org/fatdog/packages/700/grub2-efi32-2.00-i686-1.txz.
5. Extract the tarball from previous step, make sure you get a copy of grubx64.efi (or grubia32.efi) from inside the tarball and rename it to bootx64.efi (or bootia32.efi).
6. On you flash drive:
- mkdir -p EFI/boot
- copy bootx64.efi (or bootia32.efi) and put it under EFI/boot
- Extract the contents of Slacko 6.3 ISO and put the following files to the root of the flash drive:
* vmlinuz
* initrd.gz
* puppy_slacko_6.3.0.sfs
* zdrv_slacko_6.3.0.sfs
- on the root of the flash drive, create a new file named "grub.cfg" and fill it with the following text:
menuentry "Start Slacko" {

linux /vmlinuz
initrd /initrd.gz
}


7. If you have Windows, boot to Windows and disable hibernation (aka fast boot, aka hybdrid sleep, etc). Your Slacko doesn't need this, this is more to protect Windows.
8. Configure your UEFI to disable Secure Boot.
9. Now boot with the flash drive plugged and tell your UEFI bios to boot from that flash drive.

You can run Slacko64 6.3 in the same way. Your success with other Puppies may vary, but the process is generally the same.

PS: In my (qemu) test, mouse doesn't work. But this is something I'm sure Mick can fix later :)

Posted on 1 Apr 2016, 01:12 by jamesb - Categories: Puppy
Comments - Edit - Delete


Fido Progress


So far I have built a slacko64 iso image with Fido available with his own 'home'. It boots fine and on shutdown nothing is changed in the routine that anyone would notice except that /home/fido is created using /root as the skeleton.

Here is a snap (click to enlarge):



What works:
  • browsing

  • text editing

  • package manager

  • virtual terminal (urxvt)

  • mounting drives

  • word processing

  • spread sheet

  • paint

  • videos (mplayer)

  • music (pmusic)


  • What doesn't
  • drive icon markers inconsistent

  • hot plugging

  • sfs management

  • updates management

  • ptheme

  • menu refresh

  • firewall tray icon


  • This is only fairly initial testing.There is probably a bunch more stuff that doesn't work but much of the gui stuff (gtkdialog/xdialog) will be rectified by adding the following line to the top of the application:

    [ $UID -ne 0 ] && exec sudo -A ${0} ${@}


    - which just pops the "askpass" box to type the password. For simplicity, fido and root passwords are the same - entered at first shutdown on creation of fido.

    So, plenty to do - most of it low level ugly stuff.

    Note: this version of slacko64 is built from the woof-CE xorg branch.






    Posted on 30 Mar 2016, 21:28 by 01micko - Categories: Puppy Development
    Comments - Edit - Delete


    pMusic 5 and its bad reputation


    pMusic has become a grown up program. Version 0.1 was released back in 2008. It quickly arose both glorifying and criticism. - And that was fair depending on the viewpoint. pMusic 1 was extremely hungry on CPU-power, but it also showed some fresh capabilities of Gtkdialog. The pushing of limits has continued, and it has become a showcase of features I didn't realize was possible using Bash/Gtkdialog.

    While pMusic 2 basically put more flesh to the bone, the 3. generation shipped the homemade internal dynamic db. That was very ambitious - maybe too ambitious. So the arguing flamed up again. Cpu-usage was now reduced to the half, but the db had become active and working on its own grabbing music information while playing. New valid arguments had come to the battle...

    pMusic 4 focused on all the goodies Thunor gave us with his outstanding work on Gtkdialog. With all kinds of new features the dynamic db became even more active, and it showed its bottlenecks and weaknesses. - The criticism to it was still fair. The last year of pMusic 4, most effort went to stabilize the db-usage. It has become clearer to me why Amarok, Clementine and friend use an external db like Mysql or Mariadb. But when focus is on size and dependencies, that was never an option.

    pMusic 4 became stable, but of course for a price. Introducing routines for queuing db pulls and continuously checking db status slowed down the general usage of the audioplayer. If it should fit the mantra of Puppy, it should work snappy also on older pc's. As mentioned, pMusic-code has been written since 2008, and I have learned some bits and pieces since then. There had to be a potential benefit of rewriting the code. The result is seen in pMusic 5, and the benefit is above my expectations. It seems that much of the stability from version 4.7.4 has survived, and it has become noticeable faster. - That means a lot faster. The cpu-usage has decreased, but more important, many functions are much more responsive. An overall snappier user-experience.

    http://murga-linux.com/puppy/viewtopic.php?p=213694#213694

    Posted on 25 Mar 2016, 8:41 by zigbert - Categories: Puppy
    Comments - Edit - Delete


    Great new blog!


    01micko has invited me to join the new blog.
    Yes, it looks great.
    This will be the place to come and get the latest news about what is happening in Puppy-land, and releases.


    Posted on 22 Mar 2016, 13:06 by BarryK - Categories: Puppy
    Comments - Edit - Delete


    Puppy Releases


    Somebody that has followed Puppy from the days when Barry was still holding the torch may wonder - what happens with the Puppy releases these days? During its heyday, Puppy can get a new release every 2-3 weeks, or at least one can expect a new release in 2-3 months.

    Nowadays, releases seem to be few and far between. Is this slowing down caused by lack of resources, lack of developers interest, or simply, lack of developers?

    Actually, the answer is "none of the above". When Barry was at helm, Puppy was in its growing phase. A lot of ideas were tried and dropped, new tools were added (and later dropped), etc. It was also in flux. Nowadays, Puppy is more mature and less tinkering is needed, so you don't see releases that often.

    Another reason is, there were complaints when releases were made too often. A personal Puppy installation took time and effort to customise, and to start over again after just 3 or 4 weeks was too much for many.

    To balance all this, the implicit agreement is that Puppy releases are now made once every 6 months, give or take.

    And lastly - there are actually point releases (or bug fix releases). You probably are not aware of them because they are not announced in Barry's blog; or they are not announced as a separate thread in the forum - they are posted in the same thread that announced the original release, but those posts quickly get drowned by other forum traffic.

    And that's what this blog is supposed to do - the author of the Puppy can announce his or her own release here, with links back to the forum for discussion. In a way, this blog is to play the same role that Barry's blog played in the past (now that his blog covers a wider range of topics).

    Posted on 15 Mar 2016, 13:31 by jamesb - Categories: Puppy
    Comments - Edit - Delete


    Pages: [1] [2] [3]