site  contact  subhomenews

Quirky Xerus64 8.2 coming soon

July 19, 2017 — BarryK
I thought that I had built 8.2 final this afternoon, but it failed one test. This is what can happen when one introduces changes at the 12th hour.

The problem is the introduction of the ntfs-3g driver into the initramfs, as I reported yesterday:
http://bkhome.org/news/201707/ntfs-3g-driver-in-initramfs.html

I had compiled this driver statically sometime ago, I thought that it was configured to use its internal fuse driver. The ntfs-3g driver can be configured to have its own internal fuse driver, or use the fuse driver of the Linux kernel.

Testing "8.2", the ntfs-3g driver reported fuse to be missing. There is no setup to have kernel modules in the initramfs, all drivers required for bootup are expected to be builtin to the kernel.

Instead of recompiling the ntfs-3g driver, I decided to recompile the kernel. Have bumped to the latest, 4.11.11, and just made one change, fuse driver now builtin. It is compiling right now.

So, hopefully, 8.2 will be out about another 24 hours from now. Will of course have to do more sanity testing before releasing.

Tags: quirky, linux

YASSM 3.0

July 18, 2017 — BarryK
As well as the "peasy" series, rcrsn51 also created Yet Another Share Mounter (YASSM) for Samba. Now up to version 3.0:
http://murga-linux.com/puppy/viewtopic.php?t=63090

Quirky has version 2.9, have updated to 3.0.

Tags: quirky, linux

ntfs-3g driver in initramfs

July 17, 2017 — BarryK
The guys on the Puppy Forum are testing Quirky 8.1.94, most recently an issue with ntfs:
http://murga-linux.com/puppy/viewtopic.php?p=961004#961004

There is something strange going on here. The Linux kernel has the ntfs driver builtin, and configured to allow writes when ntfs partitions are mounted.

Except that we can't. Get an error when try to write. It used to work, something has changed.

Anyway, writing to an ntfs filesystem is supposed to be less reliable using the kernel driver, and ntfs-3g fuse-based driver is preferred.

I didn't have ntfs-3g in the initramfs as compiled statically it is about 410KB. Have now put it in and modified the 'init' script to use it.

This is a good thing, as writing to ntfs filesystems will now be more reliable. Though, it may be possible to avoid writing from the initramfs, and remount with ntfs-3g when running in the main Quirky f.s.

The downside of ntfs-3g is that being fuse-based, it is slow.

Tags: quirky, linux

JWMDesk 2.3

July 17, 2017 — BarryK
Forum member radky has created JWMDesk, a very comprehensive GUI desktop manager, for configuring JWM and many other things:
http://www.murga-linux.com/puppy/viewtopic.php?t=101460

It overlaps configuration tools already in Quirky, however has the advantage of being an integrated manager.

So, I have decided to give it a go in Quirky. The latest version is 2.3, and I have created a PET named 'JWMDesk-2.3-1.pet'. The "-1" is because I have made a couple of changes -- I removed the 'pinstall.sh' file, and created /usr/local/jwmdesk/window_width with "510" in it.

The problem with pinstall.sh is that it has absolute paths in it, so not suitable for woof* builder. Also, I scanned through it, and I couldn't see anything that is really required. Admittedly, my look was brief, but a quick check (also brief), it seems to work without having run pinstall.sh.

JWMDesk will be in the next Quirky.

Read more...

UrxvtControl 1.3

July 17, 2017 — BarryK
Ha ha, I was lamenting the proliferation of GUI popup message box utilities in Quirky:
http://bkhome.org/news/201707/bcm-popup-messages.html

I have now removed one of them: 'yad'.

It is only required by 'urxvtset', a urxvt terminal emulator configuration utility:
http://www.murga-linux.com/puppy/viewtopic.php?t=68624

However, I have removed urxvtset, replaced it with radky's UrxvtControl 1.3:
http://murga-linux.com/puppy/viewtopic.php?t=97337

Tags: quirky, linux

PupSysInfo 2.7

July 17, 2017 — BarryK
Puppy forum member radky created PupSysInfo, a very detailed system information GUI app for Puppy.

Quirky has version 2.6.3, however radky has released 2.7:
http://murga-linux.com/puppy/viewtopic.php?t=73101

I have upgraded the PET for Quirky.

Note, Quirky also has HardInfo, which is written in C and requires GTK.
https://github.com/lpereira/hardinfo

They are similar, but PupSysInfo is specifically designed for Puppy (and Puppy-derivatives), so provides more Puppy-specific information.

Tags: quirky, linux

PeasyPort 2.2

July 17, 2017 — BarryK
Puppy Forum member rcrsn51 created the "peasy" series of apps for Puppy.

Quirky has many of them, including PeasyPort, a network scanner. Quirky has version 2.0, but rcrsn51 has now released version 2.2:
http://murga-linux.com/puppy/viewtopic.php?t=79913

I have created a PET, named 'peasyscan-noarch-2.2.pet' and updated Quirky.

Note, rcrsn51's PET has two binary executables, 'pnscan' and 'arp-scan', but Quirky already has those, so I have repackaged the PET without them.

Tags: quirky, linux

0setup script fails in Woof

July 09, 2017 — BarryK
The '0setup' script in Woof* downloads package database files and converts them to Puppy-standard-format.

Sometime ago, yes I have a date, 160411, I applied a fix to the 0setup script in woofQ. UTF-8 multi-byte characters were breaking the script for Ubuntu-based builds.

These characters only occur in the description fields of the Ubuntu database files.

Back then, I inserted this code into 0setup, around line 200:
      #[ $RETSTAT -eq 0 ] && mv -f $xDLFILE ${PKGLISTFILE}pre

#160411 filter out utf-8 chars...
if [ $RETSTAT -eq 0 ];then
iconv -c -f utf-8 -t ascii $xDLFILE > ${PKGLISTFILE}pre
rm -f $xDLFILE
fi
<

Today, the script was again failing. But it wasn't obvious that it failed. The Ubuntu "updates" DB files were not getting completely converted to Puppy-format, it was stopping partway through.

I wouldn't have known, except that discovered a DEB that I knew to be in the updates db, wasn't in the build, only the original version.

It took me hours, staring at the screen and wondering what was wrong. Eventually, the penny dropped, the above code also has to be inserted further down, around line 398.
That's where the update database files are being downloaded.

Well, those line numbers are in woofQ, but I just now looked in woof-CE and the line number for insertion will be 272 ...oh, it has become very different from my script, that is the only place that I can see to insert.

Note, the failure occurs at the assignment of "MANIPULATED1".

Woof-CE page:
https://github.com/puppylinux-woof-CE/woof-CE/blob/testing/woof-code/0setup

Note also, another way to do the conversion:
# perl -i.bk -pe 's/[^[:ascii:]]//g;' filename
where filename.bk will become the original file.

Tags: linux