Re: Debian Stable Updates Announcement SUA 197-1

On Tue, Mar 23, 2021 at 04:04:29PM -0700, David Christensen wrote: > On 3/23/21 12:31 PM, Andrew M.A. Cater wrote: > > On Tue, Mar 23, 2021 at 10:40:01AM -0700, David Christensen wrote: > > > > I use Stretch for my daily driver laptop (Dell Latitude E6520) and UniFi > > > Controller VPS. ... > >

Re: Debian Stable Updates Announcement SUA 197-1

On 3/23/21 12:31 PM, Andrew M.A. Cater wrote: On Tue, Mar 23, 2021 at 10:40:01AM -0700, David Christensen wrote: I use Stretch for my daily driver laptop (Dell Latitude E6520) and UniFi Controller VPS. ... I need to migrate the daily driver to Buster, but Buster does not like the Optimus grap

Re: Debian Stable Updates Announcement SUA 197-1

On Tue, Mar 23, 2021 at 10:40:01AM -0700, David Christensen wrote: > On 3/23/21 9:44 AM, David Wright wrote: > > On Tue 23 Mar 2021 at 07:52:52 (-0400), The Wanderer wrote: > > > On 2021-03-23 at 07:43, Greg Wooledge wrote: > > > > > > > I think the request was really "Please tell us how to use th

Re: Debian Stable Updates Announcement SUA 197-1

On 3/23/21 9:44 AM, David Wright wrote: On Tue 23 Mar 2021 at 07:52:52 (-0400), The Wanderer wrote: On 2021-03-23 at 07:43, Greg Wooledge wrote: I think the request was really "Please tell us how to use this buster-proposed-updates thing, which I've never heard of before." Actually I thought

Re: Debian Stable Updates Announcement SUA 197-1

On Tue 23 Mar 2021 at 09:31:52 (-0700), David Christensen wrote: > On 3/22/21 8:34 PM, David Wright wrote: > > On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote: > > > On 3/22/21 5:03 PM, Keith Wyatt wrote: > > > > > > > As o[f] > > > > now it will include the following bug fixes. Th

Re: Debian Stable Updates Announcement SUA 197-1

On Tue 23 Mar 2021 at 07:52:52 (-0400), The Wanderer wrote: > On 2021-03-23 at 07:43, Greg Wooledge wrote: > > > I think the request was really "Please tell us how to use this > > buster-proposed-updates thing, which I've never heard of before." Actually I thought David wanted to do what I did, w

Re: Debian Stable Updates Announcement SUA 197-1

On 3/23/21 4:43 AM, Greg Wooledge wrote: On Mon, Mar 22, 2021 at 10:34:12PM -0500, David Wright wrote: On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote: On 3/22/21 5:03 PM, Keith Wyatt wrote: As o[f] now it will include the following bug fixes. They can be found in "buster- pro

Re: Debian Stable Updates Announcement SUA 197-1

On 3/22/21 8:34 PM, David Wright wrote: On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote: On 3/22/21 5:03 PM, Keith Wyatt wrote: As o[f] now it will include the following bug fixes. They can be found in "buster- proposed-updates", which is carried by all official mirrors. Plea

Re: Debian Stable Updates Announcement SUA 197-1

On Ma, 23 mar 21, 07:52:52, The Wanderer wrote: > On 2021-03-23 at 07:43, Greg Wooledge wrote: > > > I think the request was really "Please tell us how to use this > > buster-proposed-updates thing, which I've never heard of before." > > > > Here's a wiki page:

Re: Debian Stable Updates Announcement SUA 197-1

On 2021-03-23 at 07:43, Greg Wooledge wrote: > I think the request was really "Please tell us how to use this > buster-proposed-updates thing, which I've never heard of before." > > Here's a wiki page: > However, I would not follow its advice litera

Re: Debian Stable Updates Announcement SUA 197-1

On Mon, Mar 22, 2021 at 10:34:12PM -0500, David Wright wrote: > On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote: > > On 3/22/21 5:03 PM, Keith Wyatt wrote: > > > > > As o[f] > > > now it will include the following bug fixes. They can be found in "buster- > > > proposed-updates", wh

