corepup

[wanderer]

libatomic.so.1

i dont find it in the tinycore repository

wanderer

[darry19662018]

Use this pet contains what you need
http://www.murga-linux.com/puppy/viewto ... &id=105825

[wanderer]

thanks darry

wanderer

[darry19662018]

By the way Wanderer if you need any dependencies/packages this site is brilliant:

https://pkgs.org/

[wanderer]

thanks again darry

wanderer

[fredx181]

Hi wanderer, just mentioning, don't know if you can use deb packages the way you run Tcore :
Debian has firefox-esr builds that don't depend on pulseaudio (I tested Jessie and Stretch).
https://packages.debian.org/search?keywords=firefox-esr
Recently tried the jessie package in Tahrpup and sound works.

Btw, "bug" me anytime you want, wanderer

Fred

[wanderer]

also much thanks fredx

thanks for all your work


wanderer

[wiak]

Hello wanderer

EDIT: Okay, since checked TC itself and there seems to already be an 'ezremaster' app installed so some of the following may be more useful for command info than actually required for remastering.

Since taking a new look at tiny core linux (64bit) I stumbled across a script that takes the CorePure64 iso of tiny core linux and allows user to customise it, whereupon it creates new iso containing the customisations. Isn't that something magical and useful...?! (i.e. a simple remaster utility)

https://gist.github.com/dankrause/2a9ed5ed30fa7f9aaaa2

I would imagine it wouldn't be impossible to modify the script to work with 32bit tiny core linux as an alternative, though I'm not myself planning to do that cos too busy 'playing'-with/(configuring) the current setups I'm experimenting with. However, at a glance, might just be a matter of changing the URL and the INPUTISO name near the beginning of the script.

I haven't actually tried the script myself as yet, but I expect it works since been under development/maintained for some years apparently. Note, that I'm not even exactly sure what it does at the moment... I'm more interested in it for now because it contained a number of underlying commandlines I need to use a lot on an individual basis and helps me remember them...

wiak

EDIT: Most of the following, though old, remains relevant for doing a manual remaster:

http://sirlagz.net/2011/05/17/how-to-re ... ore-linux/

Come to think of it, I haven't actually checked if tinycore has a remaster utility installed by default nowadays - but I've never heard of such. There are wiki instructions though:

http://wiki.tinycorelinux.net/wiki:remastering

There's also a convert deb to tcz here:
https://gist.github.com/nuxlli/ddd3fa2ceed7b2cecdd3

[wanderer]

hi wiak

thanks for all your help and support


i am using coreplus 9 32 bit for my base now

yes it does have an ezremaster utility already in it

but i just un cpio the core, make changes and cpio the core up again

its very easy and straightforward

same way with tcz just unsquash, make changes and squash them


at this time i have 2 problems

1.

i need to have a recipe (not a script since i want to do it manually)

to unsquash puppy sfs files pets and debs

once they are in a normal folder

i can make them either into a linked directory or a tcz

and

2.

i am trying to set up an up to date firefox

with apulse

and the necessary codecs like flash etc

rather than pulseaudio

tinycore has a script to download and build the newest firefox

but the resulting firefox is incomplete


i am working on these things in my usual slow and inexpert way

and will eventually accomplish them

but of course any help is appreciated


eventually i will convert some more puppy stuff to work in corepup

since that is one of the main ways to puppify it


on a related note

i do not think you can find a better design

to make a minimal modular system

and i think it would be useful

to both the puppy and tinycore community

to develop it

as i will do


but like i said any help is appreciated


and thanks again wiak

best regards

wanderer

[RedQuine]

hi wiak


i need to have a recipe (not a script since i want to do it manually)

to unsquash puppy sfs files pets and debs

once they are in a normal folder

i can make them either into a linked directory or a tcz

Not sure if this is the sort of thing you're looking for, but here's what I did for iron.tcz (if my memory is correct!):

