its in a sub-folder called PDFshuffler as it also requires the poppler PET to be loaded (PDF renderer).

PDF Shuffler enables you to import several PDF's, rearrange the pages and then export to a single PDF. If you want to edit individual PDF pages then the full blown inkscape caters for importing single PDF pages, editing, and then exporting the edited page (after which PDF shuffler might be used to reconstruct a multi-page PDF).

Just uploaded Latex/LyX (in a sub-folder as it requires python which is also included in the same sub-directory).

LyX is a document program that can create PDF's and allows you to concentrate on the content, without worrying about its format. i.e. forces you focus on the words rather than the layout. Select a template for your document/letter/article/thesis and fill in the words.

I've recently switched to fatten Thin-Slacko up again and have now remastered with zdrv incorporated into puppy sfs - using no compression, and then dropped that puppy sfs inside initrd, again with initrd uncompressed.

That weighs in at around 280MB, if compressed that drops to around 75MB.

Booting doesn't take that much longer when using the larger size and whilst it uses more memory space things run quicker because it doesn't have to do any decompressing. 280MB sounds a lot in older hardware terms, but in modern day terms that's relatively small, i.e. memory costs have declined and memory space increased at a relatively faster rate than have drivers/firmware (puppy file size).

I've just finished changing remasterpup2 so that now it remasters directly into a initrd file that's dropped into my frugal home folder (ready for the next reboot). With no compression that remastering takes less than a minute. Handy as I ram boot and use no savefile, so any changes I do want to make persistent involves remastering.

For other stuff, Office, Browsing etc I'm using Portable Apps (Rox Apps wrapped around sfs's) so that changes are persistent (stored on HDD along with data/docs etc.).

I've also tweaked init and other bootup code to strip (comment) out a lot that is irrelevant when using ram boot/no savefile (Pupmode 5). So now there's no searching of disks etc - puppy sfs (and drivers) are right alongside initrd and immediately to hand with no searching being required. Boots in less than 10 seconds (from when vmlinuz/initrd have been copied to ram to when the puppy desktop is first seen).

Keeping the core puppy lean and mean has resulted in the 'other' apps (HDD based) folder expanding quite a lot, that's now over 1GB when tidy, close to 2GB in its current untidy form. i.e. where firefox, libre, audacity, openshot etc. apps are stored (as rox-apps with sfs's). I've recently also taken the low/no compression choice with those files as well - my libre office for instance is now all totally uncompressed, which makes loading/running that much faster, but obviously eats more disk space.

Inform them whatever you need as improvements
3.0.0 seems going on garbling save docs ! (tarhpup Puppy)_________________Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.Last edited by Pelo on Fri 16 Jan 2015, 22:15; edited 1 time in total

I added some applications,also using radky's FbBox.
==============================================
EDIT: Discovered that I should have installed Mesa-GLX before
compiling the proprietary Nvidia driver.

why don't you share your version with us? When 01micko make thinslacko, it was originally to prove it was still possible to get under 100Mb. In fact, I think he made 2 versions, one based on slackware 13.37, and a bigger one based on slackware 14.
I am not sure thinslacko ever went through a decent debugging and validation. You however, are using it for a year (or more) and you are making improvements. shrinking it, and i must have become quite stable (otherwise you would not be using it anymore).

note that the kernel command line wraps around in the above extract, but it should all be on one line in grub4dos.

You'll need to adjust the root (hd0,2) according to whichever drive/partition you use to store the two files (they count from 0 being the first)

That's Slacko 533t, adjusted and re-remastered a lot. Updated from 3.01 to 3.10 kernel so supports later hardware