Re: Debian Stable Updates Announcement SUA 197-1

On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote: > On 3/22/21 5:03 PM, Keith Wyatt wrote: > > > As o[f] > > now it will include the following bug fixes. They can be found in "buster- > > proposed-updates", which is carried by all official mirrors. > > Please provide a URL. Do you

Re: Debian Stable Updates Announcement SUA 197-1

On 3/22/21 5:03 PM, Keith Wyatt wrote: As o now it will include the following bug fixes. They can be found in "buster- proposed-updates", which is carried by all official mirrors. Please provide a URL. David

Debian Stable Updates Announcement SUA 197-1

Debian Stable Updates Announcement SUA 197-1 https://www.debian.org/ debian-rele...@lists.debian.org Adam D. Barratt March 22nd, 2021

Re: Recent flex security announcement

On Fri, Aug 26, 2016 at 9:52 PM Greg Wooledge wrote: > On Fri, Aug 26, 2016 at 12:41:54PM +, Mark Fletcher wrote: > > Stretch and sid are quoting version 2.6.1 and I can't see where they got > > that from, as upstream (sourceforge) latest version seems to be 2.6.0. > And > > 2.6.1 claims to b

Re: Recent flex security announcement

On Fri, Aug 26, 2016 at 12:41:54PM +, Mark Fletcher wrote: > Stretch and sid are quoting version 2.6.1 and I can't see where they got > that from, as upstream (sourceforge) latest version seems to be 2.6.0. And > 2.6.1 claims to be the version with the fix. *sigh* ... it just figures, as soon

Re: Recent flex security announcement

On Fri, Aug 26, 2016 at 9:19 PM Greg Wooledge wrote: > On Fri, Aug 26, 2016 at 12:11:30AM +, Mark Fletcher wrote: > > However I also have Linux machines that don't use a package management > > system, and there I also have a version of flex with the vulnerability, > so > > I wanted to get the

Re: Recent flex security announcement

On Fri, Aug 26, 2016 at 12:11:30AM +, Mark Fletcher wrote: > However I also have Linux machines that don't use a package management > system, and there I also have a version of flex with the vulnerability, so > I wanted to get the source tarball of the fixed version (v2.6.1) so I could > build

Recent flex security announcement

I have a feeling I'm about to embarrass myself by displaying either ignorance or a failure to spot the obvious, but here goes... The other day there was a Debian security advisory about the flex package. In my Debian machines, the fix can be installed by the usual apt commands. However I also hav

ANNOUNCEMENT: AMD processor microcode security update

THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE AMD PILEDRIVER MICROPROCESSORS (AMD-FX, and AMD Opteron 3300 / 4300 / 6300). AMD has released a microcode update that fixes a severe fault (also known as "erratum") on AMD Piledriver processors. This erratum can cause danger

[Debian 6 Squeeze] ANNOUNCEMENT: Intel processor microcode security update

THIS ANNOUNCEMENT IS ONLY MEANINGFUL FOR PEOPLE USING DEBIAN 6 (SQUEEZE) ON COMPUTERS WITH INTEL PROCESSORS. IT DOES NOT APPLY TO THE MORE RECENT DEBIAN RELEASES. A new Intel microcode update is available for Debian 6 (codename Squeeze). This microcode update is considered a security update

[j...@debian.org: [SECURITY] [DSA 2907-1] Announcement of long term support for Debian oldstable]

...@lists.debian.org Subject: [SECURITY] [DSA 2907-1] Announcement of long term support for Debian oldstable Reply-To: debian-secur...@lists.debian.org User-Agent: Mutt/1.5.23 (2014-03-12) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

ANNOUNCEMENT: Intel processor microcode security update (20130906)

A new Intel microcode update (dated 20130906) is available on unstable, testing and also on wheezy-backports. A Debian Stable update (through stable-proposed-updates) has been requested, but it may take some time for it to be approved. If you cannot wait, please use the wheezy-backports packages

Re: ANNOUNCEMENT: Intel processor microcode security update

