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

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

Code:

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?

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!

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

Code:

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.

The screen is a little garbled when running the Nvidia installer so
it's pretty hard to see the prompts

So I'm not the only one.

Quote:

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, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

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 _________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Xorgwizard-old only allows selection of proper resolution, option to choose the vesa driver never appears

Correct.
[quote]Putting "pfix=vesa" in my menu.lst and rebooting after deleting nouveau files also trashes the save file{/quote] 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.

Quote:

. 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?

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.

Quote:

But I found not way to install firefox on it. No ppm.

PPM is inside Control Panel - System Firefox is in the package repository.

Quote:

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, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

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.

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 _________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum