Fatdog64-600b1

A home for all kinds of Puppy related projects
Message
Author
User avatar
tronkel
Posts: 1116
Joined: Fri 30 Sep 2005, 11:27
Location: Vienna Austria
Contact:

#46 Post by tronkel »

Yes, the reason for using it is to install the Brother DCP7030 driver. Brother only provides a 32 driver version for the printer component of this multi-function device. The scanner driver is provided as 32 bit and 64 bit versions though.

Thanks for doing this. I'll test this in fd-64600B1 over the weekend and let you know how it goes.

Thanks again.

Tronkel.
Life is too short to spend it in front of a computer

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

#47 Post by rcrsn51 »

I just tested this with my HL2070N.

1. I fixed the CUPS backend permissions.

2. I hooked in the 32-bit compat pack and did the CUPS start32 setup.

3. I downloaded and debbi'd the two Brother driver packages.

4. The USB printer that was auto-installed worked OOTB.

The 32-bit Brother setup is much simpler than the Canon.

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

Re: Fatdog64-600b1

#48 Post by Jim1911 »

Billtoo wrote: OpenGL
Vendor NVIDIA Corporation
Renderer GeForce GT 220/PCIe/SSE2
Version 3.3.0 NVIDIA 295.59
Direct Rendering Yes

# glxgears
32084 frames in 5.0 seconds = 6416.749 FPS
32106 frames in 5.0 seconds = 6421.148 FPS
32083 frames in 5.0 seconds = 6416.583 FPS

Working great so far. :)
Billtoo, what's your secret for installing the NVIDIA driver? When I execute

Code: Select all