On 08/09/13 09:38, Henrique de Moraes Holschuh wrote: > For a P4, which is extremely unlikely to get > any further microcode updates (unlikely but not impossible, as there are > "embedded" P4 parts that have a 10-year support life and might still get an > update for whatever reason), I guess the N

Re: Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

On Mon, Sep 9, 2013 at 12:55 AM, Henrique de Moraes Holschuh wrote: > On Sun, 08 Sep 2013, Joel Rees wrote: >> I was hoping that AMD was not going to have the license and >> non-visibility issue that plagues the Intel processor microcode >> updates. But I find this original a

Re: Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

(Thanks for obliging, Henrik. ;-) On Sun, Sep 8, 2013 at 5:34 PM, Henrik Ahlgren wrote: > On Sun, Sep 08, 2013 at 08:00:12AM +0900, Joel Rees wrote: >> (1) This requires enabling two repositories that I have been avoiding >> enabling, contrib and non-free. That means I have to watch the >> reposi

Re: Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

On 9/09/2013 2:18 AM, Volker Birk wrote: > On Sun, Sep 08, 2013 at 12:55:05PM -0300, Henrique de Moraes Holschuh wrote: >> Note that even the internal errata/fix information is bound to be really >> uninteresting anyway. Backdoors would not be documented anywhere, heck, it >> is very likely that o

Re: Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

On Sun, 08 Sep 2013, Joel Rees wrote: > I was hoping that AMD was not going to have the license and > non-visibility issue that plagues the Intel processor microcode > updates. But I find this original announcement from when Henrique made > the updater tool available: > > http:

Re: Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

On Sun, 08 Sep 2013, Henrik Ahlgren wrote: > > or synaptic to look for new tools, right? Or can we just enable those > > two repositories long enough to load Henrique's tool and the microcode > > updates, then disable them again? > > Why do you feel that you even need to ask? You are free to handl

Re: Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

On Sun, Sep 08, 2013 at 08:00:12AM +0900, Joel Rees wrote: > (1) This requires enabling two repositories that I have been avoiding > enabling, contrib and non-free. That means I have to watch the > repository more carefully when using > > apt-cache search > > or synaptic to look for new tools

Re: ANNOUNCEMENT: Intel processor microcode security update

* Henrique de Moraes Holschuh [2013-09-07 18:55 -0300]: > On Sat, 07 Sep 2013, Elimar Riesebieter wrote: > > * Elimar Riesebieter [2013-09-07 15:32 +0200]: > > > ACK, loaded as module. Thanks for the hint. But I can't find a note > > > on how to verify the new microcode is loaded? > > > > $ dme

Re: ANNOUNCEMENT: Intel processor microcode security update

* On 2013 07 Sep 16:40 -0500, Henrique de Moraes Holschuh wrote: > On Sat, 07 Sep 2013, Nate Bargmann wrote: > > I have an older P4 system with hyperthreading and it seems the updated > > microcode was loaded when I installed the package: > > It was loaded, but the messages you sent do not imply a

Re: ANNOUNCEMENT: Intel processor microcode security update

On Sun, 08 Sep 2013, shirish शिरीष wrote: > microcode bundle 1: /lib/firmware/intel-ucode/06-17-0a > 01/001: sig 0x0001067a, pf mask 0xa0, 2010-09-28, rev 0x0a0b, size 8192 > 01/002: sig 0x0001067a, pf mask 0x11, 2010-09-28, rev 0x0a0b, size 8192 > 01/003: sig 0x0001067a, pf mask 0x44, 2010-0

Microcode update conundrum (was Re: ANNOUNCEMENT: Intel processor microcode security update)

updates. But I find this original announcement from when Henrique made the updater tool available: http://lists.debian.org/debian-devel/2012/11/msg00109.html And that shoots that dream. So, (1) This requires enabling two repositories that I have been avoiding enabling, contrib and non-free. That

Re: ANNOUNCEMENT: Intel processor microcode security update

in-line :- On 9/8/13, Henrique de Moraes Holschuh wrote: > On Sat, 07 Sep 2013, shirish शिरीष wrote: >> I also read the README.gz and realized it's kinda pointless till Intel >> starts distributing some sort of errata and changelog information > > They do distribute some information, but only to

Re: ANNOUNCEMENT: Intel processor microcode security update

On Sat, 07 Sep 2013, Elimar Riesebieter wrote: > * Elimar Riesebieter [2013-09-07 15:32 +0200]: > > ACK, loaded as module. Thanks for the hint. But I can't find a note > > on how to verify the new microcode is loaded? > > $ dmesg | grep micro > microcode: CPU0 sig=0x10676, pf=0x80, revision=0x610

Re: ANNOUNCEMENT: Intel processor microcode security update

On Sat, 07 Sep 2013, shirish शिरीष wrote: > I also read the README.gz and realized it's kinda pointless till Intel > starts distributing some sort of errata and changelog information They do distribute some information, but only to Intel hardware partners which have access to microcode updates dir

Re: ANNOUNCEMENT: Intel processor microcode security update

On Sat, 07 Sep 2013, Nate Bargmann wrote: > I have an older P4 system with hyperthreading and it seems the updated > microcode was loaded when I installed the package: It was loaded, but the messages you sent do not imply an update took place. Check for microcode messages with "updated". If you f

Re: ANNOUNCEMENT: Intel processor microcode security update

at bottom :- On 9/7/13, Henrique de Moraes Holschuh wrote: > On Sat, 07 Sep 2013, shirish शिरीष wrote: >> Would installing the intel processor microcode package and the >> icu-tools have any benefit to me ? >> >> cpuid -1 | grep 'Intel Pentium' >> family = Intel Pentium Pro/II/III

Re: ANNOUNCEMENT: Intel processor microcode security update

I have an older P4 system with hyperthreading and it seems the updated microcode was loaded when I installed the package: Sep 7 08:29:23 kernel: [1268878.007882] platform microcode: firmware: agent loaded intel-ucode/0f-04-01 into memory Sep 7 08:29:23 kernel: [1268878.007943] platform microcode

Re: ANNOUNCEMENT: Intel processor microcode security update

* Elimar Riesebieter [2013-09-07 15:32 +0200]: > ACK, loaded as module. Thanks for the hint. But I can't find a note > on how to verify the new microcode is loaded? $ dmesg | grep micro microcode: CPU0 sig=0x10676, pf=0x80, revision=0x610 microcode: CPU1 sig=0x10676, pf=0x80, revision=0x610 micr

Re: ANNOUNCEMENT: Intel processor microcode security update

* Henrique de Moraes Holschuh [2013-09-07 09:13 -0300]: > > * Henrique de Moraes Holschuh [2013-09-03 09:05 -0300]: [...] > The two easy ways are: either you start using initramfs, or you > need to make sure the microcode driver is a module (it is a module in the > standard Debian kernel), and t

Re: ANNOUNCEMENT: Intel processor microcode security update

On Sat, 07 Sep 2013, Elimar Riesebieter wrote: > * Henrique de Moraes Holschuh [2013-09-03 09:05 -0300]: > > You must also update the initramfs so that the processor microcode will be > > updated after a reboot/power off. The packages will try to do it > > automatically for the running kernel and

Re: ANNOUNCEMENT: Intel processor microcode security update

On Sat, 07 Sep 2013, shirish शिरीष wrote: > Would installing the intel processor microcode package and the > icu-tools have any benefit to me ? > > cpuid -1 | grep 'Intel Pentium' > family = Intel Pentium Pro/II/III/Celeron/Core/Core > 2/Atom, AMD Athlon/Duron, Cyrix M2, VIA C3 (6)

Re: ANNOUNCEMENT: Intel processor microcode security update

* Henrique de Moraes Holschuh [2013-09-03 09:05 -0300]: [...] > You must also update the initramfs so that the processor microcode will be > updated after a reboot/power off. The packages will try to do it > automatically for the running kernel and that should be enough for most > users. > > Ho

Re: ANNOUNCEMENT: Intel processor microcode security update

