12:25 a.m.
Hi all,
I updated my XO 1.75 to 12.1.0. Everything seemed to work great.
I ran "yum update" on it and after rebooting my /etc/resolv.conf is no
longer updated when the network connection is established.
/var/log/messages:
Sep 19 23:58:40 xo-74-39-52 NetworkManager[363]: <warn> could not commit
DNS changes: (0) Could not replace /etc/resolv.conf: Device or resource busy
I can add my DNS settings manually, but after a reboot they disappear
again... so NM is lying to me. :)
Is this a reported bug already? My Google-fu didn't turn up anything.
Thanks,
Michael
10:52 a.m.
On Thu, Sep 20, 2012 at 00:25:18 -0500,
Michael Cronenworth <mike(a)cchtml.com> wrote:
Hi all,
I updated my XO 1.75 to 12.1.0. Everything seemed to work great.
I ran "yum update" on it and after rebooting my /etc/resolv.conf is
no longer updated when the network connection is established.
/var/log/messages:
Sep 19 23:58:40 xo-74-39-52 NetworkManager[363]: <warn> could not
commit DNS changes: (0) Could not replace /etc/resolv.conf: Device or
resource busy
I can add my DNS settings manually, but after a reboot they disappear
again... so NM is lying to me. :)
Is this a reported bug already? My Google-fu didn't turn up anything.
I noticed that, but I thought it was maybe the networks I was connecting
to not providing DNS (because they test wireless networks at work, that
I thought maybe weren't supposed to do that to keep them from being used
like the production network), but it had worked at least at some point on
my home network. But I am not sure I tested that again after my latest
update.
In the long run I'll probably be disabling that feature anyway and run
dnscache on the XO.
4:07 p.m.
On Thu, Sep 20, 2012 at 00:25:18 -0500,
Michael Cronenworth <mike(a)cchtml.com> wrote:
I ran "yum update" on it and after rebooting my /etc/resolv.conf is
no longer updated when the network connection is established.
/var/log/messages:
Sep 19 23:58:40 xo-74-39-52 NetworkManager[363]: <warn> could not
commit DNS changes: (0) Could not replace /etc/resolv.conf: Device or
resource busy
I can add my DNS settings manually, but after a reboot they disappear
again... so NM is lying to me. :)
Is this a reported bug already? My Google-fu didn't turn up anything.
I confirmed I am seeing this consistently now, but I wasn't seeing the
problem right after installing 12.1.0.
Have you reported it yet?
4:11 p.m.
On 09/22/2012 04:07 PM, Bruno Wolff III wrote:
I confirmed I am seeing this consistently now, but I wasn't seeing the
problem right after installing 12.1.0.
Have you reported it yet?
I have not yet. If you create a bug report, please link me. I haven't
researched how-to report a bug for OLPC yet.
7:43 p.m.
On Sat, Sep 22, 2012 at 16:11:39 -0500,
Michael Cronenworth <mike(a)cchtml.com> wrote:
On 09/22/2012 04:07 PM, Bruno Wolff III wrote:
>
>I confirmed I am seeing this consistently now, but I wasn't seeing the
>problem right after installing 12.1.0.
>
>Have you reported it yet?
I have not yet. If you create a bug report, please link me. I haven't
researched how-to report a bug for OLPC yet.
http://dev.laptop.org/ticket/12121
12:30 p.m.
Bruno Wolff III on 09/22/2012 07:43 PM wrote:
Since we were informed that package updates are not supported, would it
be appropriate to create bugs in the Fedora bugzilla instead?
2:04 p.m.
On Wed, Sep 26, 2012 at 12:30:27 -0500,
Michael Cronenworth <mike(a)cchtml.com> wrote:
Bruno Wolff III on 09/22/2012 07:43 PM wrote:
>
> http://dev.laptop.org/ticket/12121
Since we were informed that package updates are not supported, would it
be appropriate to create bugs in the Fedora bugzilla instead?
Maybe. If they don't happen in normal Fedora installs, then I'd think you'd
only want to do it if you have a suggested fix that will work for OLPC and
not break things for Fedora. Otherwise the usage case is out of scope.
If you haven't read the article linked to in the ticket about why not to use
yum with XOs, you really should.
2:12 p.m.
Bruno Wolff III on 09/26/2012 02:04 PM wrote:
Maybe. If they don't happen in normal Fedora installs, then
I'd think
you'd only want to do it if you have a suggested fix that will work for
OLPC and not break things for Fedora. Otherwise the usage case is out of
scope.
Since the repo is specified in the yum update (fedora, olpc, etc) we
could narrow down which group was responsible for the breakage.
Also: Since Fedora ARM is not PA, yet, I'm not sure Fedora maintainers
would want to see any ARM bugs yet, or how current ARM bugs are
reported. The Fedora ARM wiki page doesn't give any specifics.
If you haven't read the article linked to in the ticket about why
not to
use yum with XOs, you really should.
I read it and could agree with it yum-pre-deltarpms, but now yum is
pretty streamlined. The only drawback I see with yum now is the CPU
power required for Python. I'd love to see Zim (or an equivalent in C)
take over yum, but that is for another thread. Using apt-* on my Nokia
N900 is light years faster than yum on my OLPC.
2:48 p.m.
On Wed, Sep 26, 2012 at 14:12:00 -0500,
Michael Cronenworth <mike(a)cchtml.com> wrote:
I read it and could agree with it yum-pre-deltarpms, but now yum is
pretty streamlined. The only drawback I see with yum now is the CPU
power required for Python. I'd love to see Zim (or an equivalent in C)
take over yum, but that is for another thread. Using apt-* on my Nokia
N900 is light years faster than yum on my OLPC.
Relevant to breaking things is that changes are made to Fedora packages
in some case after the packages are install. Reinstalling the packages
will break things in that case and it really wouldn't necessarily be a bug
from the Fedora side as OLPC isn't using the rpms as supplied in those cases.
3:13 a.m.
On Wed, Sep 26, 2012 at 8:04 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
On Wed, Sep 26, 2012 at 12:30:27 -0500,
Michael Cronenworth <mike(a)cchtml.com> wrote:
>
> Bruno Wolff III on 09/22/2012 07:43 PM wrote:
>>
>>
>> http://dev.laptop.org/ticket/12121
>
>
> Since we were informed that package updates are not supported, would it
> be appropriate to create bugs in the Fedora bugzilla instead?
Maybe. If they don't happen in normal Fedora installs, then I'd think you'd
only want to do it if you have a suggested fix that will work for OLPC and
not break things for Fedora. Otherwise the usage case is out of scope.
If you haven't read the article linked to in the ticket about why not to use
yum with XOs, you really should.
So the "no yum updates" is more aimed at deployments so random updates
don't cause undue pain for deployments with tens of thousands of
units. That's not to say it shouldn't be done for an average Fedora
user. I do it by standard and as per standard Fedora your mileage may
vary and if it breaks you get to keep both pieces :-)
I documented what you need to do to ensure you get all updates you
want (ie you don't want the kernel ;-) ) here
http://nullr0ute.com/2012/09/using-fedora-on-your-shiny-new-olpc-xo/
Peter
12:54 p.m.
On Sat, Sep 29, 2012 at 09:13:12 +0100,
Peter Robinson <pbrobinson(a)gmail.com> wrote:
I documented what you need to do to ensure you get all updates you
want (ie you don't want the kernel ;-) ) here
http://nullr0ute.com/2012/09/using-fedora-on-your-shiny-new-olpc-xo/
I had just read that post. One thing I thought odd was that it didn't
mention setting a root password or taking the olpc account out of wheel
as part of using gdm to login.
So far of gotten a number of comments from people who have seen my XO, that
it looks like a toy for kids. So that part of the design is working well.
4:31 p.m.
On Sat, Sep 29, 2012 at 6:54 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
On Sat, Sep 29, 2012 at 09:13:12 +0100,
Peter Robinson <pbrobinson(a)gmail.com> wrote:
>
>
> I documented what you need to do to ensure you get all updates you
> want (ie you don't want the kernel ;-) ) here
> http://nullr0ute.com/2012/09/using-fedora-on-your-shiny-new-olpc-xo/
I had just read that post. One thing I thought odd was that it didn't
mention setting a root password or taking the olpc account out of wheel
as part of using gdm to login.
The point of the post wasn't about security and account management.
Everyone has their opinion on how best to do that and so I left that
up to the user to decide. It's a very political and personal
preference (my core laptop is encrypted and locked and no one has
access to my primary account for example) and people will do with it
as they please and should know the basics of setting passwords on
accounts and changing groups, if they don't the fact it's not secured
probably doesn't bother them.
As one of the OS people I have a number of XOs around my house that
are never secured, I personally don't keep any personal data on them
and they are reflashed often. Friends and their kids that come around
are invited to play with them and people attempt things on them and
break the core OS all the time. They're easy to reflash back to
factory image and there's nothing lost.
So far of gotten a number of comments from people who have seen my
XO, that
it looks like a toy for kids. So that part of the design is working well.
Tool more than a toy but it's certainly for kids and always a
conversation starter :-)
Peter
3:42 p.m.
On Thu, 2012-09-20 at 00:25 -0500, Michael Cronenworth wrote:
Hi all,
I updated my XO 1.75 to 12.1.0. Everything seemed to work great.
Just curious did you did flash it or run olpc_update to install 12.1.0?
Your running the official/latest version from download.laptop.org?
I ran "yum update" on it and after rebooting my
/etc/resolv.conf is no
longer updated when the network connection is established.
That's odd, if there were OLPC specific packages to exclude from the
updating process yum should of excluded them automatically. I install
rpms on top of the base XO install all the time and have never ran into
this issue on a flashed install.
/var/log/messages:
Sep 19 23:58:40 xo-74-39-52 NetworkManager[363]: <warn> could not commit
DNS changes: (0) Could not replace /etc/resolv.conf: Device or resource busy
There was a change at the olpc-os-builder level affecting resolv.conf
between 11.3.1 and 12.1.0, that is why I'm asking if you did a
olpc-update to arrive at 12.1.0.
I can add my DNS settings manually, but after a reboot they disappear
again... so NM is lying to me. :)
That might related, there are bind-mounts in play with resolv.conf. When
did you run yum update? Did you reboot after updating to 12.1.0 before
running yum?
Is this a reported bug already? My Google-fu didn't turn up
anything.
The XO connected to the internet at one point, did you have to enter the
nameservers in resolv.conf before being able surf the web or run yum
successfully?
Jerry
3:46 p.m.
Jerry Vonau on 09/26/2012 03:42 PM wrote:
Just curious did you did flash it or run olpc_update to install
12.1.0?
Your running the official/latest version from download.laptop.org?
I used the flash image and placed it on a USB stick.
That might related, there are bind-mounts in play with resolv.conf.
When
did you run yum update? Did you reboot after updating to 12.1.0 before
running yum?
I ran yum update after flashing the image. I had internet access
(without modifying resolv.conf) before, during, and after the yum
update. It only broke after a reboot.
The XO connected to the internet at one point, did you have to enter
the
nameservers in resolv.conf before being able surf the web or run yum
successfully?
No.
4235
days inactive
4244
days old
13 comments
4 participants
participants (4)
-
Bruno Wolff III -
Jerry Vonau -
Michael Cronenworth -
Peter Robinson