On Oct 3, 2013, at 3:01 PM, Reartes Guillermo wrote:
>> I guess what I find confusing is when anaconda uses one naming convention in
>> its UI, but upon reboot the installed system uses a different naming
>> convention.
>> And neither convention helps me know which of two ethernets are > being
> I guess what I find confusing is when anaconda uses one naming convention in
> its UI, but upon reboot the installed system uses a different naming
> convention.
> And neither convention helps me know which of two ethernets are > being used.
When i installed F19, anaconda wrote the config file
Le jeudi 22 août 2013 à 18:16 -0600, Chris Murphy a écrit :
> On Aug 22, 2013, at 5:54 PM, Adam Williamson wrote:
> > On Sat, 2013-08-17 at 11:57 -0700, Samuel Sieb wrote:
> >> On 08/17/2013 12:28 AM, Adam Williamson wrote:
> >
> > Yeah, I've seen that kind of thing in some of my tests. A lot of
On Oct 3, 2013, at 8:45 AM, Bill Nottingham wrote:
> "Jóhann B. Guðmundsson" (johan...@gmail.com) said:
>>> Apologies, I haven't had time to do investigation. The note in CommonBugs is
>>> certainly correct as far as anaconda using biosdevname by default still - if
>>> there are other consequen
"Jóhann B. Guðmundsson" (johan...@gmail.com) said:
> >Apologies, I haven't had time to do investigation. The note in CommonBugs is
> >certainly correct as far as anaconda using biosdevname by default still - if
> >there are other consequences where different names are written to the
> >interface c
On 10/03/2013 01:56 PM, Bill Nottingham wrote:
Adam Williamson (awill...@redhat.com) said:
On Mon, 2013-08-26 at 15:04 -0400, Bill Nottingham wrote:
Adam Williamson (awill...@redhat.com) said:
I should remember to check common bugs, but since I follow this list I'm
normally familiar with the e
Adam Williamson (awill...@redhat.com) said:
> On Mon, 2013-08-26 at 15:04 -0400, Bill Nottingham wrote:
> > Adam Williamson (awill...@redhat.com) said:
> > > > I should remember to check common bugs, but since I follow this list
> > > > I'm
> > > > normally familiar with the existing issues. B
On Mon, 2013-08-26 at 15:04 -0400, Bill Nottingham wrote:
> Adam Williamson (awill...@redhat.com) said:
> > > I should remember to check common bugs, but since I follow this list I'm
> > > normally familiar with the existing issues. But after looking at the
> > > entry, it wouldn't have been he
Adam Williamson (awill...@redhat.com) said:
> > I should remember to check common bugs, but since I follow this list I'm
> > normally familiar with the existing issues. But after looking at the
> > entry, it wouldn't have been helpful to my case since it says there
> > shouldn't be any issues.
On Thu, 2013-08-22 at 18:30 -0600, Chris Murphy wrote:
> On Aug 22, 2013, at 6:24 PM, Adam Williamson wrote:
>
> > No, we're not talking about the bash prompt on tty2, but there's an
> > actual *login prompt* on like tty6 or something. So far as I and the OP
> > knows, there is no account with a
On Aug 22, 2013, at 6:24 PM, Adam Williamson wrote:
> No, we're not talking about the bash prompt on tty2, but there's an
> actual *login prompt* on like tty6 or something. So far as I and the OP
> knows, there is no account with a known password for you log in as, and
> you have the root prompt
On Thu, 2013-08-22 at 18:16 -0600, Chris Murphy wrote:
> On Aug 22, 2013, at 5:54 PM, Adam Williamson wrote:
> > On Sat, 2013-08-17 at 11:57 -0700, Samuel Sieb wrote:
> >> On 08/17/2013 12:28 AM, Adam Williamson wrote:
> >
> > Yeah, I've seen that kind of thing in some of my tests. A lot of my li
On Aug 22, 2013, at 5:54 PM, Adam Williamson wrote:
> On Sat, 2013-08-17 at 11:57 -0700, Samuel Sieb wrote:
>> On 08/17/2013 12:28 AM, Adam Williamson wrote:
>
> Yeah, I've seen that kind of thing in some of my tests. A lot of my live
> installs wind up with New York as the timezone, IIRC.
I'm
On Sat, 2013-08-17 at 11:57 -0700, Samuel Sieb wrote:
> On 08/17/2013 12:28 AM, Adam Williamson wrote:
> >> VLAN setup for installing! Yay! However, after rebooting,
> >> NetworkManager wasn't able to bring it up, something about not knowing
> >> the "virtual interface name". Turned out to be th
On 08/17/2013 12:28 AM, Adam Williamson wrote:
VLAN setup for installing! Yay! However, after rebooting,
NetworkManager wasn't able to bring it up, something about not knowing
the "virtual interface name". Turned out to be the ethernet interface
name changed from what it was at install time.
On Fri, 2013-08-09 at 15:54 -0700, Samuel Sieb wrote:
> I realize it's been a while since F19 was released but I finally got
> around to do a server install. Since there have been a few negative
> reviews here of the installation process I thought it might be nice to
> have a mostly positive on
I realize it's been a while since F19 was released but I finally got
around to do a server install. Since there have been a few negative
reviews here of the installation process I thought it might be nice to
have a mostly positive one. Here are my observations:
VLAN setup for installing! Ya
17 matches
Mail list logo
