 |
(OLD) (ARCHIVED) Puppy Linux Discussion Forum Puppy HOME page : puppylinux.com "THE" alternative forum : puppylinux.info This forum can also be accessed as http://oldforum.puppylinux.com It is now read-only and serves only as archives. Please register over the NEW forum https://forum.puppylinux.com and continue your work there. Thank you.
|
FAQ
Search
Memberlist
Usergroups
Profile
Log in to check your private messages
Log in|
The time now is Thu 01 Oct 2020, 02:02 All times are UTC - 4 |
 Forum index » Advanced Topics » Cutting edge |
|
tiny_puduan_ascii-PreAlpha11.5 (made via a woof-next fork)
Moderators: Flash, Ian, JohnMurga |
|
View previous topic :: View next topic |
| Page 2 of 6 [82 Posts] | Goto page: Previous 1, 2, 3, 4, 5, 6 Next |
| Author | Message | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
After more thought I think the following is more what I want:
I'm wondering if the missing symlink is due to not having the right version of aufs-tools. For some reason I have a mount.aufs binary that requires too new a version of libc. I'm not sure how I would have got this "too new" version because my libc is newer than the one in devaun ascii. Anyway, full mount fails if mount.aufs is too new. Also "busybox mount" fails if we use tinycores version of busybox. Here's an example that fails from sc0ttman's pkg:
https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4918 the reason is that tinycore has separated the busybox applets into two parts. Those which only root can use are in /bin/busybox. Those in which some non-root users can use are in busybox.suid I could create a wrapper script for busybox that calls the correct binary, although there would be a slight performance cost to do this. Edit 1: Here is more on this error:
https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4820
/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh#L26
/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh#L254 _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
 |
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
Related to the previous post:
https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L147
https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4563 The following explimation sounds wrong to me: The above tar command might delete the pup_ro1 symlink. For some reason this isn't a problem if the following mount statment works:
can also use the full version of mount instead if one has a working "mount.aufs". However, if the mount fails, then tar extracts stuff to a new directory called pup_ro1 and the symlink is broken. ...but I think I"m looking in the right area I just don't completly understand why the symlink breaks if mount fails. _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
I was thinking that if I write a wrapper script for busybox, that there might be the possibility of handling options not supported by busybox. The goal would be so that the wrapper script could handle these options well enough that coreutils wouldn't be required for sc0ttman's package manager "i.e. pkg". _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
sc0ttman
 Joined: 16 Sep 2009 Posts: 2806 Location: UK |