Dear Henrique de Moraes Holschuh and all, Sorry for being late to the party. I installed Debian about a month ago. Would installing the intel processor microcode package and the icu-tools have any benefit to me ? cpuid -1 | grep 'Intel Pentium' family = Intel Pentium Pro/II/III/C

Re: ANNOUNCEMENT: Intel processor microcode security update

On Wed, 04 Sep 2013, David Guntner wrote: > used because of the scale of how many CPUs are affected. It's > "non-free" in the sense that they hold patents, etc., on the code that > restrict how you can use it and so on. It is non-free because of the license attached to the microcode distribution,

Re: ANNOUNCEMENT: Intel processor microcode security update

Carlo grabbed a keyboard and wrote: > Hi Verde Denim, I like to think with free software, I saw that it is a > non-free, can we trust of it ? Or this isn't againt debian free software > guidelines? Why Intel doesn't give a free microcode??? Please don't top post in a E-Mail reply, *especially* on

Re: ANNOUNCEMENT: Intel processor microcode security update

On 09/03/2013 08:42 PM, Vincent Lefevre wrote: > On 2013-09-03 16:20:56 -0700, David Christensen wrote: >> On 09/03/13 05:05, Henrique de Moraes Holschuh wrote: >>> THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL >>> MICROPROCESSORS. >> Please provid

Re: ANNOUNCEMENT: Intel processor microcode security update

wrote: > > On 2013-09-03 16:20:56 -0700, David Christensen wrote: > >> On 09/03/13 05:05, Henrique de Moraes Holschuh wrote: > >>> THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL > >>> MICROPROCESSORS. > >> Please provide a URL to the int

Re: ANNOUNCEMENT: Intel processor microcode security update

On 2013-09-04 08:49:47 +0700, Rick Valenzuela wrote: > On 09/04/2013 07:42 AM, Vincent Lefevre wrote: > > "apt-get changelog intel-microcode" leads you to: > > > > https://bugs.launchpad.net/intel/+bug/1212497 > > > > which provides the URL to the intel.com web page: > > > > https://download

Re: ANNOUNCEMENT: Intel processor microcode security update

On 09/04/2013 07:42 AM, Vincent Lefevre wrote: > "apt-get changelog intel-microcode" leads you to: > > https://bugs.launchpad.net/intel/+bug/1212497 > > which provides the URL to the intel.com web page: > > https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23082 There's also

Re: ANNOUNCEMENT: Intel processor microcode security update

On 2013-09-03 16:20:56 -0700, David Christensen wrote: > On 09/03/13 05:05, Henrique de Moraes Holschuh wrote: > >THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL > >MICROPROCESSORS. > > Please provide a URL to the intel.com web page that tells us about the >

Re: ANNOUNCEMENT: Intel processor microcode security update

On 09/03/13 05:05, Henrique de Moraes Holschuh wrote: THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL MICROPROCESSORS. Please provide a URL to the intel.com web page that tells us about the microcode update. TIA, David -- To UNSUBSCRIBE, email to debian-user-requ

Re: ANNOUNCEMENT: Intel processor microcode security update

On Tue, 03 Sep 2013, Henrique de Moraes Holschuh wrote: > Alternatively, you can install the packages manually. To get the updated > packages directly, please install the current "intel-microcode" and > "iucode-tool" packages normally, then download and install the updated > "intel-microcode" pack

ANNOUNCEMENT: Intel processor microcode security update

THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL MICROPROCESSORS. Intel has released a microcode update that fixes at least one severe fault on every desktop and mobile Intel Core i* and server Intel Xeon system processor models since (and including) the 1st generation Core-i3/i5/i7

[Thread closed] Announcement: D-community-offtopic -- Offtopic discussions happen here -- It's not a garbage can -- It's a serious list

http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/d-community-offtopic Feel free even to discuss, if the correct language for an English language list is English. Have fun :) Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Troubl

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

On Tue, 06 Nov 2012, Stan Hoeppner wrote: > So I'm left assuming that this initiative is the result of more and more > Debian users purchasing systems sufficiently new enough that errata are > being discovered, and new microcode being issued, after they receive > their systems, and these folks aren

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

