[gentoo-user] Re: RUBY_TARGETS and eselect ruby
On Mon, 30 Dec 2013 18:25:38 +0400, Pavel Volkov wrote: I currently set my RUBY_TARGETS in make.conf to: RUBY_TARGETS=ruby20 ruby21 World is updated. But ruby21 profile can't be selected with eselect: $ eselect ruby list Available Ruby profiles: [1] ruby20 (with Rubygems) * If I remove ruby20 from RUBY_TARGETS, there would be no profiles left. Because we haven't gotten around to that yet. Also note that only a few packages currently have ruby21 support, so eselecting it right now is not very useful yet. We should be updating the ruby eselect module in the next week or so. Hans
Re: [gentoo-user] USB permission/owner - change not allowed as root
On 31/12/2013 04:30, waben...@gmail.com wrote: Am Dienstag, 31.12.2013 um 01:38 schrieb Neil Bothwick n...@digimed.co.uk: On Mon, 30 Dec 2013 17:52:56 +0100, waben...@gmail.com wrote: For some reason or another the system doesn't like my fstab entry: /dev/sdb1 /media/stickauto noauto,rw,users 0 0 AFAIK the option to permit user mount is user and not users. Could this cause the problem? user and users are both valid, slightly different, options. THX for the info, I didn't know that. It's all fully described in the mount man page. You should read that man page to discover what mount can do. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] USB permission/owner - change not allowed as root
On 30/12/2013 19:22, Joseph wrote: On 12/30/13 17:36, Randolph Maaßen wrote: [snip] With the line in fstab: /dev/sdb1 /media/stickautonoauto,rw,users 0 0 Some USB stick are mounted as root:root and I can not change that even as root. When I remove this like from fstab. The USB stick are mounting correctly as joseph:users owner except they have different mounting location which I don't like. -- Joseph You can specify the user/group that mounts a device with some mount options. I think they are uid=username/gid=groupname but I'm not sure and unfortunatly not on my Linux box at the moment. I've tried in fstab: /dev/sdb1 /media/stickauto noauto,uid=1000,gid=100,umask=0770 0 but I'm getting an error: Error mounting system-managed device /dev/sdb1: Command-line `mount /media/stick' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, What am I missing? mount cannot auto-identify the fs type on your USB stick, or /dev/sdb1 is the wrong node. blkid as Bruce mentioned will help identify what is really going on. Also, tail -f /var/log/messages, insert the stick, and post the entries that produces. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: RUBY_TARGETS and eselect ruby
On Tuesday 31 December 2013 08:03:10 Hans de Graaff wrote: Because we haven't gotten around to that yet. Also note that only a few packages currently have ruby21 support, so eselecting it right now is not very useful yet. We should be updating the ruby eselect module in the next week or so. Ok, I see. The only ruby-related packages I have installed are ruby, rubygems, rake, json, racc and rdoc, those are build-time-deps, so eselecting ruby21 will be ok for me.
Re: [gentoo-user] Apache died this morning... why?
On 30/12/2013 15:44, Tanstaafl wrote: This happened by the way when the logs were rotated by logrotate. Maybe that is significant? Yes, that is highly significant. IIRC logrotate can work in one of two ways: 1. rename the log file and create a new empty one 2. copy the log file elsewhere and truncate the original I forget which way it does it for the moment... #1 is fast but leaves the daemon (apache or syslog) trying to write to a file that isn't there anymore. Or worse, it's writing to an open file that has been deleted and a new one with the same name still exists. #2 is slower but safer. Either way, the apache daemon has to be told it's log file went away. Not all daemons can use inotify to just find this out, some have to be told, so logrotate resets/restarts/hups them. In the case of apache it does a graceful restart (what you get with apachectl graceful). Your apache re-read it's config file at that point, found any error for php and decided to roll over and die. Ok, but, if that is the case, why did it startup just fine when I simply did /etc/init.d/apache2 start? Shouldn't it have still died? Logically, one would assume so. But that's not the full picture, many other things could have happened in the interim. Portage could have been busy with preserved libs in the background, later emerges could have fixed some issue. Or maybe Apache was having a bad day. These things happen, no use wondering about them, especially if they are not reproducible. Instead: /etc/init.d/apache2 start apachectl graceful apachectl reload and check those commands do what they ought to. If so, shrug and get on with real life. Not everything that happens on a computer is worth spending brain cycles on, and not everything has a reason you can figure out. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Apache died this morning... why?
On 2013-12-30 8:35 PM, Neil Bothwick n...@digimed.co.uk wrote: On Mon, 30 Dec 2013 08:44:45 -0500, Tanstaafl wrote: Interesting. Wonder how I missed that, or why my new install doesn't have it enabled - or is it enabled somewhere other than in /etc/portage/make.conf? It's enabled in the profile, like most defaults. You can see whether it is set by looking at the output from emerge --info. Ok, removed it from /etc/portage/make.conf, and emerge --info still shows it is set, so that wasn't the cause of the problem... Thx anyway... Like Alan said, sometimes things just happen... but I don't have to like it. ;) I like to at least try to figure out why something that *shouldn't* have happened, happened.
Re: [gentoo-user] Apache died this morning... why?
On 2013-12-31 5:57 AM, Alan McKinnon alan.mckin...@gmail.com wrote: These things happen, no use wondering about them, especially if they are not reproducible. Instead: /etc/init.d/apache2 start apachectl graceful apachectl reload and check those commands do what they ought to. Well, if the last two (it is apache2ctl though) should both result in: # /usr/sbin/apache2ctl reload * Gracefully restarting apache2 ...[OK] Then, yeah, everything seems normal... I just hate it when I have to leave things unexplained, but yeah, sometimes you have to...
Re: [gentoo-user] NFS static ports - driving me crazy...
On 2013-12-30 6:21 PM, Pavel Volkov negai...@gmail.com wrote: I've tried specifying the ports in /etc/conf.d/nfs, and /etc sysctl.conf, but I must be missing something, because every time I reboot, some other port comes up being blocked when I try to mount the shares... Anyone? The references I've found are older, so maybe there is something new I'm missing? Maybe you it's the lockd port: $ cat /etc/modprobe.d/lockd.conf options lockd nlm_udpport=13003 nlm_tcpport=13003 According to the comment at the top of /etc/conf.d/nfs, the lockd ports are set at /etc/sysctl.conf, which I now have as: # You should compile nfsd into the kernel or add it # to modules.autoload for this to work properly # TCP Port for lock manager fs.nfs.nlm_tcpport = 4001 # UDP Port for lock manager fs.nfs.nlm_udpport = 4001 One other question... What service(s) do I need to restart after making a change to test (so I don't have to reboot every time)?
Re: [gentoo-user] NFS static ports - driving me crazy...
On 2013-12-30 3:25 PM, Tanstaafl tansta...@libertytrek.org wrote: This is for NFS CLIENT... I'm mounting NFS shares from my remote QNAP NAS boxes. I've tried specifying the ports in /etc/conf.d/nfs, and /etc sysctl.conf, but I must be missing something, because every time I reboot, some other port comes up being blocked when I try to mount the shares... Anyone? The references I've found are older, so maybe there is something new I'm missing? Ok, to recap... I've made the following changes to the following config files: /etc/conf.d/nfs OPTS_RPC_MOUNTD=-p 32767 OPTS_RPC_STATD=-p 32765 -o 32766 I've also changed the lockd ports /etc/sysctl.conf # You should compile nfsd into the kernel or add it # to modules.autoload for this to work properly # TCP Port for lock manager fs.nfs.nlm_tcpport = 4001 # UDP Port for lock manager fs.nfs.nlm_udpport = 4001 But when I try to mount the remote filesystem, I see the outbound request being blocked by the firewall. If I open up the port in the firewall, it mounts immediately. But after a reboot, the next time I try mounting it, some other random port shows up in the firewall logs... This can't be all that difficult... I must be missing something obvious.
Re: [gentoo-user] NFS static ports - driving me crazy...
On 2013-12-31 7:30 AM, Tanstaafl tansta...@libertytrek.org wrote: I've made the following changes to the following config files: /etc/conf.d/nfs OPTS_RPC_MOUNTD=-p 32767 OPTS_RPC_STATD=-p 32765 -o 32766 I've also changed the lockd ports /etc/sysctl.conf # You should compile nfsd into the kernel or add it # to modules.autoload for this to work properly # TCP Port for lock manager fs.nfs.nlm_tcpport = 4001 # UDP Port for lock manager fs.nfs.nlm_udpport = 4001 But when I try to mount the remote filesystem, I see the outbound request being blocked by the firewall. If I open up the port in the firewall, it mounts immediately. But after a reboot, the next time I try mounting it, some other random port shows up in the firewall logs... This can't be all that difficult... I must be missing something obvious. # rpcinfo -p program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 32765 status 1000241 tcp 32765 status Again, this system is NOT running an NFS SERVER, I am only trying to use the nfs CLIENT to mount a remote NFS share - so, is the above what I should expect to see? something tells me no... Shouldn't the lockd ports be showing up to?
Re: [gentoo-user] IPTables question... simple as possible for starters
On Dec 30, 2013 7:31 PM, shawn wilson ag4ve...@gmail.com wrote: Minor additions to what Pandu said... On Mon, Dec 30, 2013 at 7:02 AM, Pandu Poluan pa...@poluan.info wrote: On Mon, Dec 30, 2013 at 6:07 PM, Tanstaafl tansta...@libertytrek.org wrote: The numbers within [brackets] are statistics/countes. Just replace them with [0:0], unless you really really really have a good reason to not start counting from 0... AFAIK, there's no reason this shouldn't alway be set to 0. If you want to keep your counter do --noflush NOTE: In that ServerFault posting, I suggested using the anti-attack rules in -t raw -A PREROUTING. This saves a great deal of processing, becase the raw table is just that: raw, unadulterated, unanalyzed packets. The CPU assumes nothing, it merely tries to match well-known fields' values. And because nothing is assumed, you can't prepend a conntrack rule. I can't think of why you'd ever want those packets (and I should probably move at least those 4 masks to raw) but just an FYI - no processing means no processing. Also see nftables: http://netfilter.org/projects/nftables/ Very interesting... were they aiming for something similar to *BSD's pf firewall? I personally prefer iptables-style firewall; no guessing about how a state machine will respond in strange situations. Especially since I greatly leverage ipset and '-m condition' (part of xtables-addons), which might or might not be fully supported by nftables. Rgds, --
Re: [gentoo-user] IPTables question... simple as possible for starters
On Tue, Dec 31, 2013 at 9:08 AM, Pandu Poluan pa...@poluan.info wrote: On Dec 30, 2013 7:31 PM, shawn wilson ag4ve...@gmail.com wrote: Minor additions to what Pandu said... On Mon, Dec 30, 2013 at 7:02 AM, Pandu Poluan pa...@poluan.info wrote: On Mon, Dec 30, 2013 at 6:07 PM, Tanstaafl tansta...@libertytrek.org wrote: The numbers within [brackets] are statistics/countes. Just replace them with [0:0], unless you really really really have a good reason to not start counting from 0... AFAIK, there's no reason this shouldn't alway be set to 0. If you want to keep your counter do --noflush NOTE: In that ServerFault posting, I suggested using the anti-attack rules in -t raw -A PREROUTING. This saves a great deal of processing, becase the raw table is just that: raw, unadulterated, unanalyzed packets. The CPU assumes nothing, it merely tries to match well-known fields' values. And because nothing is assumed, you can't prepend a conntrack rule. I can't think of why you'd ever want those packets (and I should probably move at least those 4 masks to raw) but just an FYI - no processing means no processing. Also see nftables: http://netfilter.org/projects/nftables/ Very interesting... were they aiming for something similar to *BSD's pf firewall? IDK (I think I remember reading that, but maybe I was just dreaming as I can't recall where), but that's sorta what it's looking like at this point. I personally prefer iptables-style firewall; no guessing about how a state machine will respond in strange situations. Especially since I greatly leverage ipset and '-m condition' (part of xtables-addons), which might or might not be fully supported by nftables. pf is easier to learn. I use iptables much more, but if I need to do something with pf, it wouldn't take me very long to re-learn what's going on so that's sorta a plus for pf. IIRC, nftables is supposed to be backward compatible. But, will x module work I hope they didn't go and break stuff too much :)
Re: [gentoo-user] USB permission/owner - change not allowed as root
On 12/31/13 10:49, Alan McKinnon wrote: On 30/12/2013 19:22, Joseph wrote: On 12/30/13 17:36, Randolph Maaßen wrote: [snip] With the line in fstab: /dev/sdb1 /media/stickautonoauto,rw,users 0 0 Some USB stick are mounted as root:root and I can not change that even as root. When I remove this like from fstab. The USB stick are mounting correctly as joseph:users owner except they have different mounting location which I don't like. -- Joseph You can specify the user/group that mounts a device with some mount options. I think they are uid=username/gid=groupname but I'm not sure and unfortunatly not on my Linux box at the moment. I've tried in fstab: /dev/sdb1 /media/stickauto noauto,uid=1000,gid=100,umask=0770 0 but I'm getting an error: Error mounting system-managed device /dev/sdb1: Command-line `mount /media/stick' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, What am I missing? mount cannot auto-identify the fs type on your USB stick, or /dev/sdb1 is the wrong node. blkid as Bruce mentioned will help identify what is really going on. Also, tail -f /var/log/messages, insert the stick, and post the entries that produces. -- Alan McKinnon alan.mckin...@gmail.com Thank you for the hints, here is the output of: tail -f /var/log/messages My line if fstab is: /dev/sdb1 /media/stick auto noauto,rw,user and this USB below file are mounted as root:root (not joseph:users) Dec 31 09:02:16 syscon7 kernel: [231771.029376] usb 8-1: new high-speed USB device number 33 using xhci_hcd Dec 31 09:02:16 syscon7 kernel: [231771.042189] usb 8-1: default language 0x0409 Dec 31 09:02:16 syscon7 kernel: [231771.043442] usb 8-1: udev 33, busnum 8, minor = 928 Dec 31 09:02:16 syscon7 kernel: [231771.043445] usb 8-1: New USB device found, idVendor=058f, idProduct=6366 Dec 31 09:02:16 syscon7 kernel: [231771.043447] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 31 09:02:16 syscon7 kernel: [231771.043448] usb 8-1: Product: Mass Storage Device Dec 31 09:02:16 syscon7 kernel: [231771.043450] usb 8-1: Manufacturer: Generic Dec 31 09:02:16 syscon7 kernel: [231771.043451] usb 8-1: SerialNumber: 058F63666433 Dec 31 09:02:16 syscon7 kernel: [231771.043515] usb 8-1: usb_probe_device Dec 31 09:02:16 syscon7 kernel: [231771.043517] usb 8-1: configuration #1 chosen from 1 choice Dec 31 09:02:16 syscon7 kernel: [231771.043614] usb 8-1: Successful Endpoint Configure command Dec 31 09:02:16 syscon7 kernel: [231771.043689] usb 8-1: adding 8-1:1.0 (config #1, interface 0) Dec 31 09:02:16 syscon7 kernel: [231771.043722] usb-storage 8-1:1.0: usb_probe_interface Dec 31 09:02:16 syscon7 kernel: [231771.043726] usb-storage 8-1:1.0: usb_probe_interface - got id Dec 31 09:02:16 syscon7 kernel: [231771.043728] usb-storage 8-1:1.0: USB Mass Storage device detected Dec 31 09:02:16 syscon7 kernel: [231771.043787] scsi41 : usb-storage 8-1:1.0 Dec 31 09:02:17 syscon7 kernel: [231772.175846] scsi 41:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0 Dec 31 09:02:17 syscon7 kernel: [231772.176055] sd 41:0:0:0: Attached scsi generic sg2 type 0 Dec 31 09:02:18 syscon7 kernel: [231772.836523] sd 41:0:0:0: [sdb] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Dec 31 09:02:18 syscon7 kernel: [231772.836932] sd 41:0:0:0: [sdb] Write Protect is off Dec 31 09:02:18 syscon7 kernel: [231772.836934] sd 41:0:0:0: [sdb] Mode Sense: 03 00 00 00 Dec 31 09:02:18 syscon7 kernel: [231772.837316] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.837318] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.838812] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.838815] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.846512] sdb: sdb1 Dec 31 09:02:18 syscon7 kernel: [231772.848062] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.848065] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.848067] sd 41:0:0:0: [sdb] Attached SCSI removable disk Dec 31 09:02:25 syscon7 udisksd[3624]: Mounted /dev/sdb1 (system) at /media/stick on behalf of uid 1000 -- Joseph
Re: [gentoo-user] Can not update @world
On Tue, 31 Dec 2013 02:46:45 -0500 Mansour Al Akeel mansour.alak...@gmail.com wrote: I haven't updated my portage tree for a while. I tried to update recently but got some conflicts. So I removed some packages manually. This didnt' solve the issue. So I decided to remove all the masked packages that I unmasked. To do so, I moved package.mask and package.accept_keyword, and did a --autounmask-write. And added: gnome-base/gnome-2.32.1-r2:2.0 to package.mask to prevent gnome3 from being pulled. You need to keep masking GNOME 3 stuff that pops up then; but note though, that GNOME 2 is near the end of its times so it might be removed some point in the future. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D signature.asc Description: PGP signature
[gentoo-user] perl update gone wrong
A remote system I manage has a problem with perl. Hasn't been updated in a while. I'm finding references to similar problems, but can't figure this out. I was updating portage, which wanted to update perl to 5.16.3, and now perl seems to be broken. perl-cleaner -p --reallyall produces: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-lang/perl:0 (dev-lang/perl-5.16.2-r1::gentoo, installed) pulled in by =dev-lang/perl-5.16 required by (perl-core/Digest-MD5-2.520.0::gentoo, ebuild scheduled for merge) =dev-lang/perl-5.16* required by (virtual/perl-File-Temp-0.220.0-r2::gentoo, ebuild scheduled for merge) (and 64 more with the same problems) (dev-lang/perl-5.12.4-r2::gentoo, ebuild scheduled for merge) pulled in by ~dev-lang/perl-5.12.4 required by (virtual/perl-Digest-SHA-5.47::gentoo, installed) (and 1 more with the same problem) (dev-lang/perl-5.14.2::gentoo, ebuild scheduled for merge) pulled in by =dev-lang/perl-5.14* required by (virtual/perl-digest-base-1.160.0-r1::gentoo, installed) (and 1 more with the same problem) It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. The following mask changes are necessary to proceed: (see package.unmask in the portage(5) man page for more details) # required by virtual/perl-digest-base-1.160.0-r1 # required by perl-core/Digest-MD5-2.520.0 # required by virtual/perl-Digest-MD5-2.520.0 # required by dev-perl/Digest-HMAC-1.30.0 # required by dev-perl/Authen-SASL-2.160.0 # required by dev-vcs/git-1.8.3.2-r1[perl] # required by dev-vcs/git:0 (argument) # /usr/portage/profiles/package.mask: # Torsten Veller t...@gentoo.org (18 Jun 2011) # Mask perl-5.14. See tracker bug #356171 =dev-lang/perl-5.14.2 NOTE: The --autounmask-keep-masks option will prevent emerge from creating package.unmask or ** keyword changes. * perl-cleaner is stopping here: * Fix the problem and start perl-cleaner again. Any ideas?
Re: [gentoo-user] USB permission/owner - change not allowed as root
On 31/12/2013 18:06, Joseph wrote: On 12/31/13 10:49, Alan McKinnon wrote: On 30/12/2013 19:22, Joseph wrote: On 12/30/13 17:36, Randolph Maaßen wrote: [snip] With the line in fstab: /dev/sdb1 /media/stickauto noauto,rw,users 0 0 Some USB stick are mounted as root:root and I can not change that even as root. When I remove this like from fstab. The USB stick are mounting correctly as joseph:users owner except they have different mounting location which I don't like. -- Joseph You can specify the user/group that mounts a device with some mount options. I think they are uid=username/gid=groupname but I'm not sure and unfortunatly not on my Linux box at the moment. I've tried in fstab: /dev/sdb1 /media/stickauto noauto,uid=1000,gid=100,umask=0770 0 but I'm getting an error: Error mounting system-managed device /dev/sdb1: Command-line `mount /media/stick' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, What am I missing? mount cannot auto-identify the fs type on your USB stick, or /dev/sdb1 is the wrong node. blkid as Bruce mentioned will help identify what is really going on. Also, tail -f /var/log/messages, insert the stick, and post the entries that produces. -- Alan McKinnon alan.mckin...@gmail.com Thank you for the hints, here is the output of: tail -f /var/log/messages My line if fstab is: /dev/sdb1/media/stickauto noauto,rw,user and this USB below file are mounted as root:root (not joseph:users) Dec 31 09:02:16 syscon7 kernel: [231771.029376] usb 8-1: new high-speed USB device number 33 using xhci_hcd Dec 31 09:02:16 syscon7 kernel: [231771.042189] usb 8-1: default language 0x0409 Dec 31 09:02:16 syscon7 kernel: [231771.043442] usb 8-1: udev 33, busnum 8, minor = 928 Dec 31 09:02:16 syscon7 kernel: [231771.043445] usb 8-1: New USB device found, idVendor=058f, idProduct=6366 Dec 31 09:02:16 syscon7 kernel: [231771.043447] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 31 09:02:16 syscon7 kernel: [231771.043448] usb 8-1: Product: Mass Storage Device Dec 31 09:02:16 syscon7 kernel: [231771.043450] usb 8-1: Manufacturer: Generic Dec 31 09:02:16 syscon7 kernel: [231771.043451] usb 8-1: SerialNumber: 058F63666433 Dec 31 09:02:16 syscon7 kernel: [231771.043515] usb 8-1: usb_probe_device Dec 31 09:02:16 syscon7 kernel: [231771.043517] usb 8-1: configuration #1 chosen from 1 choice Dec 31 09:02:16 syscon7 kernel: [231771.043614] usb 8-1: Successful Endpoint Configure command Dec 31 09:02:16 syscon7 kernel: [231771.043689] usb 8-1: adding 8-1:1.0 (config #1, interface 0) Dec 31 09:02:16 syscon7 kernel: [231771.043722] usb-storage 8-1:1.0: usb_probe_interface Dec 31 09:02:16 syscon7 kernel: [231771.043726] usb-storage 8-1:1.0: usb_probe_interface - got id Dec 31 09:02:16 syscon7 kernel: [231771.043728] usb-storage 8-1:1.0: USB Mass Storage device detected Dec 31 09:02:16 syscon7 kernel: [231771.043787] scsi41 : usb-storage 8-1:1.0 Dec 31 09:02:17 syscon7 kernel: [231772.175846] scsi 41:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0 Dec 31 09:02:17 syscon7 kernel: [231772.176055] sd 41:0:0:0: Attached scsi generic sg2 type 0 Dec 31 09:02:18 syscon7 kernel: [231772.836523] sd 41:0:0:0: [sdb] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Dec 31 09:02:18 syscon7 kernel: [231772.836932] sd 41:0:0:0: [sdb] Write Protect is off Dec 31 09:02:18 syscon7 kernel: [231772.836934] sd 41:0:0:0: [sdb] Mode Sense: 03 00 00 00 Dec 31 09:02:18 syscon7 kernel: [231772.837316] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.837318] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.838812] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.838815] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.846512] sdb: sdb1 Dec 31 09:02:18 syscon7 kernel: [231772.848062] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.848065] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.848067] sd 41:0:0:0: [sdb] Attached SCSI removable disk Dec 31 09:02:25 syscon7 udisksd[3624]: Mounted /dev/sdb1 (system) at /media/stick on behalf of uid 1000 That looks normal. Having lines in fstab for removable media is not a good solution in general - insert two sticks and the second one doesn't have a matching line (it isn't /dev/sdb1) That's why automounter apps were developed so you can get the config out of fstab and replace it with something more generic somewhere else. udisks is the app you are suing for this and it's the most common solution chosen by most DEs. When was udisks last updated on your system? What
Re: [gentoo-user] perl update gone wrong
On 2013-12-31 11:10 AM, Tanstaafl tansta...@libertytrek.org wrote: (dev-lang/perl-5.14.2::gentoo, ebuild scheduled for merge) pulled in by =dev-lang/perl-5.14* required by (virtual/perl-digest-base-1.160.0-r1::gentoo, installed) (and 1 more with the same problem) Weird... Messed around, downgraded perl to 5.16.2, then just tried updating virtual/perl-digest-base, which pulled in perl 5.16.3, and now all seems to be well (perl-cleaner --reallyall is running as we speak, installing a whole boatload of crap - mostly virtual/perl-whatever)...
Re: [gentoo-user] USB permission/owner - change not allowed as root
Am Dienstag, 31.12.2013 um 10:31 schrieb Alan McKinnon alan.mckin...@gmail.com: On 31/12/2013 04:30, waben...@gmail.com wrote: Am Dienstag, 31.12.2013 um 01:38 schrieb Neil Bothwick n...@digimed.co.uk: On Mon, 30 Dec 2013 17:52:56 +0100, waben...@gmail.com wrote: For some reason or another the system doesn't like my fstab entry: /dev/sdb1 /media/stickauto noauto,rw,users 0 0 AFAIK the option to permit user mount is user and not users. Could this cause the problem? user and users are both valid, slightly different, options. THX for the info, I didn't know that. It's all fully described in the mount man page. You should read that man page to discover what mount can do. THX for the hint. It's always good to RTFM. :-) In the meantime I read the man page and now I understand the difference between the users and the user option. But as I'm the only physical user on my computer it doesn't makes a difference for me.
Re: [gentoo-user] Firefox 24.1.1 - and PFD viewer UGLY fonts
Am Montag, 30.12.2013 um 22:03 schrieb Bruce Hill da...@happypenguincomputers.com: On Mon, Dec 30, 2013 at 07:38:00PM -0700, Joseph wrote: I just upgraded to Firefox-24.1.1 and when an online pdf file is generated some ugly view pops up that is using monospace fonts impossible to read and it looks ugly on a print out. Is there a solution to it? How about giving a link to that file? How does this one look? http://www.adobe.com/content/dam/Adobe/en/products/acrobat/pdfs/adobe-acrobat-xi-pdf-sanitization-remove-hidden-data-from-pdf-files-tutorial-ue.pdf Cheers, Bruce I have exact the same problem and found no solution so far.
Re: [gentoo-user] Firefox 24.1.1 - and PFD viewer UGLY fonts
On 12/31/13 18:47, waben...@gmail.com wrote: Am Montag, 30.12.2013 um 22:03 schrieb Bruce Hill da...@happypenguincomputers.com: On Mon, Dec 30, 2013 at 07:38:00PM -0700, Joseph wrote: I just upgraded to Firefox-24.1.1 and when an online pdf file is generated some ugly view pops up that is using monospace fonts impossible to read and it looks ugly on a print out. Is there a solution to it? How about giving a link to that file? How does this one look? http://www.adobe.com/content/dam/Adobe/en/products/acrobat/pdfs/adobe-acrobat-xi-pdf-sanitization-remove-hidden-data-from-pdf-files-tutorial-ue.pdf Cheers, Bruce I have exact the same problem and found no solution so far. One solution is to disable Firefox preview in Preference -- Application Portable Document Format (disable preview) it will revert to original setting (based on your options) allowing you to download and save the PDF file, this way it the fonts will look normal. I think that Firefox preview has a build in limited number of fonts, it is not using system fonts (I might be wrong). -- Joseph
Re: [gentoo-user] USB permission/owner - change not allowed as root
On Tue, Dec 31, 2013 at 09:06:38AM -0700, Joseph wrote: Thank you for the hints, here is the output of: tail -f /var/log/messages My line if fstab is: /dev/sdb1 /media/stickautonoauto,rw,user and this USB below file are mounted as root:root (not joseph:users) Dec 31 09:02:16 syscon7 kernel: [231771.029376] usb 8-1: new high-speed USB device number 33 using xhci_hcd Dec 31 09:02:16 syscon7 kernel: [231771.042189] usb 8-1: default language 0x0409 Dec 31 09:02:16 syscon7 kernel: [231771.043442] usb 8-1: udev 33, busnum 8, minor = 928 Dec 31 09:02:16 syscon7 kernel: [231771.043445] usb 8-1: New USB device found, idVendor=058f, idProduct=6366 Dec 31 09:02:16 syscon7 kernel: [231771.043447] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 31 09:02:16 syscon7 kernel: [231771.043448] usb 8-1: Product: Mass Storage Device Dec 31 09:02:16 syscon7 kernel: [231771.043450] usb 8-1: Manufacturer: Generic Dec 31 09:02:16 syscon7 kernel: [231771.043451] usb 8-1: SerialNumber: 058F63666433 Dec 31 09:02:16 syscon7 kernel: [231771.043515] usb 8-1: usb_probe_device Dec 31 09:02:16 syscon7 kernel: [231771.043517] usb 8-1: configuration #1 chosen from 1 choice Dec 31 09:02:16 syscon7 kernel: [231771.043614] usb 8-1: Successful Endpoint Configure command Dec 31 09:02:16 syscon7 kernel: [231771.043689] usb 8-1: adding 8-1:1.0 (config #1, interface 0) Dec 31 09:02:16 syscon7 kernel: [231771.043722] usb-storage 8-1:1.0: usb_probe_interface Dec 31 09:02:16 syscon7 kernel: [231771.043726] usb-storage 8-1:1.0: usb_probe_interface - got id Dec 31 09:02:16 syscon7 kernel: [231771.043728] usb-storage 8-1:1.0: USB Mass Storage device detected Dec 31 09:02:16 syscon7 kernel: [231771.043787] scsi41 : usb-storage 8-1:1.0 Dec 31 09:02:17 syscon7 kernel: [231772.175846] scsi 41:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0 Dec 31 09:02:17 syscon7 kernel: [231772.176055] sd 41:0:0:0: Attached scsi generic sg2 type 0 Dec 31 09:02:18 syscon7 kernel: [231772.836523] sd 41:0:0:0: [sdb] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Dec 31 09:02:18 syscon7 kernel: [231772.836932] sd 41:0:0:0: [sdb] Write Protect is off Dec 31 09:02:18 syscon7 kernel: [231772.836934] sd 41:0:0:0: [sdb] Mode Sense: 03 00 00 00 Dec 31 09:02:18 syscon7 kernel: [231772.837316] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.837318] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.838812] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.838815] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.846512] sdb: sdb1 Dec 31 09:02:18 syscon7 kernel: [231772.848062] sd 41:0:0:0: [sdb] No Caching mode page present Dec 31 09:02:18 syscon7 kernel: [231772.848065] sd 41:0:0:0: [sdb] Assuming drive cache: write through Dec 31 09:02:18 syscon7 kernel: [231772.848067] sd 41:0:0:0: [sdb] Attached SCSI removable disk Dec 31 09:02:25 syscon7 udisksd[3624]: Mounted /dev/sdb1 (system) at /media/stick on behalf of uid 1000 -- Joseph The blkid output would have shown this device, it's UUID, and filesystem. At any rate, for my flash drives I want them mounted with perms for rw for user mingdao, so I put something like this in /etc/fstab: baruch ~ # blkid /dev/sdc1 /dev/sdc1: LABEL=AMD UUID=CA00-9136 TYPE=vfat baruch ~ # grep CA00-9136 /etc/fstab UUID=CA00-9136 /AMDvfat noauto,users,rw,gid=1000,dmask=0002,fmask=0113 0 0 Different for NTFS, of course. And btw, I don't automount anything anything that is plugged in. Just my preference. As Alan mentioned, man mount would be a good read; as well as man fstab. And, did I give you a link to an article on file permissions? The difference between user and users mean simply that with user only the user who mounted the device can unmount it; with users any user can unmount it, not just the user who mounted it. Cheers, Bruce -- List replies preferred. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] Firefox 24.1.1 - and PFD viewer UGLY fonts
Am Dienstag, 31.12.2013 um 10:56 schrieb Joseph syscon...@gmail.com: On 12/31/13 18:47, waben...@gmail.com wrote: Am Montag, 30.12.2013 um 22:03 schrieb Bruce Hill da...@happypenguincomputers.com: On Mon, Dec 30, 2013 at 07:38:00PM -0700, Joseph wrote: I just upgraded to Firefox-24.1.1 and when an online pdf file is generated some ugly view pops up that is using monospace fonts impossible to read and it looks ugly on a print out. Is there a solution to it? How about giving a link to that file? How does this one look? http://www.adobe.com/content/dam/Adobe/en/products/acrobat/pdfs/adobe-acrobat-xi-pdf-sanitization-remove-hidden-data-from-pdf-files-tutorial-ue.pdf Cheers, Bruce I have exact the same problem and found no solution so far. One solution is to disable Firefox preview in Preference -- Application Portable Document Format (disable preview) it will revert to original setting (based on your options) allowing you to download and save the PDF file, this way it the fonts will look normal. I think that Firefox preview has a build in limited number of fonts, it is not using system fonts (I might be wrong). Of course that solves the ugly fonts problem and I already changed that setting, so that firefox starts the evince document viewer when I open a PDF document. But it's not a solution for the ugly preview in firefox. It would be nice to also solve this issue, but I don't know how. Nevertheless I thank you for your reply.
[gentoo-user] Re: USB permission/owner - change not allowed as root
On 12/31/2013 08:18 AM, Alan McKinnon wrote: That looks normal. Having lines in fstab for removable media is not a good solution in general - insert two sticks and the second one doesn't have a matching line (it isn't /dev/sdb1) Having a dos label on a memory stick allows you to mount it using the usual LABEL='mylabel' syntax, which is independent of the device name. sys-fs/dosfstools includes dosfslabel, which lets you put a disk label on a vfat-formatted memory stick. Since I stopped using consolekit (Canek talked me into it ;) I've had to authenticate as root for several things that were transparent before, like mounting removable drives and rebooting/powering-off the computer. While security is always annoying, I think the new behavior is probably better because it's non-M$ behavior and therefore safer.
[gentoo-user] Re: USB permission/owner - change not allowed as root
On Tue, 31 Dec 2013 14:08:18 -0800 walt w41...@gmail.com wrote: sys-fs/dosfstools includes dosfslabel, which lets you put a disk label on a vfat-formatted memory stick. Thanks for this! I had been using mtools, which works, but dosfslabel is much less annoying to use.
Re: [gentoo-user] USB permission/owner - change not allowed as root
On 12/31/13 12:03, Bruce Hill wrote: [snip] The blkid output would have shown this device, it's UUID, and filesystem. At any rate, for my flash drives I want them mounted with perms for rw for user mingdao, so I put something like this in /etc/fstab: baruch ~ # blkid /dev/sdc1 /dev/sdc1: LABEL=AMD UUID=CA00-9136 TYPE=vfat baruch ~ # grep CA00-9136 /etc/fstab UUID=CA00-9136 /AMDvfat noauto,users,rw,gid=1000,dmask=0002,fmask=0113 0 0 Different for NTFS, of course. And btw, I don't automount anything anything that is plugged in. Just my preference. As Alan mentioned, man mount would be a good read; as well as man fstab. And, did I give you a link to an article on file permissions? The difference between user and users mean simply that with user only the user who mounted the device can unmount it; with users any user can unmount it, not just the user who mounted it. Cheers, Bruce Thanks for the input. In my case blkid is not showing any LABEL It depends on what USB I insert: #blkid /dev/sdb1 /dev/sdb1: UUID=2f5fc53e-4f4c-4e74-b9c4-fca316b47fea TYPE=ext2 #blkid /dev/sdb1: UUID=3136-3934 TYPE=vfat so it would be hard to specify UUID in fstab for each momory card I insert. In the past the line in fstab: /dev/sdb1 /media/stickautonoauto,rw,users 0 0 mounted both ext2 and vfat USB as /media/stick so it is easier to reference to it in scripts. But after recent update if I have this line in fstab the ext2 USB is mounted as joseph:users but vfat USB is mounted as root:root If I remove the mounting line from fstab they mount with correct permission joseph:users but the mount point is reference as UUID and it makes it hard to reference it in bash scripts. -- Joseph