sh NVIDIA-Linux-x86_64-295.53.run
it naturally complains about the nouveau driver being in use. Every time I try to get rid of it I manage to trash the save file when I delete nouveau files. Xorgwizard-old only allows selection of proper resolution, option to choose the vesa driver never appears. Putting "pfix=vesa" in my menu.lst and rebooting after deleting nouveau files also trashes the save file. So I wind up having to restore the save file with the nouveau driver. :( What file do I need to edit so that vesa will be selected?

Thanks,
Jim

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

01micko's get_libreoffice-0.16.pet

#49 Post by Jim1911 »

01micko's "get_libreoffice-0.16.pet" successfully creates a sfs of LibreOffice 3.5.4.2 which works great including printing.
Attachments
image-4.jpg
(40.57 KiB) Downloaded 818 times

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#50 Post by 01micko »

Re Printing:

So I fixed permissions:

Code: Select all

# chmod 0500 /usr/lib64/cups/backend/*
and added the tiff symlink, did nothing else and I can print and so can unprivileged user. I didn't need to reinstall the printer,

/dev/usb/lp0 still is the same as before crw-rw---- or 660. I guess if I switched back the group from lpadmin to root in /etc/cups/cupsd.conf I'd need to reinstall the printer? I'm happy with it as is and I learned something!

Thanks
Puppy Linux Blog - contact me for access

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

#51 Post by rcrsn51 »

@01micko: Good news! The latest release of Gutenprint supports your Canon MP490. I have posted the 64-bit version for FD600 here.

So you don't need the 32-bit compatibility stuff.

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#52 Post by kirk »

Thanks rcrsn51. Could you test this pet? I compiled it to be smaller.

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

Re: Fatdog64-600b1

#53 Post by Billtoo »

Jim1911 wrote:Billtoo, what's your secret for installing the NVIDIA driver? When I execute

Code: Select all

sh NVIDIA-Linux-x86_64-295.53.run
it naturally complains about the nouveau driver being in use. Every time I try to get rid of it I manage to trash the save file when I delete nouveau files. Xorgwizard-old only allows selection of proper resolution, option to choose the vesa driver never appears. Putting "pfix=vesa" in my menu.lst and rebooting after deleting nouveau files also trashes the save file. So I wind up having to restore the save file with the nouveau driver. :( What file do I need to edit so that vesa will be selected?

Thanks,
Jim
Hi jim,

When the installer warns about the nouveau driver it then offers to
try to remove it, I answer yes to that, and then hit enter once
more to get back to the prompt.
Once back at the prompt I enter reboot, after rebooting and getting
back to the desktop I exit to the prompt again and rerun the Nvidia
installer, once it has finished I answer yes when it asks to update
the xorg.conf.
Now just enter xwin to get back to the desktop and the driver is
working.

The screen is a little garbled when running the Nvidia installer so
it's pretty hard to see the prompts, I always say no when it asks to
install the 32 bit compatability stuff.

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

Re: Fatdog64-600b1

#54 Post by jamesbond »

Billtoo wrote:The screen is a little garbled when running the Nvidia installer so
it's pretty hard to see the prompts
:lol: So I'm not the only one.
I always say no when it asks to
install the 32 bit compatability stuff.
Yes, this is important. /usr/lib and /usr/lib64 points to the same location, so if you install 32-bit library it will bork your installation. Always say "no" when asked about 32-bit library.
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

#55 Post by jamesbond »

01micko wrote:Re Printing:

So I fixed permissions:

Code: Select all

# chmod 0500 /usr/lib64/cups/backend/*
and added the tiff symlink, did nothing else and I can print and so can unprivileged user. I didn't need to reinstall the printer,

/dev/usb/lp0 still is the same as before crw-rw---- or 660. I guess if I switched back the group from lpadmin to root in /etc/cups/cupsd.conf I'd need to reinstall the printer? I'm happy with it as is and I learned something!

Thanks
Mine was mode 0600 (default because udev rule doesn't specify settings for the mode), owned by root:lp (as it should be, as specified by udev rule). When the backend mode are set to 0500, they all will run as root, so non-root device discovery/printing should be okay.

I still don't understand what SystemGroup is for, I've read and re-read the doc a couple of times, but still don't get it :oops:
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-600b1

#56 Post by jamesbond »

Jim1911 wrote:Xorgwizard-old only allows selection of proper resolution, option to choose the vesa driver never appears
Correct.
Putting "pfix=vesa" in my menu.lst and rebooting after deleting nouveau files also trashes the save file{/quote] :shock: It shouldn't do that. All it does is delete /etc/X11/xorg.conf and replace it with a copy that has vesa driver in it.
. So I wind up having to restore the save file with the nouveau driver. :( What file do I need to edit so that vesa will be selected?
Have you tried pfix=vesa,xorgwizard?
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
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#57 Post by rcrsn51 »

kirk wrote:Thanks rcrsn51. Could you test this pet? I compiled it to be smaller.
Looks good.

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

#58 Post by jamesbond »

nooby wrote:I Set it up as easy as I could so maybe
the grub4dos menu.lst is too simple?

title fatdog
find --set-root --ignore-floppies --ignore-cd /fatdog/initrd
kernel /fatdog/vmlinuz PMEDIA=idehd PDEV1=sda2 psubdir=fatdog pfix=fsck
initrd /fatdog/initrd
Boot parameters have changed, please read the FAQ. The equivalent to the above is:
kernel /fatdog/vmlinuz savefile=direct:device:sda2:/fatdog/fd64save.ext4
It reported it could not find a certain file but it went by
too fast for me to read
Probably saying it can't find the savefile, which is okay.
But I found not way to install firefox on it. No ppm.
PPM is inside Control Panel - System :) Firefox is in the package repository.
that simplified html file that I use as my "home page"
lies on my sda2 file and have tested it on some 25 different
OS and many many puppies and only fatdog with this SM
failed to read it. So that where odd.
Fatdog runs the browser as spot. Spot does not have access to your sda2 (by design). If you don't like this, edit /usr/local/bin/defaultbrowser and change "seamonkey-spot" to just "seamonkey".
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
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#59 Post by rcrsn51 »

jamesbond wrote:Mine was mode 0600 (default because udev rule doesn't specify settings for the mode), owned by root:lp (as it should be, as specified by udev rule). When the backend mode are set to 0500, they all will run as root, so non-root device discovery/printing should be okay.
For the vast majority of printer setups, this is a non-issue. The old Patriot Canon PETs auto-install a printer using /dev/usb/lp0, so permissions can be a problem. But if you let CUPS install the printer, it does it correctly.

The 32-bit Brother drivers also do an auto-install, but they get it right. None of my 64-bit printer driver PETs in the repo do an auto-install.

FWIW, I took 55-cups.rules out of a regular Puppy and inserted it into 54-fatdog-permissions.rules. This gave /dev/usb/lp* a more general ownership/permission and all the problems went away, including the 0500 backend issue.

But this may violate the security model you want for FD.

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

#60 Post by jamesbond »

rcrsn51 wrote:FWIW, I took 55-cups.rules out of a regular Puppy and inserted it into 54-fatdog-permissions.rules. This gave /dev/usb/lp* a more general ownership/permission and all the problems went away, including the 0500 backend issue.

But this may violate the security model you want for FD.
Thanks, I'll take a look, but I guess it will grant mode 0666 for all lp* device nodes. There used to be 55-puppy-default.rules that sets mode 0660 to *all* devices; I modified it when I started multi-user work (that file still lives on as 55-fatdog-action.rules but the part that manages permission is commented out). As you say, there is no point of running as non-root when non-root users can access (and possible screw up) every thing just like root does :wink:
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
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#61 Post by smokey01 »

XvidCap works much better for me than screencaster.

http://www.smokey01.com/software/graphi ... tdog64.pet

My printer driver is not included in the default package. Samsung ML1660 but it was recognised after:
chmod 0500 /usr/lib64/cups/backend/*
Although recognised, still not working.

JWM has a few missing icons in the menu system. I'm not a fan of OpenBox, far too bland.

I think a better calculator is required as default. Galculator in the PPM is a better choice.

All in all, looking and working quite nice.

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

#62 Post by jamesbond »

Lobster wrote:Any documentation/tips on going multi-user for other developers welcome 8)
That depends on which "level" of multi-user you want to achieve.

Generally speaking, at minimum one needs to do these:
  1. Xorg must be setuid (so that it can be started by non-root)
  2. su must be setuid (so that non-root can gain priviledge to do stuff that only root can)
  3. passwd must be setuid (so that non-root can change own password)
  4. check with apps require root access, for them have a mechanism for GUI apps to ask permission to become root (Fatdog uses homebrew gtksu; Puppy uses sudo+askpass which is okay too)
  5. Do not hardcode paths to /root, use $HOME instead.
  6. Do not hardcode user to root, use $USER instead
  7. Think about permission model you want to give to non-root users. It can be as strict or as loose as you want. Remember if it is too loose (non-root can access everything) then there is no point of running as non-root at all. Remember if it is too strict then it will cause inconvenience.
Realise the different purposes of the different init scripts, and put proper initialisation code in the proper location. By "proper initialisation code" I mean init code that requires root access (e.g. setup system-wide symlinks; loading kernel modules) must be placed in scripts that run as root.

These applies if you use busybox /sbin/init, if you run busybox runit the details will be different but in principle it is still the same:
  • rc.sysinit runs as root and starts services; all non-X related code that has to run as root must be put here. rc.sysinit is run *before* login
  • /etc/profile is executed by the login shell (the first shell run after login), it is run as *user*, so don't do root-only stuff here. And remember it is only executed *once* per every login.
  • Fatdog and also puppy starts Xorg using xinit. Know exactly what xinit is doing - it launches .xserverrc to start Xorg and launches .xinitrc as the first X client. Remember that although Xorg runs as root (because it is setuid), everything in .xinitrc is run as *user*.
  • When using temporary variables make use of "mktemp" or at least prefix/suffix that with $USER so that leftover temporary files do not prevent the script to fail if executed as another user. E.g. creating "/tmp/output.log" is a bad idea because if that script is first run as root, another user running the same script will try to output to the same file and will fail.
  • Use and separate system-wide settings and per-user settings. For example, Rox keeps its system-wide settings in /etc/xdg/rox.sourceforge.net, while its per-user setting is $HOME/.config/rox.sourceforge.net (usually hardcoded to as /root/.config/rox.sourceforge.net, but see above about $HOME). Openbox has it in /etc/xdg/openbox and $HOME/.config/openbox. Lxpanel has it in /usr/share/lxpanel and $HOME/.config/lxpanel, etc. Not sure about jwm - I don't use it ... but I'm sure it has both settings as well. Application should install in system-wide settings not per-user (this is debatable - some would say the app should offer choice whether to install system-wide or only for one particular user...)
The rest is just hardwork checking and verifying and fixing and moving and shuffling and re-writing scripts ... :shock:
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]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#63 Post by nooby »

JamesBond Much appreciated I did a test again
and now I get the thing working but not sure of
where to put the savefile. I usually have those in
the subdir but it got placed on / so I moved it to fatdog subdir
and will reboot to see if it loads it.

I failed to use the Opera sfs that Terry made so maybe
that works only on Lupu and Slacko?
I renamed it to fd64save.ext3 ?
The easier way for me where to move my html file from home to spot!
That would keep the structure set up and I can have Firefox in root
and SeaMonkey in spot?

Thanks, cool that it is a true multiuser. Ask Barry if you can have it
recognized as an official Puppy when it is out of Beta. That way
we could have something to say to all the anti-root critics being
upset over that puppy is root.

As it is now it asked for password for root but can be defaulted to using woofwoof but when does it need this password?
Last edited by nooby on Sat 16 Jun 2012, 08:12, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
tronkel
Posts: 1116
Joined: Fri 30 Sep 2005, 11:27
Location: Vienna Austria
Contact:

Brother DCP7030 with latest Debbi

#64 Post by tronkel »

@rcrsn51

Have tested the upgraded DEBBI pet in Fatdog600b1 with the Brother DCP7030 drivers as provided on the Brother website at http://solutions.brother.com

Seems to have done the trick OK. Neither the Fatdog Package Manager nor the system itself crash now.

Printer installed OK but needed to initialise CUPS with:
'start32 /usr/sbin/cupsd' to get CUPS to output a test page.

To save having to mess with the 32-bit libs, it would be better if Brother made native 64-bit drivers available on their site. They do have 64-bit brscan drivers for scanners but not for the DCP7030 printer which are only provided as 32-bit. Wonder why not.

Anyway rcrsn51, thanks again for yet another printer rescue job! LOL, seems to be no end to these printer issues.
Life is too short to spend it in front of a computer

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

#65 Post by rcrsn51 »

smokey01 wrote:My printer driver is not included in the default package. Samsung ML1660 but it was recognised after:
chmod 0500 /usr/lib64/cups/backend/*
Although recognised, still not working.
How is it not working? Did you install a driver package? The repo contains the samsung_print_fd600-4.00.35.pet which supports your model.

Post Reply