Odd ownership of files in tarball [Re: Debian 5.0 (lenny) tar ball for the SheevaPlug - USB install]
On May 8, 2009, at 11:09 AM, Rick Thomas wrote: Cool! My first shivaplug arrived this morning. It's now installed and doing useful work. A fairly painless process -- thanks very much for the step-by-step instructions, Martin! I doubt if I could have done it myself with just the instructions from Marvell. I've stumbled across an anomaly in the tarball that I thought I should report. The groups for some of the files in the tarball don't correspond to those in a working system. Enclosed is a diff of everything that I've noticed... I've left out the stuff from "/dev" figuring that udev should handle that in a live system. Maybe that's a wrong assumption? Enjoy! Rick < marks the working system > marks files from the tarball 45c78 < /etc/exim4/passwd.client root Debian-exim --- > /etc/exim4/passwd.client root scanner 56c89,92 < /usr/bin/mlocate root mlocate --- > /usr/bin/mail-lock root mail > /usr/bin/mail-touchlock root mail > /usr/bin/mail-unlock root mail > /usr/bin/mlocate root Debian-exim 59c95 < /usr/bin/ssh-agent root ssh --- > /usr/bin/ssh-agent root ssl-cert 138,143c174,179 < /var/lib/exim4/config.autogenerated root Debian-exim < /var/lib/libuuid/ libuuid libuuid < /var/lib/nfs/ statd root < /var/lib/nfs/rpc_pipefs/ statd root < /var/lib/nfs/sm.bak/ statd root < /var/lib/nfs/sm/ statd root --- > /var/lib/exim4/config.autogenerated root scanner > /var/lib/libuuid/ Debian-exim libuuid > /var/lib/nfs/ messagebus root > /var/lib/nfs/rpc_pipefs/ messagebus root > /var/lib/nfs/sm.bak/ messagebus root > /var/lib/nfs/sm/ messagebus root 145,146c181,182 < /var/log/exim4/ Debian-exim adm < /var/log/exim4/mainlog Debian-exim adm --- > /var/log/exim4/ identd adm > /var/log/exim4/mainlog identd adm 148,149c184,185 < /var/run/exim4/ Debian-exim Debian-exim < /var/run/rpc.statd.pid statd root --- > /var/run/exim4/ identd scanner > /var/run/rpc.statd.pid messagebus root 155,158c191,194 < /var/spool/exim4/ Debian-exim Debian-exim < /var/spool/exim4/db/ Debian-exim Debian-exim < /var/spool/exim4/input/ Debian-exim Debian-exim < /var/spool/exim4/msglog/ Debian-exim Debian-exim --- > /var/spool/exim4/ identd scanner > /var/spool/exim4/db/ identd scanner > /var/spool/exim4/input/ identd scanner > /var/spool/exim4/msglog/ identd scanner -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Odd ownership of files in tarball [Re: Debian 5.0 (lenny) tar ball for the SheevaPlug - USB install]
On Mon, May 18, 2009 at 08:28:03PM -0400, Rick Thomas wrote: > > On May 8, 2009, at 11:09 AM, Rick Thomas wrote: > >> Cool! >> >> My first shivaplug arrived this morning. > > It's now installed and doing useful work. A fairly painless process -- > thanks very much for the step-by-step instructions, Martin! I doubt if I > could have done it myself with just the instructions from Marvell. > > I've stumbled across an anomaly in the tarball that I thought I should > report. > > The groups for some of the files in the tarball don't correspond to > those in a working system. Enclosed is a diff of everything that I've > noticed... How exactly did you produce this diff? If you extract the tarball on another system and then produced the diff on this system, then this is just expected. The tarball only stores numerical ids and the displayed names correspond to the names for these ids on the running system. Numerical ids are not garantueed to be the same accross different Debian installations. Check if the the permissons are also wrong if you actually boot the system on your plug or if you chroot into the directory of the unpacked tarball. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ signature.asc Description: Digital signature
Re: Odd ownership of files in tarball [Re: Debian 5.0 (lenny) tar ball for the SheevaPlug - USB install]
* Gaudenz Steinlin [2009-05-19 09:17]: > How exactly did you produce this diff? If you extract the tarball on > another system and then produced the diff on this system, then this is > just expected. The tarball only stores numerical ids and the displayed > names correspond to the names for these ids on the running system. > Numerical ids are not garantueed to be the same accross different Debian > installations. Yep, that's it. I just checked the files on the running system and they all look okay. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Odd ownership of files in tarball [Re: Debian 5.0 (lenny) tar ball for the SheevaPlug - USB install]
On May 19, 2009, at 4:49 AM, Martin Michlmayr wrote: * Gaudenz Steinlin [2009-05-19 09:17]: How exactly did you produce this diff? If you extract the tarball on another system and then produced the diff on this system, then this is just expected. The tarball only stores numerical ids and the displayed names correspond to the names for these ids on the running system. Numerical ids are not garantueed to be the same accross different Debian installations. Yep, that's it. I just checked the files on the running system and they all look okay. Hmmm... The diff was produced as Gaudenz says. So that explains the differences in my email. Sorry for speaking before I thought! However... I'm not quite ready to crawl back under my rock yet. Because... What prompted me to do the diff in the first place was some group/ ownership discrepancies I noticed on the running sheevaplug system. I had trouble getting "at" to work and it turned out to be ownership problems. I fixed them, and "at" runs fine now. I think I'll reinstall on a brand-new USB Flash drive and see if they are still there after a fresh installation. All, Please check the ownership and group of "/usr/bin/at*" on your own plugs... Enjoy! Rick -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
