Fatdog64-511

A home for all kinds of Puppy related projects
Message
Author
jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#151 Post by jamesbond »

rcrsn51 wrote:
rcrsn51 wrote:I couldn't resolve this. I got different USB behaviours depending if I compiled CUPS 1.4 in Quirky or FD64.
My mistake - I was using depmod wrong. If you install usblp and compile CUPS 1.4 with --disable-libusb, it works correctly.
Interesting. Epson tools from cups doesn't work without usblp - and yet the same cups won't work with usblp (I'm talking about default cups in FD64). So if we can still disable libusb, that sounds like the best of both worlds - unless there is some unforeseen consequences ....

Anyway, does it mean that your previous pets in this thread won't work? Haven't got any comments and not having the printers themselves, I can't test ...
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-511

#152 Post by Billtoo »

Here's the newest Ltris game.
The following is from the change log:

1.0.16:
- improved random number generator (2011/03/02 MS)
- generate pieces according to official Tetris guidelines (2011/03/02 Andrey
Maykov)
- always deal same sequence of pieces to all players (2011/03/02 MS)
- in expert mode deal most unsuitable piece out of current bag instead
of random piece (2011/03/02 MS)

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#153 Post by rcrsn51 »

All the PETs I have posted above work in the current CUPS. They do not need usblp support. However, there are two udev rules files where this is an issue.

1. 55-cups. The purpose of this rule is to give all printer device nodes 666 permissions so the unprivileged CUPS user can access them. Supposedly, without that rule in play, you couldn't print at all. However, the purpose of the usblp module is to manage those device nodes and FD64 doesn't have it. So I was surprised that any printer would work.

I suspect that printing works anyway because of the rule in 50-udev-puppy-basic that assigns ownership of all USB devices to the unprivileged user spot. That's an odd hack. Or maybe if you print via libusb, you aren't constrained by ownership/permission issues.

2. 11-hplj10xx. This is the rule used by some older non-standard HP models that downloads firmware from the host computer to the printer. It is part of the foo2xxx driver package. It requires a device node like /dev/usb/lp0, so it definitely needs usblp. But there are only nine models affected by this issue.

Like I said above, Lupu has CUPS 1.4 AND usblp. Since it is built from Ubuntu packages, I'm assuming that the big-boy distros are still compiling CUPS with libusb disabled.
Last edited by rcrsn51 on Sun 20 Mar 2011, 22:18, edited 2 times in total.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-511

#154 Post by Billtoo »

I don't see this in the fatdog repo:
Attachments
streamripper-1.64.6-x86_64.pet
(67.56 KiB) Downloaded 312 times

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#155 Post by jamesbond »

rcrsn51 wrote:All the PETs I have posted above work in the current CUPS. They do not need usblp support.
Ah, good to hear that.
However, there are two udev rules files where this is an issue.

1. 55-cups. The purpose of this rule is to give all printer device nodes 666 permissions so the unprivileged CUPS user can access them. Supposedly, without that rule in play, you couldn't print at all. However, the purpose of the usblp module is to manage those device nodes and FD64 doesn't have it. So I was surprised that any printer would work.

I suspect that printing works anyway because of the rule in 50-udev-puppy-basic that assigns ownership of all USB devices to the unprivileged user spot. That's an odd hack. Or maybe if you print via libusb, you aren't constrained by ownership/permission issues.
I remembered troubleshooting usb printing problem back in FD64 500 beta days. It was CUPS 1.4 I think - and at that time, I can assure you, permission did have effect. Apparently CUPS of that day accessed usb printers through the usbfs (/proc/usb) and there was no way I can control the access (other than doing chmod 0666 manually). The problem at that time was, the usb backend, for some reason the usb backend was run as nobody instead of root - so definitely no usb printing before I did the manual chmod. Luckily we found the issue and managed to convince CUPS to run it as root. My understanding is that usbfs is deprecated, so newer libusb should not depend on it anymore, and should depend on /dev/usb which *is* managed by udev as you said above - but I have yet to confirm this.
2. 11-hplj10xx. This is the rule used by some older non-standard HP models that downloads firmware from the host computer to the printer. It is part of the foo2xxx driver package. It requires a device node like /dev/usb/lp0, so it definitely needs usblp. But there are only nine models affected by this issue.
As far as I know, /dev/usb/lp is managed by udev. Usblp will create /dev/usblp0 nodes. But I agree, anything that require raw access to the printers (e.g. checking ink status on Epson) seems to require usblp.
Like I said above, Lupu has CUPS 1.4 AND usblp. Since it is built from Ubuntu packages, I'm assuming that the big-boy distros are still compiling CUPS with libusb disabled.
Sounds good - I'm sure kirk will take note of this, if he decides to upgrade CUPS on next release of Fatdog.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

Re: Fatdog64-511

#156 Post by jamesbond »

Billtoo wrote:I don't see this in the fatdog repo:
I used to provide a test streamripper pet for smokey01 before, but it didn't work for me (well it kind of works but I'm not a regular user of streamripper so I encountered a lot of issues with it) and in the end he didn't have the time to test it out, so I removed it.

