Quote:
Originally Posted by ziadh
3) Is /usr/local it's own filesystem, and is that read-only?
how can i know?
|
Type "
mount | grep local" if /usr/local is it's own filesystem, it'll show up in the output (and by filesystem, I mean that it shows up when you "
df -hFufs") You could also check
/etc/vfstab and see if it's set to mount read-only.
Quote:
Originally Posted by ziadh
5) Have you read the man pages for pkgadd and pkgrm?
haven't read the man because i did not want to waste too much time on 'installing' the software, and then i still have to configure it and run some tests
|
That's a dangerous mentality to have. If you've
never read the man pages for
pkgadd and
pkgrm, you need to stop what you're doing and read them.
man pkgadd
man pkgrm
If you don't get out of the "
I'll read the documentation later" phase, you're going to do something dangerous and blow away the system...and the documentation.
Quote:
Originally Posted by ziadh
6) Has this system been patched (ever)? There are some critical patches for the pkgadd and pkgrm commands that you might need.
i have no idea, 1st time using this solaris system, and its my company whi installed it and threw me in it hehe
|
Okay...case in point. Walk on eggshells. Read the man pages of commands you're unfamiliar with...before soliciting unknown strangers for help. If this is a system that your company depends on, rather than a "test box", you're going to need to get really familiar with the basics.
Let's start you off with a few basic guidelines;
Rule #1: Do not use the root account.
Rule #2: YOU do not USE the ROOT ACCOUNT, use sudo if you *really* need root! (install it if it's not present)
Rule #3: If a process halts, gives an error, or
SEGFAULTs, you read the
man pages.
Rule #4: Only one System Administrator to a computer.
Rule #5: One
fight question at a time.
Rule #6: No "Diet" drinks, no overhead lights.
Rule #7: Fights Troubleshooting sessions will go on as long as they have to.
Rule #8: If this is your first night at
FIGHT CLUB LQ, you HAVE to
fight google.
Now for a few things you're going to (eventually) need to know;
How to Boot off a Solaris CD into Single User Mode
Patch Check Advance (PCA) - Great tool for patching a system. Read the docs
first.
Basic Docs on Solaris (from Oracle) - This includes man pages.
So now that that's all out of the way...
Okay, "introduce" us to your system with the following commands (remeber to wrap the outputs in
[code] &
[/code]);
uptime
Not as important as you would think, but I don't trust anything that has the root password taped to the monitor with an uptime over 500 days.
uname -a
This will tell us the platform (sparc or x86), the revision of the kernel you're using, the version of the O.S (somewhat), and maybe the model of system you have.
cat /etc/release
This will tell us the exact version of the operating system, and what "update" it is.
prtdiag -v | head -20
This should tell us the exact make and model of system you have, and how much RAM/CPU you have.
df -hFufs
This will tell us exactly which filesystems are which, and where they're mounted at.
pkginfo -l SMCsyslng
Prints the current state of the package you installed (or attempted to).