Search results for query: *

i assume you saw under 'state' in vmsa that the disks are 'not setup'...check your /etc/vfstab to see if there are any entries that call those disk devices (commented or uncommented). they may be disks in use or legacy disks that are not under volume manager control. you can always use...

the above suggestion is fine if the file i unique otherwise you can issue "stty kill x". if you issue stty without any arguments you'll notice kill is set to @. just replace x in the previous command with some other character that is not present in the command line you're trying to issue.

this may not be the case but when i have gotten that error it's because the binary that issuing this is NOT an hp-ux binary.

not dangerous. just informative. you can modify the verbosity and content of the /usr/adm/SYSLOG file by tinkering with the /etc/syslog.conf file. i choose to let syslogd do whatever it wants and mentally weed out the fluff when looking at the SYSLOG file.

edit the /etc/inetd.conf file and comment the following line: bootp dgram udp wait root /usr/etc/dhcp_bootp dhcp_bootp -o /etc/config/dhcp_bootp.options and then issue /etc/killall -HUP inetd to effect the changes.

it actually is as simple as you described but you need to get your router/switch people involved. we used to do it here all the time to 'bridge' gaps between subnets. it really has a small niche now though. especially when dealing with 'inside' vlans and 'outside' ones. switching and routing...

which subnet is the remote workstation on? when you posted the netstat it looks as though you omitted the n as one of the options. the reason for -rn is netstat will return ip #'s and not hostname resolutions. in my experience with these situations you're better off with a default gateway that...

you will need to export the parent directory of the file that you want to have root access to. after editing the exports file issue 'exportfs -a'. /etc/exports entry: /dirname_to_share -root=hostname_of_machine_to_have_root_access

i actually had this exact same issue. i ended up replacing the network card and was good to go. this was on a sun ultra5 that we still use as a license server. hope this helps.

just change the root entry default shell in the passwd file to /bin/ksh. that's the standard shell for root in the hp and sun world anyway. then just create a /.profile with your stuff. the reason people say to NEVER change root's default shell is because it's shocking how often people screw it...

maybe i'm the rookie but i'm confused....you have in your first post a 192.168.0.10 but then mycomp and sgic are different yet. i also notice in the second post that your netstat doesn't have the default destination. can you repost an ifconfig -av and a netstat -rn please??

if you issue hinv -vvv while in the command monitor (prom) you'll get rev #'s, serial numbers and all sorts of info. if you're using a dumb terminal just use ctrl-s and c for contolling the stop and continue of the massive amount of info that purs out. the above command can take 1-3 v's...

did you check the /etc/nnswitch.conf file? hosts line should have files nis dns...

that sounds like a graphics card issue to me. we have about 250 octanes here and clone all the time when needed without issues. i do know that we have cloned a variety of configs and they plug and play quite nicely. graphics card problems with octanes are not that uncommon. i assume you have...

this could be a few things. but the most likely is that the disk in this machine is not a systems disk. if you have a boot/install server you could get the machine up in miniroot and snoop around the disk OR use the irix install disks to do the same. it's also possible that the volume header is...

you can get this straight from sgi http://support.sgi.com but i think you need a supportfolio acct because it's bundled in the irix os releases.

i always edit the /etc/rc2.d/S69inet and put all the netmask, route and related at the bottom. more fun that creating a new file....

forgot: if i recall correctly the /tftpboot directory and subsequent files happen automatically when you issue add_install_client.

it gets complicated but i'll give you something to go on. you need the os sftwr in an exported directory on machine1 and you use setup_install_server to do this. you need a machine2 that is the boot server. they can be and often are the same host. the bootserver needs the command...

if you want to permanently change the look of your winterms edit the following file /usr/lib/X11/app-defaults/XWsh at the "winterm*font:" or the "startconsole*font:" for system consoles. you can create aliases for winterm such as "winterm -bg black -fg white -fn...