Fatdog64 700 alpha1

[Bindee]

LOL , there was i thinking it would be complex.

Thanks , I'll give it a go as the rendering in FF29 seems very small for a 1080p screen.

[step]

YASSM honours the Fatdog philosophy of being multi-user, so it always mounts shares in $HOME/YASSM. That will not change.

So step has two choices: Set his browser to run as root or put Fatdog in multi-user mode and login as spot.

I have attached an upgrade to YASSM.

[Edit] No reply on this? I guess that it's not a very high priority.

Hi rcrsn51, I'm ready to reply about the upgrade pet you attached. First of all, thank you for providing it and your advice. So I converted the pet to the new FD64-700 package format and tested it.

It works very well and I think it should become the default for the 700 series.

I noticed the new pet does not include files samba-login.png and samba-menu.xpm in /usr/local/yassm. Are those files redundant now?

I concur with you that mounting shares in $HOME/YASSM shouldn't change. In addition to the two alternatives that you suggested, I will try linking $HOME/YASSM from /tmp/YASSM to enable browsing within SeaMonkey running as user spot. Can you see any downsides to such a work-around? (It wouldn't be standard behavior in FD; just a simple script in my ~/Startup folder.)

[rcrsn51]

@step: Thanks for testing. YASSM is now using the standard location /usr/share/pixmaps for its icons.

Regarding linking $HOME/YASSM to /tmp/YASSM, I can't see a problem. But it raises a basic security issue. The whole point of running your browser as spot is to prevent any malicious code from attacking your system beyond spot's environment. If you are concerned with this possibility, why would you give your browser access to external shares?

[step]

@step: Thanks for testing. YASSM is now using the standard location /usr/share/pixmaps for its icons.

Regarding linking $HOME/YASSM to /tmp/YASSM, I can't see a problem. But it raises a basic security issue. The whole point of running your browser as spot is to prevent any malicious code from attacking your system beyond spot's environment. If you are concerned with this possibility, why would you give your browser access to external shares?

I agree about the security argument.
Why/when would I want for spot to be able to access shares? Mainly it's for large downloads that I can't or don't want to put on my hard drive even temporarily. I have plenty of free space on shares, but not much space left on my hdd (or USB stick).

[rcrsn51]

I see your point. In a true multi-user system, there isn't a real distinction between files in your home directory and files on a share that you own.

[step]

I don't know how and why but pet2txz - invoked by ROX right-click - got loose and deleted all links it could find on its way before I realized that it was doing so. Running ps revealed the nasty

Code: Select all

find . -type l -exec rm {} \;

Now my fatdog 700 looks all messed up - most ROX/desktop icons show as question signs, and some links are deleted. Which ones?

I had some drives and shares mounted when pet2txz went berserk. I hope it didn't damage those as well, that would make me mad. (It didn't, see further down.)

OK, let's start assessing the extent of the damage... I'll post back.

Edit 1: I'm not 100% positive, but I think the find command ran in /root only ($HOME). I'll take that as an assumption.
As regards shares, the find command started descending my shares from /root/YASSM. But since those are samba shares they don't support symlinks, so find could do no harm there. Hurray.
As for mounted drives, /mnt is outside /root so mounted drives couldn't be damaged. Hurray again!
As regards missing links... I booted FD 631 and listed all links in /root. The idea is that if 631 has a link then probably 700 should have the same link too. After recreating the links FD 700 looks normal and acts normal.

Question
I couldn't recreate some links due to FD 700 lacking some paths that FD 631 does have. Can you confirm that the following paths aren't included in FD 700 a1 iso?

/root/.config/rox.sourceforge.net/MIME-types
/root/.config/rox.sourceforge.net/OpenWith
/root/puppy-reference
/root/spot/.icons/ROX

Case closed.


Note to myself: This command creates a link-cloning script

Code: Select all

find ./root -type l -exec readlink {} \; -print | awk 'NR%2{printf"ln -s \"%s\"\t",$0}!(NR%2){printf"\"%s\"\n",$0}' | sort -k 2,2 -t "`printf "\t"`" > /tmp/link-maker.sh

# purpose: make script that clones frugal FD 631 root links to frugal FD 700 root links
# run above command in FD 631 path /
# copy /tmp/link-maker.sh to safe storage and reboot
# run resulting script in FD 700 path /