1. Unsquashed the latest iron.deb with UExtract (which will unsquash just about everything you throw at it as long as it's been squashed in the first place - .pet, .deb., .sfs, .tcz ...) - creating 'iron.deb.extracted'
2. Created a separate directory, just called 'iron'
3. Opened the control file in 'iron.deb.extracted' as text, which gave me a list of dependencies
4. Deleted all the other stuff in the file, added .tcz to the end of each dependency, and saved it as iron.dep
5. Copied across /usr/share/* from 'iron.deb.extracted' to 'iron', as /usr/local/share/*
6. Squashed 'iron' as iron.tcz
7. Copied both iron.tcz and iron.dep to 'optional' in Coreplus
8. In Coreplus: ran a dependency check, downloaded the missing dependencies, then loaded iron.tcz and launched it from the command line.

I'm pretty sure I had to edit iron.dep a few times, as the Tinycore repository had different names for some of the dependencies. But that was basically it. [Edit: just remembered, I needed to download the .deb for Chromium as well, as the Iron control file was kind of empty. But you shouldn't have any problem with Firefox, or any other "primary" application.]

I've also found Pkg incredibly useful for reporting and downloading dependencies. You just need the location of the repository; Pkg "talks" you through everything else.

I haven't had a chance to try the new iron.tcz/iron.sfs in Corepup yet owing to other commitments, but it's on my list of things to do. (Also planning to repackage Gimp 2.10 from the AppImage, as UExtract does those too.)

All of the above can be done on the command line if you prefer, but personally, I tend to use whatever tools happen to be lying about.

[wanderer]

wow redquine

i will try to follow your work


thanks

wanderer

[wiak]

Not sure if this is the sort of thing you're looking for, but here's what I did for iron.tcz

Yes, what you write is all that is needed for that kind of thing RedQuine. TinyCore package manager itself has good dependency resolution (so correctly later loads also the dependencies of whatever dependencies you state for iron browser). i.e. the dependencies of the dependencies!

It certainly is a simple system to upgrade and work with once you understand the basics of how it works (the loop mounting to one place and auto-symlinking into the usual fs hierarchy - so many symlinks, but it just works, most of the time). And unlike many other distro's, building tcz packages, like you describe is equally simple really - just need that extra deps file, when deps are involved.

Using UExtract rather than having to manually bother with 'ar' and then tar <options> (or dpkg-deb command) is a good tip for extracting deb packages in the first place.

https://www.cyberciti.biz/faq/how-to-ex ... ntu-linux/

wiak

[wiak]

In another thread, I suggested this:

i.e. Puppy as: core + package-manager

where package-manager could be PetGet, sc0ttman's pkg, dpkg/apt, void xbps and so on.

http://www.murga-linux.com/puppy/viewto ... 38#1023638

I wasn't actually talking about tiny core linux (rather, it was the 'core' Puppy boot scripts etc). However, it almost evidences the 'idea' that it would probably be easily possible to use a minimum tiny core and add petget or sc0ttman's pkg manager to it. In that case you would probably want to aim to only use the Puppy's petget or pkg since, owing to the way they work, package managers do not work well together (they can't track each other). I'm not suggesting to do this, however - tazpkg manager is just too great and much of tinycorelinux excellence comes from that (and see below issue regarding aufs versus loopback/symlinking mechanisms).

Of course tazpkg might also be adopted as package manager for a system based on a Puppy core (though not so likely since Puppy using aufs or experimentally overlayfs for its merging in mechanisms whereas tinycore uses loop mounts followed by symlinks - however that tinycore mechanism could be tried in a new Puppy build).

wiak

[s243a]

It's not hard to sync petget with tazpkg, granted each package manager will likely work from differn't repos.

[wanderer]

hi all

corepup/tinycore core is 9-13 mgs

and is already being maintained by the tinycore community

it is fully functional and can get on wired internet and download packages

the puppy community and the tinycore community

could maintain it easily and indefinitely

and it could form the base of a minimal modular puppy/tinycore system

the complexity of the puppy boot process
and the layered file system

are irrelevant to what makes a puppy a puppy

small size flexibility and functionality

thats what makes a puppy a puppy and a tinycore a tinycore


a process (recipe or script)

that allows corepup to use puppy stuff

would combine the virtues of both

in addition dcore gives access to the debian respositories
and makes application packages
and that could be the only main distro that is used
making the maintenance of things easier still



in my humble opinion

wanderer

[wanderer]

hi all

i now know how to open

an sfs file

and a deb file

how do i open a pet file


thanks

wanderer

[s243a]

hi all

i now know how to open

an sfs file

and a deb file

how do i open a pet file


thanks

wanderer

Typically a pet file is either a tar.gz archive it an xz archive. For an SFS either mount it or unsquash it.

[wanderer]

thanks s243a

wanderer

[musher0]

hi all

i now know how to open

an sfs file

and a deb file

how do i open a pet file


thanks

wanderer

Hi wanderer.

Fellow forum member SFR has produced a magnificent tool that opens
almost all known archives, including pet files.

It's called UExtract. SFR has just updated it. You can get it from here.

It's a real time saver. I hope you like it.

BFN.

[wanderer]

thanks musher0

wanderer