The normal puppy menu has been shifted to only be accessible via right mouse click on the desktop and the taskbar menu replaced with another menu. Includes Libre and latest Firefox and is relatively easy to swap out from a older to a later firefox as/when they become available. Firefox is also set to load up with zoom, no script, you tube downloader and is also set to view youtube videos as HTML5 videos instead of flash (which isn't installed). You do have to set the noscript to allow youtube for the video to display.

Also includes PXE server so any other PC's in your local LAN can boot puppy using net boot. you'll have to change /root/tftpboot/pxelinux.cfg directory contents to point vmlinuz and initrd.lzo to wherever those files are on your system i.e. symlink. Then start up the server (main menu PXE choice) and set other PC's to net boot - i.e. typically turn of secure booting in windows, reboot and hit <esc> during the initial startup and select net boot (or maybe F12 during boot up).

In the root directory there's a file called INITRD_LOCATION, that will likely need to be edited to point to where your initrd.lzo is stored. Remastering uses that as the pointer for which initrd.lzo to replace.

Remastering is slower on that version as the puppy contains Libre Office and Firefox which doubles the puppy size, so around a minute to remaster on my single core system. Main Menu (taskbar), Config, Remaster will kick that off.

It all runs in ram, only touching the HDD as that's where initrd.lzo and vmlinuz are loaded from, if they were stored on CD then you wouldn't have to touch HDD at all. Once booted you can unmount all drives.

Needs I guess at least 1GB of ram to work ok as puppy is stored uncompressed inside initrd and hence is stored uncompressed in ram once loaded.

There's no save files, nor is it intended to be run with a save file, just store data/docs outside of puppy space and if you want to make changes then reboot a clean/fresh version, make the changes and then remaster

You'll probably have to set the network up (click on the network tray icon) and sound (right click desktop to being up the puppy menu and select setup, setup puppy, wizards wizards .... etc).

Whilst the personal main menu includes "config" options, they're mostly just links to the files that need to be manually edited. Puppy is basically vmlinuz kernel, initrd initial ramdisk and puppy sfs main linux and desktop - where the desktop is fundamentally a xml text file(s) (ROX) and jwm provides a menu using text files to provide a graphical way to access programs. After any changes you need to run fixmenus and jwm -restart to install the changes - one of the config menu options is to run those commands.

Nothing polished, just something that works for me and likely has some things that I don't use that don't work (vga upgrade and PPM etc I suspect are 'faulty').

A great thing about ram booting is that you can try things out (leave all HDD's unmounted) and perhaps trash the system - and simply reboot to get back to a clean working version again. With a full install puppy if you go to a dodgy web site that manages to crack into your system that could install something that remains resident across reboots (persistent), with a ram booted puppy that virus only remains present for that one single session.

Use at your own risk, make backup's first ...etc after all this is a weird one, a Slackware 13 series based puppy (slacko 5.3.3) with a series 14 kernel dropped in (sourced from slacko 5.7), so I've no idea what may or may not work with that. Fun trying things out and if they work great, if they don't then you may need to reboot.

The one thing that attracted me originally to Slacko is was that it was one of the very few that booted straight to desktop on my hardware - after having tried numerous others beforehand that didn't. So I've stayed with slacko since. The repositories might not be good, but I hunt and try out other choices - from any version. Sometimes they work, sometimes they don't, being able to experiment and simply reboot out failures has made me more fond of having a read only core puppy. I'd be uncomfortable returning to a full install where one bad case can trash the system to a level where a full reinstall is required. The other factor is speed. When you get used to things being quick you're less inclined to move to slower alternatives. My son often mentions how his old hand-me-down rappy system is so much quicker than his winblows system.

The PXE server files/configuration in /root/tftpboot/pxelinux.cfg currently has pointers (sym links) to where initrd.lzo and vmlinuz are expected to be stored. That initrd.lzo could equally have been a initrd.gz file - what is expected however is that puppy sfs is contained within that initrd file

To put puppy sfs into initrd.lzo you create a directory below where initrd.gz and puppy sfs are stored, cd to that directory and run the commands

where that last line forms the new larger initrd file with puppy sfs contained in that file.

Or if you prefer gzip (.gz) the first two lines are the same but the last line is

find | cpio -o -H newc | gzip -4 >/somedir/initrd.gz

Using lzo for larger initrd is nicer in my opinion as there's a clearer distinction between a small initrd.gz (that doesn't contain puppy sfs) and the larger initrd.lzo that does contain puppy sfs. If you use gzip for both then you end up with small initrd.gz and large initrd.gz where only the filesize is a indicator of whether the file contains puppy sfs or not.

In /root/tftpboot/pxelinux.cfg you can create other files so as to serve up different boot choices to different PC's (MAC addresses)

For example for a Ethernet with address "88:99:AA:BB:CC:DD" it would search for the filename "01-88-99-aa-bb-cc-dd"

Which implies that if you had some old computer running on your LAN (perhaps even something like a always on (low power) Raspberry pi) that ran a PXE server, and somewhere in the wider internet there was a vmlinuz and initrd that you trusted and wanted to boot, then any PC in your LAN could net boot to that. i.e. Windows PC with secure boot turned off, when first booted press F12 (netboot) [or repeatedly press <esc> until the menu comes up and then select the net boot option], which then accesses the Raspberry pi (or old PC's) PXE server configuration, which then loads up the vmlinuz and initrd.gz (or whatever) from http://www.somewhere.com/vmlinuz and http://www.somewhere.com/initrd.gz, which could be the latest puppy as provided by Micko or Barry or ... whoever.

If the puppy boots and runs entirely in ram/memory, and you used the cloud for document storage (google drive or whatever), then the Windows HDD's might never even need to be opened (mounted).

This may all be old hat stuff for some, but its interesting to a newbie like me.

all that is in english, i shall read (... and translate it !) when not hurried. I like thin Slacko as it is, around 100MB. I understand that you are improving it. is that possible ?..
Thanks again to have done such a light Puppy.
Trains in ontario countryside as background, why not ? Les canadiens n'ont pas toujours de magnifiques forêts ou des chemins enneigés.
La question n'est pas pourquoi Slacko est si léger, la question est pourquoi les autres font plus !
ThinSlacko should be the standard, and other puppies ask them why they are so fat...
one would like to get abiword bigger ! no !_________________Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.

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