Re: [gentoo-user] 4G Stick Huawei E3276
On Tuesday 02 Apr 2013 16:48:26 Stefan G. Weichinger wrote: Am 02.04.2013 16:27, schrieb Stefan G. Weichinger: Am 02.04.2013 15:52, schrieb Stefan G. Weichinger: So I am back on cdc_ncm now. And I removed all the stuff I installed when testing that huawei-driver-package. phew. Next small steps (but somehow promising): I was able to connect via wvdial and pull an IPv4-IP-adress via dhcpcd ... but the connection only lasted for maybe 10 seconds. Wrong parameters? After that I have to re-plug the modem to get it working again. Update: It works. Although rather un-polished: I run wvdial ... it connects ... in a second terminal I pull an IP-adress via dhcpcd and then started a ping to some remote IP immediately. The wvdial-session then somehow loses connection to the modem or something (I have to retry and provide the logs ... right now I am so happy to have it working that I don't want to stop the connection ) this mislead me all the times as I thought it lost connectivity. But it still pings and works thereafter. So it is somehow useable for me as an admin ... not so much for an end-user. Contacted the dev from the thread ... he told me that the modules coming with linux 3.8.5 should work just fine. So it's more of a UI-issue right now ;-) connectivity is good so far ... phew! Glad to hear to you got somewhere with this effort! :-) If you configure your /etc/conf.d/net for wwan0 (or whatever it is now called) to use dhcpcd you should not need to manually attempt getting an IP address: config_wwan0=dhcpc Don't forget to create a symlink for your interface in /etc/init.d/net.lo: cd /etc/init.d ln -s net.lo net.wwan0 rc-update add net.wwan0 default PS. No idea if NM will barf with these settings, but this is the vanilla gentoo approach to network configuration and it will deal with the non-admin user problem. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] 4G Stick Huawei E3276
Am 03.04.2013 08:07, schrieb Mick: Glad to hear to you got somewhere with this effort! :-) Yes, all the precious time spent :-) If you configure your /etc/conf.d/net for wwan0 (or whatever it is now called) to use dhcpcd you should not need to manually attempt getting an IP address: config_wwan0=dhcpc Don't forget to create a symlink for your interface in /etc/init.d/net.lo: cd /etc/init.d ln -s net.lo net.wwan0 rc-update add net.wwan0 default PS. No idea if NM will barf with these settings, but this is the vanilla gentoo approach to network configuration and it will deal with the non-admin user problem. Thanks for the reminder/suggestion ... for now it's enough to get it working in the mentioned way as that stick is here for some weeks only. It's only a a test drive and I have to return it if I don't decide to do sign a contract (which is pretty expensive ...). I research if we have good enough LTE-coverage at a customer's numerous sites as we consider to back up their insufficient internet connectivity somehow. I would have to get it running with some router-distro like ipfire or pfsense to be able to use it ... - some more work ahead ;-) Thanks, Stefan
Re: [gentoo-user] stage3 only for i486?
On 03/04/2013 01:41, Daniel Frey wrote: On 04/02/2013 12:17 PM, Alan McKinnon wrote: Oh, and gentoo is fast is a nono swear word these days. That's ricing :-) Nowadays we say the benefit of gentoo is USE so you get what *you* want :-) When I'm asked, I say that gentoo is extremely flexible and can be tailored in almost infinite ways depending on its application. It's why I'm still using it on the desktop, maintenance time be damned. I've tried other distros and always come back to gentoo. The lack of flexibility with other package managers (or lack of being able to replace the default package manager) on other distros is very disappointing. Guess I've been spoiled too much... You and me both :-) To this day on the servers at work I *still* reach to USE=-avahi -zeroconf -mdns -ldap -gnutls nls -other-bundled-crap and then I remember oh wait, this is centos. Spoiled by Gentoo? Yes, indeed, most definitely. -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] dhcpcd + bonding problem
Some time ago I upgraded openrc and dhcpcd, after this upgrade I face next problem: /etc/conf.d/net has next content config_bond0=dhcp config_eth0=null slaves_eth0=eth0 For some reason dhcpcd runs on both bond0 and eth0 assigning the same address to both and of course I have double entries in routing table leading to unusable network. The only way to keep dhcpcd running on eth0 is to add denyinterfaces=eth* to /etc/dhcpcd config. dhcpcd does ethernet interfaces discovery and automatically run for any one of them that has carrier. Should config_eth0=null preventdhcpcd from dealing with eth0? Also additional observation: dhcpcd does not create /var/run/dhcpcd-bond0.pid. The only thing that is created is /var/run/dhcpcd.pid (without iface name). I do not know if this is important or not Versions: openrc is 0.11.8 dhcpcd is 5.6.4 So the question Is if this is expectable behaviour or is this a bug in initialization system? Best regards, Alexander.
Re: [gentoo-user] ntp-daemons
On Wednesday 03 April 2013 05:06:00 AM IST, Stefan G. Weichinger wrote: I always used net-misc/ntp for syncing time. Now I found net-misc/chrony and set it up looks good so far. Any opinions and experiences on the various ways of getting THE TIME? Stefan I use busybox :D
Re: [gentoo-user] Re: [way OT but interesting] Massive recent DDOS attack
On Wed, 03 Apr 2013 05:46:07 +0200, J. Roeleveld wrote: Do guinea pigs work better or worse than tribbles at calming you? Tribbles don't keep people calm indefinitely. At some point they all die from starvation and humans would follow soon after :) AFAIR guinea pigs don't last forever either... -- Neil Bothwick Processor: (n.) a device for converting sense to nonsense at the speed of electricity, or (rarely) the reverse. signature.asc Description: PGP signature
Re: [gentoo-user] ntp-daemons
Am 03.04.2013 10:28, schrieb Nilesh Govindrajan: On Wednesday 03 April 2013 05:06:00 AM IST, Stefan G. Weichinger wrote: I always used net-misc/ntp for syncing time. Now I found net-misc/chrony and set it up looks good so far. Any opinions and experiences on the various ways of getting THE TIME? Stefan I use busybox :D Interesting ;-) Switched to chrony on 4 machines already and like it ...
Re: [gentoo-user] ntp-daemons
Am 03.04.2013 01:36, schrieb Stefan G. Weichinger: I always used net-misc/ntp for syncing time. Now I found net-misc/chrony and set it up looks good so far. Any opinions and experiences on the various ways of getting THE TIME? Just two different hammers for the same nail. Another alternative is OpenNTPD btw, http://www.openntpd.org/
Re: [gentoo-user] [way OT but interesting] Massive recent DDOS attack
On Wed, 03 Apr 2013 03:33:17 +0200 Volker Armin Hemmann volkerar...@googlemail.com wrote: But somebody had to blow it up. And even more people jumped on it. Boohoo. So the next time you start insulting people, base your findings on more than a blog written by those guys who have an economical interest to blow the whole mess out of proportion. Of course, those responsible - all those guys with unpatched boxes whose little zombies took part in this attack, need a good kicking. But that is no excuse for spamming mailing lists with something the media already abused to no end. Yeah because it is all their fault. You know the cleaner down the road and not Microsoft (linux is beginning to follow a similar road awayfrom it's secure fs based and modular approach with polkit), Adobe or the IETF who though warned turned 3gbit/s into 300gbit/s. Hmmm, imagine a worm red now and with ntp so prevalent too. Blown out of proportion, really?, maybe this particular instance? I can understand the list spam argument though.
Re: [gentoo-user] ntp-daemons
Am 03.04.2013 12:21, schrieb Marc Stürmer: Just two different hammers for the same nail. Sure. I just like the quicker syncing/adjusting of chrony. Another alternative is OpenNTPD btw, http://www.openntpd.org/ I will have a look as well ;-) Thanks, Stefan
Re: [gentoo-user] dhcpcd + bonding problem
On Wed, April 3, 2013 10:04, ÐлекÑÐ°Ð½Ð´Ñ Ð¢ÑмаÑов wrote: Some time ago I upgraded openrc and dhcpcd, after this upgrade I face next problem: /etc/conf.d/net has next content config_bond0=dhcp config_eth0=null slaves_eth0=eth0 this should be: slaves_bond0=eth0 and you also might want to add: rc_net_bond0_need=net.eth0 For some reason dhcpcd runs on both bond0 and eth0 assigning the same address to both and of course I have double entries in routing table leading to unusable network. The only way to keep dhcpcd running on eth0 is to add denyinterfaces=eth* to /etc/dhcpcd config. dhcpcd does ethernet interfaces discovery and automatically run for any one of them that has carrier. Should config_eth0=null preventdhcpcd from dealing with eth0? Also additional observation: dhcpcd does not create /var/run/dhcpcd-bond0.pid. The only thing that is created is /var/run/dhcpcd.pid (without iface name). I do not know if this is important or not Versions: openrc is 0.11.8 dhcpcd is 5.6.4 So the question Is if this is expectable behaviour or is this a bug in initialization system? I don't myself use DHCP on a bonded interface, but I do use a bonded interface for 4 NICs. -- Joost
Re: [gentoo-user] Re: [way OT but interesting] Massive recent DDOS attack
On Wed, April 3, 2013 11:09, Neil Bothwick wrote: On Wed, 03 Apr 2013 05:46:07 +0200, J. Roeleveld wrote: Do guinea pigs work better or worse than tribbles at calming you? Tribbles don't keep people calm indefinitely. At some point they all die from starvation and humans would follow soon after :) AFAIR guinea pigs don't last forever either... True, but they don't eat ALL the food first ;) -- Joost
[gentoo-user] kmod requires modules in kernel??
Ok, I am prepping for the udev update this weekend, getting everything updated that doesn't pull in the udev updates. First thing I did was to eliminate the module-init-toolskmod Blocker: emerge -C module-init-tools %% emerge kmod and noted the following warnings/errors: Checking for suitable kernel configuration options... ERROR: setup CONFIG_MODULES:is not set when it should be. CONFIG_MODULE_UNLOAD: is not set when it should be. This is a server, and I do not WANT loadable modules enabled... So, how do I get rid of this warning/error? Or is this nothing to be concerned about if I do not want/need loadable modules? Thanks
[gentoo-user] kded4 keeping a flash drive busy
Hello All Issuing a fuser -m [mount-point] shows that kded4 keeps using the flash drive device, so I am not allowed to umount it. Any hints on how to solve this? The most relevant search result is in http://forum.kde.org/viewtopic.php?f=67t=99419start=15 , but I just can't believe that I have to kill any process to make something so usual. Thanks Francisco -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] kded4 keeping a flash drive busy
On 03/04/13 at 10:56am, Francisco Ares wrote: Hello All Issuing a fuser -m [mount-point] shows that kded4 keeps using the flash drive device, so I am not allowed to umount it. Any hints on how to solve this? The most relevant search result is in http://forum.kde.org/viewtopic.php?f=67t=99419start=15 , but I just can't believe that I have to kill any process to make something so usual. Thanks Francisco Hi, This is just a hunch but do you have nepomuk and friends enabled ? If so in the nepomuk server configuration is ignore all removable media set? If that's not the case then maybe look under the service manager and try disabling services that look like they might want to access your flash drive. When I glanced at that list the only one that might be guilty is the Nepomuk Search Module. -- - Yohan Pereira The difference between a Miracle and a Fact is exactly the difference between a mermaid and a seal. -- Mark Twain
Re: [gentoo-user] kmod requires modules in kernel??
On Wed, Apr 3, 2013 at 8:54 AM, Tanstaafl tansta...@libertytrek.org wrote: Ok, I am prepping for the udev update this weekend, getting everything updated that doesn't pull in the udev updates. First thing I did was to eliminate the module-init-toolskmod Blocker: emerge -C module-init-tools %% emerge kmod and noted the following warnings/errors: Checking for suitable kernel configuration options... ERROR: setup CONFIG_MODULES:is not set when it should be. CONFIG_MODULE_UNLOAD: is not set when it should be. This is a server, and I do not WANT loadable modules enabled... So, how do I get rid of this warning/error? Or is this nothing to be concerned about if I do not want/need loadable modules? Thanks The check is nonfatal; feel free to ignore it if you know what you are doing.
Re: [gentoo-user] kmod requires modules in kernel??
On 03/04/2013 14:54, Tanstaafl wrote: Ok, I am prepping for the udev update this weekend, getting everything updated that doesn't pull in the udev updates. First thing I did was to eliminate the module-init-toolskmod Blocker: emerge -C module-init-tools %% emerge kmod and noted the following warnings/errors: Checking for suitable kernel configuration options... ERROR: setup CONFIG_MODULES: is not set when it should be. CONFIG_MODULE_UNLOAD: is not set when it should be. This is a server, and I do not WANT loadable modules enabled... So, how do I get rid of this warning/error? Or is this nothing to be concerned about if I do not want/need loadable modules? Thanks The warning makes sense and is correct. kmod is a set of tools to manipulate kernel modules. It's pointless having it if the kernel does not use modules. Therefore, the error check exists. Furthermore, $ equery depends kmod * These packages depend on kmod: sys-fs/udev-200 (kmod ? =sys-apps/kmod-12) virtual/modutils-0 (sys-apps/kmod[tools]) $ equery depends virtual/modutils * These packages depend on virtual/modutils: app-emulation/virtualbox-modules-4.2.10 (kernel_linux ?virtual/modutils) app-emulation/vmware-modules-271.2 (kernel_linux ? virtual/modutils) sys-apps/rescan-scsi-bus-1.56 (virtual/modutils) $ equery depends rescan-scsi-bus * These packages depend on rescan-scsi-bus: sys-apps/sg3_utils-1.35 (=sys-apps/rescan-scsi-bus-1.24) $ equery depends sg3_utils * These packages depend on sg3_utils: media-libs/libgpod-0.8.2 (sys-apps/sg3_utils) sys-apps/rescan-scsi-bus-1.56 (=sys-apps/sg3_utils-1.24) sys-fs/udisks-1.0.4-r5 (=sys-apps/sg3_utils-1.27.20090411) It's hard to escape those hard masks. Do these steps: 1. File a bug, this behaviour is overly constrictive 2. Copy kmod to your local overlay and delete the kernel modules check 3. USE=-kmod -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Re: Udev update and persistent net rules changes
On 2013-04-02, Neil Bothwick n...@digimed.co.uk wrote: On Tue, 2 Apr 2013 20:31:10 + (UTC), Grant Edwards wrote: In Flameyes blog, he showed an example of using udev rules pretty much identical to the ones I already had, so I couldn't figure out what was different (other than the default interface names, which still aren't really predictable). They are totally predictable, As long as you know the PCI bus IDs of the slots, which board is plugged into which slot, the PCI bus IDs of the USB controllers, and which USB ports are connected to which controllers, and so on. For most of us that equates to not predictable. :) The one thing (AFAICT) that does sort of make them what I would call predictable is the support for BIOS labels for ports. I've never actually seen a machine that supported that. since the names are specified in the rules, so you can predict what the interface will be called, In _theory_ you can, but you need to gather a lot of very low-level information first. In practice, I bet nobody does that -- they just boot up the kernel and see what they get. it's what the rules file says it will be called. However, the important issue is persistence, whatever name an interface has is the name it will always have. Until you move it to a different USB port or PCI slot. Names still aren't persistent (or, in practical terms, predictable), they're just based on a different parameter than they used to be. For some people the new 'prameter' is apparently more useful -- so I guess it's an improvement. The rules renaming within the kernel namespace, eth, wlan etc, could not guarantee that because of race conditions, and the so-called persistent names from the new udev still cannot do the same for devices that can be physically moved (mainly USB). The simplest solution is to do what the news item suggests, rename the persistent-net rules file Why does the file need to be renamed? and rename the interfaces within it to not clash with the kernel. So the kernel is still using the names eth[0-n]? And there's a race condition if I use the names eth[0-n] in my rules? Same as before? That's all you need to worry about when going from 197 to 200, upgrading from earlier versions means you should act on the parts about DEVTMPFS and runlevel files. -- Grant Edwards grant.b.edwardsYow! My life is a patio at of fun! gmail.com
Re: [gentoo-user] ntp-daemons
On Wednesday 03 Apr 2013 11:38:56 Stefan G. Weichinger wrote: Am 03.04.2013 12:21, schrieb Marc Stürmer: Just two different hammers for the same nail. Sure. I just like the quicker syncing/adjusting of chrony. Another alternative is OpenNTPD btw, http://www.openntpd.org/ I will have a look as well ;-) Thanks, Stefan I use chrony on a box of mine and found that it is listening for connections on UDP 123 - I assume it is running as a server. I didn't find a way of switching this off though. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Udev update and persistent net rules changes
On Wed, 3 Apr 2013 15:13:12 + (UTC), Grant Edwards wrote: On 2013-04-02, Neil Bothwick n...@digimed.co.uk wrote: On Tue, 2 Apr 2013 20:31:10 + (UTC), Grant Edwards wrote: In Flameyes blog, he showed an example of using udev rules pretty much identical to the ones I already had, so I couldn't figure out what was different (other than the default interface names, which still aren't really predictable). They are totally predictable, As long as you know the PCI bus IDs of the slots, which board is plugged into which slot, the PCI bus IDs of the USB controllers, and which USB ports are connected to which controllers, and so on. For most of us that equates to not predictable. :) We're at cross-purposes here. You mentioned udev rules, which I took to mean user-installed rules in /etc/udev. The names udev comes up with in the absence of any rules are not completely predictable, nor persistent. [snip more cross-purpose confusion] The simplest solution is to do what the news item suggests, rename the persistent-net rules file Why does the file need to be renamed? and rename the interfaces within it to not clash with the kernel. So the kernel is still using the names eth[0-n]? And there's a race condition if I use the names eth[0-n] in my rules? Same as before? Have you read the news item? It explains why the file should be renamed and also why you should change the names in the rules to not use ethN. -- Neil Bothwick My Go this amn keyboar oesn't have any 's. signature.asc Description: PGP signature
Re: [gentoo-user] stage3 only for i486?
On Wednesday 03 April 2013 08:59:51 Alan McKinnon wrote: To this day on the servers at work I *still* reach to USE=-avahi -zeroconf -mdns -ldap -gnutls nls -other-bundled-crap Seeing -gnutls in there prompted me to go and find out why I have it on this box. Turns out that phonon requires it, indirectly, and is itself pulled in by several core components of KDE and QT. So no doing without it hereabouts. -- Peter
Re: [gentoo-user] ntp-daemons
On Wednesday 03 April 2013 00:36:00 Stefan G. Weichinger wrote: I always used net-misc/ntp for syncing time. Now I found net-misc/chrony and set it up looks good so far. Any opinions and experiences on the various ways of getting THE TIME? I've been using chrony for years now. It always seems smooth and simple to me - apart from a silly log message that's emitted any time it goes for a time source it hasn't seen before. Instead of saying it's created a new log file for it, it says it's failed to open the log file. And then it just creates it anyway. Ho hum... -- Peter
Re: [gentoo-user] Re: Udev update and persistent net rules changes
On 02-Apr-13 21:58, Alan McKinnon wrote: On 02/04/2013 21:41, Tanstaafl wrote: Are you saying that now, with udev-200, the default is the OLD way, and you have to intentionally enable the NEW way?? No, you are stilling misunderstanding. The news item goes to great lengths to explain that there is a new way and it is different from the old way. Jarry mentioned an EMPTY file, not an absent file. The ebuild does not install an empty file, so it is not the default. Well, believe me or not, but I had empty (only comments) file /etc/udev/rules.d/80-net-name-slot.rules : -- # Udev 197 and above has implemented predictable network interface names ... # To activate this function, move this file to a name that doesn't end # in .rules, or remove it then reboot your system -- And I am pretty sure I did not create it manually, so it must have come previously with some stable package, maybe udev197 (it has 25-Jan-2013 time-stamp). So yes, I had to activate new interface names manually by renaming the above mentioned file... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
[gentoo-user] Re: Udev update and persistent net rules changes
On 2013-04-03, Neil Bothwick n...@digimed.co.uk wrote: Have you read the news item? Yes. I found it rather confusing. It refers to a new format for rules, but the examples use the exact same format as the old rules. It talks about how 80-net-name-slot.rules needs to be either an empty file or a synmlink to /dev/null if you want to disable the new naming scheme -- but that doesn't seem to be right. After the upgrade my 80-net-name-slot.rules file was neither an empty file nor a symlink to /dev/null, but I'm still getting the same old names. It explains why the file should be renamed and also why you should change the names in the rules to not use ethN. The only explanation I found was the old way is now deprecated. -- Grant Edwards grant.b.edwardsYow! Kids, don't gross me at off ... Adventures with gmail.comMENTAL HYGIENE can be carried too FAR!
Re: [gentoo-user] kmod requires modules in kernel??
On Wednesday 03 April 2013 17.10:15 Alan McKinnon wrote: On 03/04/2013 14:54, Tanstaafl wrote: Ok, I am prepping for the udev update this weekend, getting everything updated that doesn't pull in the udev updates. First thing I did was to eliminate the module-init-toolskmod Blocker: emerge -C module-init-tools %% emerge kmod and noted the following warnings/errors: Checking for suitable kernel configuration options... ERROR: setup CONFIG_MODULES: is not set when it should be. CONFIG_MODULE_UNLOAD: is not set when it should be. This is a server, and I do not WANT loadable modules enabled... So, how do I get rid of this warning/error? Or is this nothing to be concerned about if I do not want/need loadable modules? Thanks The warning makes sense and is correct. kmod is a set of tools to manipulate kernel modules. It's pointless having it if the kernel does not use modules. Therefore, the error check exists. Furthermore, $ equery depends kmod * These packages depend on kmod: sys-fs/udev-200 (kmod ? =sys-apps/kmod-12) virtual/modutils-0 (sys-apps/kmod[tools]) $ equery depends virtual/modutils * These packages depend on virtual/modutils: app-emulation/virtualbox-modules-4.2.10 (kernel_linux ?virtual/modutils) app-emulation/vmware-modules-271.2 (kernel_linux ? virtual/modutils) sys-apps/rescan-scsi-bus-1.56 (virtual/modutils) $ equery depends rescan-scsi-bus * These packages depend on rescan-scsi-bus: sys-apps/sg3_utils-1.35 (=sys-apps/rescan-scsi-bus-1.24) $ equery depends sg3_utils * These packages depend on sg3_utils: media-libs/libgpod-0.8.2 (sys-apps/sg3_utils) sys-apps/rescan-scsi-bus-1.56 (=sys-apps/sg3_utils-1.24) sys-fs/udisks-1.0.4-r5 (=sys-apps/sg3_utils-1.27.20090411) It's hard to escape those hard masks. Do these steps: 1. File a bug, this behaviour is overly constrictive 2. Copy kmod to your local overlay and delete the kernel modules check 3. USE=-kmod I am having exactly the same issue, server with module-less kernel, USE=-kmod set, but portage still wants to pull in virtual/modutils and sys-apps/kmod (and I have nothing depending on either of those two). At the moment I am looking into mdev instead of udev for these servers. If you open a bug please post the bug# here. -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! ***
Re: [gentoo-user] Re: Udev update and persistent net rules changes
And if it's confusing for the 'bit jockeys' on this mailing list what do you think will be the effect on the casual user? This could have been handled better, imho. What happened to that documentation mojo Gentoo is known for? The post-install notes are a real head scratcher. On Apr 3, 2013 9:40 AM, Grant Edwards grant.b.edwa...@gmail.com wrote: On 2013-04-03, Neil Bothwick n...@digimed.co.uk wrote: Have you read the news item? Yes. I found it rather confusing. It refers to a new format for rules, but the examples use the exact same format as the old rules. It talks about how 80-net-name-slot.rules needs to be either an empty file or a synmlink to /dev/null if you want to disable the new naming scheme -- but that doesn't seem to be right. After the upgrade my 80-net-name-slot.rules file was neither an empty file nor a symlink to /dev/null, but I'm still getting the same old names. It explains why the file should be renamed and also why you should change the names in the rules to not use ethN. The only explanation I found was the old way is now deprecated. -- Grant Edwards grant.b.edwardsYow! Kids, don't gross me at off ... Adventures with gmail.comMENTAL HYGIENE can be carried too FAR!
[gentoo-user] Re: Udev update and persistent net rules changes
Hi, Grant Edwards wrote: On 2013-04-03, Neil Bothwick n...@digimed.co.uk wrote: Have you read the news item? Yes. I found it rather confusing. It refers to a new format for rules, but the examples use the exact same format as the old rules. It talks about how 80-net-name-slot.rules needs to be either an empty file or a synmlink to /dev/null if you want to disable the new naming scheme -- but that doesn't seem to be right. After the upgrade my 80-net-name-slot.rules file was neither an empty file nor a symlink to /dev/null, but I'm still getting the same old names. same for me. I followed the upgrade guide and removed any 70-* files, renamed the net.eth0 link to the new scheme net.enp0s1 just to to find out that the kernel could not bring up a network with the such a device. The machine booted fine after using eth0 instead again. One a second machine I kept eth0 immediately and it booted without problems afterwards. It explains why the file should be renamed and also why you should change the names in the rules to not use ethN. The only explanation I found was the old way is now deprecated. And the new name simply did not work. - Jörg
[gentoo-user] Re: stage3 only for i486?
Alan McKinnon alan.mckinnon at gmail.com writes: James is our embedded guy. No-one knows exactly what James does, but it involves teeny weeny systems with less RAM than your wristwatch, and somehow Gentoo runs on it. I think it's $MAGIC, he will say it is $SCIENCE, I won't argue. My X would refer to me, as an interupt processor with no return vector.I'd argue it is sporadic and random, at best . i486interesting I would point out that there has been much discussion (gentoo-dev and elsewhere) bout changing the install manuals to system-rescue based. Over the years the installation options have mutiplied, to say the least. It seems everybody has there own approach. Gentoo is like golf: eventually everybody sinks the putt... nobody (sane) keeps score! Alan McKinnon Cheers! James
Re: [gentoo-user] kded4 keeping a flash drive busy
2013/4/3 Yohan Pereira yohan.pere...@gmail.com On 03/04/13 at 10:56am, Francisco Ares wrote: Hello All Issuing a fuser -m [mount-point] shows that kded4 keeps using the flash drive device, so I am not allowed to umount it. Any hints on how to solve this? The most relevant search result is in http://forum.kde.org/viewtopic.php?f=67t=99419start=15 , but I just can't believe that I have to kill any process to make something so usual. Thanks Francisco Hi, This is just a hunch but do you have nepomuk and friends enabled ? If so in the nepomuk server configuration is ignore all removable media set? If that's not the case then maybe look under the service manager and try disabling services that look like they might want to access your flash drive. When I glanced at that list the only one that might be guilty is the Nepomuk Search Module. -- - Yohan Pereira The difference between a Miracle and a Fact is exactly the difference between a mermaid and a seal. -- Mark Twain Hi, I am sorry, I think I did not make myself clear. The only process using the flash drive is kded4. The link I sent was the closest search result about the same issue (not able to umount a flash drive). Thanks Francisco -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] kded4 keeping a flash drive busy
On 03/04/2013 20:47, Francisco Ares wrote: 2013/4/3 Yohan Pereira yohan.pere...@gmail.com mailto:yohan.pere...@gmail.com On 03/04/13 at 10:56am, Francisco Ares wrote: Hello All Issuing a fuser -m [mount-point] shows that kded4 keeps using the flash drive device, so I am not allowed to umount it. Any hints on how to solve this? The most relevant search result is in http://forum.kde.org/viewtopic.php?f=67t=99419start=15 , but I just can't believe that I have to kill any process to make something so usual. Thanks Francisco Hi, This is just a hunch but do you have nepomuk and friends enabled ? If so in the nepomuk server configuration is ignore all removable media set? If that's not the case then maybe look under the service manager and try disabling services that look like they might want to access your flash drive. When I glanced at that list the only one that might be guilty is the Nepomuk Search Module. -- - Yohan Pereira The difference between a Miracle and a Fact is exactly the difference between a mermaid and a seal. -- Mark Twain Hi, I am sorry, I think I did not make myself clear. The only process using the flash drive is kded4. The link I sent was the closest search result about the same issue (not able to umount a flash drive). How do you mount the flash drive? I find dolphin gives me quite different behaviours between using the Device Notifier widget, clicking a stored shortcut in dolphin's left sidebar and the old fashioned way on the command line. It's not unexpected that kded4 is the process using the mount point; the kioslaves are plugins and the worker process that uses them is a child of kded4 (and keeps the name kded4). My next step would be to record what ps says about the process before and after trying to umount it the first time. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] stage3 only for i486?
On 03/04/2013 17:37, Peter Humphrey wrote: On Wednesday 03 April 2013 08:59:51 Alan McKinnon wrote: To this day on the servers at work I *still* reach to USE=-avahi -zeroconf -mdns -ldap -gnutls nls -other-bundled-crap Seeing -gnutls in there prompted me to go and find out why I have it on this box. Turns out that phonon requires it, indirectly, and is itself pulled in by several core components of KDE and QT. So no doing without it hereabouts. :-) that's not my really real USE - it's just a bunch of flags I whipped up to illustrate. Many people would want to disable some of those, it was an easy way to show that Gentoo lets your tweak what support you want as opposed to Centos which does not -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: stage3 only for i486?
On 03/04/2013 20:44, James wrote: i486interesting I would point out that there has been much discussion (gentoo-dev and elsewhere) bout changing the install manuals to system-rescue based. Over the years the installation options have mutiplied, to say the least. It seems everybody has there own approach. Gentoo is like golf: eventually everybody sinks the putt... nobody (sane) keeps score! I have my own view on that. I'd say the handbook should just tell people to make a chroot in any old distro of their choice. Personally, I use RiplinuX, mostly because I've used it for years The reason I say Gentoo shouldn't worry about installers is that the typical person installing Gentoo already knows about chroots. Someone who doesn't is unlikely to consider Gentoo at all (unless they are looking to rice, but we long since moved past that). This idea will of course not be popular, I'll be told I'm trying to be elitist, and so the search for the perfect installer will continue unabated -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: Udev update and persistent net rules changes
On Wed, Apr 03, 2013 at 08:06:20PM +0200, Jörg Schaible wrote:
Hi,
Grant Edwards wrote:
On 2013-04-03, Neil Bothwick n...@digimed.co.uk wrote:
Have you read the news item?
Yes. I found it rather confusing.
It refers to a new format for rules, but the examples use the exact
same format as the old rules.
It talks about how 80-net-name-slot.rules needs to be either an empty
file or a synmlink to /dev/null if you want to disable the new naming
scheme -- but that doesn't seem to be right. After the upgrade my
80-net-name-slot.rules file was neither an empty file nor a symlink to
/dev/null, but I'm still getting the same old names.
same for me. I followed the upgrade guide and removed any 70-* files,
renamed the net.eth0 link to the new scheme net.enp0s1 just to to find out
that the kernel could not bring up a network with the such a device. The
machine booted fine after using eth0 instead again. One a second machine I
kept eth0 immediately and it booted without problems afterwards.
It explains why the file should be renamed and also why you should
change the names in the rules to not use ethN.
The only explanation I found was the old way is now deprecated.
And the new name simply did not work.
- Jörg
When the news item is too convoluted to understand without writing it on
paper, and doing a diagram of my LAN, I just get out the USB SystemRescueCD
and have it ready on first reboot. So far I've just sailed along as it's been
since before last March or so when WilliamH first put out the news item about
udev about to fubar the universe. I'd not wanted to go to or past udev-181,
but kerframil told me to stop being scared and upgrade to stable, so I did.
And here are the results, just upgrading, not changing ANY file:
mingdao@router ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@router ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t
**^t {{acl action_modeswitch build debug doc edd extras +firmware-loader
floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux
static-libs test}}
Installed versions: 200^t(05:01:58 PM 04/02/2013)(acl firmware-loader
kmod openrc -doc -gudev -hwdb -introspection -keymap -selinux -static-libs)
Homepage:http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support
(aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **^t
Installed versions: 25^t(05:02:08 PM 04/02/2013)
Homepage:http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@router ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==68:05:ca:03:05:5d, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth0
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==68:05:ca:03:05:50, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth1
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==f4:6d:04:e8:1d:d9, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth2
mingdao@server ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@server ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t
**^t {{acl action_modeswitch build debug doc edd extras +firmware-loader
floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux
static-libs test}}
Installed versions: 200^t(06:01:45 PM 04/02/2013)(acl firmware-loader
kmod openrc -doc -gudev -hwdb -introspection -keymap -selinux -static-libs)
Homepage:http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support
(aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **^t
Installed versions: 25^t(06:01:58 PM 04/02/2013)
Homepage:http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@server ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of
[gentoo-user] Re: sys-fs/udev-200 and my wireless interface
On Sunday 31 Mar 2013 18:06:19 Mick wrote: From the elog which I applied carefully and the links to Flameeyes blog kindly shared in this M/L, I thought that I would have to rename *all* my interfaces. Therefore I was surprised to find that only my eth0 changed to enp11s0, while my wlan0 stayed the same. I even rebooted to make sure and had no problem connecting wirelessly. Is this how it is supposed to be? $ ifconfig -a enp11s0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1492 inet 10.10.10.7 netmask 255.255.255.0 broadcast 10.10.10.255 inet6 fe80::226:b9ff:fe20:b49c prefixlen 64 scopeid 0x20link ether 00:26:b9:20:b4:9c txqueuelen 1000 (Ethernet) RX packets 38 bytes 946921086 (903.0 MiB) RX errors 0 dropped 132 overruns 0 frame 0 TX packets 346579 bytes 26003941 (24.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 ip6tnl0: flags=128NOARP mtu 1452 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 0 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128NOARP mtu 1500 tunnel txqueuelen 0 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 789896 bytes 914674121 (872.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 789896 bytes 914674121 (872.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sit0: flags=128NOARP mtu 1480 sit txqueuelen 0 (IPv6-in-IPv4) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4098BROADCAST,MULTICAST mtu 1500 ether 70:1a:04:d7:c3:09 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I think I may have found the reason that my wlan0 interface was not renamed, although I don't fully understand why it may be so. It seems that my wireless interface is treated as a USB device, not a PCI device, despite the hardware being on a pci-express controller. From lshw: *-pci:2 description: PCI bridge product: 5 Series/3400 Series Chipset PCI Express Root Port 2 vendor: Intel Corporation physical id: 1c.1 bus info: pci@:00:1c.1 version: 05 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:17 ioport:4000(size=4096) memory:f090-f09f ioport:f020(size=2097152) *-network description: Network controller product: BCM4312 802.11b/g LP-PHY vendor: Broadcom Corporation physical id: 0 bus info: pci@:05:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=b43-pci-bridge latency=0 resources: irq:17 memory:f090-f0903fff and further down: ... *-network description: Wireless interface physical id: 4 logical name: wlan0 serial: 70:1a:04:d7:c3:09 capabilities: ethernet physical wireless configuration: broadcast=yes driver=b43 driverversion=3.7.10-gentoo firmware=666.2 ip=XX.XXX.XX.X link=yes multicast=yes wireless=IEEE 802.11bg From lsusb: # lsusb Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:640e Microdia Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 002 Device 004: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 002 Device 005: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 002 Device 006: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card It may be that the
Re: [gentoo-user] ntp-daemons
On Wednesday 03 Apr 2013 16:41:14 Peter Humphrey wrote: On Wednesday 03 April 2013 00:36:00 Stefan G. Weichinger wrote: I always used net-misc/ntp for syncing time. Now I found net-misc/chrony and set it up looks good so far. Any opinions and experiences on the various ways of getting THE TIME? I've been using chrony for years now. It always seems smooth and simple to me - apart from a silly log message that's emitted any time it goes for a time source it hasn't seen before. Instead of saying it's created a new log file for it, it says it's failed to open the log file. And then it just creates it anyway. Ho hum... Yes, I noticed the same here. Do you have chronyc set up to signal off/online status to chronyd? If so, where do you run it from? -- Regards, Mick smime.p7s Description: S/MIME cryptographic signature
[gentoo-user] How to get pam_gnome_keyring do concurrent unlocking work with pam_ssh?
I would like my Gnome Keyring to be unlocked during login, but also run pam_ssh to unlock my ssh key. I'm pretty sure I'm running into this https://live.gnome.org/GnomeKeyring/Pam#Advanced_configuration since I have pam_ssh sufficient in system-auth. This is my system-login: authrequiredpam_tally2.so onerr=succeed authrequiredpam_shells.so authrequiredpam_nologin.so authinclude system-auth authoptionalpam_gnome_keyring.so
Re: [gentoo-user] kded4 keeping a flash drive busy
2013/4/3 Alan McKinnon alan.mckin...@gmail.com On 03/04/2013 20:47, Francisco Ares wrote: 2013/4/3 Yohan Pereira yohan.pere...@gmail.com mailto:yohan.pere...@gmail.com On 03/04/13 at 10:56am, Francisco Ares wrote: Hello All Issuing a fuser -m [mount-point] shows that kded4 keeps using the flash drive device, so I am not allowed to umount it. Any hints on how to solve this? The most relevant search result is in http://forum.kde.org/viewtopic.php?f=67t=99419start=15 , but I just can't believe that I have to kill any process to make something so usual. Thanks Francisco Hi, This is just a hunch but do you have nepomuk and friends enabled ? If so in the nepomuk server configuration is ignore all removable media set? If that's not the case then maybe look under the service manager and try disabling services that look like they might want to access your flash drive. When I glanced at that list the only one that might be guilty is the Nepomuk Search Module. -- - Yohan Pereira The difference between a Miracle and a Fact is exactly the difference between a mermaid and a seal. -- Mark Twain Hi, I am sorry, I think I did not make myself clear. The only process using the flash drive is kded4. The link I sent was the closest search result about the same issue (not able to umount a flash drive). How do you mount the flash drive? I find dolphin gives me quite different behaviours between using the Device Notifier widget, clicking a stored shortcut in dolphin's left sidebar and the old fashioned way on the command line. It's not unexpected that kded4 is the process using the mount point; the kioslaves are plugins and the worker process that uses them is a child of kded4 (and keeps the name kded4). My next step would be to record what ps says about the process before and after trying to umount it the first time. -- Alan McKinnon alan.mckin...@gmail.com Thanks, gonna try that. Francisco -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] Re: Udev update and persistent net rules changes
On Wednesday 03 Apr 2013 20:46:37 Bruce Hill wrote: Therefore, all's well that's still working! And AFAIR, on at least 2 of those machines, the 70-persistent-net.rules was never something I did manually. Right, it used to be auto-generated by udev scripts. With udev-200 you are meant to remove it along with any other files from your /etc/udev/rules.d/ If you left them there and their syntax is still valid, then udev will parse them and do as is told. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] sys-fs/udev-200 compile failed during new installation
Hello all,I was trying to reinstall gentoo on my PC and when I was emerging gentoo-sources-3.8.5,sys-fs/udev-200 was required.However,after installation of gentoo-sources,comlpilation of udev failed and there is no output of error message.And this is the output of emerge --inform =sys-fs/udev-200: Portage 2.1.11.60 (default/linux/x86/13.0/desktop/kde, gcc-4.5.4, glibc-2.15-r3, 3.8.5-gentoo i686) = System Settings = System uname: Linux-3.8.5-gentoo-i686-Intel-R-_Core-TM-_i3-2100_CPU_@_3.10GHz-with-gentoo-2.1 KiB Mem: 3625856 total, 3442248 free KiB Swap:2000892 total, 2000892 free Timestamp of tree: Wed, 03 Apr 2013 11:45:01 + ld GNU ld (GNU Binutils) 2.22 app-shells/bash: 4.2_p37 dev-lang/python: 2.7.3-r3, 3.2.3 dev-util/pkgconfig: 0.27.1 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.11.8 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.68 sys-devel/automake: 1.10.3, 1.11.6 sys-devel/binutils: 2.22-r1 sys-devel/gcc:4.5.4 sys-devel/gcc-config: 1.7.3 sys-devel/libtool:2.4-r1 sys-devel/make: 3.82-r3 sys-kernel/linux-headers: 3.6 (virtual/os-headers) sys-libs/glibc: 2.15-r3 Repositories: gentoo ACCEPT_KEYWORDS=x86 ~x86 ACCEPT_LICENSE=* -@EULA CBUILD=i686-pc-linux-gnu CFLAGS=-O2 -march=i686 -pipe CHOST=i686-pc-linux-gnu CONFIG_PROTECT=/etc CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/terminfo CXXFLAGS=-O2 -march=i686 -pipe DISTDIR=/usr/portage/distfiles FCFLAGS=-O2 -march=i686 -pipe FEATURES=assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch FFLAGS=-O2 -march=i686 -pipe GENTOO_MIRRORS=http://mirrors.163.com/gentoo/; LDFLAGS=-Wl,-O1 -Wl,--as-needed MAKEOPTS=-j4 PKGDIR=/usr/portage/packages PORTAGE_CONFIGROOT=/ PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/usr/portage PORTDIR_OVERLAY= SYNC=rsync://mirrors.163.com/gentoo-portage USE=X a52 aac acl acpi alsa avi berkdb bindist branding bzip2 cairo cdda cdr cli consolekit cracklib crypt cups cxx dbus declarative dri dts dvd dvdr emboss en encode evdev exif fam firefox flac flv fortran gdbm gif gpm hal iconv ipv6 jpeg kde keymap kipi lcms ldap libnotify mad mng modules mp3 mp4 mpeg mudflap ncurses nls nptl nvidia ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds qt3 qt3support qt4 readline rmvb sdl semantic-desktop session spell sqlite ssl startup-notification svg tcpd tiff truetype udev udisks unicode upower usb vorbis wxwidgets x264 x86 xcb xcomposite xinerama xml xorg xscreensaver xv xvid zh_CN zlib ABI_X86=32 ALSA_CARDS=ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci ALSA_PCM_PLUGINS=adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol APACHE2_MODULES=authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias CALLIGRA_FEATURES=kexi words flow plan sheets stage tables krita karbon braindump CAMERAS=ptp2 COLLECTD_PLUGINS=df interface irq load memory rrdtool swap syslog ELIBC=glibc GPSD_PROTOCOLS=ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx INPUT_DEVICES=keyboard mouse evdev KERNEL=linux LCD_DEVICES=bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text LIBREOFFICE_EXTENSIONS=presenter-console presenter-minimizer OFFICE_IMPLEMENTATION=libreoffice PHP_TARGETS=php5-3 PYTHON_SINGLE_TARGET=python2_7 PYTHON_TARGETS=python2_7 python3_2 RUBY_TARGETS=ruby18 ruby19 USERLAND=GNU VIDEO_CARDS=nvidia XTABLES_ADDONS=quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac
Re: [gentoo-user] ntp-daemons
[Sorry if this not entirely coherent: it's growing late here.] On Wednesday 03 April 2013 22:45:11 Mick wrote: Do you have chronyc set up to signal off/online status to chronyd? If so, where do you run it from? No, I don't need to bother with manual control: it just works for me. I did play with chronyc years ago but I soon got bored. I have chronyd running on my LAN server, getting its time from several hosts Out There, then internal hosts get their time from the LAN server. All very straightforward. Any time errors just ramp themselves steadily down to zero. I can show you my config files if you like. In those old 486/586 days the author used to publish a new version for each new generation of CPU, but I haven't seen that since x86_64 came on the scene. I suppose he must have found another way of calibrating his object code's execution time. Whatever the case, I'm happy that gkrellm etc. show the time to at least the nearest half-second relative to BBC time signals. I started using chrony in those old dial-up days because it can handle slow links. Also intermittent ones, by which I mean systems that shut down for some of the day, or that dual-boot with Windross,. I haven't felt a need to change since then. At that time ntpd was at a disadvantage IIRC. You might say that chrony is designed for desktop boxes rather than the servers that ntpd likes, though the edges are pretty blurred. -- Yours, happy camper of Tideswell, Peter
[gentoo-user] Big drive + UEFI boot questions
I checked the Gentoo wiki http://en.gentoo-wiki.com/wiki/UEFI about handling UEFI boot. I'm still a bit confused. The way I read it, there are 2 separate issues... * UEFI boot * GPT versus MBR partitions Apparently, I get to choose between unmasking ELILO or GRUB2 to do a UEFI boot. As near as I can tell... * A separate EFI partition (FAT32) is required * The EFI partition needs to be mounted via /etc/fstab Is that correct? -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
Re: [gentoo-user] stage3 only for i486?
On 3 April 2013, at 20:36, Alan McKinnon wrote: ... The reason I say Gentoo shouldn't worry about installers is that the typical person installing Gentoo already knows about chroots. Someone who doesn't is unlikely to consider Gentoo at all It's been a while, but I don't think I knew what a chroot was when I installed Gentoo. I can't say that I have a great understanding of chrooting today, or that I've ever used it for anything but installing Gentoo. Stroller.
Re: [gentoo-user] Big drive + UEFI boot questions
On Apr 4, 2013 4:27 AM, Walter Dnes waltd...@waltdnes.org wrote: I checked the Gentoo wiki http://en.gentoo-wiki.com/wiki/UEFI about handling UEFI boot. I'm still a bit confused. The way I read it, there are 2 separate issues... * UEFI boot * GPT versus MBR partitions Apparently, I get to choose between unmasking ELILO or GRUB2 to do a UEFI boot. As near as I can tell... * A separate EFI partition (FAT32) is required * The EFI partition needs to be mounted via /etc/fstab Is that correct? -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications For the partition: Yes and no. You have to create a sepearate efi partition (type: ef; fs: fat32) but there is no need to keep it mounted while th system is running. For the boot loader: I have no experience wit elilo, but grub 2 works well if you like the menu and autoconfig it provides. There is a 3. Way loading the kernel: efi_stub. If you compile the commandline in the kernel and you don't use an initrd enable CONFIG_EFI_STUB in the kernel and copy the bzimage to your efi partition as an .efi file and announce the kernel image instead of grub2. The arch linux wiki page was verry helpfull for me. Ps: be sure to test your kernel before using efi, there are reports that the firmware gets brickt in some cases. (It came out on samsung laptops) HTH Randolph
