TahrPup 5.8.4

[shinobar]

Fixed sfs_load.
ydrv against tahrpup 5.8.3.rc1 includes fixed sfs_load and puppyinstaller.
Place ydrv_tahr_5.8.3.rc1.sfs at the same place where the tahrpup 5.8.3.rc1 is installed.
http://shino.pos.to/party/bridge.cgi?pu ... .3.rc1.sfs

[gyro]

Fixed sfs_load.

Yes, with the ydrv in place, pupmode=5 boot works as expected. Once it's up, none of the disk partitions are mounted.
Thanks shinobar.

gyro

[gyro]

Odd...any puppy I run on a bootable usb formatted as FAT will write the save file to the fat partition with no problem.

Yes, that's the big plus for a savefile. It can be stored on any file system because it's just a file. But the content of that file is a Linux file system, and it is the root directory of that internal Linux file system that Puppy uses as it's save space.

gyro

[gcmartin]

Hi @TLChost.

I might add for some additional clarity: In the past, prior to Spring-Summer 2014, the SaveSession subsystem ONLY offered to create a file to store your work into. (DVD/CD do NOT save sessions on the DVD/CD by creating a file).

Since much work by community members this year, the ability to keep your session's work in a folder has been added. This has some obvious positive benefits should one choose to save work in a folder than to have the system create a file, first, then save your work into the file.

Hope this makes clear the new option added to new PUPs like this PUP.

[tlchost]

Hope this makes clear the new option added to new PUPs like this PUP.

How puppy worked in versions prior to this generation relative to save files was never unclear....I've been using muiltiple puppies on FAT formatted USB drives for several years.

Your response really added nothing to the discussion of if/why the save to file mode does not work when the usb drive is formatted in FAT.

It seems the save to file mode will not work for me, since my usb drive is used both for Windows and Puppy.

Thom

[shinobar]

It seems the save to file mode will not work for me, since my usb drive is used both for Windows and Puppy.

TahrPup 5.8.3.rc1 saves session to a file as for FAT partitions.
You mean you failed to save the session?

[mavrothal]

tlchost
you originally said

Apparently tahr does not allow save to folder if it's used on a bootable usb drive formatted as FAT

(color is mine).
All the responses try to explain why save to folder will not work on a FAT partition. Save to file should work fine. Doesn't it?

[tlchost]

tlchost
you originally said

Apparently tahr does not allow save to folder if it's used on a bootable usb drive formatted as FAT

(color is mine).
All the responses try to explain why save to folder will not work on a FAT partition. Save to file should work fine. Doesn't it?

Hard to believe.....i said it does NOT save to a folder. People have explained it will not do so when the drive is formatted as FAT. I think we can stop beating the dead horse at this point.

[mavrothal]

Hard to believe.....i said it does NOT save to a folder. People have explained it will not do so when the drive is formatted as FAT.

Yeh... but 3 posts above you said

It seems the save to file mode will not work for me, since my usb...

...

[peebee]

AZpainter program now the Tahr.5.8.3.rc1 default!!!!

First off, it would NOT load several important graphics I had designed with mtpaint, no matter the extension!!! ..... AZpainter may well be better than mtpaint in the long-haul but let the users ease into it and decide for themselves!

>>>---Indian------>

Tahr Pup 5.8.3-rc1

azpainter will not open png files for me....no errors given if run from terminal....

Cheers
peebee

[wjaguar]

azpainter will not open png files for me....no errors given if run from terminal....

Because it parses PNGs entirely by itself. Without the "indignity" of linking to libpng.
Or more precisely, it parses a smallish subset of possible valid PNGs. The weirdest case of NIH syndrome that I ever seen.

As for error reporting, on my system, it does show a "Failed to load" popup.

[wyzguy]

I added 2 lines to /root/.Xresources using geany.

URxvt.background: black
URxvt.foreground: white

Then ran: xrdb -query -all and verified the changed lines were there.

I rebooted and reverified using the line above. The changed were there.

When I clicked on the URxvt terminal icon, nothing changed.
The background was still a pale blue.

The process seems broken someplace.

I also tried URxvt.background: #000000 and URxvt.foreground #999999.
The colors I picked are not important, the process is.

Oh, this was on 5.8.3.rc1. (not tested on any other one).

[mavrothal]

I added 2 lines to /root/.Xresources using geany.

URxvt.background: black
URxvt.foreground: white

Edit the
urxvt.foreground:
urxvt.background:
lines in /root/.Xdefaults

[B.K. Johnson]

A possible bug
On 2 occasions, I had installed seamonkey from quickpet and when I installed firefox later, seamonkey was removed. I posted about it here http://www.murga-linux.com/puppy/viewto ... 608#797608
but it wasn't a bug of any interest.

Today, I wanted to set up a direct call to Composer as I have done in some other pups before. Why? It avoids me opening the seamonkey browser when I need only the editor. In my search for icons, desktop files etc, I did not find a seamonkey.desktop file but found firefox.desktop although firefox was not installed. Could it be that the desktop file for firefox has the same name and clobbers seamonkey when installed? Will I be able to install firefox if I create a seamonkey.desktop?

B.K. Johnson

[peebee]

For a version of LxPup (Puppy + LXDE) based on TahrPup 5.8.3.rc1 (with thanks to 666philb) see:

http://lx-pup.weebly.com/upup-tahr.html

and http://www.murga-linux.com/puppy/viewto ... 464#798464

Cheers
peebee

[666philb]

I can not reproduce the issue so is hard to figure out .
/usr/local/bin/drive_all is a place to start looking for possible hints.

Is it also true in slacko 6 beta? What about older puppies (precise, slacko 5.7).
If only in newer maybe related to the changes introduced to accommodate save folder. If in Tahr but not slacko-6 maybe is some quircky package that does it.
But again without being able to reproduce it...
BTW which phone is it? (model/OS version) Any special PC communication app on the phone?

hi mavrothal,

i've managed to reproduce the bug, once with a samsung camera and once with a sony android phone. after unmounting and removing the device all drive icons disappear and won't come back until you reboot. same thing occurs if i use slackos drive_all script.
this is the output of xerrs.log after it's happened

Code: Select all

/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: 

same thing happens if i use slackos 'frontend_funcs'

Code: Select all

/usr/local/pup_event/frontend_funcs: line 422: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory

EDIT: same thing happens in slacko beta 5.9.3

[666philb]

@666philb

The kernel in tahr-5.8.3.rc1 is 3.14.11 (same as original).
In order for me to swap in a 3.15.4 kernel into tahr-5.8.3.rc1, won't you need to build a 5.8.3.rc1 with k3.15.4 and make it available in your Dropbox as you did with 5.8.3? Or is there another way?

B.K. Johnson

hi B.K. Johnson,

i've re-uploaded the kernels for use with rc1

A possible bug
On 2 occasions, I had installed seamonkey from quickpet and when I installed firefox later, seamonkey was removed. I posted about it here http://www.murga-linux.com/puppy/viewto ... 608#797608
but it wasn't a bug of any interest.

Today, I wanted to set up a direct call to Composer as I have done in some other pups before. Why? It avoids me opening the seamonkey browser when I need only the editor. In my search for icons, desktop files etc, I did not find a seamonkey.desktop file but found firefox.desktop although firefox was not installed. Could it be that the desktop file for firefox has the same name and clobbers seamonkey when installed? Will I be able to install firefox if I create a seamonkey.desktop?

you're right... the seamonkey desktop file was named firefox!.. i've fixed and re-uploaded the seamonkey .pet

thanks

[666philb]

i've uploaded a new kernel with the suggested configs https://www.dropbox.com/s/pq3cfhh0mdq1w ... PAE.tar.xz

http://www.murga-linux.com/puppy/viewto ... 753#790753

Tharpup-5.8.3-rc1 has kernel 3.14.11, whereas i expected 3.14.13.

there had been a few problems with the kernel kit which i think are fixed now (i need to test) ... i hope for tahrpup final to have the latest 3.14 kernel with the patches & configs you posted

Fixed sfs_load.
ydrv against tahrpup 5.8.3.rc1 includes fixed sfs_load and puppyinstaller.
Place ydrv_tahr_5.8.3.rc1.sfs at the same place where the tahrpup 5.8.3.rc1 is installed.
http://shino.pos.to/party/bridge.cgi?pu ... .3.rc1.sfs

thanks shinobar,

now unmounts on a harddrive install and also a usb install,
one thing though, with the usb install even though the usb is unmounted after booting, you still get a warning not to unplug the usb.

[666philb]

to everyone who's commented on azpainter ....... mtpaint will be back in the next release

[mavrothal]

hi mavrothal,

i've managed to reproduce the bug, once with a samsung camera and once with a sony android phone. after unmounting and removing the device all drive icons disappear and won't come back until you reboot. same thing occurs if i use slackos drive_all script.
this is the output of xerrs.log after it's happened

Code: Select all

/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory
/usr/local/pup_event/frontend_funcs: line 430: [: 

same thing happens if i use slackos 'frontend_funcs'

Code: Select all

/usr/local/pup_event/frontend_funcs: line 422: [: /tmp/pup_event_frontend_identify1_sr*: binary operator expected
cp: target '/tmp/pup_event_frontend_identify1_sr0' is not a directory

EDIT: same thing happens in slacko beta 5.9.3

Both slacko and tahr errors are from probe_optical_func().
Are the devices show up as optical drives somehow?
Is it happening consistently with the said camera or phone or is a miss and hit?