Dennis Clarke [EMAIL PROTECTED] wrote:
The boot -m milestone=none resulted in this :
Booting to milestone none.
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to
[EMAIL PROTECTED] wrote:
Yes.
And we've long said you shouldn't be doign that :-)
Show me the doc or white paper that says so and why.
Read my Usenet postings :-)
But the explanation is fairly simple: you cannot recover from a number
of failures (corrupt vfstab, bad /dev* links
But the explanation is fairly simple: you cannot recover from a number
of failures (corrupt vfstab, bad /dev* links for boot device) without
having /usr mounted; you cannot mount /usr when those things happen.
And you cannot recover if the same happens with a big / installation
either.
You
Please explain why you believe this.
the only difference I see in your case is that you would need to find
the /devices entry to mount /usr so it makes sense to have find or
a name completing shell in /
When you boot from a device the node does not need to be present in
/dev* in order for you
[EMAIL PROTECTED] wrote:
Please explain why you believe this.
the only difference I see in your case is that you would need to find
the /devices entry to mount /usr so it makes sense to have find or
a name completing shell in /
When you boot from a device the node does not need to be
Joerg Schilling schrieb:
[EMAIL PROTECTED] wrote:
When you boot from a device the node does not need to be present in
/dev* in order for you to remoutn it r/w so you can fix it.
This was true before /devices was on the devfs filesystem.
But having /usr ready helps a lot.
It is no fun,
Daniel Rock [EMAIL PROTECTED] wrote:
Joerg Schilling schrieb:
[EMAIL PROTECTED] wrote:
When you boot from a device the node does not need to be present in
/dev* in order for you to remoutn it r/w so you can fix it.
This was true before /devices was on the devfs filesystem.
But
On Wed, 2005-11-16 at 03:52, Dennis Clarke wrote:
The boot -m milestone=none resulted in this :
Booting to milestone none.
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance
-sh: /bin/i386: not found
-sh: /usr/sbin/quota: not found
-sh: /bin/cat: not found
-sh: /bin/mail: not found
#
# df -ak
df: not found
# ls
ls: not found
# pwd
/root
That looks like you have split / and /usr, right ?
And we've long said you shouldn't be doign that :-)
Not sure
On Wed, 2005-11-16 at 15:01, [EMAIL PROTECTED] wrote:
But I'm certain our best practices now are something like:
/
/var- for servers only
/export - separate the users/data from the rest.
I'd agree with that completely. In fact I'd actually say that
on general purpose
[EMAIL PROTECTED] writes:
- you run out of space more quickly because you dividing line
will not be correct
- hard recoverability issues become impossible with net/cdrom boot
- the gain in stability is fairly minimal (a read-only /usr mount
mostly increases
Darren J Moffat [EMAIL PROTECTED] writes:
On Wed, 2005-11-16 at 15:01, [EMAIL PROTECTED] wrote:
But I'm certain our best practices now are something like:
/
/var- for servers only
/export - separate the users/data from the rest.
I'd agree with that completely. In
DJM == Darren J Moffat Darren writes:
DJM I also tend to have /var/core and /var/crash separate as well but
DJM thats because I don't actually want live upgrade to copy the core and
DJM crash files over to the new boot environment, because they aren't
DJM relevant.
DJM
On Wed, 2005-11-16 at 16:21, Matthew Simmons wrote:
DJM == Darren J Moffat Darren writes:
DJM I also tend to have /var/core and /var/crash separate as well but
DJM thats because I don't actually want live upgrade to copy the core and
DJM crash files over to the new boot
DJM == Darren J Moffat Darren writes:
DJM I use to do that but if using dumpadm and coreadm to actually put them
DJM else where seemed like a better solution to me - mainly because they
DJM have the functionality built in so why not use it.
On the other hand, /var/crash is a
On Wed, 2005-11-16 at 16:43, Matthew Simmons wrote:
DJM == Darren J Moffat Darren writes:
DJM I use to do that but if using dumpadm and coreadm to actually put
them
DJM else where seemed like a better solution to me - mainly because they
DJM have the functionality built in so
DJM == Darren J Moffat Darren writes:
DJM Which brings me to very minor grip about the default config of
DJM Solaris, it is /var/crash/hostname at the first time you booted
DJM which when using DHCP in the default Solaris config can change. Sure
DJM I can find out what it is
The boot -m milestone=none resulted in this :
Booting to milestone none.
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
single-user privilege assigned to
18 matches
Mail list logo
