Well, AIF I don't think is needed. Memtest is nice but really only useful for live cds, not very useful on a server. Nmap could just stay in the repo and they can get it later because for basic site serving we wouldn't use it. Parted is nice as part of the live CD but not necessary since we do our disk management in the setup using cfdisk. Fuse is nice but for a beta ISO not needed. dmraid i don't think would be needed.
I would say for a starter ISO we could get in just the basics with our mods to config files and such so that it's AS ready off the cd. Then we can work on making a more expanded one to include normal server utils like samba, bind, httpd(default but not required) and the like. Markus M. May wrote: > Hmm, > > it is really not taking any orders from me as well :-) > > Whatsoever, I am still quite unsure, what packages we do need to execute a > first ISO. From what I have gathered the following packages are required: > > 1 aif > 2 aufs2 > 3 aufs2-util > 4 base > 5 bash > 6 coreutils > 7 cpio > 8 dhcpcd > 9 dmraid > 10 dnsutils > 11 dosfstools > 12 elinks > 13 file > 14 fuse > 15 gnu-netcat > 16 inetutils > 17 kernel26 > 18 memtest86+ > 19 nfs-utils > 20 nmap > 21 openssh > 22 parted > 23 vim > > We should at least provide most of these on our CD as well. Therefor I will > start to build some packages of the above list, which do belong on the CD, or > are needed for the ArchLinux ISO-Image creation (using Overlays): > > AIF (do we really need this?) > AUFS2 and AUFS2-Utils (these are needed for the CD) > > Is dmraid, dosfstools really needed? Probably this one could be shifted into > the next release? Could we also move fuse, memtest86+, nmap and parted? I > think vim would be a real good one to put into the distro as well. > > Have I forgotten anything, or have I misunderstood anything? > > What do you think, shadowbranch, since you seem to have made already your > first experiences with archiso????!!! > > R, > > Markus > > > > > > ----- Original Message ----- > From: dmoree at shadowbranch.com > To: general at lists.archserver.org > Date: 16.12.2009 15:13:50 > Subject: Re: [ArchServer-General] [ ArchServer-General ][ ArchServer-General > ] To Do List > > > >> I was working on it but I always seem to have a problem if I use archiso >> to do my bidding! Muhahahaha! Oh sorry, evil side came out. >> >> Markus M. May wrote: >> >>>> 2009/12/15 Markus M. May : >>>> >>>> >>>>> The Todo list is quite a big thing. Especially the task concerning the >>>>> Package Management. I am also very interested in this, and already know, >>>>> that quite some people on AL are interested in something like this as >>>>> well. Let me just suggest some additional requirements: >>>>> >>>>> >>>> Yes, the APP is certainly the biggest task, probably followed not far >>>> behind by the Installation ISO :-/ >>>> >>>> >>> Since I started already the creation of an ISO for a different project >>> (ArchLinux Development Stack), I would like to stand up and build an >>> initial ISO. >>> >>> R, >>> >>> Markus >>> >>> >>> >>>>> 1) no real db-dependencies, if at all possible, by using a common >>>>> DB-Framework >>>>> >>>>> >>>> Database agnostic is even better, as long as it does support >>>> PostgreSQL one way or another :) The rest of the apps (flyspray, >>>> mediawiki etc) are all using PG for their database and I'd really hate >>>> to have to be running 2 DBMS packages on the server ;-) >>>> >>>> >>>> >>>>> 2) probably we could factor out the SCM (SVN, Git) stuff and put these >>>>> into separate modules, so that the application is agnostic of the used >>>>> SCM (this is probably a step 2 thing). >>>>> >>>>> >>>> That sounds like it would be very complicated, but it would definitely >>>> help the AL guys use it as AURv2 so if Daniel, or someone else, can >>>> work out a way to make it work then even better again! >>>> >>>> >>>> 2009/12/16 Daniel Moree : >>>> >>>> >>>>> I'd be happy to take on the APP. I currently work for a college doing web >>>>> applications programming and database support, as well as a bunch of other >>>>> stuff. I currently have a CMS solution that is very portable and highly >>>>> configurable that could just about drop in on the server. The most I would >>>>> have to do is write a module for working with the git repos. I'll setup a >>>>> version on my site and start working on something to see how it goes. >>>>> Should >>>>> have a beta in a week or two. >>>>> >>>>> >>>> Sounds ace! :D Thanks for putting your hand up Daniel :) >>>> >>>> >>>> >>>>> BTW, my site is www.shadowbranch.com and I am also willing to mirror for >>>>> AS >>>>> if needed. I have 100mb stream to the net so plenty of bandwidth for now. >>>>> >>>>> >>>> Let me know the IP address that rsync connections will come from so I >>>> can whitelist it to let you pull from the main server. Also the >>>> server's physical location, and the URI(s) where the AS tree will be >>>> available :-) >>>> >>>> >>>> 2009/12/16 Markus M. May : >>>> >>>> >>>>> if you are going to integrate the git-repo as well, then there is no need >>>>> for any theming there. probably we could then just use something like >>>>> http://www.xiphux.com/programming/php/gitphp/ (GitPHP), so that the whole >>>>> stuff is done using one application as a base? >>>>> >>>>> What do you think? >>>>> >>>>> >>>> I like not reinventing the wheel ;-) >>>> _______________________________________________ >>>> ArchServer Project General Mail List >>>> Post messages to: general at lists.archserver.org >>>> Administer your subscription: http://lists.archserver.org/listinfo/general >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> ArchServer Project General Mail List >>> Post messages to: general at lists.archserver.org >>> Administer your subscription: http://lists.archserver.org/listinfo/general >>> >>> > > > > > _______________________________________________ > ArchServer Project General Mail List > Post messages to: general at lists.archserver.org > Administer your subscription: http://lists.archserver.org/listinfo/general > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.archserver.org/pipermail/general/attachments/20091216/b7f1c62e/attachment-0001.html>