When I have the time I'll put this into staging and if we hear good feedback I'll move it to the official repo.

Thanks for the updated Ltris also - I'll make time to put it to the official repo later.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

rayberau
Posts: 29
Joined: Fri 25 Feb 2011, 05:04

Can Linux Wine be used with Fatdog64?

#157 Post by rayberau »

I'm wondering whether Linux Wine can be used with Fatdog64. I managed to download Wine using Fedora 13 OS so I can now use the Japanese and Chinese Word Processors that contain supurb dictionaries which I was using on the Windows 7 OS that was on my Acer Aspire 5542G-304G50Mn Model MS2277 Notebook Computer with AMD Athlon 64-bit II M300 2.00GHz dual-core (X2) processor before I put Fedora 13 on it.

I'm wondering whether the same thing can be done with Fatdog64?

Regards from Ray Bergmann

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#158 Post by jamesbond »

Oh yes you can. Fatdog SFS repo http://distro.ibiblio.org/pub/linux/dis ... g/sfs/500/ has wine. But since it's a 32-bit package, you need to use 32-bit library SFS also.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-511

#159 Post by Billtoo »

Here's the latest Geany text editor:
Attachments
geany_DEV-0.20-x86_64.pet
(91.37 KiB) Downloaded 285 times

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#160 Post by jamesbond »

Billtoo, thanks, but I think kirk has also compiled geany 0.20 with all its plugins....
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-511

#161 Post by Billtoo »

jamesbond wrote:Billtoo, thanks, but I think kirk has also compiled geany 0.20 with all its plugins....
oops, I should have checked the repo first.

Bruce_n_Duane
Posts: 71
Joined: Wed 02 Nov 2005, 01:40
Location: Washington State

Broken Firefox / Namoroka [SOLVED]

#162 Post by Bruce_n_Duane »

Two Firefoxes on new FatDog 511 install???????

Just installed FatDog 511 as frugal install in Intel Core2 64-bit computer.

There appears to be two Firefox's. (Namoroka)
One accessible from the desktop icons both on the desktop and from the bottom panel. This Firefox will not import or export the bookmarks and can not read an html file on the hard disk. I added 10 Addons to this firefox.

Second accessible by clicking on an HTML file.
If I use ROX file manager to show a directory with the exported Stardust Bookmarks in an html file, a new copy of Firefox appears which can import/export/and read html files on the hard disk. Only "FTP Upload" extension appears in the Tools==>Addons display and none of the other 10 extension above appear.

Question:
How do I get the second firefox version to be my default for the icons?

Why is this happening?

Why do they have separate extension and bookmark files?

Thanks in advance for the help.

This FatDog is FAST!!!! The fastest puppy yet!!

Duane wants to make this his default Puppy, if Firefox can be fixed, replacing MINT Linux.

-Edit See Jamesbond and our post below for solution.

-Bruce and Duane.
Last edited by Bruce_n_Duane on Thu 24 Mar 2011, 18:32, edited 1 time in total.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#163 Post by jamesbond »

Bruce/Duane, there aren't two Firefoxes on Fatdog. There is only one. But one is associated with the user spot (a non-root user), and the other is associated with root user (the default user in most puppies, including Fatdog).

kirk designed Fatdog with security in mind, and he figured out that the biggest risk comes from network-based programs. To reduce this risk, all network-based programs (including Firefox) will not run as the default root user, but it will run as the non-root limited "spot" user. This is what you get when you click the Firefox icon on the desktop, or the browser icon on the taskbar.
Unfortunately (or fortunately, depending on your point of view), "spot" being a limited user, means that there are a lot of places that it cannot (or not allowed) to access. Depending on where you store you HTML files, they may be located in a folder that spot cannot access - thus, from your point of view, Firefox cannot display those pages.

