在 2013-7-26 晚上8:00， <centos-request@xxxxxxxxxx>写道：
>
> Send CentOS mailing list submissions to
> centos@xxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.centos.org/mailman/listinfo/centos
> or, via email, send a message with subject or body 'help' to
> centos-request@xxxxxxxxxx
>
> You can reach the person managing the list at
> centos-owner@xxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CentOS digest..."
>
>
> Today's Topics:
>
> 1. CentOS-announce Digest, Vol 101, Issue 17
> (centos-announce-request@xxxxxxxxxx)
> 2. Re: Help with thread Centos 6.4 won't reboot on install
> (Ted Miller)
> 3. Re: What on Centos is wiping out my eth0 IP address every 5
> minutes? (J.Witvliet@xxxxxxxxx)
> 4. Re: What on Centos is wiping out my eth0 IP address every 5
> minutes? (J.Witvliet@xxxxxxxxx)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 25 Jul 2013 12:00:04 +0000
> From: centos-announce-request@xxxxxxxxxx
> Subject: CentOS-announce Digest, Vol 101, Issue 17
> To: centos-announce@xxxxxxxxxx
> Message-ID: <mailman.5.1374753604.1016.centos-announce@xxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
>
> Send CentOS-announce mailing list submissions to
> centos-announce@xxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.centos.org/mailman/listinfo/centos-announce
> or, via email, send a message with subject or body 'help' to
> centos-announce-request@xxxxxxxxxx
>
> You can reach the person managing the list at
> centos-announce-owner@xxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CentOS-announce digest..."
>
>
> Today's Topics:
>
> 1. CEBA-2013:X006 Xen4CentOS kernel Update (Johnny Hughes)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 24 Jul 2013 07:08:09 -0500
> From: Johnny Hughes <johnny@xxxxxxxxxx>
> Subject: [CentOS-announce] CEBA-2013:X006 Xen4CentOS kernel Update
> To: CentOS-Announce <centos-announce@xxxxxxxxxx>
> Message-ID: <51EFC3A9.3010501@xxxxxxxxxx>
> Content-Type: text/plain; charset="iso-8859-1"
>
> CentOS Errata and Bug Fix Advisory 2013:X006 (Xen4CentOS)
>
> The following updated files have been uploaded and are currently
> syncing to the mirrors: ( sha256sum Filename )
>
> -----------------------------
> X86_64
> -----------------------------
> e1000e-2.4.14-3.4.54.1.el6.centos.alt.x86_64.rpm:
> 42e5a701631d08eca5a62c0f3cb1c9cc527fad358fe74e72f426dd4ce16e384a
>
> kernel-3.4.54-8.el6.centos.alt.x86_64.rpm:
> f33e351084f5952a863cb8ba8f1e5ceb51999958e10fbf539bab52b89166b100
>
> kernel-devel-3.4.54-8.el6.centos.alt.x86_64.rpm:
> 2bc8fc1f3b276d151ca50ad5943cacde5ce168cb026dd328008b021c28fd5865
>
> kernel-doc-3.4.54-8.el6.centos.alt.noarch.rpm:
> 2608e0189f98dfd78b35feb0a14c2050e96bb7bd04e17a74b58028a143421354
>
> kernel-firmware-3.4.54-8.el6.centos.alt.noarch.rpm:
> 5c6ff0197936db9a3d26241ae92543f2b56d3a342393b9c3d416598f0eab22a4
>
> kernel-headers-3.4.54-8.el6.centos.alt.x86_64.rpm:
> 145392ddd7953f7e2aa9e7cc4a4a6ed64f2e1e73cb59a1db6d86ef7bb3797dba
>
> perf-3.4.54-8.el6.centos.alt.x86_64.rpm
> e83327bfc33b5dcde1eaa239ebadea9769895419a8c1f0f2a9bd02e99bc2b03c
>
> -----------------------------
> Source:
> -----------------------------
> e1000e-2.4.14-3.4.54.1.el6.centos.alt.src.rpm:
> 2c2a71b086ec3d1cab87466c11d9f33874c25652c9a91afb3f2fc79d7ff3602a
>
> kernel-3.4.54-8.el6.centos.alt.src.rpm:
> caeeceef9a9bb890fa852f22f51249f4c4102cb4bb30a988e983dc3638c75c3a
>
> ==================================================================
>
> Corrected the following CentOS Bugs in this kernel:
>
> http://bugs.centos.org/view.php?id=6561
>
> http://bugs.centos.org/view.php?id=6570
>
> ==================================================================
>
> kernel Changelog info from the SPEC file:
>
> * Mon Jul 22 2013 Johnny Hughes johnny@xxxxxxxxxx 3.4.54-8
> - upgraded to upstream version 3.4.54
> - Turned on CONFIG_XEN_BALLOON_MEMORY_HOTPLUG
> in this kernel (centos bug 6561)
> - added patch 131 and patch 132 per centos bug 6570
>
> ==================================================================
>
> The following kernel.org changelog entries are applicable since the last
> kernel update:
>
> https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.54
>
> ==================================================================
>
> Note: After kernel updates on a Xen Dom0 machine, you must run
> "/usr/bin/grub-bootxen.sh" to add the xen hypervisor to
> /boot/grub/grub.conf See this page for grub.conf details:
>
> http://wiki.centos.org/HowTos/Xen/Xen4QuickStart
>
> Note: As before, the e1000e driver provided replaces the mainline
> driver. It has some support for newer hardware and should only be used
> if the mainline driver does not detect your e1000e NIC.
>
> --
> Johnny Hughes
> CentOS Project { http://www.centos.org/ }
> irc: hughesjr, #centos at irc.freenode.net
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: OpenPGP digital signature
> Url :
http://lists.centos.org/pipermail/centos-announce/attachments/20130724/d64b8400/attachment-0001.bin
>
> ------------------------------
>
> _______________________________________________
> CentOS-announce mailing list
> CentOS-announce@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos-announce
>
>
> End of CentOS-announce Digest, Vol 101, Issue 17
> ************************************************
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 25 Jul 2013 23:45:18 -0400
> From: Ted Miller <tedlists@xxxxxxxxxxxxx>
> Subject: Re: Help with thread Centos 6.4 won't reboot on
> install
> To: centos@xxxxxxxxxx
> Message-ID: <51F1F0CE.5060808@xxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> > Have inconsistency in getting it to let me login. Yesterday no
> > luck. At '$ runlevel' got 5 3 so it must have been at runlevel 3.
> > startx no help, back to blue screen. Today, just started it first time
> > and it booted right to GUI login screen. All is OK that has been set up
> > like email, FF, printer etc. Checked Pref/System/Network Connection and
> > the box is greyed out. Pref/SysytemNetwork Proxy only 'Direct Internet
> > connection' is ticked. Everything else is greyed out. Ran updates also.
> > This happened a few days back and was fine as long as I stay logged in.
> > Re-boot or shutdown was not good. Couldn't log in again. Then
> > surprisingly today it is back. WTF ? Other HDs are OK and work
reliably.
> >
> > Bob
>
> Just a random thought that may trigger something in the wider brain trust:
>
> At various times you have mentioned that you had "shutdown". How did you
> do a "shutdown" both from Gnome and from the terminal?
>
> The reason I ask is that Linux supports more than one kind of "shutdown",
> but they are not all equal.
>
> The safest one is labeled something like "Turn Off Computer" (on KDE, not
> sure what wording Gnome uses) or you type "halt" at the command line, and
> it takes a good part of a minute to shut down. On many computers you can
> achieve the same effect by pressing the power button for LESS than half a
> second (quick poke).
>
> For some laptop users, just shutting the lid on the laptop is how they do
a
> "shutdown". This does NOT shut down the computer, but just puts into
> "suspended animation". When you wake it up, it tries to resume where it
> was before you shut down. This is also sometimes labeled "hibernate" on
> GUI screens (I have not idea how to do it from the command line).
>
> Hibernation works well on some laptops, but is very problematic on other
> laptops. Basically Linux tries to make a complete record of how
everything
> was set when it is commanded to hibernate, then write its entire memory
> contents onto disk, then take a nap. When you wake it back up it tries to
> restore its memory from hard disk, and put all the hardware back the way
it
> was before. Laptops are notorious for having special hardware, specific
to
> a particular model, that has some secret setting that has to be restored.
> Until the kernel maintainers find out about and accommodate each of those
> secret settings, the laptop may get out of bed on the wrong side, and be
> very contrary. For this reason, whenever you are having any kind of
> problems, one of the first things to do is to NEVER do anything except
turn
> it off all the way with a full, long shutdown.
>
> Another (problematic) way to "shutdown" is to hold down the power button
> for about 5 seconds. This is equivalent to wanting someone to go to bed,
> but they don't want to, so you hold your hand over their mouth until they
> pass out, lay them in a bed, and say they "went to sleep". Yes, the
> computer is "shutdown", but it didn't have time to do it in an orderly
> manner, and so there may be a mess to clean up when you power it back up.
>
> This may be entirely irrelevant, but if not, it may be helpful, especially
> when you sometimes seem to be describing a situation where you only can
get
> into gnome if the last time you shut down you were using the command line.
> Also, the one time you described the computer starting up very
> quickly--this is the (desirable) characteristic of hibernation. If your
> "shutdown" is different from the command line than it is from the GUI,
then
> you may be facing a hibernation (or similar) problem.
>
> Ted Miller
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 26 Jul 2013 11:00:11 +0200
> From: <J.Witvliet@xxxxxxxxx>
> Subject: Re: What on Centos is wiping out my eth0 IP address
> every 5 minutes?
> To: <centos@xxxxxxxxxx>
> Message-ID: <20130726090013.ECE4317CCDB@xxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
>
> -----Original Message-----
> From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
Behalf Of Rock
> Sent: Wednesday, July 24, 2013 4:01 PM
> To: centos@xxxxxxxxxx
> Subject: Re: What on Centos is wiping out my eth0 IP address
every 5 minutes?
>
> On Tue, 23 Jul 2013 23:03:00 -0700, John R Pierce wrote:
>
> > you should be able to get 300 feet of mostly open space with a simple
> > panel antenna
>
> Understood. The Nanobridge M2 may be far more than I need.
> But, it should work as it's advertised to go five miles.
> All I need is a few hundred feet.
>
> -----Original Message-----
> Five miles?
> Only with line of sight, no other stations on the same or neighboring
channel, and no electric equipment (engines)..
> Increasing power is hardly ever an good option, as it only do something
for TX, nothing for RX.
> If you have troubles with covering 300 feet, you need a 295 foot cable
and an additional antenna...
>
> ______________________________________________________________________
> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u
niet de geadresseerde bent of dit bericht abusievelijk aan u is
toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht
te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van
welke aard ook, die verband houdt met risico's verbonden aan het
electronisch verzenden van berichten.
>
> This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. The State
accepts no liability for damage of any kind resulting from the risks
inherent in the electronic transmission of messages.
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 26 Jul 2013 11:18:17 +0200
> From: <J.Witvliet@xxxxxxxxx>
> Subject: Re: What on Centos is wiping out my eth0 IP address
> every 5 minutes?
> To: <centos@xxxxxxxxxx>
> Message-ID: <20130726091819.D300021DCDA@xxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
>
> -----Original Message-----
> From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
Behalf Of m.roth@xxxxxxxxx
> Sent: Wednesday, July 24, 2013 4:07 PM
> To: CentOS mailing list
> Subject: Re: What on Centos is wiping out my eth0 IP address
every 5 minutes?
>
> Rock wrote:
> > On Tue, 23 Jul 2013 23:03:00 -0700, John R Pierce wrote:
> <snip>
> > I think my "original" problem was what you guys sensed from
> > the start.
> >
> > It was supremely frustrating having my manually typed eth0
> > IP address being wiped out - but - apparently that was what
> > Network Manager was supposed to do.
> >
> > Apparently Network Manager was set to pick up a DHCP address
> > for eth0, and, when none were forthcoming, it wiped out the
> > existing IP address.
> >
> > I only need to figure out now how to switch gracefully between
> > using wlan0 connected to the home broadband router inside the
> > house, and using eth0 wired to the Nanobridge M2 outside the
> > house.
> <snip>
> Several thoughts:
> on the router, see if it will accept a fixed IP, rather than one
> assigned by DHCP; if so, you can set it on the laptop. I'd also check to
> see if you need to deal with NetworkManager to do that. I don't know - I
> *loathe* NM, and am majorly annoyed that upstream decided to put a tool
> appropriate for a laptop as the default for *everything*... says the guy
> dealing with 150 or more servers and workstations that are hardwired.
>
> -----Original Message-----
> I give servers a fixed address, but they are also defined in the dhcp
server.
> It might look overflues, but when doing an installation with PXE, you
need dhcp.
> Just gotta be careful that the hard coded and the dhcp ones are the
same....
>
> Regarding N.M.: It is a wonderful tool.
> At least for end-users on desktops/laptops with frequently changing WIFI
or UMTS connections.
>
> But for servers, without a GUI, but with vlans, load-balancing or H-A?
Nah!
>
> ______________________________________________________________________
> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u
niet de geadresseerde bent of dit bericht abusievelijk aan u is
toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht
te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van
welke aard ook, die verband houdt met risico's verbonden aan het
electronisch verzenden van berichten.
>
> This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. The State
accepts no liability for damage of any kind resulting from the risks
inherent in the electronic transmission of messages.
>
>
> ------------------------------
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
>
> End of CentOS Digest, Vol 102, Issue 26
> ***************************************
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
