Re: [gentoo-user] Unable to mount USB sticks using file manager

[Alexander Kapshuk]

On Sat, Nov 26, 2016 at 8:56 PM, Mick  wrote:
> Hi All,
>
> I'm not sure what I am missing on a laptop to be able to mount USB sticks as
> plain user.  This laptop has been built with a no-multilib profile.  The users
> are members of the plugdev group.
>
> I don't want to create an fstab entry to be able to do this, because various
> USB sticks are being plugged in at any time.  In dolphin I get this error
> reported:
>
> "An error occurred while accessing '512MB', the system responded:  An
> unspecified error has occurred:  Not authorized to perform operation."
>
> This laptop is using x11-wm/enlightenment-0.20.6, just like other laptops
> which have no problem mounting USB sticks using a file manager.  The only
> difference being other laptops have multilib profiles.
>
> When I plug in a USB disk I get:
> ==
> Nov 26 18:08:39 [dbus] [system] Activating service
> name='org.freedesktop.UDisks2' (using servicehelper)
> Nov 26 18:08:39 [udisksd] udisks daemon version 2.1.7 starting
> Nov 26 18:08:39 [dbus] [system] Successfully activated service
> 'org.freedesktop.UDisks2'
> Nov 26 18:08:39 [udisksd] Acquired the name org.freedesktop.UDisks2 on the
> system message bus
> Nov 26 18:09:11 [kernel] [  950.236065] usb 2-1: new high-speed USB device
> number 3 using ehci-pci
> Nov 26 18:09:11 [kernel] [  950.354981] usb 2-1: New USB device found,
> idVendor=1516, idProduct=8628
> Nov 26 18:09:11 [kernel] [  950.354994] usb 2-1: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> Nov 26 18:09:11 [kernel] [  950.355001] usb 2-1: Product: Gizmo!
> overdrive505724545
> Nov 26 18:09:11 [kernel] [  950.355073] usb 2-1: Manufacturer: Crucial
> Nov 26 18:09:11 [kernel] [  950.355083] usb 2-1: SerialNumber: 505724545
> Nov 26 18:09:11 [kernel] [  950.355970] usb-storage 2-1:1.0: USB Mass Storage
> device detected
> Nov 26 18:09:11 [kernel] [  950.357622] scsi host6: usb-storage 2-1:1.0
> Nov 26 18:09:11 [kernel] [  950.389457] usbcore: registered new interface
> driver uas
> Nov 26 18:09:12 [kernel] [  951.360232] scsi 6:0:0:0: Direct-Access
> Crucial  Gizmo! overdrive 1.00 PQ: 0 ANSI: 2
> Nov 26 18:09:12 [kernel] [  951.360677] sd 6:0:0:0: Attached scsi generic sg2
> type 0
> Nov 26 18:09:12 [kernel] [  951.363207] sd 6:0:0:0: [sdb] 997888 512-byte
> logical blocks: (511 MB/487 MiB)
> Nov 26 18:09:12 [kernel] [  951.365780] sd 6:0:0:0: [sdb] Write Protect is off
> Nov 26 18:09:12 [kernel] [  951.366583] sd 6:0:0:0: [sdb] No Caching mode page
> found
> Nov 26 18:09:12 [kernel] [  951.366586] sd 6:0:0:0: [sdb] Assuming drive
> cache: write through
> Nov 26 18:09:12 [kernel] [  951.370104]  sdb:
> Nov 26 18:09:12 [kernel] [  951.372102] sd 6:0:0:0: [sdb] Attached SCSI
> removable disk
> Nov 26 18:10:01 [CROND] (root) CMD (test -x /usr/sbin/run-crons &&
> /usr/sbin/run-crons)
> ==
>
>
> Udisks shows this when I plug in the USB stick:
> ==
> $ udisksctl monitor
> Monitoring the udisks daemon. Press Ctrl+C to exit.
> 18:24:41.715: The udisks-daemon is running (name-owner :1.11).
> 18:24:52.659: Added
> /org/freedesktop/UDisks2/drives/Crucial_Gizmo_21_overdrive_505724545
>   org.freedesktop.UDisks2.Drive:
> CanPowerOff:true
> Configuration:  {}
> ConnectionBus:  usb
> Ejectable:  true
> Id: Crucial-Gizmo!-overdrive-505724545
> Media:
> MediaAvailable: true
> MediaChangeDetected:true
> MediaCompatibility:
> MediaRemovable: true
> Model:  Gizmo! overdrive
> Optical:false
> OpticalBlank:   false
> OpticalNumAudioTracks:  0
> OpticalNumDataTracks:   0
> OpticalNumSessions: 0
> OpticalNumTracks:   0
> Removable:  true
> Revision:   1.00
> RotationRate:   -1
> Seat:   seat0
> Serial: 505724545
> SiblingId:
> /sys/devices/pci:00/:00:1d.7/usb2/2-1/2-1:1.0
> Size:   510918656
> SortKey:01hotplug/1480184692658374
> TimeDetected:   1480184692658374
> TimeMediaDetected:  1480184692658374
> Vendor: Crucial
> WWN:
> 18:24:52.661: Added /org/freedesktop/UDisks2/block_devices/sdb
>   org.freedesktop.UDisks2.Block:
> Configuration:  []
> CryptoBackingDevice:'/'
> Device: /dev/sdb
> DeviceNumber:   2064
> Drive:
> '/org/freedesktop/UDisks2/drives/Crucial_Gizmo_21_overdrive_505724545'
> HintAuto:   true
> HintIconName:
> HintIgnore: false
> HintName:
> HintPartitionable:  

