On Fri, 1 Aug 2003 19:25, Buchan Milne wrote:
> I don't agree that we should be encouraging users to log in to a
> desktop as root ...
Agree. But it may be more important to do that one time only.
> But maybe the first user that logs in should be assumed to be the
> "admin"?
Too risky. What happens when you forget about this and put hundreds of
boxes out there whose first user will be an admin?
>> Start Here
>> Would you like to copy the installation media to disk?
> Would you like to setup a software repository for this and other
> machines, and/or a deployment server? (PXE/DHCP the whole bang
> shoot).
Sure... if they can easily go for the simple option first (KISS, most
installs will be small).
>> This Setup Guide would need to be clearly and explicitly referenced
>> by the installer and documentation, for example:
>>
>> +---------------------------
>> | Finished installation
>> |
>> | If you would like simple instructions to set everything up
>> | and get the best out of your new Mandrake system, login as
>> | the root user and click on the Setup Guide.
> Agree.
Ta! (-:
> I am not sure about the tool itself, but IMHO we need to consider
> getting *really* *excellent* documentation available, all in one
> place, either Yelp (for GNOME users) or KHelpcenter. Since they both
> support scrollkeeper, it may be feasible this way, but at present the
> search capabilities are not good enough.
> I haven't managed to get db2omf to convert docbook to an omf file
> that scrollkeeper will validate yet (I tried with the rpm-howto). I
> will try with some others, such as the samba howto collection.
Please! If we can have one reasonable help system *with*search* that
both major WMs share (and call it nirvana if it works on other WMs as
well), we're onto a winner.
> BTW, before there is a tool for setting up the entire server, we need
> to have tools for some of the individual pieces. For example, the
> Active Directory wizard in Win2k/Win2k3 sets up the following (in
> linux equivalents):
> - -primary DNS for forward and revers lookups, with client updates
...for which we need to ask:
LAN address: [ . . . ] (fill in from network setup)
Netmask: [255.255.255.0 ] (ditto, or /width, e.g. /24)
LAN domain: [mydomain ] (ditto)
> - -DHCP server
Basically yes/no plus ask if they want a restricted range else default
to 100..199?
> - -OpenLDAP master (with kerberos-style service records)
Tougher. Need a fair whack of information.
> - -Kerberos master (with kerberos-style service records)
I've not used Kerberos yet, so can't speak to it.
> - -Samba domain controller
Ditto LDAP comment. And while we might steal some principles from
another tool (e.g. WebMin) I vote we don't rape the config file as
thoroughly. (-:
> I have done some testing against win2k3, mainly for samba3 + kerberos
> support, and I have some things I would like implemented, but don't
> have the time ...
Ah! If I could just clone me half a dozen times and set two of us
working to fill mouths, fuel tanks and real estate agents' hands, I'd
have four of me to spare for such things...
> We could start with having Kerberos client-side setup tools, and
> break the authentication setup out into a drakxtool, which may get us
> Active Directory membership (which other competitors named after
> clothing seem not to have realised yet, even though they ship samba3
> in their latest beta!).
Now for the language wars: PERL or Python? (-:
Cheers; Leon
