on 09.11.2010 21:45, KP Kirchdoerfer wrote:
> Am Dienstag, 9. November 2010, 16:27:52 schrieb Andrew:
>> 09.11.2010 00:41, KP Kirchdoerfer пишет:
>>> Every other, possible intrusive, change should IMHO better moved to 4.1 -
>>> let's make use of Trac to not forget our plans and ideas.
>>>
>>> jm2c
>>> kp
>>
>> IMHO we need to do some small modifications to base system  before
>> freezing it - at least, today I discovered that busybox's modprobe can
>> load modules with parameters if they are specified into
>> /etc/modules/<module_name> - this is very suitable for NICs and so on.
>> Unfortunatelly, current distro has file named /etc/modules - so that
>> feature can't be used. IMHO we need to replace it's name to, for ex.,
>> modules.conf.
> 
> This is definitely something which is important, if that's the only way to 
> support modules parameter.

And turns upgrades into a nightmare, let's face it, this is not LEAF
anymore, we might just as well use any stripped down Debian soon.


> 
>> Also I doubt against /etc/default directory, that contains config for
>> init.d scripts - possible we must rename it to /etc/conf.d - like in
>> other modern Debian-based distros and distros with Debian roots?
> 
> I vote against for two reasons:
> First and not that important it's still /etc/default in current Debian stable 
> and it's also /etc/default in Ubuntu and derivates - so we are in good 
> neighborhood.
> Second and more important, I don't see a real benefit other than just looking 
> "modern". As an embedded distro we don't have the need and capabilities to be 
> on par with the big ones. Our target is to be rock-solid and to work for 
> years 
> without attendance if possible. Easying deployment and updates will be more 
> than enough for LEAF users. The naming of directories is less important.
> 
> Third it will break  a lot packages.

It definitely will. I don't grok the hang on modprobe. In my little spot
in the universe one has to know the modules and their parameters. What
good will it do to, le't say the system can find out that an ALIX board
needs mii and via-rhine. I still have to provide those modules so I
might as well just uncomment them in /etc/modules. And I still have to
copy them to moddb unless moddb is a real monster and holds everything.
This does not make for a lean distro. And please remember, every
function yields a potential attack vector.

I think it is a good thing to go for 2.6, but honestly I consider some
of the other changes somewere between unneccessary and nice to have. We
still have happy Dachstein users, you know why? Because they are happy
to run it on their old fashioned 386. And we have even more Bering users.

How many times in the past few years has anyone asked for an automatic
device detection? How often did people ask for a GUI?

I understand that with the plethora of packages it is extremely
difficult to make a config package which covers everything and most of
the time space was a concern for not building a user friendly config
system. If there is a reason for LEAF then it is its versatility and we
don't improve that by building something that resembles Debian. Why, I
could always use Debian or OpenSuse or Ubuntu if it was not for space.
And if it was for space there are other firewall distros which are years
ahead as they provided 2.6 for a number of years.

I am not easily taken aback, but I have stopped to even think about
trying to get a system running for me, everytime I could consider to
install it there are at least a dozen or so changes, some for the
better, some for the worse.

cheers

Erich


------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to