Puppy Linux Discussion Forum

playdayz · Joined: 25 Apr 2008 Posts: 3794

pemasu and don570, You have made me a believe in the right-click convenience. I am already starting to rely on it Wink

I think it will be a big hit among users. Thanks for all the work.

Béèm · Posted: Sun 31 Jul 2011, 19:15 Post subject:

bigpup · Posted: Sun 31 Jul 2011, 19:30 Post subject:

rerwin · Joined: 24 Aug 2005 Posts: 1884 Location: Maine, USA

playdayz,
I have discovered a surprising situation. It appears that the udev rules in the relatively new /lib/udev/rules.d directory are not being processed. I have been frustrated by my inability to solve dalderton's issue of the modeswitch rules being ignored. As a test, I moved a working test rules file from /etc/udev/rules.d to /lib/udev/rules.d. It no longer works!

This implies that not only are the modeswitch rules being ignored, but also the rest of the rules files in /lib/udev/rules.d. Maybe we should pause a little longer to resolve that.
Richard

Here is evidence that the udev version (124-2) in lupu does not know about the "default" rules directory. That must have come in later.

Snail · Joined: 18 Oct 2009 Posts: 334

Smokey01 Playdayz

I would be happy to write the HowTo. How urgent is it? I have never used Notecase, is there much of a learning curve? I don't see any picture in 101 at the moment, are they possible or do I have to get that sort of detail over by being clever with links?

Playdayz I am very, very pleased that you now see the use of right-clicks. If it helps you, just think how good it is for the casual user. If I write the HowTo, it would be my preference to assume that you have binned the "Customise" menu options, for the reasons that I have given above. Would this be acceptable to you? It's your distro after all.

I had a mad idea about right clicks. The .desktop files already hold info about icons and executable files and are a Linux standard, unlike RoxApps. Wouldn't it be nice if you could use the .desktop instead of duplicating the same info in the form of a Roxapp? So I tried adding the "$1" parameter to the Exec= line in a .desktop and then symlinking the .desktop to the Open-with subdirectory. Alas it doesn't work, nor does "$@". Pity.

Béèm · Posted: Sun 31 Jul 2011, 20:27 Post subject:

Snail,
Notecase is very easy and intuitive.
It is based on creating nodes and eventually nodes on nodes.

Just make up your mind about a structure and hierarchy you want to set up.

Snail · Joined: 18 Oct 2009 Posts: 334

Thanks for the reassurance Béèm.

I have thought a bit more about the subject, should have done it before my last post Embarassed

I know how to set up a right click, provided that the filetype is one already assigned a mime-type. For the case of an entirely new file-type that doesn't have an existing mime-type, I will have to do some research. If we drop the "Customise" options in the menus, the user also needs to check if his particular file-type is already known to Rox or not. Anyone got any pointers?

Snail · Joined: 18 Oct 2009 Posts: 334

Smokey01

Quick question. Is there a reason that PH101-001.ncd is in /usr/share/doc and not /usr/share/doc/help? Shouldn't it be PH101-002.ncd?

bigpup · Posted: Mon 01 Aug 2011, 02:07 Post subject:

Got the idea from here
http://murga-linux.com/puppy/viewtopic.php?t=39505

Product key for your computer

bigpup · Posted: Mon 01 Aug 2011, 02:19 Post subject:

Got idea from here:
http://murga-linux.com/puppy/viewtopic.php?t=39505

Sticker for the front of computer

Sage · Joined: 04 Oct 2005 Posts: 5371 Location: GB

rerwin:

smokey01 · Joined: 30 Dec 2006 Posts: 2682 Location: South Australia

peebee · Posted: Mon 01 Aug 2011, 06:00 Post subject: smbc printer error

Hi playdayz

I did my usual setup of a remote smbc printer to my XP box.

Got the attached error when I tried to print.....

Cheers
peebeee

rcrsn51 · Posted: Mon 01 Aug 2011, 08:28 Post subject: Re: smbc printer error

pemasu · Joined: 08 Jul 2009 Posts: 5484 Location: Finland

Playdayz and rerwin. About udev 151-12. I remember when Playdayz tested it and got some bad experience about it. I just cant remember what went wrong.

But....I had to change to the udev 151-12 when I started to use kernel 2.6.35.7. I couldnt get audio working otherwise. I have used udev 151-12 since then with 2.6.38.2, 2.6.38.4 and now with 2.6.39.3 kernels. Audio has worked. I havent noticed any problems with using it.

Now...People have woofed using ez woof 525 and they have used my kernels 2.6.38.4 and maybe 2.6.39.3 and they have had a lot problems with audio. Maybe older udev is one reason of the audio problems with ez woof 525

If....you are going to create ez woof 527 and there is plan to test newer kernels with it....updating the udev to 151-12 is again current.