1. Use kernel parameter "keepvar". The system will automatically clean out everything inside /var during restart unless this parameter is set. It works fine for Fatdog, but slackware keeps a lot of stuff in /var (e.g - list of installed packages), so if you don't keep the content of var, well - lotsa things will break sooner or later (e.g. can't uninstall packages). I should make it the default in the future.

2. Q5sys, before you burn your time building those packages, it is worthwhile to check what slackware already has, I think things like sysstat and traceroute is already there. Go and get http://mirrors.slackware.com/slackware/slackware64-14.0/slackware64/MANIFEST.bz2 and it will show you which package contains the file; alternatively, boot to Slackbones and use "slackpkg --file-search xxxx" to search for a package that contains xxxx.

3. I deposited xarchiver with xz and txz patch to the incoming ftp directory.

1. Use kernel parameter "keepvar". The system will automatically clean out everything inside /var during restart unless this parameter is set. It works fine for Fatdog, but slackware keeps a lot of stuff in /var (e.g - list of installed packages), so if you don't keep the content of var, well - lotsa things will break sooner or later (e.g. can't uninstall packages). I should make it the default in the future.

Ah, that explains why I had to update slack-pkg after a reboot. Yes, things will break!.

I can cross-compile them to any other architecture. The list contains some Puppy-specific packages (e.g elspci) and I'm working on more build scripts for such packages.

I want to make the building of all packages under Packages-puppy-common-official automated, so we can port Puppy to x86_64 or any other architecture easily. It's an on-'n-off project I've been working on for months now._________________My homepageMy GitHub profile

Q5sys, before you burn your time building those packages, it is worthwhile to check what slackware already has, I think things like sysstat and traceroute is already there. Go and get http://mirrors.slackware.com/slackware/slackware64-14.0/slackware64/MANIFEST.bz2 and it will show you which package contains the file; alternatively, boot to Slackbones and use "slackpkg --file-search xxxx" to search for a package that contains xxxx.

yea, im aware that i can use the slackware repo. but since slacware doesnt do dev packages, the packages can be bloated for what most users need. while it will work, id rather build the packages in a way thats more in line with the puppy creedo.
im sure ill grab some packages, but others ill rebuild myself.

koulaxizis wrote:

Can i work a 32bit distro on this?

if you are asking if this has 32bit compatibility built in, the answer is no. you could build this in using aliens multi-lib stuff, but im not going there for the official release.

# Base url to directory with a PACKAGES.TXT.
# This can point to any release, ie: 9.0, 10.0, current, etc.
#SOURCE=http://mirrors.slackware.com/slackware/slackware64-14.0/:OFFICIAL
SOURCE=http://download.salixos.org/x86_64/slackware-14.0/:OFFICIAL

# Sources for the testing, extra, and pasture areas - if you use them.
# SOURCE=http://mirrors.slackware.com/slackware/slackware64-14.0/extra/:PREFERRED
# SOURCE=http://mirrors.slackware.com/slackware/slackware64-14.0/testing/

I was working on a EFI booting 64 bit iPup for mac mini, it needed to be less than 200MB to 'store' and directly boot on mostly unused EFI partition found on Mac products. Tried in vain to strip Fatpuppy but was never able to get it under magic 200MB no matter what I did. Had all elements working including sound via HDMI at full resolution.
Also been pulling my hair out at the dozens of forced UDF into older CD iso formats.
This version has already has been remastered and burned as a pure UDF blu-ray bootable puppy. Which is a first. All other puppies that could boot had to be a nasty hybrid of old-iso and UDF that only booted a few versions of Wary. Likewise the mount program provided mounted and read UDF directly, nicely done.
Now need to find a 64bit growisofs to burn from within slack-bones. Hampered by lack of dialup support I'll have to wait until I can get to a wired lan next weekend.

I didn't check but slapt-get -i dvd+rw-tools should do it, has growisofs.or just search the GUI tool gslapt (there's a menu entry). Don't forget to have the keepvar kernel param on the kernel line, else you'll need to update slapt-get every reboot._________________Puppy Linux Blog - contact me for access

This version has already has been remastered and burned as a pure UDF blu-ray bootable puppy. Which is a first. All other puppies that could boot had to be a nasty hybrid of old-iso and UDF that only booted a few versions of Wary. Likewise the mount program provided mounted and read UDF directly, nicely done.

Out of topic, but this is very interesting. I know of no program, open source or otherwise, that will create a pure UDF bootable disc. How did you do that? Did you use mkudffs and then craft your own Eltorito boot sector by hand? Does it work only on EFI machines, or does it work with BIOS machines too?_________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

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