You are clearly doing lots of work, so why not try some fixes for Pkg itself, to remove those deps? .. It's surely less work than a lot of the other stuff you have been willing to get stuck into... The quickest way may be to remove core utils after boot (manually delete/move stuff), replace with busybox, and keep running/fixing Pkg till it works again.. (Ideally where I can check the changes in a PR or at least a diff, and incorporate it into Pkg..) _________________ Pkg, mdsh, Woofy, Akita, VLC-GTK, Search |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
I'm not sure if this is an easy or hard thing to do but it's not the most critical thing that I need at the moment. At the moment, I will be experimenting with integrating Mistire's ppm 3 with with pkg. I think that many of the changes in Mistfire's ppm3 have been incorporated into Woof-CE, so I might eventually get in better sync with the woof-CE ppm. For the moment, I"m more interested in Mistfire's version because (at this moment) I can't keep pace with all changes in woof-CE. Also, I'm interested in back compatibility and Mistire's ppm was built for older versions of puppy than the bleeding edge woof-CE code is likely built for. _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
Apologizes for being slow on updating this. I've put off easier fixes while I dig both into Sc0ttmann's and Mistfire's package managers because I think that this is a critical piece. Tonight I look at Mistfire's first post in the PPMv3 thread for some inscite:
http://murga-linux.com/puppy/viewtopic.php?p=914058&search_id=934267901#914058 The key info here is the file "/root/.packages/database/COMPAT_DB_REPO" Here is what I have for this file in Tiny_Devaun
We can see that this file gives the complete path to the DB file for the repo and it doesn't depend on the DISTRO_SPEC file. This is important. In Sc0tmann's thread, I noted that I think that there should be enough info in Sc0tmann's package to be able to update the repo despite errors in DISTRO_SPECS. Such robustness would make it easier for people to configure "pkg". My Post: http://murga-linux.com/puppy/viewtopic.php?p=1030857#1030857 Sc0ttman's reply: http://murga-linux.com/puppy/viewtopic.php?p=1030898#1030898 I will note that Mistfire's approach is more explicit. Conversly to infer this exact path from one of the pkg configuration files (in sc0tman's ppm) such as :
requires some knowledge about how the repos are structured but perhaps most versions of linux structure their repos in very standard ways. I will also note that that sc0tman provides a more standard way of adding repos:
https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L1776 That is with pkg if a repo follows the debian formant (but not the standard puppy format) then you can add it by updating /etc/sources.list. Note this is slower than the way that the puppy package manager does it but will make it easier to add repos that don't fit puppies standard format (e.g. the tor repo). _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
I thought I would add a bit more info on how Mistfire's PPMv3 made this change. Recall from the previous post that the file "COMPAT_DB_REPO" contains the complete path the the package DB file (AKA the REPO doc file). Each line of this file is contactenated into a space seperated string:
*around line 61 to 68 of /usr/bin/sync-repo and the result is stored in a variable in the following the file "DISTRO_COMPAT_REPOS"
*around line 78 of /usr/bin/sync-repo Note that this file is the standard puppy file. The main thing we are doing here is putting the full paths to the repo DB file into the var PKG_DOCS_DISTRO_COMPAT. I had some issues (about a year or more ago) when I tried this approach with the tor REPO and had to make some hacky mods to 0setup but perhaps this is no longer an issue with the puppy package manager or perhaps Mistfire modified 0setup just enough to make it work. Note that 0Setup still contains references to DISTRO_SPECS so it might be possible to use these vars in the path if one wants to. _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
darry19662018
Joined: 31 Mar 2018 Posts: 731 Location: Rakaia |
First of all thank you very much for this new exciting Pup. I have one question regarding installing puppy linux firewall - I got this message when it installed. Is there an answer to fixing this, otherwise enjoying this test release. Connected fine to internet and pkgdialog enabled me to install Pfind. _________________ Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage https://freemedia.neocities.org/ |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
darry19662018
Joined: 31 Mar 2018 Posts: 731 Location: Rakaia |
I have been working with this iso and have go quite a lot working including mpv and a working firewall, isomaster, retrovol, pfind, xarchive and peasy firewall monitor as well as getting ntp, ntpd set-up working for correct system time. I made an iso using isomaster as remaster2 wouldn't work here is my first working iso https://archive.org/details/tiny_puduan_asciiprealpha11revised iso: https://archive.org/download/tiny_puduan_asciiprealpha11revised/tiny_puduan_asciiPrealpha11%28revised%29.iso _________________ Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage https://freemedia.neocities.org/ |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
darry19662018
Joined: 31 Mar 2018 Posts: 731 Location: Rakaia |
Well this Pup is quite a journey. Got .pet installing working by finding a missing link to .petget in /usr/sbin which links to /usr/local/petget Found that installwatch probably needs to be installed. Pwallpaper so that wallpaper can be changed. There was no firewall so installed from the very reliable pkgdialog Linux-firewall 2.0-rc9-patched-3-1 and peasy firewall monitor. Will not install from package manager - mpv this really added a quite a few libs should have used one OscarTalks .pets. To get time to work properly installed I installed ntp and ntpd. _________________ Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage https://freemedia.neocities.org/ |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
Lobster
Official Crustacean  Joined: 04 May 2005 Posts: 15588 Location: Paradox Realm |
This pre-alpha is interesting. 
It would be an ideal base for those of us interested in: - learning about cli - security base Puppy - return to minimal/core pup honing Bravo guys 
Puppy Linux Inspired by Chihuahua _________________ Puppy Raspup 8.2 Final
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
It's quite preliminary but the bugs posted in this thread thus far will help alot. 
Alternatively, one could create a script that calls "pkg -i". Thanks for noticing this . What I think I will do is create a script that calls "pkg -i" by default but if not installed will try some fallbacks like petget.
I'll look into this. As a side note wallpapers aren't a big thing to me, which means if I add it it might eventually be pushed out of the main sfs to something like the adrv or an extra_sfs.
I'm glad pkg is working well for you. When running in pmedia=usb mode it had some major issues for me. **as a side note I prefer just using IPTABLES rather then a specific firewall ap.
I'll also look into that. Note that at this moment pkg might be installing more libs than are needed.
Thanks for the tip. I'll add this in the next release. _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
I think I'll give your technique a try mostly as a way to test changes that I've made to pkg: https://pastebin.com/Q8KUt6wa but I'll post both yours and my remaster in the second post. Most of the upcomming changes to "pkg" are related to coding style (using variables instead of explict paths) but such changes will allow better integration with mistfire's package manager (i.e. PPMv3). However, one of the changes is semi-criticle for running in pmedia=usb mode. http://murga-linux.com/puppy/viewtopic.php?p=1030958#1030958 I will add the changes to my woof-next github fork once they've been tested more. P.S. one aspect of this integration is to use (when it exists) the subdirectory "package-files" for the files ending in ".file". If one makes my changes to pkg then if said path exists (e.g. /var/packages/package-files) then one must move these files into this sub directory. _________________ Find me on minds and on pearltrees. |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
s243a
Joined: 02 Sep 2014 Posts: 2626 |
Just to clarify here. There are two issues. One is whether or not pkg looking in the right place to see if a package is installed. 1. For instance if there is a file like:
then pkg shouldn't (in my opinon) install the package. In the case of the first path the issue is that I need to better integrate pkg with mistfire's PPMv3 (see previous post about how to do this). In the second case I need to verify whether or not pkg does this properly. This might not be default behavor (need to verify). I did notice though, that I do have an issue with the way that I syncked the dpkg build (via woof-next) with the puppy package managers (e.g. PPMv3 & pkg). The issue is that for some reason if I look in:
that for some files listed in
there is no coresponding file with either of the following forms:
In which case I'll have to generate said list rather than relying on dpkg to generate it. _________________ Find me on minds and on pearltrees. Last edited by s243a on Wed 10 Jul 2019, 14:37; edited 8 times in total |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
|
darry19662018
Joined: 31 Mar 2018 Posts: 731 Location: Rakaia |
I'm going to put up my second iso as well at archive.org because it includes my final fixes such as working petget. Thanks for your replies. https://archive.org/download/tiny_puduan_asciiprealpha11revised/tiny_puduanasciiprealpha11revised2.iso Still using isomaster method at this stage as remaster2 doesn't work and neither does Shinobar's program. _________________ Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage https://freemedia.neocities.org/ |
||||||||||||||||||
|
|||||||||||||||||||
|
|||||||||||||||||||
| Page 2 of 6 [82 Posts] | Goto page: Previous 1, 2, 3, 4, 5, 6 Next |
|
|
View previous topic :: View next topic |
|
Forum index » Advanced Topics » Cutting edge |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum |
Powered by phpBB © 2001, 2005 phpBB Group