01-22-2012
I guess you probably switch the disk label from a SMI to EFI one with your BSD experiments. You need to switch it back to SMI with "format -e" command.
Also, instead of Solaris 9 which is quite outdated, you might want to try installing the latest OpenSolaris release (textinstall-134-sparc.iso from
Index of /isos/opensolaris) on that box. It fits on a CD so doesn't require a DVD.
This User Gave Thanks to jlliagre For This Post:
10 More Discussions You Might Find Interesting
1. UNIX Benchmarks
Sun Blade 2000 UltraSparc III Solaris 8
Notes:
prtdiag:
System Configuration: Sun Microsystems sun4u SUNW,Sun-Blade-1000 (UltraSPARC-III+)
System clock frequency: 150 MHZ
Memory size: 3GB
==================================== CPUs ====================================
... (0 Replies)
Discussion started by: tnorth
0 Replies
2. Solaris
It's me again, I was taking my Sun Blade 100 apart last night to see what kind of drive I have. It is a Seagate ST320011A Barracuda ATA IV 20 GB 7200 RPM Ultra ATA/100 IDE.
Now 20 gig ain't all that big anymore and I got to thinking about putting a couple bigger drives in there. although I... (7 Replies)
Discussion started by: BrewDudeBob
7 Replies
3. Solaris
Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies
4. Solaris
FYI noob to here and sun blades...
I have a sun blade 100 and I can't get the cdrom to work. if i try using vold that doesn't seem to work either...maybe i'm not using it correctly.
Upon boot you can open/close the cdrom and it runs but after i'm logged in it won't open and i can't access it... (2 Replies)
Discussion started by: shaun138
2 Replies
5. Solaris
We had to replace a hard drive in one of our Sun Blade 150s, but now it hangs during the Jumpstart. It will show 1 or 2 Timeout for ARP/RARP messages and then start the spinning numbers. It always stops at 2ae00 and just hangs there.
We have 1 combined jumpstart server and it is also our NIS+... (5 Replies)
Discussion started by: stottsja
5 Replies
6. UNIX for Dummies Questions & Answers
Hi,
If someone please help as my efforts been exhausted in connecting my sun blade 100 serial to my pc. I am using null modem with DB9(female) in sun blade and DB9(female, using gender change) in pc.
I am trying both hyper/putty 9600 8 N 1 configurations.
Thanks (2 Replies)
Discussion started by: younics
2 Replies
7. Solaris
Hello,
I'm trying to compile PHP 5.3.6 with Apache2 and MySql 5.5.12. I hit a problem that I can't seem to resolve by myself and I could not find a solution on the web.
It looks like Apache and MySql installed ok, I can start/stop them with no problem.
When I try to compile PHP the... (4 Replies)
Discussion started by: pn8830
4 Replies
8. Solaris
Hi everyone
can someone please explain to me how to install solaris 10 on a sunblade 1500 using cdrom?
Thanks for your assistance (1 Reply)
Discussion started by: cjashu
1 Replies
9. Solaris
Hello,
I cant get my blade box to boot off the harddrive after installing solaris 10.I can get to a root prompt after issuing "boot cdrom -s".I tried booting off disk0 and disk1,but I get "the file just loaded does not seem to be executable".Thanks for any help.:wall: (4 Replies)
Discussion started by: chucky
4 Replies
10. Solaris
Hi everybody,
I'm having big troubles in installing Solaris 8 on a Sun Blade 150.
Here are some system specs:
Sun Blade 150 (UltraSPARC-IIe 550MHz)
RAM: 256MB
OBP 4.10.6 2003/06/06 12:30
POST 2.0.1 2001/08/23 17:13
When I try to boot from Solaris 8 CD with boot cdrom or... (10 Replies)
Discussion started by: Vortigern
10 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)