Hi KP Am 28.02.2015 um 18:40 schrieb kp kirchdoerfer: > Hi Erich; > > Sounds like an interesting and useful task. > > > Am Mittwoch, 25. Februar 2015, 12:56:15 schrieb Erich Titl: >> Hi Folks >> >> I am investigating into an upgrade function for LEAF, I did not grok the >> stuff Andrew wrote, so I am looking for easy and easily understandable >> ways to get there. >> >> A few questions pop up which I have not been able to find an easy >> aproach (probably too lazy) >> >> - How to access the actual running release (or it's release family like >> 5.x.x (beta n)) The kernel version which can be easily retrieved IMHO is >> insufficient) > > How about /var/lib/lrpkg/initrd.version?
That is what I am using right now. > > >> - How can we identify the latest stable release. A fixed URL might >> suffice but it would be easier to use a TXT DNS record for this >> information. Unfortunately there appears to be no easy way to retrieve >> anything but A records with the current tools on LEAF. > > An alternative could be using git (tags). > I try to provide packages for each upgrade in the packages repository - could > be improved though. If you want to access these tags you need git on the target system. My aproach right now is to run a command on the router which fetches all the latest stuff right now. > >> - How to determine compatibility between the running release and the >> latest stable release >> >> - Can we identify platform and release independent packages? > > >> I am currently using an internal web site to deliver the packages to my >> routers as they typically don't have sufficient storage for the whole >> package repository. It would be nice to enhance the files section at >> sourceforge to take over this task (at the same time old and obsolete >> links could be cleaned up) > > > You may have a look into > leaf.zetam.org > > I worked with Yves recently to provide a new and working Packages page there, > > no further decisions made about mocing webpages permamently - any input will > be welcome. leaf.think.ch should be accessible from the net. I just unpacked the serial tarball, in there the modules.tgz is unpacked into a modules directory and I will also unpack the firmware tarball, so individual files can be checked and accessed. I placed a file called 'version' there which allows easy check of the latest version. Also for my specific purposes I need a combined initrd.lrp as grub does not like initmod,lrp Right now upgrade can replace the kernel, initrd and the modules files (only the ones loaded at upgrade time), this reduces the size of moddb considerably. It builds a moddb file, leaves configdb and leaf.cfg alone. Next step will be to replace all the .lrp and .lwp files with the exception of init*.lrp. Leaving configdb alone allows for any inittab file to be used, as it will be replaced at boot time anyway, so no more fiddling with these. Upgrade is just a small script with almost no dependenciesi (basically just wget). I am testing it on a real minimalistic old WRAP system. The only important feature I see is (for backup reasons) to have a system with two bootable partitions, which I do as a standard. This way I can freely test my stuff without worrying about havong to open a box because of a mangled file. cheers Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
