mvista 2.0 cdk and login username and password

mvista 2.0 cdk and login username and password

[John F Davis]

Hello

What's the root login password for a newly installed sbs-k2, cdk 2.0,
target login?  The final paragraph of the sbs-k2
installation section (in the pdf) says to login, but doesn't specify a
password for root.

I installed the cd and when I try to login to a nfs root mounted partition,
I get a login prompt, but I can't login.
My installation doesn't   have a /..../target/etc/passwd file, which leads
me to believe I missed something during
the install.  However, I searched the CD for rpm's and none of them
owns/supplies  the /.../target/etc/passwd file.
Am I supposed to modify the inittab on the host machine so it boots single
user mode and create the /etc/password
file by hand, modify the inittab for multiuser mode and then reboot?

Also, when am I going to get a hardhat zone login id?  I am sure MVista has
a FAQ which addresses this issue.

John F. Davis
IBM


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: mvista 2.0 cdk and login username and password

[Mark Hatle]

John F Davis wrote:
>
> Hello
>
> What's the root login password for a newly installed sbs-k2, cdk 2.0,
> target login?  The final paragraph of the sbs-k2
> installation section (in the pdf) says to login, but doesn't specify a
> password for root.

There is no root password by default.  Normally you type root and you
are logged in.. (Security hole?  for a desktop/workstation distro yes,
but not for an embedded distro!)

> I installed the cd and when I try to login to a nfs root mounted partition,
> I get a login prompt, but I can't login.
> My installation doesn't   have a /..../target/etc/passwd file, which leads
> me to believe I missed something during
> the install.  However, I searched the CD for rpm's and none of them
> owns/supplies  the /.../target/etc/passwd file.
> Am I supposed to modify the inittab on the host machine so it boots single
> user mode and create the /etc/password
> file by hand, modify the inittab for multiuser mode and then reboot?

Sounds like the install did not work.  (Did you use the installer?)  The
"base-passwd" package controls the password files.  It installs a
passwd/group template into (target filesystem) /usr/share/base-passwd
and then proceeds to copy them over into /etc/passwd,group.  This is
done in case you already have an /etc/passwd,group so that it will not
be over written, but "upgraded".

> Also, when am I going to get a hardhat zone login id?  I am sure MVista has
> a FAQ which addresses this issue.

If you are a paying customer, contact your support representative, and
not the linuxppc-embedded list as they have nothing to do with our
product.

Mark Hatle
MontaVista Software, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: mvista 2.0 cdk and login username and password

[John F Davis]

Hello Mark,

I don't have a /etc/passwd file.  Thus I can't login.  I didn't use the
install script.  I just installed the rpm's by hand
like we did in cdk 1.2. i.e rpm -ivh --ignorearch *.rpm.  I didnt want to
use the script because I didn't use the
cdrom.  I had a copy of the cdrom filesystem mounted via AFS.  The script
seems to think it is only used via a cdrom or mountable media.
I figured it would be easier to just install all the rpm's rather than try
to patch your script.  I already have problems installing
both a 405 CDK and 750 CDK on the same machine.  I get errors about rpm
conflicts with common files.  My coworker says mvista has
released a patch for this, but I haven't tried using it yet.

I will try to reinstall the passwd package again by hand.  However, I don't
see how installing the rpm manualy would cause
it not to create the /etc/passwd file.  I also don't understand why the rpm
which creates the files doesnt register with the rpm database
that it owns the file.  ie. 'rpm -q -f
/opt/hardhat/devkit/ppc/7xx/target/etc/passwd' comes up blank.

Also, I didnt see anything in the install script which would make a
etc/passwd file so it must be as you said below.  The file is
created via a rpm.

I got my hhzone password now.  I look forward to seeing what's up there.

Thanks to you and the rest of the mvista team for the quick response.  I
dont consider the issue closed yet, but
I do appreciate your help so far.

John

Mark Hatle <fray@mvista.com>@mvista.com on 11/05/2001 05:44:46 PM

Sent by:  fray@mvista.com


To:   John F Davis/Raleigh/IBM@ibmus
cc:   linuxppc-embedded@lists.linuxppc.org, support@mvista.com
Subject:  Re: mvista 2.0 cdk and login username and password



John F Davis wrote:
>
> Hello
>
> What's the root login password for a newly installed sbs-k2, cdk 2.0,
> target login?  The final paragraph of the sbs-k2
> installation section (in the pdf) says to login, but doesn't specify a
> password for root.

