Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 09 Dec 2019, 00:52
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
Post new topic   Reply to topic View previous topic :: View next topic
Page 4 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Sat 03 Aug 2019, 12:41    Post subject:  

darry19662018 wrote:
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


Do you prefer "peasy firewall" or the standard puppy one "firewall_ng".

/puppylinux-woof-CE/woof-CE/tree/master/woof-code/rootfs-packages/firewall_ng
http://murga-linux.com/puppy/viewtopic.php?t=108403

I will add one of these either to the official release or one of my remaster tests. Note that as an alternative to having these installed to the base system; in my last commit (6527a450c07635dfec081131661260e0225a5520) I added, a script to install a package directly frome the woof-CE github code folders:

Code:

#!/bin/sh
#CURDIR="`realpath .`"
#. ./build.conf

SVN_ROOT="/var/tmp/svn"
#SVN_REPO_BASE="woof-CE"
mkdir -p "$SVN_ROOT"
cd "$SVN_ROOT"

#https://stackoverflow.com/questions/7106012/download-a-single-folder-or-directory-from-a-github-repo
BASE_URL=https://github.com
REPO=puppylinux-woof-CE/woof-CE
BRANCH=trunk #either "trunk" or "branches/branch"
#Checked out revision 1.
F_PATH=woof-code/rootfs-packages
FOLDER="$1" #rootfs-packages
mkdir -p "$REPO/$BRANCH/$F_PATH"
cd $REPO/$BRANCH/$F_PATH
#TODO add check that dir is empty then do svn command
if [ ! -d $FOLDER ]; then
  svn export $BASE_URL/$REPO/$BRANCH/$F_PATH/$FOLDER
fi
cd $FOLDER
F_NAME_DIR="$BASE_URL/$REPO/$BRANCH/$F_PATH/$FOLDER" #Keep this for historical reasons. See: https://pastebin.com/q3J2eEVu
TARGET_DIR="/"
( cd $F_NAME_DIR; find . -name '*' ) | cpio -pd "$TARGET_DIR"

s243a/woof-CE/blob/woof-next/woof-code/rootfs-packages/install_git_pkg/usr/bin/install_woof_CE_package

To use this script one must install it's dependencies as follows:
Code:

pkg --get subversion
pkg --get libsvn1
pkg --get libapr1
pkg --get libaprutil1
pkg --get libserf-1-1

It doesn't install the package metadata yet but I'll add that functionality shortly Smile

Regarding woof-next, I could add an option in the pinstall.sh script to automatically install these dependencies. Normally dependencies should be installed by the package manager. By adding these dependencies to the metadata one could have either the package manager or the woof-next build scripts install the dependencies. Also if one doesn't want to install the dependencies they can use the import detective in woof-next.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 652
Location: Rakaia

PostPosted: Sat 03 Aug 2019, 20:40    Post subject:  

I prefer Peasy Firewall Monitor - thats what I am using in 431 redo.
_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Mon 05 Aug 2019, 14:57    Post subject:  

darry19662018 wrote:
I prefer Peasy Firewall Monitor - thats what I am using in 431 redo.


I'll give that a try in my next remaster. In this remaster I've added firewall_ng

tiny_puduan_ascii-PreA11.1-Remaster_1-s243a.iso
**Requires patching. See notes below

Currently, I'm proceeding as follows:
1. Official Releases will not include a browser:
2. Remasters will include additional aps (e.g. firefox_esr).

I'm doing this both to test the remastering functionality as I go and also to give people the option of a more full feature version. The puppy remaster scripts might miss important stuff in either the /etc or /root folder because in the puppy remaster scripts this info is taken from the orginal iso, unless one chooses to add "hardware customization" in which case a small select amount of files are updated based on the save. I've created two scripts to add futhere updates to these folders than is provided by the standard puppy remaster scripts. See post:
http://murga-linux.com/puppy/viewtopic.php?p=1033645#1033645