On 11/6/2012 10:08 AM, Henrique de Moraes Holschuh wrote: > What I do know is that lack of microcode update support is a severe issue > IMO. Debian has survived and functioned very well with good stability, all the while lacking microcode update capability for all these years. This doesn't seem

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 [

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 instal

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 XE

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

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

On Mon, Nov 05, 2012 at 06:23:40PM -0300, Dr Beco wrote: > Hoping to add some 'reference', so we can compare actual microcode > versions, I find myself with > $ cat /proc/cpuinfo | grep microcode > microcode 0x1b > ... Slighly faster to type and run $ grep microcode /proc/cpuinfo

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

On Tue, 06 Nov 2012, Erwan David wrote: > On Mon, Nov 05, 2012 at 09:12:53PM CET, Henrique de Moraes Holschuh > said: > > 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 insta

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

On Mon, Nov 05, 2012 at 09:12:53PM CET, Henrique de Moraes Holschuh said: > > 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 > microc

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

On Mon, 05 Nov 2012, Dr Beco wrote: > Hoping to add some 'reference', so we can compare actual microcode > versions, I find myself with > $ cat /proc/cpuinfo | grep microcode > microcode 0x1b > ... > > Now, what is the version of the updated microcode? cpuinfo lists the current microcode running

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

systems > > that was recently added to [non-free] Wheezy. > > > > Thanks Henrique for the announcement. > > Hoping to add some 'reference', so we can compare actual microcode > versions, I find myself with > $ cat /proc/cpuinfo | grep microcode > mi

Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

ks Henrique for the announcement. Hoping to add some 'reference', so we can compare actual microcode versions, I find myself with $ cat /proc/cpuinfo | grep microcode microcode 0x1b ... Now, what is the version of the updated microcode? My best, Beco -- Dr Beco A.I. researcher

ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free

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 sequenc

[announcement] wordish in version 1.0

Hello, Wordish helps with the edition and testing of documentation on shell manipulation. Like the Python doctests but for the shell, it is meant to be run on a restructured text file, parses the snippet of code, executes the commands and compares the output to produce a report. It was written to

Re: melding na inloggen (announcement after login.

Roy Snabilié schreef: Als ik mij ingelogd heb krijg ik de volgende melding: Beste Roy, Dit is de Engelse lijst, er is ook een Nederlandse lijst: debian-user-du...@lists.debian.org. Hoewel je mail ook de Engelse vertaling bevat, worden andere talen dan Nederlands op deze lijst niet zo gewaar

melding na inloggen (announcement after login.

Als ik mij ingelogd heb krijg ik de volgende melding: " Er ging iets mis bij het starten van de Gnome instellingen-voorziening. Sommige dingen zoals thema's, geluiden of bureaubladinstellingen zouden verkeerd kunnen functioneren. De laatste foutmelding was: Did not receive a reply. Possible

Re: announcement

On Thu,02.Apr.09, 12:38:53, John W Foster wrote: [snip unwanted message] > Why is this on a Debian List??? Because it's spam? Please do not answer (and definitely don't quote) to messages that look like spam. Regards, Andrei -- If you can't explain it simply, you don't understand it well enou

Re: announcement

On Wed, 2009-04-01 at 18:25 +, Tzafrir Cohen wrote: > On Wed, Apr 01, 2009 at 11:30:10PM +0530, Jeffrin Jose wrote: > > hello all, > > > > I have a good news to announce. > > I have started a Fundamnetal Research(as i call ) on Installers and > > Builders. > > > > You can see the scratch wor

Re: announcement

On Wed, 2009-04-01 at 23:30 +0530, Jeffrin Jose wrote: > hello all, > > I have a good news to announce. > I have started a Fundamnetal Research(as i call ) on Installers and > Builders. > > You can see the scratch work at > http://www.trueangle.org/ and > http://www.gnuresearch.com/ > All supp

Re: announcement

On Wed, Apr 01, 2009 at 11:30:10PM +0530, Jeffrin Jose wrote: > hello all, > > I have a good news to announce. > I have started a Fundamnetal Research(as i call ) on Installers and > Builders. > > You can see the scratch work at > http-//www_trueangle_org/ and > http-//www_gnuresearch_com/ (URL

announcement

hello all, I have a good news to announce. I have started a Fundamnetal Research(as i call ) on Installers and Builders. You can see the scratch work at http://www.trueangle.org/ and http://www.gnuresearch.com/ All support in terms of suggestion and advice are welcome. I like to have donation i

Older Mozilla not supported anymore (was: Re: Sunset Announcement for Fx/Tb 1.0.x and Mozilla Suite 1.7.x -- what does it mean to sarge?)

On Apr 26 2006, Johannes Wiedersich wrote: > mozilla developer center announced 'sunset' for mozilla 1.7.x and > Firefox 1.0.x etc. ie. these won't be supported by mozilla any more. Thank you very much for this information, Johannes. > What does this mean for mozilla, firefox and thunderbird in

Sunset Announcement for Fx/Tb 1.0.x and Mozilla Suite 1.7.x -- what does it mean to sarge?

mozilla developer center announced 'sunset' for mozilla 1.7.x and Firefox 1.0.x etc. ie. these won't be supported by mozilla any more. http://developer.mozilla.org/devnews/index.php/2006/04/12/sunset-announcement-for-fxtb-10x-and-mozilla-suite-17x/ What does this mean for mozil

Announcement: The Web Security Mailing List

The Web Application Security Consortium (WASC) is proud to present 'The Web Security Mailing List'. What is The Web Security Mailing List? The Web Security Mailing List is an open information forum for discussing topics relevant to web security. Topics include, but are not limited to, industry

Re: Apt-get upgrade for security announcement

On Tue, 27 Jul 2004 10:49:43 -0700 Eric Walstad <[EMAIL PROTECTED]> wrote: > > Hi All, > > I'm having trouble trying to apt-get update/upgrade my debian unstable > machine with the latest security fixes as advertised in the > debian-security-announce emails. When I do: > > apt-get update > apt

Re: Apt-get upgrade for security announcement

On Tue, 27 Jul 2004 14:52:54 -0400 Greg Folkert <[EMAIL PROTECTED]> wrote: >On Tue, 2004-07-27 at 13:49, Eric Walstad wrote: >> Hi All, >> >> I'm having trouble trying to apt-get update/upgrade my debian unstable >> machine with the latest security fixes as advertised in the >> debian-security-an

Re: Apt-get upgrade for security announcement

On Tue, 2004-07-27 at 13:49, Eric Walstad wrote: > Hi All, > > I'm having trouble trying to apt-get update/upgrade my debian unstable > machine with the latest security fixes as advertised in the > debian-security-announce emails. When I do: > > apt-get update > apt-get upgrade > dpkg -l | gre

Apt-get upgrade for security announcement

Hi All, I'm having trouble trying to apt-get update/upgrade my debian unstable machine with the latest security fixes as advertised in the debian-security-announce emails. When I do: apt-get update apt-get upgrade dpkg -l | grep I find that the installed version of the package doesn't match

Paranoid (over?)reaction to kmail glitch and exim security announcement

nything in linbox again caused the aforementioned crash. It wasn't hard to work around, of course, and I just put it down as a wierd glitch: until I finally got around to reading the mail and discovered a security announcement concerning exim: two possible remote buffer-overflows. I

Re: [mICQ] ANNOUNCEMENT: mICQ 0.4.10.5 released

On Tue, Oct 07, 2003 at 12:17:43AM +0200, Rüdiger Kuhlmann wrote: > # ANNOUNCEMENT:mICQ 0.4.10.5 # Excellent, just upgraded from 0.4.10.4, even though I haven't yet encountered any of the bugs you mention. Anyway, great work. Thanks a lot! :)

ANNOUNCEMENT: mICQ 0.4.10.5 released

# # # # ANNOUNCEMENT:mICQ 0.4.10.5

Re: [OT, announcement] emKnoppix

Robert Michel wrote: Am Samstag, 6. September 2003 01:30 schrieb Arnt Karlsen: Do you mean would it possible to unmount the Knoppix-CD to use the CD-recorder for backups? ;))) emKnoppix is designed to run from hard disk or disk on module like devices, but with all file system compressed onto one

Re: [OT, announcement] emKnoppix

Arnt Karlsen wrote: ..DL'ed ~20% of it this far. ;-) Do tell me if you find bugs :) ..will it run off the compressed image dd'ed on a disk? Knoppix don't, unless I missed something. You do not need to dd on to disk. I am distributing the compressed knoppix file, kernel and initrd, so just add

Re: [OT, announcement] emKnoppix

On Sat, 06 Sep 2003 00:01:35 +0530, Rajkumar S <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>: > Hi all, > > For some time I have been working on a pet project of mine. To enable > Debian to run on small embedded devices. So I tweaked knoppix to bring > it under 25 MB in clooped file

Re: [OT, announcement] emKnoppix

At Sat, 06 Sep 2003 00:01:35 +0530, Rajkumar S wrote: > > For some time I have been working on a pet project of mine. To > enable Debian to run on small embedded devices. So I tweaked > knoppix to bring it under 25 MB in clooped file system > Image. Today I am happy to release it to the world. Fin

[OT, announcement] emKnoppix

Hi all, For some time I have been working on a pet project of mine. To enable Debian to run on small embedded devices. So I tweaked knoppix to bring it under 25 MB in clooped file system Image. Today I am happy to release it to the world. Find it at http://emknoppix.sarovar.org The work is far

