buzzard


Group: Members
Posts: 34
Joined: Jan. 2007 |
 |
Posted: April 15 2007,22:42 |
 |
I didn't vote, but I agree that if room is needed, apps like firefox could be stuffed off onto .uci. What I like about DSL is its modularity, and wouldn't want to lose that in the shuffle. As for kernel modules, things like imm.o (zip-plus), and like someone else said, winmodems. (needn't be included in base, just available for adding-on by users). The MyDSL files kind of remind me of mac os 8 where the extensions, left in a certain folder, were automatically added at boot. I notice there are 3 ways to add mydsl: .dsl, .uci, and .unc. Does this mean that the ultimate best way to add modules is still being searched for? I wouldn't mind it if the add-on apps were loaded via bootlocal.sh, with bootlocal.sh being loaded from a location specified in the kernel command line
|