These updates should not include hardware customization. On should also check the folders which this script updates and makes sure that no private info is in these folders. The scripts are heavily commented. This remaster includes the ability to install packages directly from github (as noted in the previous post), which means subversion and the dependencies are installed.

I've updated the zdrv and fdrv of this iso after testing due to some issues with modprobe. Once tested I will add it as an option in the original post..
On the fiewarll:
1. The firewall appears to work.
2. Unlike previous versions the generated firewall is added to /etc/init.d/rc.firewall.
3. The firewall script is generated by the script firewall_ng. Once upon a time the firewall use to generate code in /etc/rd.c/rc.local This seems to be no longer the case.
4. Start the fiewall with the command /etc/init.d/rc.firewall start

Issues:

Updated shortly...
1. The list of user-installed packages doesn't seems to be taken from the original iso rather than the save file. This should look like https://pastebin.com/tHVy8WRs . I'm not sure if this is an issues with the remaster script or an issue that is due to mistfire's puppy package manager mods.
2. The remaster script doesn't seem to create the file /var/packages/woof-installed-packages.
More issues will be listed shortly...

Here is the list of additional packages that are included in the remaster beyond the official release:

Code:

# /usr/sbin/pkg --list-installed
firefox-esr_60.6.3esr-1~deb9u1_i386
libjsoncpp1_1.7.4-3_i386
libvpx4_1.6.1-3+deb9u1_i386
alsamixergui_0.9.0rc2-1-10_i386
libfltk1.3_1.3.4-4_i386
libfltk1.1_1.1.10-23_i386
youtube-viewer-3.5.4-stretch_i386
gitweb_2.11.0-3+deb9u4_all
git_2.11.0-3+deb9u4_i386
openssh-client_7.4p1-10+deb9u6_i386
subversion_1.9.5-1+deb9u3_i386
libsvn1_1.9.5-1+deb9u3_i386
libapr1_1.5.2-5_i386
libaprutil1_1.5.4-3_i386
libserf-1-1_1.3.9-3+deb9u1_i386
geany-plugin-spellcheck_1.29+dfsg-1_i386
hunspell-en-ca_5.2.5-1_all
geany-plugins_1.29+dfsg-1_all
libenchant1c2a_1.6.0-11+b1_i386
libaspell15_0.60.7~20110707-3+b2_i386
enchant_1.6.0-11+b1_i386
aspell-en_2016.11.20-0-0.1_all
libcap2_2.25-1_i386

*Removed the following files from the output since they were in the officila iso: cdrtools-3.02a06-i686-precise-20160317 CLInet-0.8 libgnome-menu2_3.0.1-4_i386 ppm-mod-3.0 PupMenu-6.2 uextract-3.36
**These removed files from the output were the ones that were install via pkg in the build process rather than dpkg.

To patch:

Copy the following files (to /var/packages) [1]: woof-installed-packages, user-installed-packages, layers-installed-packages.

Also updating /usr/bin/pkg with the following code
https://pastebin.com/3aYuhzxF
might be helpful. The difference is that when I'm searching for searching files I"m using filenames instead of whole names. This change seems to avoid the script getting hung when certain files are missing.

Finally I'm missing the lists of files within packages in the folders builtin_files and package-files. I'll provide a tar file containing these files today.

TODO: Figure out why the remaster script didn't create the above missing files.

Notes
----------------------_
1 - On pastebin on must either copy and paste in row mode or convert the line endings of the dlownloaded file. Line endings can be converted either in geany or using the dos2unix script.

Edit 1: The files mentioned above, which need to be patched, can be found in the following archive: tiny_puduan_ascii-PreA11.1-Remaster_1-s243a_patch.tar.gz The archive also has an untested script to replace said files with the files in the archive.

This is the untested install script:
Code:

#!/bin/sh
#CURDIR="`realpath .`"
#. ./build.conf