[gentoo-user] Unable to mount USB sticks using file manager

[Mick]

Hi All,

I'm not sure what I am missing on a laptop to be able to mount USB sticks as 
plain user.  This laptop has been built with a no-multilib profile.  The users 
are members of the plugdev group.

I don't want to create an fstab entry to be able to do this, because various 
USB sticks are being plugged in at any time.  In dolphin I get this error 
reported:

"An error occurred while accessing '512MB', the system responded:  An 
unspecified error has occurred:  Not authorized to perform operation."

This laptop is using x11-wm/enlightenment-0.20.6, just like other laptops 
which have no problem mounting USB sticks using a file manager.  The only 
difference being other laptops have multilib profiles.

When I plug in a USB disk I get:
==
Nov 26 18:08:39 [dbus] [system] Activating service 
name='org.freedesktop.UDisks2' (using servicehelper)
Nov 26 18:08:39 [udisksd] udisks daemon version 2.1.7 starting
Nov 26 18:08:39 [dbus] [system] Successfully activated service 
'org.freedesktop.UDisks2'
Nov 26 18:08:39 [udisksd] Acquired the name org.freedesktop.UDisks2 on the 
system message bus
Nov 26 18:09:11 [kernel] [  950.236065] usb 2-1: new high-speed USB device 
number 3 using ehci-pci
Nov 26 18:09:11 [kernel] [  950.354981] usb 2-1: New USB device found, 
idVendor=1516, idProduct=8628
Nov 26 18:09:11 [kernel] [  950.354994] usb 2-1: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Nov 26 18:09:11 [kernel] [  950.355001] usb 2-1: Product: Gizmo! 
overdrive505724545
Nov 26 18:09:11 [kernel] [  950.355073] usb 2-1: Manufacturer: Crucial
Nov 26 18:09:11 [kernel] [  950.355083] usb 2-1: SerialNumber: 505724545
Nov 26 18:09:11 [kernel] [  950.355970] usb-storage 2-1:1.0: USB Mass Storage 
device detected
Nov 26 18:09:11 [kernel] [  950.357622] scsi host6: usb-storage 2-1:1.0
Nov 26 18:09:11 [kernel] [  950.389457] usbcore: registered new interface 
driver uas
Nov 26 18:09:12 [kernel] [  951.360232] scsi 6:0:0:0: Direct-Access 
Crucial  Gizmo! overdrive 1.00 PQ: 0 ANSI: 2
Nov 26 18:09:12 [kernel] [  951.360677] sd 6:0:0:0: Attached scsi generic sg2 
type 0
Nov 26 18:09:12 [kernel] [  951.363207] sd 6:0:0:0: [sdb] 997888 512-byte 
logical blocks: (511 MB/487 MiB)
Nov 26 18:09:12 [kernel] [  951.365780] sd 6:0:0:0: [sdb] Write Protect is off
Nov 26 18:09:12 [kernel] [  951.366583] sd 6:0:0:0: [sdb] No Caching mode page 
found
Nov 26 18:09:12 [kernel] [  951.366586] sd 6:0:0:0: [sdb] Assuming drive 
cache: write through
Nov 26 18:09:12 [kernel] [  951.370104]  sdb:
Nov 26 18:09:12 [kernel] [  951.372102] sd 6:0:0:0: [sdb] Attached SCSI 
removable disk
Nov 26 18:10:01 [CROND] (root) CMD (test -x /usr/sbin/run-crons && 
/usr/sbin/run-crons)
==


