Quirky Werewolf 64-bit 7.4 released

[BarryK]

OK, I see your process a little more clearly.

The save process REQUIRES that the CD is burned, initially, such that it is NOT closed. This must be done so that it can be reburned for a save session. Thus it MUST be a RW disc and NOT an +R/-R. Your process will rewrite the CD/DVD disc and also write a session file to local disk; namely HDD/USB/etc.

Therefore, the 2 items are a marriage required for Live CD/DVD use with save sessions.

This also means that if I want to use Live on another PC, it is best to create its own, separate Live disc media for boot and save-session use.

Is that correct?

No, that is not correct.

Look at the snapshot posted by mavrothal.

If you choose to save the session to hard drive, a once-only remaster of the CD is required. Look at the snapshot, it unambiguously states "once only", and "please insert a blank CD or DVD".
So you do not use a -RW, you burn a new CD, with the save-file location hard coded into it.

It was a design decision I made for the original CD not to probe the hard drive.
Of course, I could go the Puppy-route and put some drive-probing into it -- which I might do if it turns out that nobody likes this idea of having to burn another CD.

So, yes, the second CD is hard coded for a specific partition, filesystem and folder (with optional path), so won't work on another PC unless you set it up with that same partition/filesystem/folder.

[BarryK]

You haven't looked at the 'init' script.

If the q.sfs is saved alongside s.sfs, it is removed from the CD.

The install instructions are unambiguous, as per the snapshot you posted above.
The CD has to get remastered as part of the process.

Maybe so but before I look again please let us know
a) if it is possible to boot from the original CD (_not_ a remaster) and have a save folder with _only_ the s.sfs on a partition? EDIT: It would appear "no"
b) if the above _is_ possible what the boot line arguments would be to use the said save folder (provided there is no /BOOT_SPECS file)? EDIT: Is possible. See below.
Thx

Latter OK

Code: Select all

quirky boot_specs=sda1:ext4:werewolf64-7.3

(or what ever partition:filesystem:folder is) works.
Kind like fatdog.

Bit later It would appear that the q.sfs _must_ be copied to hard disk too. Although the save dialog provides the option not to copy it to the HD, this results in a kernel panic on next boot with the above arguments.
This is because the init defaults in loading q.sfs from $QPATH if QPATH exits.
Maybe split QPATH to QPATH and SPATH to allow loading from different devices/partitions.

Yes, you are right!

Booting the live-CD, then saving a session, which requires burning another CD, might seem a hassle, but apart from hard-coding the save-file location, it does one more thing, move the q.sfs out of the CD to the hard drive.

Frugal install does the same thing.

This results in very fast booting, as q.sfs was previously inside the initrd so had to get loaded at bootup.

Note, the reason I put q.sfs inside the initrd was to avoid any drive probing at bootup. This makes the init script very "situation agnostic", for net boots or whatever.

[BarryK]

- why are perl and python not in devx ?
- why is there /usr/local/install_quirky/ when there is a standalone version ?

This quirky is quite nice at the moment, except for seamonkey crashes.

There is only perl_tiny, the full perl is in the devx. I want to keep perl_tiny for now.

Yes, sometime ago I decided to put python into the main f.s.
I need to rethink this, should probably put it out to the devx.

/usr/local/install_quirky has /usr/sbin/installquirky, which runs it.

The standalone version is an alternative, that can be created to use anywhere, in another distro.

Running in Quirky, the standalone version is not needed, it is builtin, in the menu.

[BarryK]

This quirky is quite nice at the moment, except for seamonkey crashes.

I am running SM 2.39 now, so far so good!

[DanielSong39]

Can this version of Quirky Werewolf run 32-bit applications?

If so - time to give it a spin.

[BarryK]

Can this version of Quirky Werewolf run 32-bit applications?

If so - time to give it a spin.

Not Out Of The Box.

You would have to use the Package Manager to install the Ubuntu 32-bit libs.

I haven't tried it, I don't know which packages are required.

[Rodney Byne]

Well done Barry.
For me QW-7.3 on USB made from DVD is a nice stable release
and for what it's worth SM 2.38 is rock solid so far.

Only two questions, will 7.3.1 be available via the
Version Upgrade Manager and will all my SM 2.38
bookmarks & settings be transferred across to SM 2.39,
as would happen in Firefox?

Thanks, best regards.

[partsman]

Very nice Barry !

I did a full install to an 8gig flash drive
A couple of things:

1. cpu freq. scaling from the menu doesn't work

2. When installing from ppm when there are a lot of depends. the window is to large and can't click on the radio buttons !

I didn't get a lot of time with it yet but I did notice those 2 things !
Other than that I did install supertuxkart from ppm ! All good !
Looking nice ! Thanks !

More Later !

[gcmartin]

Thanks @BarryK. Your post here, emphasizes exactly what I shared in how the process works, physically.

And, in the subsequent post, I see why you are making a new CD to match the changes that are being made locally on local, albeit faster, peripheral. As such it could allow a faster boot as the boot system data is coming from 2 buffers directions.

I took a look at the size of the 2 boot system needs and dont see a major change in actual data size, per se.

I have one simple idea: I say :"simple" as it comes from me.
Why not pre-plan the boot manager with a save session concept where the original CD is packaged with its pre-planned design and has a boot option to use that pre-designed layout.

This would meet both your objective and minimize the complexity that currently exist while potentially cutting down on DVD disc media needs.

Here's why. @Stemsee, early on this year, showed the community how to have a boot manager that gives users the option of what they want to boot. In his design, he allows the user to select "boot this version" or "boot that version". In his case, he allows the user to select to boot the 64bit version or the 32bit version. In concept, this exactly matches what you intend: Just here, its boot Pristine or boot using the pre-designed save session.

If you are willing to consider his design, this could easily match your objective where the user selects to boots pristine OR the user boots with a pre-designed save-session where the local media probe occurs by the boot manager. The save-session name, then, is static in the pre-design.

Thus, take away the folder name selection altogether and only allow user to select the partition placement.

Complexity is reduced and only one DVD which remains matching local save needs via boot option 2 and portable (pristine) needs via boot option 1.

Of course, your present save app doesn't change much by merely removing the option from the screen as the work in done at the time of boot by user selection.

Further, the user, by this boot option has a way to get back into his system, pristine, should he need/choose.

It again, is a "simple" idea for consideration as you ponder how best to meet the objective you intend for your users to understand in use.

I see one flaw in my "simple" view where the probing for the folder would eat time, especially if it was the very last partition that exist in the local storage system. (I have seen some users, like me, sometimes on PCs that have many many partitions, across differing drives/devices. But everyone is not like me and this might be perfect for their needs.). This, of course, is a problem today's distro with boot probing for a save-session. for example, on some of my occasions I have told GRUB4DOS to "find" a root partition based upon some folder name.

Boot time Probing via a Boot Manager for a folder on storage, in my view, is not bad, but may not match with the views of others. Some may feel that looking for something specific, as the boot manager does, somehow violates them.

[don570]

I hope the new kernel will solve my problems with i915 driver.
Here is summary of changes....

According to the diff from Linux kernel 4.2.5, the new maintenance release is here to add various improvements to the ARM, ARM64, PowerPC (PPC), and x86 hardware architectures. Moreover, it fixes several issues in the Btrfs and OverlayFS filesystems, repairs a couple of networking problems, mostly related to mac80211 and Netfilter, as well as to adds a few mm and sound enhancements.

"I'm announcing the release of the 4.2.6 kernel. All users of the 4.2 kernel series must upgrade," says Greg Kroah-Hartman. "The updated 4.2.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.2.y and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/g ... ;a=summary.
Drivers, lots of updated drivers

Besides the changes mentioned above, Linux kernel 4.2.6 updates numerous drivers, especially for things like GPU (AMD, Intel i915, Nouveau, Radeon, and vmwgfx), BUS, CLK, CPUFreq, EDAC, I2C, iiO, InfiniBand, IOMMU, IRQ chip, MD-RAID, DVB, MMC, networking (mostly Wireless), PCI, PINCTRL, SCSI, thermal, TTY, USB, and video.

[don570]

Review of werewolf64 7.3 installed on USB stick

- I found I had to to blacklist i915 driver to achieve VESA 1280x1080 resolution

- installquirky.x86 ---> if a folder is chosen rather than a file
then a strange warning is given

- pschedule is still not working correctly on my machine
because of confusion of local and GMT time

- fsck now works when booting

Code: Select all

quirky qfix=fsck

Around seven errors found ???

________________________________________

[BarryK]

Well done Barry.
For me QW-7.3 on USB made from DVD is a nice stable release
and for what it's worth SM 2.38 is rock solid so far.

Only two questions, will 7.3.1 be available via the
Version Upgrade Manager and will all my SM 2.38
bookmarks & settings be transferred across to SM 2.39,
as would happen in Firefox?

Thanks, best regards.

Yes, I am hoping that a Service Pack will be available, used by the Version Upgrade Manager, and SM bookmarks etc should transfer.

[BarryK]

Very nice Barry !

I did a full install to an 8gig flash drive
A couple of things:

1. cpu freq. scaling from the menu doesn't work

2. When installing from ppm when there are a lot of depends. the window is to large and can't click on the radio buttons !

I didn't get a lot of time with it yet but I did notice those 2 things !
Other than that I did install supertuxkart from ppm ! All good !
Looking nice ! Thanks !

More Later !

Anyone know about frequency scaling, can check that out?

Regarding PPM, yes, I increased the allowed number of dependencies, as some apps have so many, even hundreds.

But then, ran into a window-size problem.

With all puppies and quirkies, just hold down the Alt key and drag, to move a window around.

[gcmartin]

BarryK, I know you have mentioned a new kernel for your upcoming 7.3.1 based upon a message you received.

As you progress, have you seen this 2-week old announcement from Tovalds?

[partsman]

With all puppies and quirkies, just hold down the Alt key and drag, to move a window around.

Yes remembered that after I posted !

Anyone know about frequency scaling, can check that out?

