Re: [leaf-devel] What I don't like about Bering uClibc
Hans Ulrich Niedermann wrote: snip 3. (lrcfg aka config) Every time I have modified a config file of package XYZ in lrcfg, I have to a) run /etc/init.d/XYZ restart from another shell b) make the changes permanent doing this: - go up two levels in the menu - enter the backup menu - read through the list to find XYZ' number (different from XYZ' number in the Packages configuration menu) NOTE: You can use the package name instead of the number. I haven't typed a package number in ages (they're too hard to locate when you've got a lot of packages loaded). - type b to back up - wait for some time - manually compare two numbers without given units, where one shows Bytes (new file size) and the other Kilobytes (free space) - if enough space is available, I have to manually confirm I'd like to have to menu entries in the package configuration: i) restart service ii) make changes permanent This should check for the amount of free space by itself. Both are good ideas. Checking for free space is harder than you'd think, especially at the limits (when the backup media is almost full), as you have to compare available space with file size taking into account sector sizes that might be different between the /tmp ramdisk and the backup media. The lack of du amd some other tools on earlier versions of LRP/LEAF when the backup scripts were written also contributes to the current behavior. 4. (lrcfg, buildtool, ???) Every time I have an updated package and install it, I have to manually save my config files and somehow merge them into the new package. Keeping the config, or having diff/edit, or even 3-way merge would be very nice. Try using partial backups, which backup just the configuration files. As long as you don't update to a new version with incompatable config files, you should be OK. I upgrade my systems by just inserting a new CD (with updated packages) and rebooting...the configuration data is all on a floppy (as partial backups) and is seamlessly used by the newly updated package(s) from the CD. -- Charles Steinkuehler [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What I don't like about Bering uClibc
Hans Ulrich Niedermann wrote: 2. (buildtool?) There is no build-hdd-image-for-my-board which copies all the necessary lrp files, sets up leaf.cfg with all the lrp names, possibly installs grub on the image, and so on. I'm surprised that LEAF to this day does not automate the process of reading in all of the *.lrp files. This was suggested many, many years ago and implemented in Oxygen. This way you don't have to list all of the LRP names. 3. (lrcfg aka config) Have you looked at acfg and apkg? They are shell scripts that are packaged as *.lrp and can be used instead of lrcfg. They use a menu interface using dialog and ncurses. I might add that apkg does check for space constraints (if desired) and will verify that there is enough space prior to saving the package. Charles mentioned that du was limited or unavailable previously; the Oxygen build of busybox is quite substantial compared to other systems, so this could be a problem - but you never know... --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] What I don't like about Bering uClibc
Hi, don't get me wrong - I love Bering uClibc. But while installing Bering uClibc on a WRAP and building, installing and testing yate packages, I got to hate some aspects of it :) I'll make a list so you can give some input about it: 1. (buildtool) There is no build-all-packages to (re-)build all packages. 2. (buildtool?) There is no build-hdd-image-for-my-board which copies all the necessary lrp files, sets up leaf.cfg with all the lrp names, possibly installs grub on the image, and so on. 3. (lrcfg aka config) Every time I have modified a config file of package XYZ in lrcfg, I have to a) run /etc/init.d/XYZ restart from another shell b) make the changes permanent doing this: - go up two levels in the menu - enter the backup menu - read through the list to find XYZ' number (different from XYZ' number in the Packages configuration menu) - type b to back up - wait for some time - manually compare two numbers without given units, where one shows Bytes (new file size) and the other Kilobytes (free space) - if enough space is available, I have to manually confirm I'd like to have to menu entries in the package configuration: i) restart service ii) make changes permanent This should check for the amount of free space by itself. 4. (lrcfg, buildtool, ???) Every time I have an updated package and install it, I have to manually save my config files and somehow merge them into the new package. Keeping the config, or having diff/edit, or even 3-way merge would be very nice. Gru, Uli pgpXubfDGXX95.pgp Description: PGP signature
