Quirky SlaQ 8.1.6 x86_64 released
sr0 can not be mounted - but you can boot the live-CD
Drive sr0 can not be mounted - but you can boot the live-CD.
CDs and DVDs are not detected by the system as mountable.
DVD drive works fine with Quirky Xerus 8.1.6 .
Used the SlaQ live-CD for testing.
CDs and DVDs are not detected by the system as mountable.
DVD drive works fine with Quirky Xerus 8.1.6 .
Used the SlaQ live-CD for testing.
Re: SlaQ-8.1.6-amd64.iso
Quirky SlaQ 8.1.6 x86_64
- some useless folders :
/usr/bin/lib64/ -- empty
/usr/bin/svn-tools/ -- empty
/usr/etc/ -- empty
/usr/games/ -- empty
/usr/local/share/ -- empty
/usr/lib/modules/ -- empty
- /etc/profile too complex, what is only needed is export PATH= ...
- perl can be moved to devx or is it needed somewhere ?
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.FeodorF wrote:Solution to the problem:
- some useless folders :
/usr/bin/lib64/ -- empty
/usr/bin/svn-tools/ -- empty
/usr/etc/ -- empty
/usr/games/ -- empty
/usr/local/share/ -- empty
/usr/lib/modules/ -- empty
- /etc/profile too complex, what is only needed is export PATH= ...
- perl can be moved to devx or is it needed somewhere ?
Ok, this is to follow-up for those of you that want to 'frugal' install this latest Quirky-Slaq/Xenial and also have the ability to have a savefile recognized during boot. Currently, this latest edition (this goes for QuirkyXenial too) cannot see the savefile you created on the 1st frugal boot, and thus won't load it.
The problem is in the init script, which gets loaded from the initrd.q. This is how you solve it for now, until Barry can take a deeper look at why the latest changes in this 'init' script caused the problem:
1) It does not matter if you are booting into Slaq/Xenial for the 1st time, or if you've already created a savefile and are stumped why it isn't loading on subsequent boots.
2) go into your /mnt (or your desktop shortcut, if it exists) and get to where the vmlinuz and initrd.q are located (they should be un-mounted)
3) Left-click on the initrd.q (it has the black& white puppyface)
4) Up will pop a yellow dialog box. It says:
initrd.q: expand?
Do you want to open up initrd.q, and optionally edit it?
(click yes here)
5) Then a mint green dialog box pops-up. It tells you it opened/epxpanded the initrd.q to: /root/initrd-expanded
Also, it is helpful if you leave open the file manager above that still shows the black&white initrd.q file. We're going to need it in a minute.
(click 'ok' in this mint green dialog box)
6) up pops Rox with the expanded initrd.q. Right-click on the "init" file, and choose "open-as-text"
(we are going to edit this file)
7) once it is open in Geany, scrolldown just barely, near the top, and you will see the following lines (without the # comment outs):
hwclock --hctosys --localtime #160427 from util-linux. assuming hw clock set to local
if grep -qw aufs /proc/filesystems; then
LAYERFS='aufs'
RO='=ro'
else
LAYERFS='overlay'
RO=''
fi
(put a "#" in front of each and every one of these lines, so the init script will ignore them).
Now, go back to that Rox open window (we left it open) I mentioned to keep open above.
9) Left-click on the black&white puppy 'initrd.q' file
10) it will ask you if you want to save your edits to the initrd.q file:
initrd.q: update?
A CPIO-archive........./initrd.q?
(Click "Yes")
11) up will pop another mint-green dialog box saying:
initrd.q: success
File.........initrd-expanded.
(Click "Ok")
12) up pops a yellow dialog box:
initrd.q: finished
Do you want to delete /root/initrd.q-expanded? If in doubt, please choose Yes
(Defintely choose 'Yes' here)
13) That's it!! Close out any remaining Rox windows open, and either go about setting up your Quirky and the 'savefile', or just reboot (assuming you already have a 'savefile') and you will find that upon booting up, Quirky now sees your previously created 'savefile'.
***Please note: this exact same procedure will/should work in QuirkyXenial, as the inits are the same****
P.S. Barry, I just played it safe and had them comment out both the "hwclock" change you made, and also the offending "layer/aufs" section, which seems by itself to be the problem causing both QuirkyXenial and QuirkySlaq to not see any savefile created after first boot. I tested, and once this stuff is commented out, my savefile files (on a frugal install) are now being seen at boot and loading up perfectly.
The problem is in the init script, which gets loaded from the initrd.q. This is how you solve it for now, until Barry can take a deeper look at why the latest changes in this 'init' script caused the problem:
1) It does not matter if you are booting into Slaq/Xenial for the 1st time, or if you've already created a savefile and are stumped why it isn't loading on subsequent boots.
2) go into your /mnt (or your desktop shortcut, if it exists) and get to where the vmlinuz and initrd.q are located (they should be un-mounted)
3) Left-click on the initrd.q (it has the black& white puppyface)
4) Up will pop a yellow dialog box. It says:
initrd.q: expand?
Do you want to open up initrd.q, and optionally edit it?
(click yes here)
5) Then a mint green dialog box pops-up. It tells you it opened/epxpanded the initrd.q to: /root/initrd-expanded
Also, it is helpful if you leave open the file manager above that still shows the black&white initrd.q file. We're going to need it in a minute.
(click 'ok' in this mint green dialog box)
6) up pops Rox with the expanded initrd.q. Right-click on the "init" file, and choose "open-as-text"
(we are going to edit this file)
7) once it is open in Geany, scrolldown just barely, near the top, and you will see the following lines (without the # comment outs):
hwclock --hctosys --localtime #160427 from util-linux. assuming hw clock set to local
if grep -qw aufs /proc/filesystems; then
LAYERFS='aufs'
RO='=ro'
else
LAYERFS='overlay'
RO=''
fi
(put a "#" in front of each and every one of these lines, so the init script will ignore them).
Now, go back to that Rox open window (we left it open) I mentioned to keep open above.
9) Left-click on the black&white puppy 'initrd.q' file
10) it will ask you if you want to save your edits to the initrd.q file:
initrd.q: update?
A CPIO-archive........./initrd.q?
(Click "Yes")
11) up will pop another mint-green dialog box saying:
initrd.q: success
File.........initrd-expanded.
(Click "Ok")
12) up pops a yellow dialog box:
initrd.q: finished
Do you want to delete /root/initrd.q-expanded? If in doubt, please choose Yes
(Defintely choose 'Yes' here)
13) That's it!! Close out any remaining Rox windows open, and either go about setting up your Quirky and the 'savefile', or just reboot (assuming you already have a 'savefile') and you will find that upon booting up, Quirky now sees your previously created 'savefile'.
***Please note: this exact same procedure will/should work in QuirkyXenial, as the inits are the same****
P.S. Barry, I just played it safe and had them comment out both the "hwclock" change you made, and also the offending "layer/aufs" section, which seems by itself to be the problem causing both QuirkyXenial and QuirkySlaq to not see any savefile created after first boot. I tested, and once this stuff is commented out, my savefile files (on a frugal install) are now being seen at boot and loading up perfectly.
Last edited by belham2 on Wed 18 Jan 2017, 16:10, edited 2 times in total.
Re: SlaQ-8.1.6-amd64.iso
linuxcbon wrote:Quirky SlaQ 8.1.6 x86_64
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.FeodorF wrote:Solution to the problem:
- some useless folders :
/usr/bin/lib64/ -- empty
/usr/bin/svn-tools/ -- empty
/usr/etc/ -- empty
/usr/games/ -- empty
/usr/local/share/ -- empty
/usr/lib/modules/ -- empty
- /etc/profile too complex, what is only needed is export PATH= ...
- perl can be moved to devx or is it needed somewhere ?
Hi Linuxcbon (and FeodorF)!
Hey, if you try my solution above (for the 'frugal' install savefile problem), somehow it not only cured the 'savefile' problem, but guess what came back to the quirky traybar? Everything (network, retrovol, storage, Bluetooth) I'm trying to parse what Barry did with the LAYER notations in the "init' script....something isn't making sense with them.....at least not yet Going to have to wait for him to chime in so we can see his thought process behind it.
Also, if you're having problems with Seamonkey, to fix it, try the following:
1) open /usr/bin/seamonkey (the script for 'spot')
2) in the 2nd line you'll see [ -f..........yada yada yada....]
3) In this 2nd line, remove the x86_64_linux-gnu. I'm not even sure how this got in there, as Seamonkey is not even located there. Just make sure that 2nd part of the line looks like this:
... && ln -snf /usr/lib/seamonkey/seamonkey /usr/bin/seamonkey.bin
Check and make sure the link is working too. If not, go back to the /usr/lib seamonkey shortcut, open it, and drag 'seamonkey' back over to /usr/bin and relative symlink it.
After making these changes, any opening and closing of Seamonkey should be ok.
Hope this helps.
1) open /usr/bin/seamonkey (the script for 'spot')
2) in the 2nd line you'll see [ -f..........yada yada yada....]
3) In this 2nd line, remove the x86_64_linux-gnu. I'm not even sure how this got in there, as Seamonkey is not even located there. Just make sure that 2nd part of the line looks like this:
... && ln -snf /usr/lib/seamonkey/seamonkey /usr/bin/seamonkey.bin
Check and make sure the link is working too. If not, go back to the /usr/lib seamonkey shortcut, open it, and drag 'seamonkey' back over to /usr/bin and relative symlink it.
After making these changes, any opening and closing of Seamonkey should be ok.
Hope this helps.
ReRe: SlaQ-8.1.6-amd64.iso
Well, it is not even a manual workaround!linuxcbon wrote:Quirky SlaQ 8.1.6 x86_64
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.FeodorF wrote:Solution to the problem:
It is good for nothing.
linuxcbon, have you ever mounted the q.sfs file of the SlaQ-8.1.6-amd64.iso and looked at /root/.jwmrc?
Well, this jwmrc runs from line 1 through 413.
The add up we see from line 414 through 824 is a duplicate of line 1 through 413.
What's strange about it? The lines 34, 55 and 74 are not duplicated.
Looks like that the layered filesystem is not o.k. or the i-node pointer.
I was able to run the graphics app nathive to run in 64 bit xersus
First install python2 addons
https://drive.google.com/file/d/0B672gI ... sp=sharing
Then download and install the app
http://www.nathive.org/dl/nathive_0.924-1_amd64.deb
Then run in console
---------------------------------------------------------------------------
First install python2 addons
https://drive.google.com/file/d/0B672gI ... sp=sharing
Then download and install the app
http://www.nathive.org/dl/nathive_0.924-1_amd64.deb
Then run in console
Code: Select all
/usr/bin/nathive
nathive in SlaQ and python
I see you mentioned Xerus, but wanted to try it in SlaQ. yet have issues with pygtk. what packages are needed for slaq Have not played with python for a while.don570 wrote:I was able to run the graphics app nathive to run in 64 bit xersus
First install python2 addons
https://drive.google.com/file/d/0B672gI ... sp=sharing
Then download and install the app
http://www.nathive.org/dl/nathive_0.924-1_amd64.deb
Then run in console
---------------------------------------------------------------------------Code: Select all
/usr/bin/nathive
any ideas?
gcav
OUT OF TOPIC
Hi Barry,
for a new cheap laptop, what it should have, in my opinion :
- 4 GB RAM (because 2GB laptops are at around the same price)
- USB 3.0
- Bluethooth 4.1 or 4.0
- card reader : micro SD, micro SDHC, micro SDXC (maybe not important)
- hard disk : eMMC 32GB at least
After some quick search :
- ASUS EeeBook L200HA-FD0093T blue
It doesnt have touch screen.
There is better but more expensive. Let me know what you think.
Cheers, linuxcbon
Hi Barry,
for a new cheap laptop, what it should have, in my opinion :
- 4 GB RAM (because 2GB laptops are at around the same price)
- USB 3.0
- Bluethooth 4.1 or 4.0
- card reader : micro SD, micro SDHC, micro SDXC (maybe not important)
- hard disk : eMMC 32GB at least
After some quick search :
- ASUS EeeBook L200HA-FD0093T blue
It doesnt have touch screen.
There is better but more expensive. Let me know what you think.
Cheers, linuxcbon
Last edited by linuxcbon on Thu 09 Feb 2017, 17:01, edited 1 time in total.
Hi,
I never trust users reviews. One example : last time I bought my smartphone, the company had put many fake good reviews on the internet, so I thought it was good. Fake good reviews are very used by companies marketing crews. They created one time use accounts just to write one fake good review... Now I don't trust any review, except professional reviews from serious tech newspapers.
About that particular laptop :
- it doesn't have touch screen.
- it is sold with windows 10 64 bits.
- Asus has excellent reputation for laptops (Toshiba and Lenovo too).
- it is new so it doesn't have many reviews.
- not sure if compatible with linux ??
Cheers
I never trust users reviews. One example : last time I bought my smartphone, the company had put many fake good reviews on the internet, so I thought it was good. Fake good reviews are very used by companies marketing crews. They created one time use accounts just to write one fake good review... Now I don't trust any review, except professional reviews from serious tech newspapers.
About that particular laptop :
- it doesn't have touch screen.
- it is sold with windows 10 64 bits.
- Asus has excellent reputation for laptops (Toshiba and Lenovo too).
- it is new so it doesn't have many reviews.
- not sure if compatible with linux ??
Cheers
You are right to be cautious. I find Trusted Reviews and Pocket Lint to be as trusting as one can get these days having been written by staffers. However, my caution re. Asus is based on observation and experience over many years. Yes, like Dell, the keys are an issue. I suspect BK is well aware of the other shortcomings. Either way, I never saw any role for laptops of any description, having caused me more grief than any other area of the technology. Always refuse 'gifts' of same - poisoned chalice. Notwithstanding, a company-owned (and repaired) machine sometimes has a position.I never trust users reviews
Making a directory persist in /var/log
I know I have read this around somewhere, but directories do not
persist on reboot for /var/log
Any ideas?
persist on reboot for /var/log
Any ideas?
You can modify the shutdown procedure at shutdown with a script change.
I would suggest copying /var/log to /tmp which is not trashed at shutdown
http://puppylinux.org/wikka/AddCommandsStartupShutdown
____________________________________________________________
I would suggest copying /var/log to /tmp which is not trashed at shutdown
Execute on Shutdown
To execute something on shutdown or reboot, edit-
/etc/rc.d/rc.shutdown
http://puppylinux.org/wikka/AddCommandsStartupShutdown
____________________________________________________________
Not sure if anyone else is seeing this, but the included "remasterpup2' script is failing in all Quirkies (not just Slaq, but also Xenials---it's happened on 2 Xenial 8.0/8.1.6 installs and on 1 Slaq 8.1.6 install). The remasterpup2 script cannot even start as it pops up the weird message as shown here:
http://murga-linux.com/puppy/viewtopic. ... 127#943127
It's weird because the installs are from different downloaded ISOs, all checksum verified. The date and system info is all correct & updated, so why is the script doing this on all Quirky installs?? Does Barry prohibit running remasters from 'frugal' installs (which all the above are)??
Thanks for help/tips/feedback
http://murga-linux.com/puppy/viewtopic. ... 127#943127
It's weird because the installs are from different downloaded ISOs, all checksum verified. The date and system info is all correct & updated, so why is the script doing this on all Quirky installs?? Does Barry prohibit running remasters from 'frugal' installs (which all the above are)??
Thanks for help/tips/feedback