On 01/15/2014 06:17 AM, Warren Young wrote:
On 1/14/2014 19:54, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris li...@spuddy.org wrote:
If you are old enough, you might remember unix versions that
named disks by controller, bus, target numbers.
On 01/14/2014 08:17 PM, Warren Young wrote:
On 1/14/2014 16:37, Scott Robbins wrote:
On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote:
Everyone, drop a tear for the dead eth0. sniff We will miss you, eth0!
Haven't played much with it in CentOS. In Fedora, at present, it is a bit
On 01/14/2014 08:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
I don't know about less consistent, but I always considered it a
feature in Linux vs the BSDs or big iron Unix that I could always count
on the first network interface being
On 01/14/2014 09:25 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:56 PM, Darr247 darr...@gmail.com wrote:
On 2014-01-14 8:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
On 01/14/14 20:17, Warren Young wrote:
On 1/14/2014 16:37, Scott Robbins wrote:
On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote:
Everyone, drop a tear for the dead eth0. sniff We will miss you, eth0!
Haven't played much with it in CentOS. In Fedora, at present, it is a bit
On Wed, 15 Jan 2014, mark wrote:
What do you mean, slot? All of my servers, and our systems at home, the
NIC's on the m/b. What slot is that? Is it labeled *anywhere*? No, of course
not.
Many servers have PCI cards for NICs in addition to those on the
motherboard (if any). For example, most
On Wed, Jan 15, 2014 at 6:08 AM, Steve Clark scl...@netwolves.com wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
run ifconfig unless I want to dig through the full listing.
Yes, but that's
On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark scl...@netwolves.com wrote:
On 01/14/2014 08:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
I don't know about less consistent, but I always considered it a
feature in Linux vs the BSDs or big
How about using ethtool -p which causes the LED of the NIC to blink?
On Wed, Jan 15, 2014 at 4:05 PM, Les Mikesell lesmikes...@gmail.com wrote:
On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark scl...@netwolves.com wrote:
On 01/14/2014 08:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17
Les Mikesell wrote:
On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark scl...@netwolves.com wrote:
On 01/14/2014 08:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com
wrote:
I don't know about less consistent, but I always considered it a
feature in Linux
Am Wed, 15 Jan 2014 16:25:04 +0200
schrieb JC Putter jcput...@gmail.com:
How about using ethtool -p which causes the LED of the NIC to blink?
Very useful, unless the datacenter isn't in the basement ;-)
___
CentOS mailing list
CentOS@centos.org
Steve Thompson wrote:
On Wed, 15 Jan 2014, mark wrote:
What do you mean, slot? All of my servers, and our systems at home,
the NIC's on the m/b. What slot is that? Is it labeled *anywhere*?
No, of
course not.
Many servers have PCI cards for NICs in addition to those on the
motherboard (if
On Wed, Jan 15, 2014 at 8:48 AM, m.r...@5-cent.us wrote:
The problem is when you clone a disk and ship it to a location with
'hands-on' support that doesn't know linux to install in a new chassis
that will arrive there at the same time. Somehow you have to get
someone to put the 4 network
Les Mikesell wrote:
On Wed, Jan 15, 2014 at 8:48 AM, m.r...@5-cent.us wrote:
The problem is when you clone a disk and ship it to a location with
'hands-on' support that doesn't know linux to install in a new chassis
that will arrive there at the same time. Somehow you have to get
someone
On Wed, Jan 15, 2014 at 12:47 PM, m.r...@5-cent.us wrote:
The problem is when you clone a disk and ship it to a location with
'hands-on' support that doesn't know linux to install in a new chassis
that will arrive there at the same time. Somehow you have to get
someone to put the 4 network
On 1/15/2014 05:41, mark wrote:
On 01/14/14 20:17, Warren Young wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
run ifconfig unless I want to dig through the full listing.
What do you mean, slot? All of my servers, and our systems at home, the
NIC's on the m/b.
On 1/13/2014 07:33, m.r...@5-cent.us wrote:
is there a CentOS
version of that beta?
Not yet publicly available.
I've heard they have something running in the development environment,
but that they're still working on getting some of the RPMs to build.
That's a prerequisite for generating
On Tue, Jan 14, 2014 at 2:27 PM, Warren Young war...@etr-usa.com wrote:
How bad is the worst case -- reinstall the OS and rebuild the software
-- anyway? By doing your initial work on the RHEL 7 beta, you learn
what you need to know to quickly redo the work on CentOS 7.
Is there anything to
Since RH7 is built on Fedora 19 and f19 is available for arm boards,
will we see a RH7 for arm boards?
I would spend time on the beta if I could get an arm build for a
reasonable arm board. Target application is a PBX.
___
CentOS mailing list
Warren Young wrote:
On 1/13/2014 07:33, m.r...@5-cent.us wrote:
snip
Reason for this: at one of my local sf clubs, I've been trying to
install Evergreen, F/OSS library software, on a system, and it's a
nightmare.
They seem to have been building it for Ubuntu
whateverthelatestanimalis. The
Les Mikesell wrote:
On Tue, Jan 14, 2014 at 2:27 PM, Warren Young war...@etr-usa.com wrote:
How bad is the worst case -- reinstall the OS and rebuild the software
-- anyway? By doing your initial work on the RHEL 7 beta, you learn
what you need to know to quickly redo the work on CentOS 7.
On 1/14/2014 13:41, Les Mikesell wrote:
It seems like taking the list from 'rpm -qa' on a
running machine and feeding it to 'yum install '
I suspect it's not actually that simple. I think you'd need to do a
fair bit of processing on the rpm -qa list to be able to build a yum
command
On 1/14/2014 14:32, m.r...@5-cent.us wrote:
configure can't
find the interface,
Were you aware that RHEL 7 now uses Consistent Network Device Naming
(http://goo.gl/Z0ydDF) in more situations? It was optional in RHEL 6
(http://goo.gl/TiuTP9) but is all but enforced in RHEL 7.
Everyone, drop
On 14 January 2014 20:41, Les Mikesell lesmikes...@gmail.com wrote:
Is there anything to simplify the process of duplicating the set of
installed packages when you didn't pay that much attention the first
time around? It seems like taking the list from 'rpm -qa' on a
running machine and
On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote:
On 1/14/2014 14:32, m.r...@5-cent.us wrote:
configure can't
find the interface,
Were you aware that RHEL 7 now uses Consistent Network Device Naming
(http://goo.gl/Z0ydDF) in more situations? It was optional in RHEL 6
On 01/15/2014 12:37 AM, Scott Robbins wrote:
On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote:
On 1/14/2014 14:32, m.r...@5-cent.us wrote:
configure can't
find the interface,
Were you aware that RHEL 7 now uses Consistent Network Device Naming
(http://goo.gl/Z0ydDF) in more
On 1/14/2014 16:37, Scott Robbins wrote:
On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote:
Everyone, drop a tear for the dead eth0. sniff We will miss you, eth0!
Haven't played much with it in CentOS. In Fedora, at present, it is a bit
of pain as both biosdevname and systemd
On 1/14/2014 17:33, Ljubomir Ljubojevic wrote:
If the system's BIOS does not have SMBIOS version 2.6 or higher and
this data, the new naming convention will not be used.
Apparently VirtualBox emulates SMBIOS, since my RHEL 7 VM uses this new
scheme.
On 1/14/2014 5:17 PM, Warren Young wrote:
I don't know about less consistent, but I always considered it a
feature in Linux vs the BSDs or big iron Unix that I could always count
on the first network interface being eth0. BSD and big iron Unix
named the interface after the Ethernet driver, as
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
I don't know about less consistent, but I always considered it a
feature in Linux vs the BSDs or big iron Unix that I could always count
on the first network interface being eth0.
What does 'first' mean? And the same one
On 01/15/2014 10:57 AM, Warren Young wrote:
On 1/14/2014 14:32, m.r...@5-cent.us wrote:
Everyone, drop a tear for the dead eth0. sniff We will miss you, eth0!
Not as dead as you may think, there are still situations where eth0 will
be used, even by default:
[root@el7-test ~]# ip a
...
2:
On 01/15/2014 02:17 PM, Warren Young wrote:
I don't know about less consistent, but I always considered it a
feature in Linux vs the BSDs or big iron Unix that I could always count
on the first network interface being eth0. BSD and big iron Unix
named the interface after the Ethernet
On 1/14/2014 18:23, John R Pierce wrote:
On 1/14/2014 5:17 PM, Warren Young wrote:
I don't know about less consistent, but I always considered it a
feature in Linux vs the BSDs or big iron Unix that I could always count
on the first network interface being eth0. BSD and big iron Unix
named
On 2014-01-14 8:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
run ifconfig unless I want to dig through the full listing.
Yes, but that's something you _can_ know.
So...
On 1/14/2014 5:55 PM, Warren Young wrote:
I know the problem you mean, but doesn't the HWADDR setting in the
ifcfg-ethX file fix the problem? Doesn't that force ifup eth0 to bind
that file's settings to the right physical interface?
In the old days, ifcfg-ethX didn't have HWADDR, so first
On 1/14/2014 18:34, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
run ifconfig unless I want to dig through the full listing.
Yes, but that's something you _can_ know.
How
On Tue, Jan 14, 2014 at 7:56 PM, Darr247 darr...@gmail.com wrote:
On 2014-01-14 8:34 PM, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young war...@etr-usa.com wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
run ifconfig unless I want to dig through
On 1/14/2014 19:10, John R Pierce wrote:
On 1/14/2014 5:55 PM, Warren Young wrote:
I know the problem you mean, but doesn't the HWADDR setting in the
ifcfg-ethX file fix the problem? Doesn't that force ifup eth0 to bind
that file's settings to the right physical interface?
In the old days,
On 1/14/2014 18:34, Les Mikesell wrote:
Puzzle for ya: What PCI slot is the Intel e1000e MAC chip in on a
Supermicro X9SCA-F motherboard? It isn't called out in the mobo manual.
I just looked. (For that matter, the actual PCI slots don't have
their numbers documented in the manual,
On Tue, Jan 14, 2014 at 8:21 PM, Warren Young war...@etr-usa.com wrote:
Now I have to remember which *PCI slot* my Ethernet card is in when I
run ifconfig unless I want to dig through the full listing.
Yes, but that's something you _can_ know.
How much time and resources do you need to
On Tue, Jan 14, 2014 at 8:27 PM, Thomas Eriksson
thomas.eriks...@slac.stanford.edu wrote:
Puzzle for ya: What PCI slot is the Intel e1000e MAC chip in on a
Supermicro X9SCA-F motherboard? It isn't called out in the mobo manual.
I just looked. (For that matter, the actual PCI slots don't
On Tue, Jan 14, 2014 at 08:35:06PM -0600, Les Mikesell wrote:
Let anaconda figure it out. I don't care what it is, just that it is
repeatable.
Awooga! Awoooga! Awooga!
Here's the fun part; devices discovered by Anaconda may not match the
devices disovered during the production boot. Device
On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris li...@spuddy.org wrote:
Ultimately what we have is a situation similar to hard disks. We've got
used to sd devices changing depending on the order disks are discovered
in, which is why we use LABEL or UUID.
But those don't work until something
On Tue, Jan 14, 2014 at 08:54:33PM -0600, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris li...@spuddy.org wrote:
Ultimately what we have is a situation similar to hard disks. We've got
used to sd devices changing depending on the order disks are discovered
in, which
On 1/14/2014 19:54, Les Mikesell wrote:
On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris li...@spuddy.org wrote:
If you are old enough, you might remember unix versions that
named disks by controller, bus, target numbers.
/dev/rdsk/c0t0n0q0w0e0p1k5n8 :)
It's another reason I took to Linux
I've seen that RHEL 7 beta is out for some time now: is there a CentOS
version of that beta? If not, is it likely to be a real pain, once CentOS
7 is released, to upgrade from RHEL 7 beta to CentOS 7?
Reason for this: at one of my local sf clubs, I've been trying to install
Evergreen, F/OSS
On 13 January 2014 14:33, m.r...@5-cent.us wrote:
I've seen that RHEL 7 beta is out for some time now: is there a CentOS
version of that beta? If not, is it likely to be a real pain, once CentOS
7 is released, to upgrade from RHEL 7 beta to CentOS 7?
Check the progress on
47 matches
Mail list logo
