On 08/06/2014 03:23 PM, Felix Miata wrote:
On 2014-08-06 11:43 (GMT-0500) Kevin Martin composed:
Hmm, I have biosdevname installed (and always have) and have never
put net.ifnames=0
anywhere that I'm aware of.
I've included net.ifnames=0 on installer cmdline for every distro I've
installe
On Wed, Aug 06, 2014 at 12:29:53PM -0700, Brandon Vincent wrote:
> Hello,
>
> I'm thrilled to have the opportunity to join the QA team. I am a
> system administrator who enjoys working on all *nix variants. I
> currently also work with the Fedora Security Team to ensure that
> vulnerabilities patc
On 2014-08-06 11:43 (GMT-0500) Kevin Martin composed:
Hmm, I have biosdevname installed (and always have) and have never put
net.ifnames=0
anywhere that I'm aware of.
I've included net.ifnames=0 on installer cmdline for every distro I've
installed for over a year. NAICT, Anaconda ignores it
Hello,
I'm thrilled to have the opportunity to join the QA team. I am a
system administrator who enjoys working on all *nix variants. I
currently also work with the Fedora Security Team to ensure that
vulnerabilities patched in upstream reach the Fedora Project
packagers. My area of expertise is i
On Wed, 6 Aug 2014, Samuel Sieb wrote:
On 08/06/2014 10:48 AM, Michael Hennebry wrote:
wrote:
For a longer time udev shipped support for assigning permanent "ethX"
names to certain interfaces based on their MAC addresses.
This turned out to have a multitude of problems, among them:
this requir
On 08/06/2014 10:48 AM, Michael Hennebry wrote:
wrote:
For a longer time udev shipped support for assigning permanent "ethX"
names to certain interfaces based on their MAC addresses.
This turned out to have a multitude of problems, among them:
this required a writable root directory which is gen
Would someone explain this to me:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
wrote:
For a longer time udev shipped support for assigning permanent "ethX"
names to certain interfaces based on their MAC addresses.
This turned out to have a multitude of proble
On 08/06/2014 09:32 AM, Scott Robbins wrote:
> On Wed, Aug 06, 2014 at 02:38:30PM +0200, Adam Williamson wrote:
>>
>> In Fedora 21 we've more or less dropped biosdevname in favour of
>> systemd. systemd's system is a cleaner implementation and the weight of
>> opinion favours the systemd approach t
On Wed, Aug 06, 2014 at 02:38:30PM +0200, Adam Williamson wrote:
>
> In Fedora 21 we've more or less dropped biosdevname in favour of
> systemd. systemd's system is a cleaner implementation and the weight of
> opinion favours the systemd approach to naming. See the discussion from
> https://bugzil
On 08/06/2014 07:08 AM, Tom Horsley wrote:
> On Wed, 6 Aug 2014 07:55:55 -0400
> Matthew Miller wrote:
>
>> "consistent on the same machine for a given OS release,
>> _across any possible hardware changes_"
>
> Maybe, but I know I watched the interface names change
> just because a new version of
On Wed, 2014-08-06 at 14:38 +0200, Adam Williamson wrote:
> In Fedora 21 we've more or less dropped biosdevname in favour of
> systemd. systemd's system is a cleaner implementation and the weight of
> opinion favours the systemd approach to naming. See the discussion from
> https://bugzilla.redhat
On Wed, 2014-08-06 at 07:41 -0400, Tom Horsley wrote:
> I've got F21 branched installed on an alternate partition on
> my system, and I noticed this nonsense. On F21 I get this:
>
> enp5s0: flags=4163 mtu 1500
> inet 10.134.30.143 netmask 255.255.255.0 broadcast 10.134.30.255
>
On Wed, Aug 06, 2014 at 08:08:10AM -0400, Tom Horsley wrote:
> > "consistent on the same machine for a given OS release,
> > _across any possible hardware changes_"
> Maybe, but I know I watched the interface names change
> just because a new version of bisodevname was released
> before biosdevname
On Wed, 6 Aug 2014 07:55:55 -0400
Matthew Miller wrote:
> "consistent on the same machine for a given OS release,
> _across any possible hardware changes_"
Maybe, but I know I watched the interface names change
just because a new version of bisodevname was released
before biosdevname was engulphe
On Wed, Aug 06, 2014 at 07:41:07AM -0400, Tom Horsley wrote:
> What was the point of "consistent" interface names again?
Completely leaving aside the question of what exactly it _should_ mean, it
appears to mean "consistent on the same machine for a given OS release,
_across any possible hardware
I've got F21 branched installed on an alternate partition on
my system, and I noticed this nonsense. On F21 I get this:
enp5s0: flags=4163 mtu 1500
inet 10.134.30.143 netmask 255.255.255.0 broadcast 10.134.30.255
inet6 fe80::20b:eff:fe0f:ed prefixlen 64 scopeid 0x20
et
Compose started at Wed Aug 6 07:15:06 UTC 2014
Broken deps for armhfp
--
[APLpy]
APLpy-0.9.8-5.fc21.noarch requires pywcs
[ModemManager]
ModemManager-1.2.0-3.fc21.armv7hl requires libmbim-glib.so.0
[PyKDE]
PyKDE-3.16.
17 matches
Mail list logo
