slacko-5.6 Final - plus testing next
(...continuation of this...)
I'm still trying to investigate what's going on in /usr/local/pup_event/ and things become a tiny bit more clear...
When Gparted is starting formatting a partition (eg. sdb1, a pendrive), /usr/local/pup_event/frontend_change receives (from .../pup_event/pup_event_frondend_d, I suppose) this string:
rem:sdb1 add:sdb1
but does nothing with it.
Whereas insertion/removal of a usb drive produces:
add:sdb add:sdb1
or
rem:sdb rem:sdb1
and frontend_change properly creates/removes an icon on/from the pinboard.
@Mick: did you mention to Barry about this yet (or should I do it?)? Maybe it's an easy fix for him..?
Well, in the end it's not a major issue, but could be confusing for a user who formats a partition to another filesystem and ends up with useless icon on the pinborard (unless X will be restarted).
Thank you.
_____________
@Zigbert: could you please add support for f2fs to your pmount version (see original pmount)?
Would be nice.
Thanks &
Greetings!
I'm still trying to investigate what's going on in /usr/local/pup_event/ and things become a tiny bit more clear...
When Gparted is starting formatting a partition (eg. sdb1, a pendrive), /usr/local/pup_event/frontend_change receives (from .../pup_event/pup_event_frondend_d, I suppose) this string:
rem:sdb1 add:sdb1
but does nothing with it.
Whereas insertion/removal of a usb drive produces:
add:sdb add:sdb1
or
rem:sdb rem:sdb1
and frontend_change properly creates/removes an icon on/from the pinboard.
@Mick: did you mention to Barry about this yet (or should I do it?)? Maybe it's an easy fix for him..?
Well, in the end it's not a major issue, but could be confusing for a user who formats a partition to another filesystem and ends up with useless icon on the pinborard (unless X will be restarted).
Thank you.
_____________
@Zigbert: could you please add support for f2fs to your pmount version (see original pmount)?
Would be nice.
Thanks &
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
I think the problem lies @line 398 in /etc/rc.d/rc.sysinit. You'll see,
Now, there is a bug in woof where the variable DEVTMPFSFLG gets set. In out situation, it should get set to 0. As you will see it's set to 2. That will make those entries irrelevant to us, but still should probably be fixed.
More later..
Now, there is a bug in woof where the variable DEVTMPFSFLG gets set. In out situation, it should get set to 0. As you will see it's set to 2. That will make those entries irrelevant to us, but still should probably be fixed.
More later..
Puppy Linux Blog - contact me for access
HP 1050 all-in-one printer
rcrsn51 wrote:
As you know, there are two steps to installing a printer in CUPS.
1. Detecting the physical device through Add Printer / Find New Printers.
2. Providing the correct printer driver software.
Which one are we talking about?
-----------------------------------------------------------------------------------------------------------
I only ever use Find New Printers!
I can't understand why it doesn't find the HP 1050? I'm aware nothing has changed since 5.5?
I believe I've tried all the little 'tricks' you've taught me over several versions of puppy's!
>>>---Indian------>
As you know, there are two steps to installing a printer in CUPS.
1. Detecting the physical device through Add Printer / Find New Printers.
2. Providing the correct printer driver software.
Which one are we talking about?
-----------------------------------------------------------------------------------------------------------
I only ever use Find New Printers!
I can't understand why it doesn't find the HP 1050? I'm aware nothing has changed since 5.5?
I believe I've tried all the little 'tricks' you've taught me over several versions of puppy's!
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
@jim1911 and sszindian:
Here is something to try:
1. Install the attached PET.
2. Run:
rmmod usblp
/etc/init.d/cups restart
3. Run CUPS.
Here is something to try:
1. Install the attached PET.
2. Run:
rmmod usblp
/etc/init.d/cups restart
3. Run CUPS.
- Attachments
-
- cups_usb_patch_slacko-5.6.pet
- (7.82 KiB) Downloaded 361 times
Cups Patch
rcrsn51 wrote:
1. Install the attached PET.
2. Run:
rmmod usblp
/etc/init.d/cups restart
3. Run CUPS.
-------------------------------------------------
Yep... that patch was needed. the 1050 printer found, setup and printed a test-page in about a minute!
'As always, Thanks rcrsn51' and hope this helps mic, looks like he has a nice build going here!
>>>---Indian------>
1. Install the attached PET.
2. Run:
rmmod usblp
/etc/init.d/cups restart
3. Run CUPS.
-------------------------------------------------
Yep... that patch was needed. the 1050 printer found, setup and printed a test-page in about a minute!
'As always, Thanks rcrsn51' and hope this helps mic, looks like he has a nice build going here!
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
sszindian: Excellent. However, you will need to permanently blacklist the usblp module for this to keep working.
Could you try one more thing for me:
1. Do a clean install.
2. Run: chmod 700 /usr/lib/cups/backend/usb
3. Run CUPS.
@Mick: This patch comes from compiling CUPS without the --disable-libusb option. So CUPS detects USB printers through libusb (like SANE) instead of through the device node.
However, a few drivers need to work through /dev/usb/lp0, so this is not a 100% solution.
I would like to hear from other users with USB printers - not just HP - about how they work.
Could you try one more thing for me:
1. Do a clean install.
2. Run: chmod 700 /usr/lib/cups/backend/usb
3. Run CUPS.
@Mick: This patch comes from compiling CUPS without the --disable-libusb option. So CUPS detects USB printers through libusb (like SANE) instead of through the device node.
However, a few drivers need to work through /dev/usb/lp0, so this is not a 100% solution.
I would like to hear from other users with USB printers - not just HP - about how they work.
Thanks rcrsn51,
I did notice that the 'usb' file in your pet was -rwx------ (0700) and is 2/3 the size of the original.
I'm just wondering though if when I revert the error in woof that causes the kernel to take over creation of device nodes whether this will be a waste of effort.
I'll run the current slacko alpha on my file/print server (cannon mp490) and see what happens, also with my dev version.
I did notice that the 'usb' file in your pet was -rwx------ (0700) and is 2/3 the size of the original.
I'm just wondering though if when I revert the error in woof that causes the kernel to take over creation of device nodes whether this will be a waste of effort.
I'll run the current slacko alpha on my file/print server (cannon mp490) and see what happens, also with my dev version.
Puppy Linux Blog - contact me for access
Even though my USB printers work, there is something else going on with udev. In other Puppies, /etc/udev/rules.d/55-cups.rule is responsible for giving the printer device nodes 666 permissions.
In this Slacko, it isn't working - /dev/usb/lp0 always has 660. But this is good enough to allow printing.
In this Slacko, it isn't working - /dev/usb/lp0 always has 660. But this is good enough to allow printing.
And the permissions is I believe the problem. SFR touched on it.rcrsn51 wrote:Even though my USB printers work, there is something else going on with udev. In other Puppies, /etc/udev/rules.d/55-cups.rule is responsible for giving the printer device nodes 666 permissions.
In this Slacko, it isn't working - /dev/usb/lp0 always has 660. But this is good enough to allow printing.
Now, the bug in woof is setting a new variable, DEVTMPFSFLG to 2 in the initrd and /etc/rc.d/rc.sysinit. It shouldn't becuase the condition is if udev >= 176. We are using 167. Our DEVTMPFSFLG var should be 0. However it is working anyway.
Here are the relevant lines from rc.sysinit (@line 395)
Code: Select all
DEVTMPFSFLG=2
#130618 devtmpfs-enabled kernel, initrd may have loaded it on /dev, if DEVTMPFSFLG<>0.
if [ $DEVTMPFSFLG -ne 0 ];then
#device nodes created by kernel in initrd are all 'root' group. fix (before starting udevd)...
chmod 660 /dev/* 2>/dev/null
chmod 666 /dev/null
chmod 666 /dev/zero
chgrp tty /dev/[pt]ty*
chgrp /dev/console
chgrp video /dev/fb0
chgrp floppy /dev/fd[0-9]
chgrp disk /dev/[hs]d[a-z]*
chgrp disk /dev/fuse
chgrp disk /dev/mmcblk*
chgrp cdrom /dev/sr[0-9]
fi
Code: Select all
chmod 666 /dev/usb/* #rcrsn51
chmod -R 1777 /dev/shm #SFR
chmod 666 /dev/urandom
EDIT: one other thing.
Pemasu probably hasn't got the variable in his rc.sysinit. That block of code will error with "unary operator expected" or something because the variable isn't in quotes. Therefore that block fails to run (which is a good thing for pemasu).
Puppy Linux Blog - contact me for access
Up to you Jim, but I just did a test build with 3.4.52 (patches for f2fs worked ) and the perms problems mentioned by SFR with using Firefox as Spot have disappeared after fixing the woof bug .Jim1911 wrote:Do you need me to try this in view of 01micko's comments? If so, it will have to be tomorrow.
Jim
I'll post the info on to BK.
Puppy Linux Blog - contact me for access
I have missed this one... When did it happenedSFR wrote:@Zigbert: could you please add support for f2fs to your pmount version (see original pmount)?
Would be nice.
If the support came after Wary 5.5, I can diff that pmount with the latest.
I am the one to blame for not keeping the original pmount that I have based my version of
Sigmund
Sigmund, I just plucked this one from the recent woof tree..(attached)
---------------------------------------
---------------------------------------
ReportedSFR wrote:@Mick: did you mention to Barry about this yet (or should I do it?)? Maybe it's an easy fix for him..?
Well, in the end it's not a major issue, but could be confusing for a user who formats a partition to another filesystem and ends up with useless icon on the pinborard (unless X will be restarted).
- Attachments
-
- pmount.gz
- REAL gzip
- (7.14 KiB) Downloaded 340 times
Puppy Linux Blog - contact me for access
It makes sense now.01micko/rc.sysinit wrote:chmod 660 /dev/* 2>/dev/null
Thanks. And yes, a blank CD/DVD icon indeed doesn't show up on the pinboard and I have vague memory that it used to do this before, somewhere in 5.3.3 or 5.4...01micko wrote:Reported
@Zigbert:
Hopefully, it's just a matter of a few additional bytes in:
VALIDPARTS="`echo "$PARTSINFO" | grep -E 'f2fs|vfat|msdos...
It seems to work fine with this, but I might be wrong...
EDIT: almost forgot again - Pburn creates a debug file in /root named "test" (looks familiar ).
Greetings!
- Attachments
-
- Screenshot.jpg
- (27.39 KiB) Downloaded 654 times
Last edited by SFR on Wed 10 Jul 2013, 17:05, edited 1 time in total.
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
chmod 700 test
rcrsn51 (per your request)
Fresh clean install of 5.6
Installed hplip-3.11.10
Run: chmod 700 /usr/lib/cups/backend/usb
Run Cups
Printer was recognized instantly, setup and run a test print in about a minute!
Now... will that 'keep' or do we need to do blacklist stuff ?
>>>---Indian------>
Fresh clean install of 5.6
Installed hplip-3.11.10
Run: chmod 700 /usr/lib/cups/backend/usb
Run Cups
Printer was recognized instantly, setup and run a test print in about a minute!
Now... will that 'keep' or do we need to do blacklist stuff ?
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
Assuming that your clean install:
1. Did NOT include a previous savefile.
2. Did NOT install the above patch.
3. Did NOT run the "rmmod" command.
Then there is nothing to blacklist.
However, I have no idea why your clean install would require a different set of permissions on /usr/lib/cups/backend/usb than my clean install, or on previous Slacko versions.
Since we have no other test reports to go on, I am leaving this issue until Mick releases his next version.
1. Did NOT include a previous savefile.
2. Did NOT install the above patch.
3. Did NOT run the "rmmod" command.
Then there is nothing to blacklist.
However, I have no idea why your clean install would require a different set of permissions on /usr/lib/cups/backend/usb than my clean install, or on previous Slacko versions.
Since we have no other test reports to go on, I am leaving this issue until Mick releases his next version.
chmod 700
rcrsn51 wrote:
Assuming that your clean install:
1. Did NOT include a previous savefile.
2. Did NOT install the above patch.
3. Did NOT run the "rmmod" command.
Then there is nothing to blacklist.
------------------------------------------------------------
You assumed correct!
We'll wait for next build.
>>>---Indian------>
Assuming that your clean install:
1. Did NOT include a previous savefile.
2. Did NOT install the above patch.
3. Did NOT run the "rmmod" command.
Then there is nothing to blacklist.
------------------------------------------------------------
You assumed correct!
We'll wait for next build.
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
Since the term "alpha" generically means an early test release , "slacko-5.6 alpha" merely means an early test release of Slacko.anikin wrote:ALPHASlacko, THINSlacko, FATSlacko ...
Looks like a good naming pattern to me.
Yep, it should be part of the name, why not.
ALPHA, applied to the right thing, can sound pretty good.
When I first saw this thread, I thought it was a joint venture.