TARGET_DIR="${ROOT:-/}"
SOURCE_DIR="${SOURCE_DIR:-fs}
cd $SOURCE_DIR
F_NAME_DIR="`realpah .`"
( cd $F_NAME_DIR; find . -name '*' ) | cpio -pdu "$TARGET_DIR"

I'll test this shortly.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 652
Location: Rakaia

PostPosted: Tue 06 Aug 2019, 04:33    Post subject:  

Sounds like a great plan I will get back to testing these releases soon.

Real world stuff at the moment.

_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Tue 06 Aug 2019, 11:37    Post subject:  

At some point I'm going to have to figure out the html5 issues with firefox_ESR. After looking at Mike Walsh comment (see post), I think that fredx might have figured this out (see post).

There are some related thread about this, which I'll add within this post below (eventually).

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Fri 09 Aug 2019, 13:51    Post subject:  

Here's another remaster:

tiny_puduan_ascii-PreA11.1-Remaster_2-s243a.iso

In addition to the extra packages noted in my previous post it also has:

Code:

espeak-ng-data_1.49.0+dfsg-11_i386
libvorbisenc2_1.3.5-4+deb9u2_i386
libvorbis0a_1.3.5-4+deb9u2_i386
libogg0_1.3.2-1_i386
libflac8_1.3.2-1_i386
libasyncns0_0.8-6_i386
libsndfile1_1.0.27-3_i386
libwrap0_7.6.q-26_i386
libpulse0_10.0-1+deb9u1_i386
libsonic0_0.2.0-4+b1_i386
libpcaudio0_1.0-1_i386
libespeak-ng1_1.49.0+dfsg-11_i386
espeak-ng_1.49.0+dfsg-11_i386

I think these are all dependencies for espeak-ng. I suspect that espeak probably has fewer dependencies than espeak-ng so if I include text2speach again I'll probably use espeak rather than espeak-ng.

Anyway, the big change here is in the remaster secript /usr/sbin/remasterpup2. I'll discuss more on this later.

As I previously noted remasters will have extra packages in addition to what is included in the official release. The intent here is both to test the remaster script and to provide a more full feature option.

P.S. I also made a change to the package manager (i.e. pkg) to better handle spaces in file paths. The fix can be found in commit acf5fe8569a6b9ebbcb035616620ca7a049d03f1

What I did was change an ash style for loop:
Code:

                    for f in $(find /tmp/$PKGNAME \( -type f -o -type l \))


into a bash style while loop:

Code:

 while read f
...
done < <(find "/tmp/$PKGNAME" \( -type f -o -type l \))


the bash style syntax is much easier to understand with regards to handling spaces. I could do this in ash if I use file descriptors. The bash syntax in <(...) automatically creates the file descriptors. However, doing this with file descriptors (or alternatively temporary files) would be more awkward and I don't know if I would need to do any clean up. (e.g. do I need to close them and do I need to do this with a trap statement). Anyway, I may eventually try to revert these types of changes to ash but for now it is easier to develop with bash syntax. Better space handling was important for installing expeak-ng because in espeak-ng-data the paths for some of the voices had spaces in the filename.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
oui

Joined: 20 May 2005
Posts: 3499
Location: near Woof (Germany) :-) - 3 PC's: DELL SX280 750 MB Pentium4, Acer emachines 2 GB AMD64. DELL XPS15

PostPosted: Fri 09 Aug 2019, 18:50    Post subject: Re: tiny_puduan_ascii-PreAlpha11 (made via a woof-next fork)
Subject description: experimental
 

s243a wrote:
A minimal Philosophy?

The reason that I wanted to experiment with some CLI networking tools is that I'm interested in minimal systems. The current iso isn't that minimal 213mb but I think it's probably about 100mb smaller then the typical puppy equivalents (ie.g. dpup stretch or puduan ascii. This is probably mostly due to not including a browser. There are lots of stuff that I could remove but I both wanted a system that works well, and didn't give me any error reports due to missing files.

