Quirky Xerus 8.6 (Aug. 16), Beaver 8.7.1 (Sept. 21), 2018

[lp-dolittle]

Hi all,

not really sure whether I simply reinvented the wheel or had a useful idea, I would like to mention a so far little or unregarded (?) installation variant that might be of interest to some users.
Thinking of the advantages (security) as well as of the limitations (no simple save option) of live-CD/DVDs, I tried to create a 'live'-flash stick as follows:

1. I dd-ed the xerus64-8.6.iso file onto a flash stick (64 GB)
2. After successfully booting xerus64-8.6 from the stick, I created a new partition and formatted it to ext4, before shutting down for the first time.
2a. as shown by the screenshot below, it seems to be essential that this partition be placed at the end of the drive, leaving space between the fat32- and the new ext4-partition. Remarkably the names of the fat32 and the ext4 partions appear to be inversed
3. at shutdown, when asked for the remaster/save option, I choose 'save' and selected the additionally created ext4 partition which in my case is sdc1 not sdc2!
4. the next boot up resulted in a so far nicely working xerus64-8.6, the flash stick can be removed if nothing needs to be saved.
When the 'live'-flash stick later is used on a different PC, the keyboard layout may need readjustment.

As compared with the full install-, the remaster- and the live-CD/DVD- options, the 'live'-flash stick can be cosidered an intermediate variant, more versatile in some respects, yet equally save as a live-CD if it is used appropriately (removed after boot up; no saving after safety-critical applications). Furthermore, a CD/DVD drive no longer is required.

See partitioning details from the attached screenshot

kind regards

[roadkill13]

pecha wrote:
I couldn't get Chromium to work, says it needs Python3:any. Firefox runs great tho. This Puppy feels more like the original ones. Love PUPPY!!! THANKS!!!!!


Regarding Chromium, I presume that you got it from the Package Manager?

gcmartin posted about that, informed that need to start it in a terminal:

Code:
# chromium --no-sandbox


...you can probably find some posts about this on the forum. I haven't tested it.

I installed Chromium from the package manager. It runs fine as user SPOT.

[BarryK]

Hi all,

not really sure whether I simply reinvented the wheel or had a useful idea, I would like to mention a so far little or unregarded (?) installation variant that might be of interest for some users.
Thinking of the advantages (security) as well as of the limitations (no simple save option) of live-CD/DVDs, I tried to create a 'live'-flash stick as follows:

1. I dd-ed the xerus64-8.6.iso file onto a flash stick (64 GB)
2. After successfully booting xerus64-8.6 from the stick, I created a new partition and formatted it to ext4, before shutting down for the first time.
2a. as shown by the screenshot below, it seems to be essential that this partition be placed at the end of the drive, leaving space between the fat32- and the new ext4-partition. Remarkably the names of the fat32 and the ext4 partions appear to be inversed
3. at shutdown, when asked for the remaster/save option, I choose 'save' and selected the additionally created ext4 partition which in my case is sdc1 not sdc2!
4. the next boot up resulted in a so far nicely working xerus64-8.6, the flash stick can be removed if nothing needs to be saved.
When the 'live'-flash stick later is used on a different PC, the keyboard layout may need readjustment.

As compared with the full install-, the remaster- and the live-CD/DVD- options, the 'live'-flash stick can be cosidered an intermediate variant, more versatile in some respects, yet equally save as a live-CD if it is used appropriately (removed after boot up; no saving after safety-critical applications). Furthermore, a CD/DVD drive no longer is required.

See partitioning details from the attached screenshot

kind regards

Congratulations on your initiative!

Yes, that is a way that you can do it. And yes, has some advantages, such as remove-after-bootup, and optional saving.

Also, you can wind back to a pristine system just by deleting the contents of that partition.

[Reneetje]

I prefer a single burned live-cd above usb/live stick, because a single burned live-cd can't and will never be infected.
About usb, because it's a bootable usb, it's possible the MBR can be infected.

[lp-dolittle]

Hi Reneetje,

