On Tue, Oct 17, 2006 at 09:46:10AM +0200, Markus Wigge wrote: > Hi, > > >> #122: new files are installed inside fwcf > > > > Pointing here for a discussion. > > > >> If I have a router where I installed some packages and I want to use it > >> for something different later, I do a "fwcf erase" and start to configure > >> it from scratch. but I really don't want broken packages then. > > > > This is not what 'fwcf erase' is for. It is for if you flash a new image > > using mtd and want clean configuration. > Well, I see my example as intention too. I don't want to reflash a > router when it comes back from a customer each time, I just want to > erase the config and start from scratch with the default config files > and scripts I got from the packages. > > Files in /etc/init.d belong to the packages for example and should be > installed on the same persistent partition. > > Another good example is "/etc/pcmcia" I never needed to touch those > files but they need to be installed and the belong to the packages. So > it is ok for me if you save the modifications to these files to fwcf, > but it is a waste of fwcf space to save the complete files there. > > > (Is it just me or... if you delete configuration files, programmes should > > not break, and you could just write new configuration files to make them > > work again.) > Why write a new one? /etc should contain all the distribution default > files after erasing fwcf. So I only have to adjust them depending on the > new use of the device. > > > For everything else, just copy /tmp/.fwcf/root/ to /etc/ instead. > I'd prefer ipkg would install all "/etc" files to "/tmp/.fwcf/root" and > then reinitialize fwcf afterwards. > > >> And when I am able to > >> install additional packages I want them installed persistent. > > > > Actually, configuration files normally should not be installed to > > /etc, in sensible packaging systems, unlike ipkg. They aren't, due > > to space constraints. If you do what you are doing - starting anew - > > you're better off flashing a new image with the packages you want > > to have added anyway. > Ok, I don't understand what you want to tell me here. There is a > Filesystem Hierachy Standard that says config-files belong to /etc. > Packages provide default configurations for common situations which > reside in /etc too. > > Where so you save you Configuration in MirOS? in > /usr/local/<package>/etc/... ? That looks more like the Redmond way of life. > > And don't belong init-scripts to your packages? And what kind of space > constraints are you talking about? > > > What you want is not what fwcf was designed/intended for. > So, I read the specification twice and I think I don't understand it yet > when I did not get the intention so far. > > > And to quote from a previous mail: > >> "fwcf erase" or if someone forgets to commit the files. > > > > If "someone forgets" whatever, be it fwcf commit, he's shoot > > himself into the foot anyway. We expect our target audience > > to have RTFM. > Well, yes. RTFM is always a good idea. But there are also common use > cases around people try to follow first. As I already mentioned "write > erase" on IOS leaves a clean empty config to start with. And to resume > it: I'd like to have this kind of analogy because people can expect a > behavior they already know from somewhere else. > Whereas "fwcf erase" breaks your package "database" for know. > > And yes, forgetting about something alway produces a hole in your feet > or knees. So that was quite a stupid example. > > ... other opinions please ...
In my opinion should the system run in a default configuration even after cleaning up with "fwcf erase". There is not discussion that /etc is _the_ position for config file, no other directory should be modified. So, why it is not possible to modify the ipkg process to install the files into /tmp/.fwcf/root instead of /etc and merging afterwards? Let's try to make this system as reliable as possible and this would be a great step forward. The current solution is only 90% and does not support additional package installations very well (btw., IOS doesn't support package installations in any way). wbx, tg, is there a technically possibility to get that feature described by Markus above? Dirk _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
