On both ocassions the experience was the same, working through the various options to set up network configurations, cards, choose keyboard and timezone etc. There is no "reinstallation" as such, it has to be a "clean install". It was when viewing the dhcp options screen (which I did not want to configure - I was just looking) and selecting Done (or whatever it was), the message is something to the effect of "there are options that remain to be set up" with no way to get to them prior to the installation proceeding and a reboot occurring. I suspect that this was the point at which I ought to have then seen the passwords screen. If I had nothing else to do I'd be tempted to install a third time and more clearly record it in order to be able to post in a forum or submit bug report. I want to be doing another install on a box at home maybe over the weekend, I'll take the same disk and see if I can reproduce the experience there...
Roger Kerry Mayes wrote: > i recently installed 1.4.15 and was asked for three passwords (root > admin and backup). There was no way of missing it either. I wonder > if it was to do with *re*installing. Seems bizarre. > > On 05/04/07, Roger Searle <[EMAIL PROTECTED]> wrote: >> > >> > Looks like you didn't set the root password... maybe there's a >> problem with the installer at 1.4.15. >> > >> that's the thought that occurred to me when missing the option the >> second time, though didn't want to say so publicly given i was in hour >> one of my experience with this distro. i'm happy enough now . . . > > ssh has definately been off by default the last few times I've > installed (1.4.9 onwards I think?) > >> > ssh used to be enabled by default (and only for root), but on port >> 222, not the default 22. >> > >> nope, wasn't enabled by default on either port - >> [EMAIL PROTECTED]:~> ssh 10.1.1.241 -p 222 -l root >> ssh: connect to host 10.1.1.241 port 222: Connection refused >> [EMAIL PROTECTED]:~> ssh 10.1.1.241 -p 22 -l root >> ssh: connect to host 10.1.1.241 port 22: Connection refused >> >> a short time later after enabling it, it was fine - >> [EMAIL PROTECTED]:~> ssh 10.1.1.241 -p 222 -l root >> The authenticity of host '[10.1.1.241]:222 ([10.1.1.241]:222)' can't be >> established. >> RSA key fingerprint is >> >> > Steve >> > >> > >> > >> > >