Udisks shows this when I plug in the USB stick:
==
$ udisksctl monitor
Monitoring the udisks daemon. Press Ctrl+C to exit.
18:24:41.715: The udisks-daemon is running (name-owner :1.11).
18:24:52.659: Added 
/org/freedesktop/UDisks2/drives/Crucial_Gizmo_21_overdrive_505724545
  org.freedesktop.UDisks2.Drive:
CanPowerOff:true
Configuration:  {}
ConnectionBus:  usb
Ejectable:  true
Id: Crucial-Gizmo!-overdrive-505724545
Media:  
MediaAvailable: true
MediaChangeDetected:true
MediaCompatibility: 
MediaRemovable: true
Model:  Gizmo! overdrive
Optical:false
OpticalBlank:   false
OpticalNumAudioTracks:  0
OpticalNumDataTracks:   0
OpticalNumSessions: 0
OpticalNumTracks:   0
Removable:  true
Revision:   1.00
RotationRate:   -1
Seat:   seat0
Serial: 505724545
SiblingId:  
/sys/devices/pci:00/:00:1d.7/usb2/2-1/2-1:1.0
Size:   510918656
SortKey:01hotplug/1480184692658374
TimeDetected:   1480184692658374
TimeMediaDetected:  1480184692658374
Vendor: Crucial
WWN:
18:24:52.661: Added /org/freedesktop/UDisks2/block_devices/sdb
  org.freedesktop.UDisks2.Block:
Configuration:  []
CryptoBackingDevice:'/'
Device: /dev/sdb
DeviceNumber:   2064
Drive:  
'/org/freedesktop/UDisks2/drives/Crucial_Gizmo_21_overdrive_505724545'
HintAuto:   true
HintIconName:   
HintIgnore: false
HintName:   
HintPartitionable:  true
HintSymbolicIconName:   
HintSystem: false
Id: by-uuid-289E-047D

[gentoo-user] Re: elog default lifespan

[Harry Putnam]

Daniel Campbell  writes:

> On 11/19/2016 04:21 PM, Harry Putnam wrote:
>> Mick  writes:
>> 
>>> On Saturday 19 Nov 2016 08:54:53 Harry Putnam wrote:
 After looking thru the portage man pages, the make.conf.example in
 /usr/share/portage/config, and the `Portage log wiki' it still is not
 clear to me how long elogs are kept if you use the `save' flag in
 make.conf or not.

 I did see something about '7 days' but it was not clear if that is the
 default and `save' over-rides it or what.  Or if there is another flag
 that controls there duration...

 Can anyone throw light on that?
>>>
>>> If you have logrotate then its configuration and associated cron jobs will 
>>> take 
>>> care of that.
>> 
>> What I want to know is if the elog program will do something on its
>> own... I'm wanting to hang on to the logs a good while... I saw
>> something in my readings about the elog system about 7 days... was not
>> clear if that is a defalult or what.
>> 
>> So my fear was losing them even if I am logrotate at them in some
>> capacity. So I'm asking about inside the elog program... what happens
>> to the logs and when.
>> 
>> 
> According to make.conf.example, PORTAGE_ELOG_SYSTEM="save" creates one
> log per package under $PORT_LOGDIR/elog (/var/log/portage/elog if unset).
>
> What this means is Portage will continue to use whatever path you have
> specified, and it's up to your syslogd or logrotate to determine whether
> those particular logs get deleted.
>
> I suggest looking through /etc/logrotate{.conf,.d/} and grokking things
> to determine how long your elogs will last. On my system, I noticed I
> have /etc/logrotate.d/elog-save-summary, so if you find a file like
> that, it's a good place to start. Without logrotate handling it, I see
> no reason to believe Portage will nix elog output after 7 days.
>

> In case I've missed something, could you link to the page that mentions
> 7 days? I searched through manpages and the wiki but haven't found any
> other "save" option or anything to do with elog and 7 days.

https://wiki.gentoo.org/wiki/Portage_log

[About mid page ... But this may not be considered `elogs'... ]  

Next, a number of FEATURES settings influence how Portage handles build logs.

 With binpkg-logs set, even binary package deployments will have their
 logs saved

 When clean-logs is set, regular log file clean operations are
 executed. The command that is executed is defined by PORT_LOGDIR_CLEAN
 and defaults to a retention of the files of 7 days.

 With split-log set, build logs are stored in category-named
 subdirectories of ${PORT_LOGDIR}/build

  When clean-logs is set, Portage will execute the command defined by
  PORT_LOGDIR_CLEAN after every build or unmerge operation. By
  default, the following command is used: