If there is an abnormal shutdown, a f.s. check is done automatically at next bootup. Or, it can be explicitly chosen by "qfix=fsck" at the boot prompt.
Quirky creates a ramdisk and populates it with a complete Linux environment and does a "switch root" into it, then unmounts and does a f.s. check of the Quirky partition.
It wasn't working because of the slightly different directory layout, with /lib64 and /usr/lib64.
I fixed script /sbin/init (rootfs-skeleton/sbin/initNEW in woofQ).
I haven't tried a snapshot recovery, but did a f.s. check, it now works.
The f.s.-check fix will be in the next build of April64.
But, it will be a couple of days away, as I am planning a big surprise. I am not quite sure about it yet, but it is looking good, and this may be an extremely interesting April64 indeed.
I need to recompile everything in T2, and I will have to start that running tomorrow evening (it is Sunday evening here right now). I "work" during the day, every Monday.
Then allow at least 24 hours for T2 to do its thing.
So, hopefully I will have something to show by Wednesday!
1 Comment wvdial, the modem dialler cli utility, for which we have a GUI frontend named PupDial, used for ye olde analog modem dialup and 3G modem dialup, crashes in April, both the x86_64 and i686 builds.
This is the error message:
wvdial: utils/wvtask.cc:381: static void WvTaskMan::get_stack(WvTask&, size_t): Assertion `task.magic_number == 0x123678' failed.
The bug, with solution is found here:
I have modified package/develop/wvstreams/wvstreams.conf in T2, compiled and tested in April64, wvdial now works.
Using my Optus 3G USB modem right now.
Interesting comments by one of the original authors of wvdial (scroll down a bit):
1 Comment I have completed an i686 build in T2, the "April series" of Quirky Linux. This is a "bigX" build, with llvm, mesa and the full gamut of xorg drivers.
If anyone is interested, it is here:
I have updated woofQ, the build system for Quirky. Go here for an introduction and download instructions:
...however, I have not yet uploaded the binary packages that were compiled in T2. I had better do that, so anyone who wants to build their own "April" may do so.
Well, it is possible to download T2 and go through the entire process of compiling everything from source, which will generate the binary packages that woofQ can use. Read about T2 here:
Now using the 3.17.8 kernel:
us#er#na#me: pu#pp#y pa#ss#wo#rd: li#nu#x
Don't have any particular forum thread for feedback, if you want to post feedback, use the "April64" thread:
...the i686 and x86_64 Aprils are just about identical. Same packages, same everything.
The only difference that I can think of right now, is that I have wvdial 1.41 in April64, as wvdial 1.6x crashes (yet I think, it has to be confirmed, 1.6x works in i686 April).
Oh yes, there was a report of Hardinfo crashing in April64, OK in i686. That may be fixed (by rolling back to an earlier version), not yet verified.
Note also, I have not entirely up-to-date with reading the feedback in the April64 thread -- there are some suggestions that still need to be investigated.
No comments In April64, File -> Open dialog window for any GTK application, only a generic document icon is displayed for each entry, regardless whether it is a folder, image file, or whatever.
I don't know why that has gone wrong. Anyway, I created some symlinks in /usr/share/icons/hicolor/16x16/mimetypes, all symlinks to /usr/local/lib/X11/mini-icons.
It is necessary to run 'update-mime-database' to recognise these.
These symlinks are now in woofQ, rootfs-skeleton/usr/share/icons/hicolor/16x16/mimetypes/
1 Comment I have done another build of April for a x86_64 CPU. This is a "bigX" build, with 'llvm', 'mesa' and heaps of xorg drivers.
Also included is 'qt' and 'vlc' media player.
See the install instructions at that link.
Pages:      ...