On Mon, Jul 28, 2008 at 06:29:24PM +0200, Paul Slootman wrote: > On Mon 28 Jul 2008, Jérémy Bobbio wrote: > > On Fri, Jul 25, 2008 at 01:27:29PM +0200, Paul Slootman wrote: > > > - I chose expert install. What's the difference with the normal install? > > > I didn't really detect anything that was particularly "expert"... > > > > The difference between "expert" and "normal" installation is just a > > matter of debconf priority. Normal installations just show debconf > > questions with priority high or critical. Expert adds medium on top of > > that.
Actually, expert is medium + low.
> Hmm, OK; perhaps that could be made a bit more clear, that this concerns
> the debconf questions? I expected "expert" to e.g. do manual
> partitioning be default instead of the guided partitioning; that sort of
> thing.
I don't have time to look up right now, but IIRC the difference is well
explained in the manual. The boot menu is a bit tight on space to write
a longer explaination.
> > > - It was impossible to setup the disk layout I wanted:
> > > - root on raid1 over 2 partitions
> > > - ditto swap and /boot
> > > - /var and other things on LVM on RAID1
> > > [???]
> > > In short, most of the configuration entered was not remembered when
> > > "writing to disk".
> >
> > Known issues, see #391479, #391483, #393728, #398668, #475479. Should
> > be fixed before Lenny.
>
> OK, great. I thought I should mention it as when I last did this in
> april with the installer then (I believe I did use the testing
> installer) it all worked fine, and this was now a regression.
This issues have been here for quite some time, as far as I know.
> > > - The question "should root be allowed to login" should indicate that this
> > > includes the console; I was thinking of ssh access. BTW, I think that
> > > offering to install an ssh server should also be asked, I expect that to
> > > always be there... which is a pain if you install the server somewhere
> > > and can't access it remotely.
> >
> > Are you talking about the following template?
> >
> > Allow login as root? If you choose not to allow root to log in, then
> > a user account will be created and given the power to become root
> > using the 'sudo' command.
> >
> > I don't see how exacltly it could be improved, as it seems pretty
> > obvious to me that this is a system-wide setting.
>
> It didn't occur to me that restricting root access to the console would
> be something useful... I guess it may be :-) I expected this to concern
> the AllowRootLogin parameter for the ssh daemon.
When answered "no" to this question, d-i setup a system fully based on
sudo, without a root account. Other distributions have such setups by
default (Ubuntu, for example).
> > > - The rescue boot also asks for hostname, domainname, country, etc.,
> > > so I was a bit worried that I was simply doing an install again.
> > > Why is that info necessary for a rescue console?
> >
> > Location and language are asked because rescue mode is also localized
> > and having help messages in your native language is a desirable choice.
> > Same for keyboard layout. The network configuration is done because
> > rescue mode might need to retrieve installer components only available
> > from a Debian mirror.
> >
> > IIRC, these are the only questions currently asked. Both newt and GTK+
>
> No, I am sure that I was asked for hostname and domainname. That was
> when I started worrying...
hostname and domain name are part of the network configuration step.
I wonder if any rescue tasks make use of it… If they don't maybe we
could preseed these values to their default when rescue mode is
activated.
Cheers,
--
Jérémy Bobbio .''`.
[EMAIL PROTECTED] : :Ⓐ : # apt-get install anarchism
`. `'`
`-
signature.asc
Description: Digital signature
