fsck at bootup improved

Comments
Quirky is in one respect very different from Puppy, in that, after bootup, the first script /sbin/init, has the option of continuing to bootup (by executing /bin/busybox init), or switch_root to a ramdisk, where various diagnostic and maintenance operations can be performed. For example, a fsck of the installed partition.

The way this differs from Puppy, is Puppy can do a fsck earlier, in the initramfs. However, a normal full install of Quirky does not have a initramfs.

Testing on the Pi3, /sbin/init failed to switch_root to the ramdisk. It is a strange failure, but I think that I have fixed it. Have put the fix into the script, haven't tested on the Pi yet.
Posted on 13 Jul 2017, 9:38 - Categories: Linux


Fixing Quirky save-session

Comments
Testers of Quirky Xerus64 8.1.6 experienced issues with saving a session in a live-CD or frugal installation.

The good news is that I fixed one show-stopper bug. It was to do with an incorrect path when using overlay instead of aufs.

The bad news is that I have hit another show-stopper bug, that seems to be a fault in overlay filesystem.
I am running kernel 4.11.9, so very recent overlay driver.

Booting the live-CD, have a zram on top, the read-write layer, and q.sfs on the bottom, the read-only layer.
When I tried to run "rm -rf <folder>" it spat out lots of errors about directories "not empty".

I googled, and found people reporting this error when using btrfs, or overlay.
btrfs I expect, it is flakey.

This is one of the overlayfs reports:
https://github.com/moby/moby/issues/9572

OK, I am going to compile the 4.11.9 kernel with aufs, see if that fixes it.
Posted on 11 Jul 2017, 22:44 - Categories: Linux


New theme for Quirky

Comments
As I mentioned in a post yesterday, the last official release of Quirky Xerus x86_64 was in January 2017:
http://barryk.org/news/?viewDetailed=00496

Ubuntu Xenial Xerus 16.04 is LTS (Long Term Supported), reaching EOL (End Of Life) in April 2021.
So, I intend to keep Quirky Xerus going for the next couple of years.

That being the case, we are due for another release. I intend this to be version 8.2, and a beta or RC before that.

Most of yesterday and this morning I worked on a new theme. Mostly created brand new themes for each of GTK, JWM, wallpaper and icons.
And, I have got to comment, it looks stunning.

I would probably have described some of my earlier themes as "stunning" also, such as the various green themes, but they weren't to everyone's liking.
This new one is very different, so we shall see ...I won't post a snapshot, will build the suspense

I will be monitoring this forum thread:
http://murga-linux.com/puppy/viewtopic.php?p=960002#960002
Posted on 10 Jul 2017, 17:22 - Categories: Linux


0setup script fails in Woof

Comments
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.
Posted on 8 Jul 2017, 21:48 - Categories: Linux


Kernel 4.11.9 and firmware

Comments
Kernel
Running Quirky Xerus x86_64 8.1.90 on my midi-tower PC, have compiled Linux kernel 4.11.9. This will be used in the next release of Quirky Xerus -- the official final release is expected to be version 8.2. Note, the current official release is 8.1.6, back in January 2017.

The PETs(31.4M, 1.1M, 145.7M):
http://distro.ibiblio.org/quirky/quirky6/amd64/packages/pet_packages-xerus/linux_kernel-4.11.9-overlay-amd64-xerus.pet
http://distro.ibiblio.org/quirky/quirky6/amd64/packages/pet_packages-xerus/linux_headers-4.11.9.pet
http://distro.ibiblio.org/quirky/quirky6/amd64/packages/pet_packages-xerus/kernel_src-4.11.9-patched.pet

The kernel source and build scripts:
http://barryk.org/sources/kernel-4.11.9/
u*se*rn*am*e: p*up*py p*as*sw*or*d: l*in*ux

Firmware
Have also created firmware PETs for networking and gpu. Note that creation of these PETs is quite easy. In a recent Quirky Linux, look in /usr/local/firmware. There you will find a couple of scripts and instructions.

I am currently getting most of the non-free firmware from here:
http://repo.kali.org/kali/pool/non-free/f/firmware-nonfree/

Firmware PETs (6.2M, 28.1M):
http://distro.ibiblio.org/quirky/quirky6/noarch/packages/pet_packages-noarch/firmware_linux_display-4.11-20170708.pet
http://distro.ibiblio.org/quirky/quirky6/noarch/packages/pet_packages-noarch/firmware_linux_network-4.11-20170708.pet
Posted on 8 Jul 2017, 10:49 - Categories: Linux


Pages: ... [4] [5] [6] [7] [8] [9] ...