if striving for the utmost security is the main goal, you are right, a live-CD (and no hard disk present) admittedly is first-choice.

In most other respects, the versatility of a live-flash stick offers interesting options. As compared with a flash stick full installation, the live-flash stick variant, not least, also may increase the stick's durability because read/write-operations only occur at boot up and while saving.

The availability of RAM - depending on the currently used PC's hardware configuration - certainly is a limiting factor which may variably affect a live-flash stick's functionality.

kind regards

[Sage]

Ah-ha:

you are right, a live-CD (and no hard disk present) admittedly is first-choice.

that may give a hint, lp, as to what's wrong, presuming it's not intentional, with the .iso version of 6.5 that's giving me this problem? The code may not have been altered from the version .img intended for USB/SD-card which does expect to write material at first boot-up. I'm certainly no coder- far from it - but I've observed the way stick/card .img versions manipulate something? at first boot and write it to the media - clearly intentional. So, the .iso from CD-RW is also trying to do this and can corrupt its own CD if it be an RW and possibly any HD already present (! must check to see if HD is corrupted, too). Needs the bossman or another savvy guy to check this and put me right.

[Billtoo]

I installed to a 64gb flash drive with easydd:

System: Host: QUIRKYPC18789 Kernel: 4.14.63 x86_64 (64 bit) Desktop: JWM git-976
Distro: Quirky 8.6 xerus64
Machine: System: Hewlett-Packard product: HPE-410f serial: MXX0370KF3
Mobo: FOXCONN model: 2AB1 v: 1.00 Bios: American Megatrends v: 6.02 date: 07/21/2010
CPU: Hexa core AMD Phenom II X6 1045T (-MCP-) speed/max: 949/2700 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570]
Display Server: X.org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
tty size: 106x29 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 1126.3GB (1.2% used)
Weather: Conditions: 64 F (18 C) - Partly Cloudy Time: August 20, 8:53 AM EDT
Info: Processes: 140 Uptime: 30 min Memory: 163.0/7986.8MB Client: Shell (bash) inxi: 2.2.35

Added a few small applications with petget,also added some kdegames.

Works okay sp far.
Thanks.

[Flash]

I downloaded the Xerus64.8.6 iso and burned it to a DVD. So far, it booted in my older desktop and in my brand new Dell Inspiron 15 (5570) laptop without having to use any boot codes in either one. I'm not sure it was necessary but I fiddled around with UEFI and Secure Boot settings in the laptop's BIOS before trying to boot the Xerus DVD. I probably have the whole thing horribly misconfigured now, but it works.

I was pleasantly astonished to discover that the laptop's touch screen worked right out of the box. In fact, no configuring was needed for most of the hardware. I had to go to my desktop computer and google how to right-click using the laptop's touch pad (press the lower right corner). The only real problem in the laptop so far is that the screen won't shut off when the lid is closed, nor does the screen saver ever shut the screen off, even though it appears to be set to do so after 10 minutes. The screen saver works in my desktop computer.

I bought this particular laptop because it was the only one in the store with a DVD burner. When I tried remastering Xerus, the program didn't complain about anything and in fact claimed that it burned a DVD, but it didn't. The same thing happened in my desktop computer, so I don't think the failure is due to a quirk in the laptop.

[lp-dolittle]

@ Sage

maybe, the attached screenshots which were taken after dd-ing the xerus64-8.6.iso onto a flash stick are of interest to you.

In fact, the dd-command has some remarkable effects:

1: As shown in the first screenshot, seemingly, 1 fat32 partition (here called sdc2) is created, while the rest of the drive's space - according to gparted - is unallocated. However, the desktop also shows a tray-icon (sdc1) for this space.
2: on second sight (screenshot 2), both tray-icons respond to the mount-command, and sdc1 proves not to be empty!
3. for what reason are the partition designations inversed?

In retrospect, no wonder that my live-flash stick configuration only works if some space is left between the (UEFI-aware) fat32 partition and the later created ext4 (save)-partition (sdc1).