Some of said errors (I would get if I stripped out some non-essential packages) would be due to puppy doing things at start-up that aren't strictly essential. Others might be due to unnecessary library dependencies that are compiled into the library. In the first case we can rectify the error by modifying the puppy startup script and in the latter case we need to use different binaries for some libs (e.g. recompile). In the latter case I might rectify these errors by re replacing a lib with the tinycore version.


the idea is fantastic!

but, after a lot of weeks reading that message, I don't see the real progress especially compared with the first Wary 64 bit from BK ((very) good working (really), size was a dream, 64 bit = probably more heavy than 32 bit, and supplied with a complete package of usual great applications! so I am actually searching for the event. devx for it). it is in my opinion the optimal stage to be better Wink in matter of minimal philosophy: the cli or no bone or one bone version has to become a bit smaller as Wary to succeed as new minimal leader of Puppy minimalistic in the extended Puppy family (as it is not (yet) a real Puppy, exactly as the first Wary 64 is not some real Puppy but simply a Quirky Wary...)

But ...

Quote:
Why the name tiny_devaun?

The name tiny_devaun is for two reasons. The first is that it is somewhat minimal and I eventually plan to make it more minimal by pushing more things to optional sfs files. The second is that both libc6 and busybox is from tinycore. I also included some other random tinycore stuff just to see what it is but anything that I thought would interfer with the system (statup stuff and user related stuff) is not included.

The tinycore components are from the tinycore9 iso which uses a newer version of libc6 that both devaun ascii and debian stretch. I will think about how I might implement more tinycore components


... I don't know what a Devaun is! perhaps it would of course explain my bad comprehension...

According the " subject" of the thread I suppose it is simply a wrong spell?

Ok.

As s243a is knowing this different stuff:

- SliTaz

I miss a bit a main clear design for a minimalistic project (BK did abandon some kind of absolute minimalistic: no cli, no no-bone, no one-bone, always about complete distributions, -excepted in one older Quirky beeing a bit more that a one-bone-).

SliTaz did have an answer to that design problem: the splitted initrd working like the Russian dolls:

- just starting (through grub) and working (the CL interpreter)
- working in CLI with all old (SliTaz specific) absolute minimal tools like clex, nano, retawq (is compilable for AMD64 and works as well or bad as for i386), rhapsody irc, and the 4 major SliTaz specific tools, especially TazPkg to handle with all extensions, also in CLI mode (you can add other text mode browser, email and messaging client, samba, cups and gutenprint, sound, as well as a x-window client, today xorg. But also you can also begin to install tools to begin to develop (in Puppy would a minimal devx have the same function).
- starting in xwindow with adequate tools but no real applications for some work excepted system work
- usual set of applications with the beautiful Slitaz panel on TazWeb (build on webkit first version; this is the reason why SliTaz did continue to stay on webkit first version, espec. concerning Midori, Midori is only a little package as added to webkit first version, but would be a big package more, if it would be actualized up to date)

I miss such a clear design of stages / domains of development in tiny puduan or analog projects...

next point, is important, alexej (the actuel contributor of SliTaz making a lot of development) did immediately explain in the wiki in detail (step by step) his methods to allow other really to stick to the exact methods of development from scratch. I did observe that a lot of willing-supplementary-developer did be defeating and explain it in the Puppy forum without to see real improvement of that situation and it can be the reason why the Puppy attractivity seems to be decreasing: nobody needs a Linux where you can about only do what it was yet possible in Puppy 1.0, a small set without differentiate all purpose extensions confronting you to main unsatisfied dependency problems if you use the depositories of some Ubuntu, Debian or Devuan because of a cribble design of the minimal core set compared to those of Ubuntu, Debian or Devuan...
Back to top
View user's profile Send private message 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Mon 12 Aug 2019, 06:34    Post subject: Re: tiny_puduan_ascii-PreAlpha11 (made via a woof-next fork)
Subject description: experimental
 

oui wrote:
s243a wrote:
A minimal Philosophy?

The reason that I wanted to experiment with some CLI networking tools is that I'm interested in minimal systems. The current iso isn't that minimal 213mb but I think it's probably about 100mb smaller then the typical puppy equivalents (ie.g. dpup stretch or puduan ascii. This is probably mostly due to not including a browser. There are lots of stuff that I could remove but I both wanted a system that works well, and didn't give me any error reports due to missing files.

Some of said errors (I would get if I stripped out some non-essential packages) would be due to puppy doing things at start-up that aren't strictly essential. Others might be due to unnecessary library dependencies that are compiled into the library. In the first case we can rectify the error by modifying the puppy startup script and in the latter case we need to use different binaries for some libs (e.g. recompile). In the latter case I might rectify these errors by re replacing a lib with the tinycore version.


the idea is fantastic!

Thankyou Smile

Quote:
but, after a lot of weeks reading that message, I don't see the real progress especially compared with the first Wary 64 bit from BK ((very) good working (really), size was a dream, 64 bit = probably more heavy than 32 bit, and supplied with a complete package of usual great applications! so I am actually searching for the event. devx for it). it is in my opinion the optimal stage to be better Wink in matter of minimal philosophy: the cli or no bone or one bone version has to become a bit smaller as Wary to succeed as new minimal leader of Puppy minimalistic in the extended Puppy family (as it is not (yet) a real Puppy, exactly as the first Wary 64 is not some real Puppy but simply a Quirky Wary...)


That would be an interesting project Smile

Quote:
But ...

Quote:
Why the name tiny_devaun?

The name tiny_devaun is for two reasons. The first is that it is somewhat minimal and I eventually plan to make it more minimal by pushing more things to optional sfs files. The second is that both libc6 and busybox is from tinycore. I also included some other random tinycore stuff just to see what it is but anything that I thought would interfer with the system (statup stuff and user related stuff) is not included.

The tinycore components are from the tinycore9 iso which uses a newer version of libc6 that both devaun ascii and debian stretch. I will think about how I might implement more tinycore components


... I don't know what a Devaun is! perhaps it would of course explain my bad comprehension...

According the " subject" of the thread I suppose it is simply a wrong spell?

Sorry. This was a spelling mistake:
https://devuan.org/
Quote:

Ok.

As s243a is knowing this different stuff:

- SliTaz

I miss a bit a main clear design for a minimalistic project (BK did abandon some kind of absolute minimalistic: no cli, no no-bone, no one-bone, always about complete distributions, -excepted in one older Quirky beeing a bit more that a one-bone-).

SliTaz did have an answer to that design problem: the splitted initrd working like the Russian dolls:

- just starting (through grub) and working (the CL interpreter)
- working in CLI with all old (SliTaz specific) absolute minimal tools like clex, nano, retawq (is compilable for AMD64 and works as well or bad as for i386), rhapsody irc, and the 4 major SliTaz specific tools, especially TazPkg to handle with all extensions, also in CLI mode (you can add other text mode browser, email and messaging client, samba, cups and gutenprint, sound, as well as a x-window client, today xorg. But also you can also begin to install tools to begin to develop (in Puppy would a minimal devx have the same function).
- starting in xwindow with adequate tools but no real applications for some work excepted system work
- usual set of applications with the beautiful Slitaz panel on TazWeb (build on webkit first version; this is the reason why SliTaz did continue to stay on webkit first version, espec. concerning Midori, Midori is only a little package as added to webkit first version, but would be a big package more, if it would be actualized up to date)

I miss such a clear design of stages / domains of development in tiny puduan or analog projects...


I hope eventually to make it more of a layered design like you discuss.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Mon 12 Aug 2019, 06:57    Post subject:  

s243a wrote:
At some point I'm going to have to figure out the html5 issues with firefox_ESR. After looking at Mike Walsh comment (see post), I think that fredx might have figured this out (see post).

There are some related thread about this, which I'll add within this post below (eventually).


I'm going to try installing the following and see if it helps:
https://packages.debian.org/stretch/libavcodec-extra57 (related post)

s243a wrote:
I'm calling this 11.1 because there are easy improvments that I haven't made yet:

tiny_puduan_ascii-PreAlpha11.1.iso

Testing has been limited to installing firefox-esr and testing pmount. The remaster script should work now but I haven't tested it yet. The above busybox wrapper improments are also included.

To install firefox-esr first update the repo db and then install with the following commands:

Code:

pkg --get libjsoncpp1
pkg --get libvpx4
pkg --get firefox-esr


Alternatively you can use JRB's portable browser installer which is available via the menus. Note that in pmedia=usbflash mode you'll get better perofmrance if the browser is installed in the save file/folder but if it is installed on a hard drive (or usb 3.0) then the ram savings of installing ouside of the save area might justfy the io cost of not running in ram.


To get all html5 formats to work with firefox-esr. I might have to do something like:
Code:

pkg --get libavcodec-extra57


p.s. for chrome based browsers one needs the following instead:
chromium-codecs-ffmpeg-extra. I also see some settings like "--with-system-libvpx" which may or may not be useful for firefox based browsers. Another setting that might be useful is media.libavcodec.allow-obsolete=true.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Tue 13 Aug 2019, 07:55    Post subject:  

Here's a new version.

tiny_puduan_ascii-PreAlpha11.2.iso (210M)

So far I've only tested installing firefox-esr:

Code:

/usr/local/petget/0setup #update package database
pkg --get libjsoncpp1
pkg --get libvpx4
pkg --get libavcodec-extra57 #Needed for some html5 videos
pkg --get firefox-esr


This is a official release so it doesn't come with a browser installed. As noted above browsers will only be included in remasters.

** I've went to a versioning system where major versions will be new builds from scratch and minor versions will be where I modify the rootfs of a previously built version.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 652
Location: Rakaia

PostPosted: Wed 14 Aug 2019, 02:38    Post subject:  

s243a wrote:
Here's a new version.

tiny_puduan_ascii-PreAlpha11.2.iso (210M)

So far I've only tested installing firefox-esr:

Code:

/usr/local/petget/0setup #update package database
pkg --get libjsoncpp1
pkg --get libvpx4
pkg --get libavcodec-extra57 #Needed for some html5 videos
pkg --get firefox-esr


This is a official release so it doesn't come with a browser installed. As noted above browsers will only be included in remasters.

** I've went to a versioning system where major versions will be new builds from scratch and minor versions will be where I modify the rootfs of a previously built version.


Hi s243a,

Test Machine:HP Pavilion dv6000.

Unfortunately it boots to desktop - then freezes and crashes.

Sorry I am out for this release. Last couple of Iso's could not get package managers working. I wonder if it is my machine? Not sure

_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Wed 14 Aug 2019, 07:50    Post subject:  

darry19662018 wrote:
s243a wrote:
Here's a new version.

tiny_puduan_ascii-PreAlpha11.2.iso (210M)

So far I've only tested installing firefox-esr:

Code:

/usr/local/petget/0setup #update package database
pkg --get libjsoncpp1
pkg --get libvpx4
pkg --get libavcodec-extra57 #Needed for some html5 videos
pkg --get firefox-esr


This is a official release so it doesn't come with a browser installed. As noted above browsers will only be included in remasters.

** I've went to a versioning system where major versions will be new builds from scratch and minor versions will be where I modify the rootfs of a previously built version.


Hi s243a,

Test Machine:HP Pavilion dv6000.

Unfortunately it boots to desktop - then freezes and crashes.

Sorry I am out for this release.

That's unfortunate. It works on my machine Sad

Quote:
Last couple of Iso's could not get package managers working.

I've only been testesting lately with scotmann's package manager (i.e pkg) from the command line. I should test the gui's though and PPMv3 as well. One issue that I was having though is that I have to frequently update the package database with either the command:

Code:

/usr/local/petget/0setup #This is the one that I've been using

or alternatively
Code:

pkg --repo-update


I'm not sure if this is because devuan linux frequently updates their package databases or if there is some other reason.

Quote:
I wonder if it is my machine? Not sure


I'm not sure. I don't yet have it working well on a virtual machine. Maybe once I get it working well on a virtual machine these issues will be sorted out. For instance, if I boot via virtualbox with the option pfx=nox then it seems to freeze when setting up networking.

On the 32bit laptop that I've done most of the testing it has been working quite well. I've also been testing on a 64 bit laptop and it also has worked without issues. It it is a quirk with your hardware then it's going to be very difficult for me to troubleshoot shince I don't have your hardware.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Wed 14 Aug 2019, 08:22    Post subject:  

Since the last release seems to be freezing for darry19662018 and I'm not having the same issue. I thought I would mention some log files.

One important log file is /tmp/xerrs.log. I will pick out a reported error in this file and see if it is an issue. One thing I see is the following:
Code:

Can't locate utf8.pm in @INC (you may need to install the utf8 module) (@INC contains: /usr/lib/urxvt /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/i386-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl) at /usr/lib/urxvt/urxvt.pm line 399.
BEGIN failed--compilation aborted at /usr/lib/urxvt/urxvt.pm line 399.
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
urxvt: unable to initialize perl-interpreter, continuing without.

I seem to be missing the following line from /etc/profile (that I included in
tiny_puduan_ascii-PreA11.1-Remaster_2-s243a.iso):
Code:

export PERL5LIB="/usr/lib/urxvt:/etc/perl:/usr/local/lib/i386-linux-gnu/perl/5.24.1:/usr/local/share/perl/5.24.1:/usr/lib/i386-linux-gnu/perl5/5.24:/usr/share/perl5:/usr/lib/i386-linux-gnu/perl/5.24:/usr/share/perl/5.24:/usr/local/lib/site_perl:/usr/lib/i386-linux-gnu/perl-base"


This shouldn't be a major issue though but I'll keep looking.

Here is another reported error in this file:
Code:

(geany:2652): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory

THis might be an error that one want to ignore for privacy reasons but I'll create the directory "/root/.local/share/" and see if it goes away.

Here's another error from the same log file:
Code:

/usr/sbin/filemnt: line 144: defaultfilemanager_x: command not found


I think this is why pmount won't automatically open the folder for me. I'll check woof-CE here. I think that defaultfilemanager_x is a new thing. I saw some discussion on woof-CE about it. Perhaps I'll copy the latest version of this file.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Wed 14 Aug 2019, 08:38    Post subject:  

s243a wrote:


Here's another error from the same log file:
Code:

/usr/sbin/filemnt: line 144: defaultfilemanager_x: command not found


I think this is why pmount won't automatically open the folder for me. I'll check woof-CE here. I think that defaultfilemanager_x is a new thing. I saw some discussion on woof-CE about it. Perhaps I'll copy the latest version of this file.


That seemed to fix the issue of pmount not being able to open the folder Smile

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Wed 14 Aug 2019, 14:26    Post subject:  

darry19662018 wrote:

Sorry I am out for this release. Last couple of Iso's could not get package managers working. I wonder if it is my machine? Not sure


Was the issue dependency resolution? Thankyou for your testing. Smile It lead me to look into this issue and as a consequence I found missing "/"'s after the tmp directory (related to dependency resolution). See fix:

https://github.com/puppylinux-woof-CE/woof-CE/commit/b0001f5dc6be0ea8f93543403b122077e364c8af

However, I have to review this fix a bit more to make sure that it isn't installing things that it shouldn't.

This issue was actually caused by a previous fix. See post:
http://murga-linux.com/puppy/viewtopic.php?p=1030838#1030838

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 4 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

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
[ Time: 0.1000s ][ Queries: 13 (0.0152s) ][ GZIP on ]