[Lincs] Distro - Clarifying some points

[Chris Adams]

Yep I am lead. I am building from a debian system. Dont worry about the code
not working ;)

On 01/04/07, iain Baker <iain.dbaker at gmail.com> wrote:
>
> Wait a minute... i hope this isn't someone trying to apply sense and
> logic to the proceedings...
>
> ok, im gonna see what i can do to add to/confirm your thought process
> (these are only my opinions! please give us yours)
>
> On 4/1/07, James Taylor <jt at imen.org.uk> wrote:
> > Can we take a second to discuss the actual requirments as this is
> getting
> > into a slag fest of favorite distos without it seems, actually applying
> any
> > logic or real discussion on the point. Now, I've made some assumptions
> here,
> > so if you disagree with any of the questions, with any of the answers or
> > want to provide better ones then please go ahead without biting my head
> > off...
> >
> > 1) Whats the genaral point?
> > To get a bootable cd with as much software on to get people using Linux.
> The
> > cd should let them use Linux whilst not destorying their windows
> > installation, but allow them to install it from the CD [without a
> network
> > connection].
>
> sounds about right
>
> > 2) What people?
> > People who arn't nessicairly computer literate, people who maybe dont
> know
> > what an OS is.
>
> sounds about right... and also people who have heard of Linux and want
> to give it a try but don't know how
>
> > 3) Limitations because of the above?
> > Well, you've got to make it bootable and theres technical tricks that
> let
> > you mount compressed drives, but you're looking at playing with about 3
> gig
> > of virtual space on the 700 Mb Cd (I just made that up, cause I cant
> > remember, and I'm not an expert on the compression mounting thing, nor
> know
> > how much space has to be on the uncompressed partition)
>
> cant correct you because i dont know either... but the theory is sound
>
> > 4) Package Management.
> > There MUST be a package manager, (I havn't seen anyone pushing slackware
> as
> > a base system). This package manager allows the installation of basic
> > pre-configured binarys and settings files AND source files for custom
> > compilation. Custom packages should be easy to create to maintain the
> system
> > integrety (for removal of any file/package)
>
> Package manager is rather inconsequential whilst in Live CD mode, but
> yes, it will be needed for post install - and should be easy to use!!
>
> > 5) Package Updating
> > The computers will pull from a customisable list of servers the contents
> of
> > updated packages for installing, through the use of various tools both
> > graphical and normal.
>
> Agree so far
>
> > 6) Default Package Repositorys
> > Supposing that we rebadge [distoX]. Are we suggesting that the [distoX
> > default servers] should be used, or are we going to have LincsDisto
> source
> > servers (and :. a requirmenet for Lincs members to be responsible for
> > package maintainance of this distribution (and generic support for
> people
> > who will want to use both our sources and other compatible sources).
> > (Obviously the latter is nearly inconcevable amount of work, but if the
> > former, how does the Linc's default settings get applied to these
> installs?)
>
> erm... yeah... about that... unless someone wants to become incredibly
> devoted i think maintaining our own repositories is a job too far...
> which may mean the branding may need to be limited to the desktop and
> not the apps... that way LUGifying the Distro is a one shot action...
> what do other people think?
>
> > 7) Official managment of release
> > Who is responsible for the official managment of releases? How will the
> > documentation of releases work? Is there going to be a checking system,
> by
> > that I mean very much committe level for which disputes or arguments can
> be
> > put to? (This can be very simple through the use of something like UK
> Voting
> > or similar)
> >
> > 8) Contributors
> > Exactly how will contributing to the system work?  (The answer to this
> > question again depends on various answers above).
>
> to 7 and 8 i say... Yes! or Good point! or maybe even, Oops! at the
> moment its a one man band with graphical input from anyone that wants
> to post... but that has its faults...
>
> > 9) Documentation
> > Is there an associated documentation project / how is this going to
> work?
> > (the answer of this question depends on various answers from above)
>
> No... not yet, but this is another place that anyone can contribute...
> referring to Chris Adams as the projects current lead.
>
> > 10) Legal bumpf
> > Are lincs covered legally for this release breaking computers. Supposing
> > there is a mistake in the instructions to install software, which causes
> > users to wipe their drives, under any situations, are Lincs
> > members/distribution maintainers/documentors at risk from being sued.
> (Has
> > legal advice (and by that I mean professional legal advice eg fsf or
> > professional body) been sought on this topic)
>
> Easy.. Not if we put a disclaimer on it (see any magazine cover disk)
>
> > 11) Install to disk What options does the disto have for pernament
> > installation?
> > The disto should allow a range of installations, including just using a
> > folder on the fat32 as well as full blwon reinstall. There should be
> options
> > to install base system without any extra packages, as well as standard
> user
> > install.
>
> in my mind i had a similar install to disk option as Knoppix- installs
> the live cd as is, then use package management afterwards to make any
> adjustments... but i may be over simplifying the options
>
> > 12) What license is the disto under?
> > hahahah im not going to try to answer that one. I will get it wrong
> > (Presumably more then one disto)
>
> again... a good point well presented (although maybe more pie charts
> are in order next time to jazz it up a bit?)
>
> _______________________________________________
> Lincs mailing list
> Lincs at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/lincs
>



-- 
"I cant afford a good nickname, so i got this one."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.lug.org.uk/pipermail/lincs/attachments/20070401/06873506/attachment.html