<div dir="ltr">On Tue, Aug 5, 2008 at 6:51 AM, Anne Wilson <span dir="ltr"><<a href="mailto:cannewilson@googlemail.com">cannewilson@googlemail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Monday 04 August 2008 23:06:16 Richard Shaw wrote:<br>
> > I can't Richard. It doesn't recognise any commands, and the file system<br>
> > isn't<br>
> > accessible if I boot from the hard drive.<br>
> ><br>
> > Anne<br>
><br>
> You'll have to rezero your overlay file and start over then... You can do<br>
> it manually from a windows or linux box but the dd command is a little<br>
> different for each. On a linux box it's something like:<br>
><br>
> dd if=/dev/zero of=/mount/path/LiveOS/overlay-{LABEL}-{UUID} bs=1M<br>
> count={size of overlay in MB}<br>
><br>
> Or on windows (the dd.exe is located under tools in the liveusb-creator<br>
> directory)<br>
><br>
> dd.exe if=/dev/zero of={drive letter}:\LiveOS\overlay-{LABEL}-{UUID} bs=1M<br>
> count={size of overlay in MB}<br>
><br>
> Just look at the current name of your overlay file and overwrite it rather<br>
> than looking up the LABEL and UUID.<br>
><br>
> I, like others, have created an extra entry in my syslinx.cfg without the<br>
> overlay option just in case I hose my overlay file and still want to be<br>
> able to use it.<br>
<br>
</div>Hi, Richard. I decided that I might as well start again from the<br>
beginning :-)<br>
<br>
The install seems to go well enough, as does the update, right to the very<br>
end. I glanced at the screen when it had about 5 packages still to go in the<br>
cleanup, but the next time I looked it said:<br>
<br>
File "usr/lib/python2.5/site-packages/dbus/connection.py", line 597, in<br>
call_blocking<br>
message.append(signature=signature, *args)<br>
TypeError: More items found in D-Bus signature than in Python arguments.<br>
<br>
Is this a big problem?</blockquote><div><br>I've never seen that one before. <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I had removed /etc/udev/rules.d/50-udev-default.rules, but I see it has been<br>
created again. This time there is also a 50-udev.nodes. Do I delete both of<br>
these?<br>
<br>
Anything else I need to deal with before attempting a reboot?<br>
<font color="#888888"><br>
Anne</font></blockquote><div><br>I probably should have chosen my words more carefully. I believe you want one file called 50-udev-default.rules, but when yum updates the udev package it chooses to not overwrite the existing file and instead creates a file called 50-udev-default.rules.rpmnew. Unfortunately, it appears that udev requests all files called 50-udev-default* or something like that and finds two matching files. Since it doesn't know which one to choose it choses neither and dumps you to a bash shell.<br>
<br>This is what I have inferred from it. There are seveal on this list that know more about udev than I. <br><br>Richard<br></div><div> </div></div></div>