Not the correct release of Solaris 8 for Sun-Blade 1000's (you need
Solaris 8 07/01 (Update 5) or later
You have invalid settings in your OBP. Set them back
by issuing "set-default boot-file" and "set-default boot-device".
Your module path isn't complete. Use "boot cdrom -a" and watch
the prompts, the default settings are the ones you want to use when
prompted. The defaults are given surrounded by [ ]'s.
Part II:
Ahh, the Enterprise 250... It has a nifty feature called "RSC"
or "Remote System Control", which allows exactly what you want,
and more. You can use the system as a headed system (i.e. with
a local keyboard/monitor), and remotely diagnose and log into it
using RSC. Checkout http://www.sun.com/servers/rsc.html.
This will erase the network configuration of the machine.
When it reboots, it will ask you the network questions again,
which you can answer YES to the "Use DHCP?" question.
A:
Using the "Admin Pack" CDROM containing AdminSuite, you need
to double-click (or manually run) the "installer" program
located at the top-level directory.
Making alternate boot environments is not something you want
to do manually. In your case, it sounds like you haven't updated the
vfstab on the other partition to point at the right / filesystem.
A:
First of all, try using Solaris 8. If that
does not work, make sure the "output-device" setting
in the PROM is set. You can access the PROM during
install (you said you could install it, so during
install, just press L1-A to get to the prom).
A:
Your Ultra-10 might have a secondary video card installed on the
video card slot. If so, try using the on-board video connector
in the lower-left (see image).
If you only have one connector, try using a different monitor,
I have had instances where perfectly good PC monitors just don't
understand the VGA signal coming from the Ultra 10.
A:
You can use "flar split -f <flar>" to extract the
contents of a flash archive (just like you can use "tar -xf"
to extract the contents of a tar file).
However, this doesn't mean that what you extract will
be bootable. To make it bootable, you must use Solaris
Install to install the archive.
A:
If the machine no longer powers up, that sounds like
a problem with the power supply or some other critical
hardware component, which Solaris Install cannot solve.
Try replacing the Ultra 10.
A:
As always, you should consult your Veritas documentation, as it
contains detailed instructions on how to upgrade Solaris. If you
lost your docs, you must contact Veritas and get additional copies.
I found a good doc online by searching the Veritas website:
A:
It sounds like you don't want to have local servers on each
subnet. If that's the case, you can use DHCP to install all
your machines, BUT you must configure each and every router
to forward DHCP request packets, as most of them do not do it
by default. Once you do this, you can have a single DHCP server
for all subnets, and you can use the DHCP vendor options embedded
in the DHCP server to make each and every netboot use the same
jumpstart profile and/or sysidcfg file. There was an earlier question
in this forum, which I answered with a pointer to the DHCP vendor
option documentation, which explains how to do this.
There are projects looking at implementing unicast DHCP, so you
would not have to modify your routers, but at this time it is
not something officially implemented in Solaris.
A:
You can press L1-A (Stop-A, kind of like Ctrl-Alt-Delete
for Windoze boxes).
However, if you break out of it, the machine will still
not boot, but simply return you to the "ok" prompt. If
you have attempted to boot from a network server,
make sure the server and client are on the same subnet,
that there is an /etc/ethers and /etc/bootparams
entry for the client on the serve, and make sure things
like in.rarpd and rpc.bootparamd are running on the
server.
A:
Did you use the special silver serial/LOM connector
that came with the Netra? You must use it at some
point in the connection, as it is a very special,
unusually-wired connector, not your typical serial
port connector.
Also, if you are plugging in through some kind of
network lab breakout room, make sure there is no
crossover going on in the wiring inside the walls
of the lab, as that will also render your connection
useless.
A:
Boot the cdrom, put it in single-user mode like this:
ok boot cdrom -s
Then run the "format utility", /usr/sbin/format,
select the disk from the numbered list, and then
select "fdisk - run the fdisk program",
which will give you an interactive fdisk session
where you can remove the windows partition and
make your solaris partition any size you want
(up to the limit of the disk).
A:
Note 'eth0' is something you may find on a Linux-based
system, but not Solaris. On solaris, the names of the
interfaces are based on the drivers driving them,
for example "le0", "hme1", or "eri2".
If you do an "ifconfig -a plumb", followed by an "ifconfig -a",
and you don't see the ethernet interface listed along with
the loopback interface, chances are you a) didn't install
the correct driver, or b) it's not a supported ethernet
interface. You can also check the output of "boot -rv" and
"dmesg" to see if there is an indication that the ethernet
adapter was found and initialized.
A:
If you have installed the appropriate locale packages
for the locale you want to switch to, you can put:
LANG=<locale>
LC_ALL=<locale>
in your /etc/default/init file. This will make the change
permanent after rebooting. For the current session, you
can put these env variables in the env of the running process
to make it switch to the new locale. However, it's easiest
to just reboot to make sure all processes receive the new
locale settings.
If you do this, and you get a bunch of "couldn't set locale
correctly" after rebooting, then you have to install the
locale package(s) from the Solaris Install CD or the "Language CD".
A:
You must install a boot server on the same subnet
as the client box. On the boot server, you would
run "addclient", and use the "-c", "-p", and
"-s" options to point at the jumpstart server's
jumpstart rules file, sysidcfg file, and
install image, respectively.
If you cannot install a boot server on the same
subnet, you must modify your jumpstart server to
become a DHCP server, and have a bootp relay agent
sit on the same subnet as the client (or modify
the existing router on that subnet to become a bootp
relay agent).
A:
Plug in both adapters, and hook up monitors to them.
Then copy /usr/dt/config/Xservers to /etc/dt/config/Xservers,
and change the last line to be something like this:
:0 Local local_uid@console root /usr/openwin/bin/Xsun :0
-nobanner -dev /dev/fb0 left -dev /dev/fb1 right
The base Solaris 8 system does not have support for
the c&t 69000 chipset. However, there are solutions
that you want to check out. The first (and probably
best chance for you) is to get the Solaris XFree86
Video Driver set, available at
http://soldc.sun.com/developer/support/driver/tools/video/video-index.html.
The entire set of XFree86 drivers were ported to Solaris.
You can also try Xi Graphics, they make a 3rd-party set of
video drivers that may work with your video adapter. Check
out http://www.xig.com.
A:
The "sysid_config" setting in your /etc/bootparams file
should point to a *directory* containing a file called
"sysidcfg". You should:
1. Run addclient again, and use the "-c servername:/jumpstart" option.
2. Rename the ws_sysidcfg file to "sysidcfg" and make sure it's
in the "/jumpstart" directory.
A:
Answerbook2 server is on the "Documentation CD", which is a separate CD
from the ones that contain the Solaris operating environment, which is what
is installed during JumpStart. Therefore, it cannot be automatically
installed during JumpStart.
You could transfer all of the AB2 packages off the CD (out of the
/common directory on the CD), using "pkgtrans" and onto a networked system.
Then, install the packages using "pkgadd" in a custom JumpStart postinstall.
A:
The best way is to use Live Upgrade. Despite the name, you
don't have to upgrade, you can simply migrate your filesystems
to a different set of devices with different sizes. For example,
if you have a system with 1000mb of / and 500mb of /home, you can
create a new boot environment using 1200mb for / and 300mb for /home
and boot to that boot environment. Creating the boot environment will essentially copy all of your files from the "old" boot environment to the "new" boot environment, the one with the right sizes.
A:
Yes, there were some patches released with incorrect file permissions in the patch. Make sure all files have read access, for example: chmod -R a+r 108434-06.
Alternatively, try to download the patch again from the source you downloaded it
originally. It may take time for the fix to propagate to whatever source you were using. It was fixed on March 18.
A:
If you are in a timezone that observes Daylight Savings Time, then you must set your timezone to that timezone, rather than using the GMT offset.
For example, if you live in Florida, USA, then you should set your timezone to "US/Eastern" or "America/New_York", rather than "GMT+5" since it's GMT+4 during the summer, and your time will be off by an hour. If you're in California,
you should set it to "US/Pacific" or "America/Los_Angeles".
You can change the timezone by editing the /etc/TIMEZONE file. Also, on Intel machines you must run "rtc -z " then "rtc -c". This corrects the Solaris time zone lag setting, since local time is stored on intel machines.
A:
No. By definition, a reinstallation of the operating environment means a fresh install, one which overwrites everything. Anything that you want to preserve should either be on a separate file system and preserved with the "filesys preserve" keyword in a JumpStart profile, or be backed up manually with a JumpStart preinstall script.
A:
If your modem is one of the supported modems, the drivers should already be loaded.
For connecting with a dial-up connection through an ISP, my recommendation is to use a combination of X-ISP and PPPD. You can get both at http://xisp.hellug.gr/.