Well It does work ok is started from /usr/sbin/wcpufreq

Looking Good !
Thanks Barry !
Having some fun !

[Puppus Dogfellow]

sha1
1dd84fd65ba9aefa915d3db9237d3f04e3edbe01 installquirky.amd64
71b94273b4cd675f977adf5f1e93142cf62946bd werewolf64-7.3-8gb.img.xz
9d699a5f0f9762c4a0816976fb26ba34b7403abd werewolf64-7.3.iso
a11bfac31a2f0ec92ce0bf38e76b3d442509dfbc werewolf64-7.3.usfs.xz

md5
ec307470df9bd027e3a7a02c9de43591 installquirky.amd64
5a2515180f3899868daddf0cc39d04cd werewolf64-7.3-8gb.img.xz
93b9292b21fbb6d96f298e80ec994d32 werewolf64-7.3.iso
c5a0b3aa6f16fb7b5fcf7d813453e86e werewolf64-7.3.usfs.xz


Quirky Werewolf 7.3

[James C]

Full install from the live cd.Looking good.

Code: Select all

# report-video
VIDEO REPORT: Quirky Werewolf64, version 7.3

Chip description:
VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

Requested by /etc/X11/xorg.conf:
  Resolution (widthxheight, in pixels): 1024x768x16
  Depth (bits, or planes):              24
  Modules requested to be loaded:       dbe 

Probing Xorg startup log file (/var/log/Xorg.0.log):
  Driver loaded (and currently in use): nouveau
  Loaded modules: dbe dri2 exa extmod fb glx kbd mouse shadowfb

Actual rendering on monitor:
  Resolution:  1440x900 pixels (381x238 millimeters)
  Depth:       24 planes

...the above also recorded in /tmp/report-video

Code: Select all

# inxi -Fff
System:    Host: puppypc9821 Kernel: 4.2.5 x86_64 (64 bit)
           Desktop: JWM git-976 Distro: Quirky 7.3 werewolf64
Machine:   Mobo: ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx serial: 150545593600028
           Bios: American Megatrends v: 2601 date: 03/24/2015
CPU:       Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB 
           clock speeds: max: 3500 MHz 1: 2000 MHz 2: 1400 MHz 3: 1400 MHz
           4: 3000 MHz 5: 1400 MHz 6: 1400 MHz
           CPU Flags: 3dnowprefetch abm aes aperfmperf apic arat avx bmi1
           clflush cmov cmp_legacy constant_tsc cpb cr8_legacy cx16 cx8 de
           decodeassists extapic extd_apicid f16c flushbyasid fma fma4 fpu
           fxsr fxsr_opt ht hw_pstate ibs lahf_lm lbrv lm lwp mca mce
           misalignsse mmx mmxext monitor msr mtrr nodeid_msr nonstop_tsc nopl
           npt nrip_save nx osvw pae pat pausefilter pclmulqdq pdpe1gb
           perfctr_core perfctr_nb pfthreshold pge pni popcnt pse pse36 rdtscp
           rep_good sep skinit sse sse2 sse4_1 sse4_2 sse4a ssse3 svm svm_lock
           syscall tbm tce topoext tsc tsc_scale vmcb_clean vme vmmcall wdt
           xop xsave
Graphics:  Card: NVIDIA GT218 [GeForce 210]
           Display Server: X.org 1.17.2 drivers: nouveau (unloaded: vesa)
           tty size: 80x25 Advanced Data: N/A for root
Audio:     Card-1 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.2.5
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169
           IF: eth0 state: up speed: 100 Mbps duplex: full
           mac: 1c:87:2c:5a:bb:e2
Drives:    HDD Total Size: 1120.2GB (0.8% used)
           ID-1: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB
           ID-2: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 34G used: 1.1G (4%) fs: ext4 dev: /dev/sdb9
           ID-2: swap-1 size: 8.60GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 120 Uptime: 4 min Memory: 202.5/7896.9MB
           Client: Shell (bash) inxi: 2.2.16 

Code: Select all

# free
             total         used         free       shared      buffers
Mem:       8086400       442000      7644400         6408        15044
-/+ buffers:             426956      7659444
Swap:      8396796            0      8396796

[linuxcbon]

Quirky Werewolf 64-bit 7.3
- /usr/include/ is not empty (belongs to devx)
- my opinion : /root is better than /file
- /lib/systemd/ ?
- gshadow missing line with audio

[BarryK]

Review of werewolf64 7.3 installed on USB stick

- I found I had to to blacklist i915 driver to achieve VESA 1280x1080 resolution

- installquirky.x86 ---> if a folder is chosen rather than a file
then a strange warning is given

- pschedule is still not working correctly on my machine
because of confusion of local and GMT time

- fsck now works when booting

Code: Select all

quirky qfix=fsck

Around seven errors found ???

________________________________________

I do have zigbert's latest version, 1.1.6, in fact I have 1.1.6-1 as I did fix something.

You need to take this up with zigbert:
http://murga-linux.com/puppy/viewtopic.php?t=22166

[BarryK]

- /usr/include/ is not empty (belongs to devx)

Thanks, fixed.