I'm aware that these observations, despite partially confirming your assumptions, cannot really explain your live-CD problem.

kind regards

[Flash]

An update to my last post: the screensaver started working (the screen shuts off after ten minutes) after I opened Menu -> Desktop -> ScreenSaver Control, clicked Disable then Enable several times, then Exit.

I think I noticed this before in my desktop. Sorry I forgot to mention it until now.

[Billtoo]

I installed to a 32gb flash drive with easydd.

System: Host: QUIRKYPC28147 Kernel: 4.14.63 x86_64 (64 bit) Desktop: JWM git-976 Distro: Quirky 8.6 xerus64
Machine: System: HP-Pavilion product: GN559AA-ABA a6220n serial: MXF7470DNX
Mobo: ASUSTeK model: Berkeley v: 1.04 serial: X312345678
Bios: American Megatrends v: 5.13 date: 10/24/2007
CPU: Dual core Intel Core2 Duo E4500 (-MCP-) speed/max: 1200/2200 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM]
Display Server: X.org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
tty size: 117x26 Advanced Data: N/A for root
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 431.6GB (1.0% used)
Weather: Conditions: 72 F (22 C) - Overcast Time: August 21, 12:36 AM EDT
Info: Processes: 100 Uptime: 1:16 Memory: 188.2/3953.1MB Client: Shell (bash) inxi: 2.2.35

I must have forgotten to tick on the fill drive option before I
rebooted, have since run gparted and made the sdb3 part of the drive
ext4.

Working well on this 11 year old pc (has a newer graphics card) apart from that.

Thanks.

[Sage]

Thanks for your comments, lp.
I never use the CLI dd command - too much to go wrong in my experience and a waste of time when USB Image Writer is available on my systems and has proved rock solid. However, I rarely use USB nor SD cards on my desktop boxes and rarely ever use laptops unless repairing for very close friends and family - they are nothing but trouble, overpriced, unreliable and recent ones don't even have a DVD drive (I have an external drive for diagnosis and repairs, though). Even newer ones use SSSD, which are overpriced, of unknown lifetime and reliability (too new to know yet) and have, for me, unacceptable limitations (early versions may not have TRIM, for example).
And now for the bad news.Yes, using the .iso of 6.5 on DVD-RW has not only corrupted the DVD but also the GRUB sector of an installed hard disc with a different distro installed. Much as I like to work from .iso on rewritable discs, BEWARE, this version of Q-X may be toxic on some systems, perhaps depending on HW and/or present installations.
As I suggested (from raw ignorance) something may have slipped into the boot code of the .iso spilling over from other media boot procedures, but as this is outside my range of expertise, I defer to those with inside knowledge. My expertise is mostly limited to HW - I fix stuff!

[foxpup]

@Barry

I installed Quirky 8.6 on hd (ssd) frugally, puppy style.
It installed very well, found wifi right away with sns and runs smoothly.
It has plenty of apps I still have to explore.
Very nice build!

The main reason I installed Quirky is EasyShare. I want to connect it to my android tablet.
I followed the instructions and it finds the tablet but when I push the Mount button it says

Directory '/mnt/phone/sdcard' not found.

and nothing happens.
But since the tablet is strictly speaking not a phone it does not have /mnt/phone/sdcard but /mnt/sdcard.
Can you fix that?

[don570]

Directory '/mnt/phone/sdcard' not found.

Did you try creating a folder /mnt/phone/sdcard/
then running easyshare again.

Perhaps Barry forgot to put line in script creating this folder
before the mount instruction??
__________________________________________________

[BarryK]

@Barry

I installed Quirky 8.6 on hd (ssd) frugally, puppy style.
It installed very well, found wifi right away with sns and runs smoothly.
It has plenty of apps I still have to explore.
Very nice build!

The main reason I installed Quirky is EasyShare. I want to connect it to my android tablet.
I followed the instructions and it finds the tablet but when I push the Mount button it says

Directory '/mnt/phone/sdcard' not found.

and nothing happens.
But since the tablet is strictly speaking not a phone it does not have /mnt/phone/sdcard but /mnt/sdcard.
Can you fix that?

Interesting. My phone has '/sdcard', a symlink. /mnt/phone is a directory created in EasyOS/Quirky, and '/' of the phone f.s. gets mounted there.

So /mnt/phone/sdcard is where your files are.

I have a tablet, will check on that.

One possibility, would be to remove "sdcard" from the script.

Try the attached. gunzip it, make sure it is executable, and place at /usr/local/EasyShare

Another thing, run "easyshare" in a terminal, so you can see any error messages.

[slackfan]

somewhat equivalent available for Quirky Xerus 8.6 ?

https://www.howtogeek.com/196933/how-to ... ard-drive/

[BarryK]

@Barry

I installed Quirky 8.6 on hd (ssd) frugally, puppy style.
It installed very well, found wifi right away with sns and runs smoothly.
It has plenty of apps I still have to explore.
Very nice build!

The main reason I installed Quirky is EasyShare. I want to connect it to my android tablet.
I followed the instructions and it finds the tablet but when I push the Mount button it says

Directory '/mnt/phone/sdcard' not found.

and nothing happens.
But since the tablet is strictly speaking not a phone it does not have /mnt/phone/sdcard but /mnt/sdcard.
Can you fix that?

Interesting. My phone has '/sdcard', a symlink. /mnt/phone is a directory created in EasyOS/Quirky, and '/' of the phone f.s. gets mounted there.

So /mnt/phone/sdcard is where your files are.

I have a tablet, will check on that.

One possibility, would be to remove "sdcard" from the script.

Try the attached. gunzip it, make sure it is executable, and place at /usr/local/EasyShare

Another thing, run "easyshare" in a terminal, so you can see any error messages.

Ha ha

I have just received an email, telling me what is wrong.

Nowhere does /usr/local/EasyShare/easyshare script create folder /mnt/phone

In my test system, I created it manually. So, do that also, then easyhare android phone should work.

[foxpup]

/mnt/phone is a directory created in EasyOS/Quirky, and '/' of the phone f.s. gets mounted there.
....
Ha ha

I have just received an email, telling me what is wrong.

Nowhere does /usr/local/EasyShare/easyshare script create folder /mnt/phone

In my test system, I created it manually. So, do that also, then easyhare android phone should work.

Haha indeed.
I was looking on the tablet for /mnt/phone/sdcard or sdcard since I did not see anything like that on my connecting laptop. lol

I created /mnt/phone in Quirky on the laptop. Connection to the android tablet works very well now.

Speaking of phones, I see there is no puppyphone (psip) in Quirky.
I looked at pidgin, but I don't think it can work as a sip softphone. Something I overlook?

[BarryK]

/mnt/phone is a directory created in EasyOS/Quirky, and '/' of the phone f.s. gets mounted there.
....
Ha ha

I have just received an email, telling me what is wrong.

Nowhere does /usr/local/EasyShare/easyshare script create folder /mnt/phone

In my test system, I created it manually. So, do that also, then easyhare android phone should work.

Haha indeed.
I was looking on the tablet for /mnt/phone/sdcard or sdcard since I did not see anything like that on my connecting laptop. lol

I created /mnt/phone in Quirky on the laptop. Connection to the android tablet works very well now.

Speaking of phones, I see there is no puppyphone (psip) in Quirky.
I looked at pidgin, but I don't think it can work as a sip softphone. Something I overlook?

I took out the puppyphone years ago, no one complained, so I thought no one was using it.

[foxpup]

I took out the puppyphone years ago, no one complained, so I thought no one was using it.

I use it to phone between laptop at home and android tablet on the road. On the tablet I have csipsimple.
I have no smartphone.

I wondered whether it would be possible to use/compile puppyphone in other distros or even for android.

I like the simplicity of puppyphone and it works very well.

There is also an article from Smokey in the latest newsletter (august 2018) about 'Psip P2P & VPN' with n2n.
It's another interesting way to use sip calling. Maybe the article will attract some people to sip/psip again.