(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (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.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 01 Oct 2020, 12:18
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Slacko32/64 700 BETA 2
Moderators: Flash, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 19 of 35 [522 Posts]   Goto page: Previous 1, 2, 3, ..., 17, 18, 19, 20, 21, ..., 33, 34, 35 Next
Author Message
zigbert


Joined: 29 Mar 2006
Posts: 6629
Location: Valåmoen, Norway

PostPosted: Mon 19 Sep 2016, 12:22    Post subject:  

I see... busybox grep works as expected ... but that doesn't really help, does it? I understand that busybox is used during startup, but we use the full_bloated_grep doesn't we?

On the other hand this might not interfere much with the Puppy core since no special chars is used in the scripts itself. Maybe pFind and other scripts handling personal file(names) will suffer ...

_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1566

PostPosted: Mon 19 Sep 2016, 16:57    Post subject:  

@zigbert: What do you suggest? Make busybox grep the default, always use grep -a, or revert all new puppies to grep-2.14?
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Tue 20 Sep 2016, 06:51    Post subject:  

zigbert wrote:
I see... busybox grep works as expected ... but that doesn't really help, does it? I understand that busybox is used during startup, but we use the full_bloated_grep doesn't we?


'busybox' is twice in the system.. a static version in the initrd.gz and the version compiled with shared libs in the main system. This is how it has always been since puppy-2.x series.

Of course busybox is a multicall binary. It has an enormous amount of symlinks that mimic full versions and depending on the configuration of busybox many more too including 'grep' which is why when you invoke 'busybox grep [some pattern] /some/file' it more or less behaves like real 'grep'.

zigbert wrote:
On the other hand this might not interfere much with the Puppy core since no special chars is used in the scripts itself. Maybe pFind and other scripts handling personal file(names) will suffer ...


Further to this, I have found that encoding of your test file makes a huge difference...

If it is encoded with unicode... (with geany > document > set encoding)

Code:
# file /root/forum
/root/forum: UTF-8 Unicode text
# grep mp3 /root/forum       
line 1.mp3
Gartnerlosjen - Tøffe tak Tute.mp3
The Beach Boys - Surfin´ U.S.A.mp3
Mötley Crüe - Primal Scream.mp3
line 5.mp3


or ISO-8859

Code:
# file /root/forum
/root/forum: ISO-8859 text
# grep mp3 /root/forum
line 1.mp3
Binary file /root/forum matches


I suspect that grep is not the problem but encoding is and perhaps some setting in slacko.

The plot thickens.

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
zigbert


Joined: 29 Mar 2006
Posts: 6629
Location: Valåmoen, Norway

PostPosted: Tue 20 Sep 2016, 15:45    Post subject:  

01micko wrote:
Further to this, I have found that encoding of your test file makes a huge difference...

[...]

I suspect that grep is not the problem but encoding is and perhaps some setting in slacko.
Good catch!

I made a test to verify - switch the grep in this Slacko alpha and the latest stable:
- Run grep 2.14 in Slacko 6.9.6.1 --> Grep finds all lines in the testfile
- Run grep 2.25 in Slacko 6.3.2 --> Grep halts after line 1

Conclusion:
It is grep that troubles with the encoding. Both Slacko's behave the same with equel versions of grep.

_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
radky

Joined: 02 May 2010
Posts: 981

PostPosted: Tue 20 Sep 2016, 23:45    Post subject:  

Most likely, the current issue of failed 'grep' in Slacko-7 is due to the new binary-detection heuristics initially implemented in grep 2.21 (2014-11-23).

In some locales, the new grep may interpret special characters as encoding errors and, by design, parsing of the input string simply aborts with truncated output.

For scripts that may process special characters, the GNU grep developers suggest setting the system's locale to a unibyte locale where all bytes are valid, or editing the affected scripts to parse input strings as binary data (grep -a).

GNU bug reports for grep >= 2.21

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22838
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24347

_________________
PupMates
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Wed 21 Sep 2016, 01:33    Post subject:  

radky wrote:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22838


A rather in depth disscussion there. Thanks radky!

Looks like grep-2.25 *might* fix the issue. Building now; packages soon.

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
zigbert


Joined: 29 Mar 2006
Posts: 6629
Location: Valåmoen, Norway

PostPosted: Wed 21 Sep 2016, 01:35    Post subject:  

radky wrote:
setting the system's locale to a unibyte locale
What does this mean? How do I do that?
_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Wed 21 Sep 2016, 01:53    Post subject:  

01micko wrote:
radky wrote:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22838


A rather in depth disscussion there. Thanks radky!

Looks like grep-2.25 *might* fix the issue. Building now; packages soon.


Of course not! That is the version we have Rolling Eyes

From the conversation in the link they don't look like reverting so going forward we might need to look at a wrapper for grep>=2.21 to preserve backward compatibility.

Surely pFind/pFilesearch will suffer as well as many others.

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1566

PostPosted: Wed 21 Sep 2016, 02:05    Post subject:  

01micko wrote:
radky wrote:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22838


A rather in depth disscussion there. Thanks radky!

Looks like grep-2.25 *might* fix the issue. Building now; packages soon.

I tried making a grep-2.25 with the 0001patch in message #64. It just skips the three lines in zigberts post then keeps going now, which is still not ideal. So even though the issue is closed, I don't think the "patch" they posted fixes the issue entirely.

Code:
# grep mp3 /root/forum
line 1.mp3
line 5.mp3
Binary file /root/forum matches
# grep -a mp3 /root/forum
line 1.mp3
Gartnerlosjen - Tøffe tak Tute.mp3
The Beach Boys - SurfinŽ U.S.A.mp3
Mötley Crüe - Primal Scream.mp3
line 5.mp3
grep.gz
Description  version 2.25 + 0001patch
gz

 Download 
Filename  grep.gz 
Filesize  79.97 KB 
Downloaded  91 Time(s) 
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Wed 21 Sep 2016, 02:11    Post subject:  

zigbert wrote:
radky wrote:
setting the system's locale to a unibyte locale
What does this mean? How do I do that?


Seems a non-UTF locale (in our context) is unibyte. UTF-8 is multibyte.

Quote:
The first problem with the C library API is the support of multibyte locales. According to the locale encoding, in general, every character is represented by one or more bytes (up to 4 bytes in practice — but use MB_LEN_MAX instead of the number 4 in the code). When every character is represented by only 1 byte, we speak of an “unibyte locale”, otherwise of a “multibyte locale”. It is important to realize that the majority of Unix installations nowadays use UTF-8 or GB18030 as locale encoding; therefore, the majority of users are using multibyte locales.


https://www.gnu.org/software/libunistring/manual/html_node/char-_002a-strings.html

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1566

PostPosted: Wed 21 Sep 2016, 05:36    Post subject:  

zigbert wrote:
radky wrote:
setting the system's locale to a unibyte locale
What does this mean? How do I do that?

I tried adding alias grep='LC_ALL=C grep' to /root/.bashrc in slacko, seems to be working now with your forum example.
Back to top
View user's profile Send private message 
zigbert


Joined: 29 Mar 2006
Posts: 6629
Location: Valåmoen, Norway

PostPosted: Wed 21 Sep 2016, 07:01    Post subject:  

Download links in http://www.murga-linux.com/puppy/viewtopic.php?p=444080#444080 is dead.

My printer works without hplip (using the cups driver), but only in 32-bit.

_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
Jades

Joined: 07 Aug 2010
Posts: 461
Location: Somewhere in Blighty.

PostPosted: Wed 21 Sep 2016, 12:40    Post subject:  

Any thoughts about the issue I have with LiveCD boots not looking for the save files?

When testing Puppy I usually boot from the CD and do some basic set up. I then copy the main SFS files from the CD to the PuppyFiles folder on sdb1 which is formatted NTFS and has my Windows XP install on. I prefer to have the Puppy files in a sub directory as it keeps the root directory nice and tidy and makes sure all of my Puppy stuff is in one place.

Once happy with the setup I then initiate a reboot, choosing to create a 1GB ext4 save file in the usual PuppyFiles folder on sdb1 and giving it a descriptive name (so 6961new for this version which becomes slacko64save-6961new.4fs). I decline the offer to copy the sfs files (having already done so manually) and wait for the computer to reboot.

When the machine has finished POST I hold down the key to bring up the menu to select the boot device and select the DVD writer. Normally this will start booting Puppy from the CD and the search routine will pick up the SFS and save files in /mnt/sdb1/PuppyFiles and use them to boot. At the moment, however, it doesn't see them and carries on with booting from the CD and ends up with a fresh first run session like you would get from intentionally booting pfix=ram on previous versions or selecting the 'boot with no savefile' option on recent test builds.

The files are clearly there in the folder (see screenshot) but they just aren't being seen. If I copied them to the root directory Puppy would then spot them on booting but I don't want to have the root directory of the XP install cluttered.
PuppyFiles.png
Description  Screenshot of /mnt/sdb1/PuppyFiles directory on my NTFS formatted hard drive, highlighted files are for a test LiveCD installation of Slacko64 6.9.6.1 and aren't being seen on booting from CD.
png

 Download 
Filename  PuppyFiles.png 
Filesize  51.13 KB 
Downloaded  195 Time(s) 

_________________
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 HardInfo Report
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Back to top
View user's profile Send private message Visit poster's website 
Jades

Joined: 07 Aug 2010
Posts: 461
Location: Somewhere in Blighty.

PostPosted: Wed 21 Sep 2016, 14:07    Post subject:  

Sailor Enceladus wrote:
Does full install work for you with Xenialpup64 7.0.7 and Xenialpup 7.0.4? I'm guessing both work but just to be sure.


I've only tested it on Xenialpup64 7.0.7, it boots up fine as a full install. LiveCD boot also works without issue and managed to see the save files in sdb1/PuppyFiles when searching for them on boot.

_________________
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 HardInfo Report
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Back to top
View user's profile Send private message Visit poster's website 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1566

PostPosted: Wed 21 Sep 2016, 14:21    Post subject:  

Jades wrote:
If I copied them to the root directory Puppy would then spot them on booting
but I don't want to have the root directory of the XP install cluttered.

@Jades: About savefiles in a sub-folder on HDD, what are your thoughts about this post?

jlst wrote:
Regarding the puppy saves, you have your stuff hidden somewhere. do you use the PSUBDIR boot param?

This is a new thing. It doesn't look in the subdirectories in all partitions unless you specify
where, to save time for those (most?) who don't want it to search everywhere, I think.

http://www.murga-linux.com/puppy/viewtopic.php?t=107178
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 19 of 35 [522 Posts]   Goto page: Previous 1, 2, 3, ..., 17, 18, 19, 20, 21, ..., 33, 34, 35 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
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.0824s ][ Queries: 13 (0.0248s) ][ GZIP on ]