There is no root password by default.  Normally you type root and you
are logged in.. (Security hole?  for a desktop/workstation distro yes,
but not for an embedded distro!)

> I installed the cd and when I try to login to a nfs root mounted
partition,
> I get a login prompt, but I can't login.
> My installation doesn't   have a /..../target/etc/passwd file, which
leads
> me to believe I missed something during
> the install.  However, I searched the CD for rpm's and none of them
> owns/supplies  the /.../target/etc/passwd file.
> Am I supposed to modify the inittab on the host machine so it boots
single
> user mode and create the /etc/password
> file by hand, modify the inittab for multiuser mode and then reboot?

Sounds like the install did not work.  (Did you use the installer?)  The
"base-passwd" package controls the password files.  It installs a
passwd/group template into (target filesystem) /usr/share/base-passwd
and then proceeds to copy them over into /etc/passwd,group.  This is
done in case you already have an /etc/passwd,group so that it will not
be over written, but "upgraded".

> Also, when am I going to get a hardhat zone login id?  I am sure MVista
has
> a FAQ which addresses this issue.

If you are a paying customer, contact your support representative, and
not the linuxppc-embedded list as they have nothing to do with our
product.

Mark Hatle
MontaVista Software, Inc.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: mvista 2.0 cdk and login username and password

[Tom Rini]

On Tue, Nov 06, 2001 at 04:15:25PM -0500, John F Davis wrote:
>
> Hello Mark,
>
> I don't have a /etc/passwd file.  Thus I can't login.  I didn't use the
> install script.  I just installed the rpm's by hand
> like we did in cdk 1.2. i.e rpm -ivh --ignorearch *.rpm.  I didnt want to
> use the script because I didn't use the
> cdrom.  I had a copy of the cdrom filesystem mounted via AFS.  The script
> seems to think it is only used via a cdrom or mountable media.

I haven't tried AFS, but loopback is fine.  --hhlimage /mnt works for
me.

> I will try to reinstall the passwd package again by hand.  However, I don't
> see how installing the rpm manualy would cause
> it not to create the /etc/passwd file.  I also don't understand why the rpm
> which creates the files doesnt register with the rpm database
> that it owns the file.  ie. 'rpm -q -f
> /opt/hardhat/devkit/ppc/7xx/target/etc/passwd' comes up blank.

The script also does some setup of the system.  If you haven't gotten
far, re-install using the script.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: mvista 2.0 cdk and login username and password

[Mark Hatle]

John F Davis wrote:
>
> Hello Mark,
>
> I don't have a /etc/passwd file.  Thus I can't login.  I didn't use the
> install script.  I just installed the rpm's by hand

If you don't use the installer script then your environment may not be
correct and you may be (and probably are) installing things out of
order.  Without the proper environment and order, post install scripts
may not run correctly (and in the case of initscripts and shell script
most likely won't.)

> like we did in cdk 1.2. i.e rpm -ivh --ignorearch *.rpm.  I didnt want to
> use the script because I didn't use the
> cdrom.  I had a copy of the cdrom filesystem mounted via AFS.  The script

This isn't CDK 1.2.  Things have been radically improved, and by having
additional features you need to use the installer.  Page 20 of the
manual provided on the CD explains the --hhlimage option.

> seems to think it is only used via a cdrom or mountable media.

Any place in the system can be used as long as the CD directory
structure is maintained.

> I figured it would be easier to just install all the rpm's rather than try
> to patch your script.  I already have problems installing

Well it's not.

> both a 405 CDK and 750 CDK on the same machine.  I get errors about rpm
> conflicts with common files.  My coworker says mvista has
> released a patch for this, but I haven't tried using it yet.

Again, this is handled by the installer.  If you have a problem (when
using the installer) contact your support representative.  They will
handle these issues!

> I will try to reinstall the passwd package again by hand.  However, I don't
> see how installing the rpm manualy would cause
> it not to create the /etc/passwd file.  I also don't understand why the rpm
> which creates the files doesnt register with the rpm database
> that it owns the file.  ie. 'rpm -q -f
> /opt/hardhat/devkit/ppc/7xx/target/etc/passwd' comes up blank.

The RPM _DOES NOT_ own those files.  No RPM owns those files.  They are
created by a post install script!

> Also, I didnt see anything in the install script which would make a
> etc/passwd file so it must be as you said below.  The file is
> created via a rpm.

Its not in the installer, it's in the base-passwd rpm's post install
script.

Again, if you are having problems installing, running, etc please
contact support as you/your company has obviously paid for the product!

--Mark

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/