Re: Spamassasin says Debian 3.0r1 announcement is spam...

list since the >> mailing list server runs it anyway. I guess those servers run >> stable ;-) Clive> I don't run spamassassin either, yet my copy of the Clive> announcement contained >> X-Spam-Status: No, hits=-0.8 required=4.0 >> tests

Re: Spamassasin says Debian 3.0r1 announcement is spam...

On Mon 16 Dec 2002 08:03:32 +(-0600), Shyamal Prasad wrote: > > Hmmmthe r1 update announcement got into my spam folder! I thought > this rather funny, since this is spamassassin running somewhere on a > Debian server, I just procmail on the header: > > >X-Spam-

Re: Spamassasin says Debian 3.0r1 announcement is spam...

sarge main Bob> It looks like a slightly older version (2.43) is available Bob> for stable from the same source. Thanks for all the clues. The truth is I do not run spamassassin on messages that are from a Debian list since the mailing list server runs it anyway. I guess those serve

Re: Spamassasin says Debian 3.0r1 announcement is spam...

On Mon, Dec 16, 2002 at 09:44:18AM -0500, Edward Guldemond wrote: > On Mon, Dec 16, 2002 at 08:03:32AM -0600, Shyamal Prasad wrote: > > I am sure some one else noticed, or did the annoucement just fly by > > most people? I know this is not a "bug" but I am sure it is a > > noteworthy fact ;-) > >

Re: Spamassasin says Debian 3.0r1 announcement is spam...

On Mon, Dec 16, 2002 at 08:03:32AM -0600, Shyamal Prasad wrote: > I am sure some one else noticed, or did the annoucement just fly by > most people? I know this is not a "bug" but I am sure it is a > noteworthy fact ;-) The spamassassin in sid let it through just fine. (Then again, I seriously do

Spamassasin says Debian 3.0r1 announcement is spam...

Hmmmthe r1 update announcement got into my spam folder! I thought this rather funny, since this is spamassassin running somewhere on a Debian server, I just procmail on the header: >X-Spam-Status: Yes, hits=5.1 required=5.0 tests=EXCUSE_3,ONE_HUNDRED_PC_FREE >version=2.20 I am sur

New Product Announcement

NEW PRODUCT ANNOUNCEMENT From: OUTSOURCE ENG.& MFG. INC. Sir/Madam; This note is to inform you of new watchdog board technology for maintaining continuous unattended operation of PC/Servers etc. that we have released for distribution. We are proud to announce Watchdog Control Ce

  1   2   >