Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free
On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: > Microcode updates will be applied immediately when the microcode > packages are installed or updated: you don't have to reboot. You will > have to keep the packages installed, though: as explained above, the > microcode updates have to be reapplied at every boot. > > You can check which version of the microcode your processors are running > by looking for "microcode" lines on /proc/cpuinfo. This information is > only available on recent kernels (such as the Wheezy kernel). This did not appear to work for me automatically. I did not upgrade my kernel in the same aptitude session. Before: > $ grep microcode /proc/cpuinfo > microcode : 0x1b After installing intel-microcode and iucode-tool 0.8.3-1: > $ grep microcode /proc/cpuinfo > microcode : 0x1b After some manual fiddling > # iucode_tool --scan-system -vv > iucode_tool: cpuid kernel driver unavailable, cannot scan system processor > signatures > # modprobe cpuid > # iucode_tool --scan-system -vv > iucode_tool: trying to get CPUID information from /dev/cpu/0/cpuid > iucode_tool: system has processor(s) with signature 0x000206a7 > iucode_tool: trying to get CPUID information from /dev/cpu/1/cpuid > iucode_tool: trying to get CPUID information from /dev/cpu/2/cpuid > iucode_tool: trying to get CPUID information from /dev/cpu/3/cpuid > iucode_tool: checked the signature of 4 processor(s) > $ grep microcode /proc/cpuinfo > microcode : 0x28 > $ dpkg -S /boot/vmlinuz-$(uname -r) > linux-image-3.2.0-4-amd64: /boot/vmlinuz-3.2.0-4-amd64 > ii udev 175-7amd64/dev/ and hotplug management daem Shall I file a bug? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121106143209.GB17743@debian
Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free
On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: I would like to bring to your attention the improved support for system processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems that was recently added to [non-free] Wheezy. Alas, this will not work for XEN users because I can’t update the microcode in Dom0 with xen-hypervisor 4.1. There exist kernel patches (over a year old), but according to the xen-devel ML they are not good enough to be included in the kernel. With XEN 4.2 the hypervisor can load the CPU microcode. Would this be a reason to include XEN 4.2 in Wheezy? Stephan -- | Stephan Seitz E-Mail: s...@fsing.rootsland.net | | Public Keys: http://fsing.rootsland.net/~stse/keys.html | smime.p7s Description: S/MIME cryptographic signature
Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free
On Tue, 06 Nov 2012, Jon Dowland wrote: > On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: > > Microcode updates will be applied immediately when the microcode > > packages are installed or updated: you don't have to reboot. You will > > have to keep the packages installed, though: as explained above, the > > microcode updates have to be reapplied at every boot. > > > > You can check which version of the microcode your processors are running > > by looking for "microcode" lines on /proc/cpuinfo. This information is > > only available on recent kernels (such as the Wheezy kernel). > > This did not appear to work for me automatically. I did not upgrade my kernel > in the same aptitude session. That can also happen if you upgrade it in a previous aptitude session, but didn't reboot yet. > Before: > > microcode : 0x1b > > After installing intel-microcode and iucode-tool 0.8.3-1: > > microcode : 0x1b > > > # iucode_tool --scan-system -vv > > iucode_tool: cpuid kernel driver unavailable, cannot scan system processor > > signatures Hmm, that should happen only if iucode-tool is installed/configured after intel-microcode. Still, it did lead me to a possible cause: I am not trying to modprobe "microcode" in the intel-microcode postinst. This can indeed cause the failure to update microcode at package install time. I forget why I didn't do it that way in the first place, but that's easily fixed. Please file a bug, severity minor. I will check for any possible problems it might cause, and if I can't find any, I will fix it in unstable. Still, those reports are very valuable. I will probably try to get some information about the microcode updates on the Wheezy release notes, and this thread will go a long way to make sure no pitfals are left behind. > > $ grep microcode /proc/cpuinfo > > microcode : 0x28 And that's why these packages exist... although you might want to check if your motherboard vendor has a BIOS/UEFI update available, as it is _always_ better to have microcode updated as early as possible, and that means the BIOS/UEFI. > Shall I file a bug? Please do. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121106160553.ga25...@khazad-dum.debian.net
Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free
On Tue, 06 Nov 2012, Stephan Seitz wrote: > On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: > >I would like to bring to your attention the improved support for system > >processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems > >that was recently added to [non-free] Wheezy. > > Alas, this will not work for XEN users because I can’t update the > microcode in Dom0 with xen-hypervisor 4.1. There exist kernel > patches (over a year old), but according to the xen-devel ML they > are not good enough to be included in the kernel. > > With XEN 4.2 the hypervisor can load the CPU microcode. Would this > be a reason to include XEN 4.2 in Wheezy? I wouldn't know, please ask the xen maintainers and the release manager about it. Maybe a backport of the relevant functionality is also a possible solution. What I do know is that lack of microcode update support is a severe issue IMO. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121106160840.gb25...@khazad-dum.debian.net
Bug#692483: ITP: dnsperf -- DNS server performance testing tool
Package: wnpp Severity: wishlist Owner: Faidon Liambotis Control: block -1 by 692467 * Package name: dnsperf Version : 2.0.0.0 Upstream Author : Nominum, Inc. * URL : http://www.nominum.com/support/measurement-tools/ * License : ISC Programming Lang: C Description : DNS server performance testing tool dnsperf is a DNS server performance testing tool. It is primarily intended for measuring the performance of authoritative DNS servers, but it can also be used for measuring caching server performance in a closed laboratory environment. . Also included is resperf, a similar tool that is more suitable for testing caching servers resolving against the live Internet. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121106161554.ga6...@tty.gr
Introducing codesearch.debian.net, a regexp code search engine
Hi, I hereby announce a new Debian project: Debian Code Search. Debian Code Search is a search engine for program source code within Debian. It allows you to search all ≈ 17000 source packages, containing 130 GiB of FLOSS source code (including Debian packaging) with regular expressions. You can use the search engine at http://codesearch.debian.net/ Here are a few sample queries: • http://codesearch.debian.net/search?q=workaround+package%3Alinux • http://codesearch.debian.net/search?q=XCreateWindow • http://codesearch.debian.net/search?q=AnyEvent%3A%3AI3+filetype%3Aperl The corresponding thesis (and source code, of course) will be released soon (2013-01-15 being the deadline, but I hope I can do it earlier). I hope you find it useful and would love to hear your feedback. -- Best regards, Michael signature.asc Description: PGP signature
Re: Introducing codesearch.debian.net, a regexp code search engine
On Tue, 6 Nov 2012 19:05:43 +0100 Michael Stapelberg wrote: > Debian Code Search is a search engine for program source code within > Debian. > > It allows you to search all ≈ 17000 source packages, > containing 130 GiB of FLOSS source code (including Debian > packaging) with regular expressions. It's pleasingly quick, which is always good. Might need to be able to exclude the debian/ directory from searches. > You can use the search engine at http://codesearch.debian.net/ > Here are a few sample queries: > • http://codesearch.debian.net/search?q=workaround+package%3Alinux > • http://codesearch.debian.net/search?q=XCreateWindow > • http://codesearch.debian.net/search?q=AnyEvent%3A%3AI3+filetype%3Aperl > > The corresponding thesis (and source code, of course) will be released > soon (2013-01-15 being the deadline, but I hope I can do it > earlier). > > I hope you find it useful and would love to hear your feedback. First thing which occurs to me is that I'd prefer a summary page as the entry point for the search results - listing package, version and possibly a link to the PTS, possibly the number of hits for that package/package+version. First thing I've needed to do with every search result so far is find a relevant package within the results. The search results (and any summary page) should probably be sorted by package name too - I'm getting results from packages starting with m before package names starting with e. Maybe extend the keywords to allow regexp matching on package names? Another important step would be a way of excluding matches within comments from the results. The filetype seems a little confused in places too. Searching for things in filetype:perl I get matches in debian/control and debian/copyright. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgp4kXw5FLbf9.pgp Description: PGP signature
Re: Introducing codesearch.debian.net, a regexp code search engine
2 words: Awe some roughly speaking, how does it work internally? On Tue, Nov 6, 2012 at 7:05 PM, Michael Stapelberg wrote: > Hi, > > I hereby announce a new Debian project: Debian Code Search. > > Debian Code Search is a search engine for program source code within > Debian. > > It allows you to search all ≈ 17000 source packages, > containing 130 GiB of FLOSS source code (including Debian > packaging) with regular expressions. > > You can use the search engine at http://codesearch.debian.net/ > Here are a few sample queries: > • http://codesearch.debian.net/search?q=workaround+package%3Alinux > • http://codesearch.debian.net/search?q=XCreateWindow > • http://codesearch.debian.net/search?q=AnyEvent%3A%3AI3+filetype%3Aperl > > The corresponding thesis (and source code, of course) will be released > soon (2013-01-15 being the deadline, but I hope I can do it > earlier). > > I hope you find it useful and would love to hear your feedback. > > -- > Best regards, > Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/calkubt69c2xtzf9qvn2shkfrkor+d0tz8t-kjgjsdetjkob...@mail.gmail.com
Re: Introducing codesearch.debian.net, a regexp code search engine
LOVE IT!!! THANK YOU SO MUCH On Tue, Nov 6, 2012 at 12:05 PM, Michael Stapelberg wrote: > Hi, > > I hereby announce a new Debian project: Debian Code Search. > > Debian Code Search is a search engine for program source code within > Debian. > > It allows you to search all ≈ 17000 source packages, > containing 130 GiB of FLOSS source code (including Debian > packaging) with regular expressions. > > You can use the search engine at http://codesearch.debian.net/ > Here are a few sample queries: > • http://codesearch.debian.net/search?q=workaround+package%3Alinux > • http://codesearch.debian.net/search?q=XCreateWindow > • http://codesearch.debian.net/search?q=AnyEvent%3A%3AI3+filetype%3Aperl > > The corresponding thesis (and source code, of course) will be released > soon (2013-01-15 being the deadline, but I hope I can do it > earlier). > > I hope you find it useful and would love to hear your feedback. > > -- > Best regards, > Michael > -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 Free Software Foundation Europe Fellow http://fsfe.org/support/?h4ck3rm1k3
Re: Introducing codesearch.debian.net, a regexp code search engine
Hi alberto, alberto fuentes writes: > roughly speaking, how does it work internally? It uses a trigram index and the RE2 regular expression engine. My work is based on Russ Cox’s ideas and code published at http://swtch.com/~rsc/regexp/regexp4.html In case you are interested, I’m happy to send you (or anyone else) the current draft of my thesis, which describes the system in much more detail. In that case, just send me an email in private. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/x6ehk6fqcw@midna.zekjur.net
Re: Introducing codesearch.debian.net, a regexp code search engine
Hi Neil, Neil Williams writes: > It's pleasingly quick, which is always good. Might need to be able to > exclude the debian/ directory from searches. File regular expressions and a minus operator is already on the TODO list :-). > First thing which occurs to me is that I'd prefer a summary page as the > entry point for the search results - listing package, version and > possibly a link to the PTS, possibly the number of hits for that > package/package+version. First thing I've needed to do with every search > result so far is find a relevant package within the results. The search > results (and any summary page) should probably be sorted by package > name too - I'm getting results from packages starting with m before > package names starting with e. Changing the entry point of the search is not going to happen — I quite like the interface it currently has. However, adding a list of packages which are present in the current page of search results would be possible. Note that displaying the entire list of matching packages is unfortunately not possible because it’d require searching through all the files, which is — depending on the query — absolutely impossible when still wanting to guarantee a timely response :-). > Maybe extend the keywords to allow regexp matching on package names? I have also considered this. Probably I will resort to making the filename keyword (not yet implemented) use regular expressions and keep the package keyword an exact match. Since the package is part of the filename, complex things are possible while easy matches stay easy :-). > Another important step would be a way of excluding matches > within comments from the results. I have considered this, but when you think about it, identifiers (variable names, function names, …) and comments are really are there is searchable in source code. Could you give me a few convincing points on why it would be useful to exclude comments (that is, examples)? > The filetype seems a little confused in places too. Searching for > things in filetype:perl I get matches in debian/control and > debian/copyright. Can you give me the exact query for which this happens, please? -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/x6390mfpmu@midna.zekjur.net
Re: Introducing codesearch.debian.net, a regexp code search engine
On Tue, Nov 6, 2012 at 9:06 PM, Michael Stapelberg wrote: > Hi alberto, > > alberto fuentes writes: >> roughly speaking, how does it work internally? > It uses a trigram index and the RE2 regular expression engine. > > My work is based on Russ Cox’s ideas and code published at > http://swtch.com/~rsc/regexp/regexp4.html That read was enough to satiate my questions on how it works. :) Now some actual details would be appreciate. Like size of database, size on memory, engine running, kind of machine, number of nodes, etc... Have you run any benchmark? greets aL -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/calkubt7iuvm8r0jgkajfzl4d-nrxalpinurfpdr4-t8cysa...@mail.gmail.com
Bug#692498: ITP: bamtools -- C++ API and toolkit for manipulating BAM (genome alignment) files
X-Debbugs-Cc: debian-...@lists.debian.org X-Debbugs-Cc: debian-devel@lists.debian.org Package: wnpp Severity: wishlist Owner: debian-...@lists.debian.org * Package name: bamtools Version : 2.2 Upstream Author : Derek Barnett * URL : https://github.com/pezmaster31/bamtools * License : Expat Programming Lang: C++ Description : C++ API and toolkit for manipulating BAM (genome alignment) files -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAD=wrcla-be-tyforwnmbje0nwwyahyli+7-nbdabnmmrau...@mail.gmail.com
Re: Introducing codesearch.debian.net, a regexp code search engine
Hi, Am Dienstag, den 06.11.2012, 19:05 +0100 schrieb Michael Stapelberg: > I hereby announce a new Debian project: Debian Code Search. Great! > I hope you find it useful and would love to hear your feedback. Since you have all code extracted anyways, could you extend the page to allow for easy code browsing? Might be faster than "apt-get source; less ..." sometimes. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Re: Introducing codesearch.debian.net, a regexp code search engine
On Tue, Nov 06, 2012 at 07:05:43PM +0100, Michael Stapelberg wrote: > Hi, Hi! > I hereby announce a new Debian project: Debian Code Search. > > Debian Code Search is a search engine for program source code within > Debian. > > It allows you to search all ??? 17000 source packages, > containing 130 GiB of FLOSS source code (including Debian > packaging) with regular expressions. cool :) > You can use the search engine at http://codesearch.debian.net/ nice > I hope you find it useful and would love to hear your feedback. yes, I think it is. it's an enabler kind of tool, people can study the code in new ways and it has applications also in the security field. if you consider that Debian is one of the more extended (and regularly used) collections of software, I'm sure it will be the joy of many :) cheers, Domenico -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121106215213.GA20829@glitch
Re: Introducing codesearch.debian.net, a regexp code search engine
Hi Joachim, Joachim Breitner writes: > Since you have all code extracted anyways, could you extend the page to > allow for easy code browsing? Might be faster than "apt-get source; > less ..." sometimes. Very basic code browsing is on my agenda, but zack@ mentioned he wants to build a new sources.debian.org. Maybe his project is what you are looking for? :-) -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/x6fw4me621@midna.zekjur.net
Re: Introducing codesearch.debian.net, a regexp code search engine
Hi, Am Dienstag, den 06.11.2012, 23:10 +0100 schrieb Michael Stapelberg: > Joachim Breitner writes: > > Since you have all code extracted anyways, could you extend the page to > > allow for easy code browsing? Might be faster than "apt-get source; > > less ..." sometimes. > Very basic code browsing is on my agenda, but zack@ mentioned he wants > to build a new sources.debian.org. Maybe his project is what you are > looking for? :-) either works. Or rather, both should be one (or at least appear as one, e.g. search input field on sources.d.o; search results on codesearch.d.n linking back to sources.d.o). Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Re: Introducing codesearch.debian.net, a regexp code search engine
On Tue, 06 Nov 2012 21:22:17 +0100 Michael Stapelberg wrote: > > Another important step would be a way of excluding matches > > within comments from the results. > I have considered this, but when you think about it, identifiers > (variable names, function names, …) and comments are really are there is > searchable in source code. Could you give me a few convincing points on > why it would be useful to exclude comments (that is, examples)? Any search term which can be a variable name and frequently occurs in licence headers or doxygen markup or email addresses (copyright). (I dread to think what results come from searching just for 'debian', even with filetype:c it's all licence headers / email addresses.) http://codesearch.debian.net/search?q=QofBook+filetype%3Ac Any similar term which is frequently used across doxygen-style API docs will give a mix of comments and code. e.g. http://codesearch.debian.net/search?q=modify+filetype%3Ac That's just swamped by licences, as would be received and lots of other common words (which are, rightly or wrongly, used as variable names or as part of function names). Without exclusions on comments (and without fixes for filetype: matches below) then any common word is going to be swamped. > > The filetype seems a little confused in places too. Searching for > > things in filetype:perl I get matches in debian/control and > > debian/copyright. > Can you give me the exact query for which this happens, please? http://codesearch.debian.net/search?q=codehelp+filetype%3Aperl filetype:perl just doesn't seem to be working: http://codesearch.debian.net/search?q=QofBook+filetype%3Aperl ... lists a lot of .c files ... filetype:python does the same - some .py but then a lot more .c -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpW7FiDGAXan.pgp Description: PGP signature
Bug#692516: ITP: python-pyxs -- Pure Python bindings to XenStore
Package: wnpp Severity: wishlist Owner: Maykel Moya * Package name: python-pyxs Version : 0.3 Upstream Author : Sergei Lebedev * URL : https://github.com/selectel/pyxs * License : LGPL Programming Lang: Python Description : A pure Python XenStore client implementation which covers all of the libxs features and adds some nice Pythonic sugar on top of it. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121106234022.31431.71093.report...@andrea.mmoya.org
Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free
On 05/11/12 22:12, Henrique de Moraes Holschuh wrote: > Hello all, > > I would like to bring to your attention the improved support for system > processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems > that was recently added to [non-free] Wheezy. > > System Processors from Intel and AMD may need updates to their microcode > (sort of a control sequence for the processor) to operate correctly. > These updates fix bugs/errata that can cause anything from incorrect > processing, to code and data corruption, and system lockups. > > [...] > > You can check which version of the microcode your processors are running > by looking for "microcode" lines on /proc/cpuinfo. This information is > only available on recent kernels (such as the Wheezy kernel). Hello. My CPU is an AMD Turion(tm)X2 Dual Core Mobile RM-76, cpu family: 17, so it doesn't need the amd64-microcode package which contains microcode updates only for cpu families: 10h - 14h & 15h. But the microcode kernel module gets loaded regardless of the fact that my CPU doesn't need it. This leads to the following message being shown at boot, taining the boot process messages (basicaly it uglifies the boot process :D): microcode: failed to load file amd-ucode/microcode_amd.bin So, shouldn't the microcode module be loaded only for the CPUs that need it? I know I can blacklist the module from loading, but I think this should be handled more elegantly - read automatically - by Debian so users wouldn't have to manually fiddle with blacklisting modules. I don't exactly know how this should be done, but seeing that the microcode.ko belongs to the linux-image package, maybe there should be some script that runs when the package is installed that checks if the CPU needs a microcode update, and if it doesn't it should blacklist the module. -- Adrian Fita -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5099a17f.7010...@gmail.com
Re: Bug#692516: ITP: python-pyxs -- Pure Python bindings to XenStore
On 6 November 2012 23:40, Maykel Moya wrote: > Package: wnpp > Severity: wishlist > Owner: Maykel Moya > > * Package name: python-pyxs > Version : 0.3 > Upstream Author : Sergei Lebedev > * URL : https://github.com/selectel/pyxs > * License : LGPL > Programming Lang: Python > Description : A pure Python XenStore client implementation which covers > all of the libxs features and adds some nice Pythonic sugar on top of it. > Which python series is this module compatible with? Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANBHLUhLd-4t5_VjyXCzGB4e=bbiW=_pvtosvzak9edhoyt...@mail.gmail.com
Re: Bug#692516: ITP: python-pyxs -- Pure Python bindings to XenStore
El 07/11/12 00:55, Dmitrijs Ledkovs escribió: >> * Package name: python-pyxs >> Version : 0.3 >> > > Which python series is this module compatible with? I've used it with python 2.6 and python 2.7. Haven't tried 2.5 yet neither 'python2.x -3'/2to3. Regards, maykel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5099a93b.7040...@mmoya.org
Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free
On Wed, 07 Nov 2012, Adrian Fita wrote: > My CPU is an AMD Turion(tm)X2 Dual Core Mobile RM-76, cpu family: 17, so > it doesn't need the amd64-microcode package which contains microcode > updates only for cpu families: 10h - 14h & 15h. But the microcode kernel Family 17 (decimal) is family 11h (hexadecimal). > module gets loaded regardless of the fact that my CPU doesn't need it. Linux loads drivers for the devices it supports. Your processor supports microcode updates, and the kernel does know how to apply them, so the microcode driver will load. Also, the modular microcode driver won't complain of missing firmware files if amd64-microcode is properly installed and working (the firmware files with the microcode will be there), so something is wrong. Are you using a custom kernel? was the initramfs for the running kernel properly updated by "update-initramfs -u" ? Are you using systemd? > So, shouldn't the microcode module be loaded only for the CPUs that need > it? I know I can blacklist the module from loading, but I think this > should be handled more elegantly - read automatically - by Debian so > users wouldn't have to manually fiddle with blacklisting modules. I It is not a very good idea to overcomplicate stuff that will break the boot process should it be buggy. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121107005052.gb5...@khazad-dum.debian.net