When you open rox and click an HTML page, the same Firefox will be launched - and this time it will run under the default root user. (I'm not sure whether this is an oversight of kirk, or whether he intends to do it this way). And of course, being the root user (=superuser, alias administrator), this particular Firefox will have power to read/write anything to the system (which, if there is a security flaw, makes it more dangerous because it can modify any part of the system without you knowing it).

Linux, being a multi-user system, can store two completely different profiles for each user - and this is what happens with Firefox. There is only one, but it can run under the identity of "spot" or "root" (or other users, if you know how to create them). Each Firefox will run with completely different profile. That's why any extensions you add with Firefox running as spot, will not be visible from Firefox running as root (and vice versa).

Have I confused you enough? :D

Now, if you want to have the "second" Firefox as your default browser (I suppose the one with the abilility to read HTML pages from anywhere in the filesystem - that is the one running under root), it's very easy.

With rox, navigate to the folder /usr/local/bin
Edit the file defaultbrowser and when you see the word firefox-spot, change that back to firefox.

Enjoy.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

radky
Posts: 977
Joined: Mon 03 May 2010, 03:13

PupSnap Screen Capture for Fatdog64

#164 Post by radky »

The PupSnap screen capture program is now available as a 64-bit version for Fatdog64.
http://www.murga-linux.com/puppy/viewtopic.php?t=61361

Bruce_n_Duane
Posts: 71
Joined: Wed 02 Nov 2005, 01:40
Location: Washington State

Broken Firefox / Namoroka

#165 Post by Bruce_n_Duane »

Thank you Jamesbond!!!!

I can completely follow your explanation.

This makes FatDog more secure by using spot.

As root I copied the Stardust-bookmark.HTML file to /root/spot directory.
In a rwxt terminal I did the following:
# cd spot
# chmod +r Stardust-bookmark.HTML
# chown spot.spot Stardust-bookmark.HTML
# exit
Thus changing the permissions to rw-r--r-- and the owner to spot.spot.

Then in the network (firefox-spot) I imported the bookmarks since it could now read the HTMP file because spot owned it.

Duane is now very, very happy as he has his bookmarks!!!

Thank you again Jamesbond for your great explanation.

-Bruce.

Bruce_n_Duane
Posts: 71
Joined: Wed 02 Nov 2005, 01:40
Location: Washington State

Loosing Wifi Connection

#166 Post by Bruce_n_Duane »

Duane is using FatDog 511 in frugal install.

Sometimes it gets into a mode where it will only stay connected to wifi for about 1 minute. Other times he can be on for hours with the computer in the same location connected to the same wifi access point.

What information do you need to debug this or fix it?

We tried both the network connect and pwireless to connect to wifi and neither seemed to connect for more than a minute.

Right clicking on the twin monitor icon on the panel does not show wlan0 as and option and only lo. It considers wlan0 an ethernet connection when I added it.

Thanks for the help in advance.
-Bruce.

WillM
Posts: 173
Joined: Wed 30 Dec 2009, 04:42
Location: Oakland, California

#167 Post by WillM »

Thank you rcrsn51 for the printer drivers.
I installed hpijs_print_fd64-3.11.1 and this worked nicely.
With hplip_scan_fd64-3.11.1 I received an I/O error.
This printer is a HP PSC 1200 series.

(edit)This is a double post I misplaced the original on Fatdog64-500 thread..

kn0w-b1nary
Posts: 2
Joined: Sat 26 Mar 2011, 19:04

#168 Post by kn0w-b1nary »

I want to install fatdog on a new patition (/dev/sda4) on my PC, by doing a manual frugal install (I can't boot from USB and I can't burn CD's). I'm not sure though what to menuentry to add to Grub2.

Any help?

WillM
Posts: 173
Joined: Wed 30 Dec 2009, 04:42
Location: Oakland, California

#169 Post by WillM »

Hi kn0w-b1nary,

Your menu item would look something like this;

cat << EOF
menuentry "Fatdog64 511" {
set root=(hd0,4)
linux /fatdog511/vmlinuz pmedia=atahd psubdir=fatdog511
initrd /fatdog511/initrd.gz
}
EOF

This is assuming you put your files in the sub folder fatdog511 at the root of the partition.

Add that menu item to /etc/grub.d/40_custom. Save the file. Then sudo update-grub

You could just add that to /boot/grub/grub.cfg, but if you ever update grub in the future you would lose that item. Actually that's what I do. Edit grub.cfg straight from Fatdog64. But it is not recommened.
Good Luck

kn0w-b1nary
Posts: 2
Joined: Sat 26 Mar 2011, 19:04

#170 Post by kn0w-b1nary »

Thanks WillM!

I made one modification:

cat << EOF
menuentry "Fatdog64 511" {
set root=(hd0,msdos4)
linux /fatdog511/vmlinuz pmedia=atahd psubdir=fatdog511
initrd /fatdog511/initrd.gz
}
EOF

But it works! Thx a lot!

Post Reply