[Bindee]

http://www.youtube.com/watch?v=5xkNy9gfKOg


BAH!

Vblank for nouveau doesn't work just like 631.

Media playback glitches , Web browser scroll ripple and flashplayer like the above tear test just breaks up as before.

I'll give the Nvidia drivers a try this week with it's Vblank before i try the pipeline fix.

[neerajkolte]

I don't know how and why but pet2txz - invoked by ROX right-click - got loose and deleted all links it could find on its way before I realized that it was doing

This happened with me too.
Some pets convert OK, some don't.
@jamesbond has advised not to use pet2txz and also said this will be corrected in 700Alpha2.

- Neeraj.

[jamesbond]

rcrsn51 - thanks, the new version will be included in next release.

step - if you mess up, look up in /aufs/pup_ro. This contains the content of the original pristine Fatdog 700 filesystem, including the symlinks and everything.

re: pet2txz: I'm attaching the updated pet2txz. This is the new pet2txz that will be in the next release, so if you're keen perhaps you can try it and let me know whether it works for you.

cheers!

[step]

step - if you mess up, look up in /aufs/pup_ro. This contains the content of the original pristine Fatdog 700 filesystem, including the symlinks and everything.

Golden info!

re: pet2txz: I'm attaching the updated pet2txz. This is the new pet2txz that will be in the next release, so if you're keen perhaps you can try it and let me know whether it works for you.

Will do!
Cheers!
p.s. 007 on 700 - the palindromic developer

[step]

re: pet2txz: I'm attaching the updated pet2txz. This is the new pet2txz that will be in the next release, so if you're keen perhaps you can try it and let me know whether it works for you.

Having been scorched yesterday with a couple of hours spent repairing my system, I want to understand what is the potential for pet2txz to break loose again. I compared this new script with the old one and it's a huge re-write (ok). I looked for a lines that run "find -type l -exec rm {} \;" but couldn't find any. Finally I found one inside /sbin/makepkg, the (patched) slackware package maker. So, that's the guy with the potential of breaking havoc in a system.

James, do you consider the way pet2txz uses makepkg totally safe?

[step]

Is Qemu working in 700a1? I tried package versions qemu-arm-x86_64 2.0.0 and qemu-arm-x86_64 2.1.0 from the 700 repo, with and without 32bit-slacko-3.sfs (should be without, right) and each time got an error message. Used Qemu_Control_Center-0.6-x86_64-PET.txz to start Qemu.

Code: Select all

# qemu-arm-x86_64 2.1.0 with 32bit-slacko-3.sfs
debug: qemu-system-x86_64 -boot c -m 512 -enable-kvm -hda /mnt/sda5/file/VM/precise-571RetroCsipeszPupV5EngHun2014Aug.iso -hdb /dev/null -cdrom /dev/null -smp 1
qemu-system-x86_64: error while loading shared libraries: libncurses.so.5: wrong ELF class: ELFCLASS32

# qemu-arm-x86_64 2.1.0
debug: qemu-system-x86_64 -boot c -m 512 -enable-kvm -hda /mnt/sda5/file/VM/precise-571RetroCsipeszPupV5EngHun2014Aug.iso -hdb /dev/null -cdrom /dev/null -smp 1
qemu-system-x86_64: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

# qemu-arm-x86_64 2.0.0
debug: qemu-system-x86_64 -boot c -m 512 -enable-kvm -hda /mnt/sda5/file/VM/precise-571RetroCsipeszPupV5EngHun2014Aug.iso -hdb /dev/null -cdrom /dev/null -smp 1
qemu-system-x86_64: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

# qemu-arm-x86_64 2.0.0 with 32bit-slacko-3.sfs
debug: qemu-system-x86_64 -boot c -m 512 -enable-kvm -hda /mnt/sda5/file/VM/precise-571RetroCsipeszPupV5EngHun2014Aug.iso -hdb /dev/null -cdrom /dev/null -smp 1
qemu-system-x86_64: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

[jamesbond]

James, do you consider the way pet2txz uses makepkg totally safe?

It should, but of course bugs can happen ...

You don't need 32bit libs to run qemu. For the time being, please install libnss and libnspr from the repo. They shouldn't be needed - qemu should use libnss/libnspr already in seamonkey/firefox - but because of a bug in /etc/profile, you do need to install them for now. qemu 2.1.0 requires libvte, this should be pulled out automatically when you install from repo.

I have no idea why your qemu fails on libncurses, it could be part of your symlink screw up before. Try running "ldconfig" to restore most of the library symlinks. Btw what's inside that qemu-control-panel pet? Does it only contain scripts, or does it also have qemu binaries (which may override the qemu from 700)?

[Gobbi]

I have no idea why your qemu fails on libncurses

Unable to run qemu at first shot , after the terminal gave me the message that I should load libnss3.so , loading libnss made Gslapt tick not only libnss package but libnspr as well . If one untick libnspr and install only libnss , then the next message in terminal tells to load also libncurses ...

[step]

You don't need 32bit libs to run qemu.

32bit-slacko-3.sfs unloaded.

For the time being, please install libnss and libnspr from the repo. They shouldn't be needed - qemu should use libnss/libnspr already in seamonkey/firefox - but because of a bug in /etc/profile, you do need to install them for now. qemu 2.1.0 requires libvte, this should be pulled out automatically when you install from repo.

Gslapt doesn't tick libvte when qemu 2.1.0 is ticked.
First I tested qemu 2.0.0 with libnss and libnspr and it failed (missing libncurses) - as Gobbi report above.
Then I tested qemu 2.0.1 with libnss, libnspr and libvte and it worked!

I have no idea why your qemu fails on libncurses, it could be part of your symlink screw up before. Try running "ldconfig" to restore most of the library symlinks.

Gobbi had the same problem, but I guess we can leave 2.0.0 behind and use the working 2.1.0.

[ Btw what's inside that qemu-control-panel pet? Does it only contain scripts, or does it also have qemu binaries (which may override the qemu from 700)?

Just script and desktop files. You replied to Qemu control panel thread here http://murga-linux.com/puppy/viewtopic. ... 787#797135. I installed the Qemu control panel from the FD 700 repo. File list from Gslapt:
/usr/
/usr/share/
/usr/share/applications/
/usr/share/applications/qemu.desktop
/usr/share/pixmaps/
/usr/share/pixmaps/qemu.png
/usr/bin/
/usr/bin/qemu_gui
/Qemu_Control_Center-0.6.pet.specs

Summary: qemu 2.1.0 txz from the repo works with the addition of three libraries. Qemu control center 0.6 from the repo works as well.
Thanks for your help!

I'd like to add some contrib packages to the 700 repo. How can I get upload access?

[Yoni]

http://distro.ibiblio.org/fatdog/packages/700/

I like the new 700 but i also have Ripple fest and can confirm Vblank for nouveau doesn't work just like 631.

No Nvidia proprietary drivers in the above package folder ?

[neerajkolte]

Hi,
How can I increase sensitivity of a mouse.
Since having 2 displays I need to cover more screen in the same space available to move mouse.

Thanks.
-Neeraj.

[step]

http://distro.ibiblio.org/fatdog/packages/700/

Thanks. I meant upload access. But perhaps I should have asked, more clearly, what is the process to add my contributed files to the official 700 repo.

[gcmartin]

... Btw what's inside that qemu-control-panel pet? Does it only contain scripts, or does it also have qemu binaries (which may override the qemu from 700)?

I think he is using the Puppy approached presented by @MikeB and maintained here. It is designed to simplify virtual PC setup and is s set of scripts. Might be a simple addition to FATDOG Menu system if QEMU is made a part of the GA. @StemSee has deployed such in his distro as an example reference.

So far, it my findings that the QEMU only impacts the ISO and does NOT impact any system performance or operation in its presence in Menu for anyone who might be interested.

Hope this helps

[jamesbond]

I installed the Qemu control panel from the FD 700 repo.

Qemu control panel isn't in the repo. You must have converted it from a pet. Make sure that the pet doesn't have qemu binary in it (looks like you've done the right thing, though).

No Nvidia proprietary drivers in the above package folder ?

No, not yet. We only package proprietary drivers when it's final or near final release. This is still alpha release, kernels will still change often. You can try to install it yourself, though.

How can I increase sensitivity of a mouse.

Control Panel --> Desktop --> pupx (or just run pupx on terminal).

I meant upload access.

I'll send you a PM.

QEMU is made a part of the GA

Qemu is part of (next-release) devx.