Sponsored Content
Full Discussion: about Sun 9 HCL
Operating Systems Solaris about Sun 9 HCL Post 50861 by rhfrommn on Tuesday 4th of May 2004 10:48:47 AM
Old 05-04-2004
Yes, if your hardware is not on the HCL Sun doesn't officially support it or guarantee that it will work. However, Solaris x86 is pretty robust and just because it isn't listed doesn't mean you won't be able to get it to work. Best thing to do is give it a try.
 

4 More Discussions You Might Find Interesting

1. Solaris

How accurate is the HCL for Solaris 10?

I have a Sun Ultra 5 that is running Solaris 8. I believe I meet the minimum requirements for Solaris 10 but the Ultra 5 is not on the HCL. This will be my first ever Solaris upgrade so do I follow the HCL guidelines? TiA (4 Replies)
Discussion started by: PapaPark
4 Replies

2. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document... (1 Reply)
Discussion started by: shafeeq
1 Replies

3. UNIX for Dummies Questions & Answers

Sun Solaris 10: How do I create a bootup disc? The Sun website confuses me

Hey there, I am starting a Computer Science Foundation year at the end of this month and am trying to get a little bit ahead of the game. I have always wanted to learn Unix and am currently struggling with creating a boot disc to run Solaris (I have chosen to study this) from as opposed to... (0 Replies)
Discussion started by: Jupiter
0 Replies

4. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
PERLBEOS(1)						 Perl Programmers Reference Guide					       PERLBEOS(1)

NAME
README.beos - Perl version 5 on BeOS DESCRIPTION
Notes for building Perl under BeOS. General Issues with Perl on BeOS To compile perl under BeOS R4 x86: ./Configure -d and hit ^C when it asks you if you want to make changes to config.sh; edit config.sh and do the following: change d_socket='define' to ='undef'; remove SDBM, Errno, and Socket from dynamic_ext= and nonxs_ext=; add '#define bool short' to x2p/a2p.h; ../Configure -S; make; make install cd ~/config/lib; ln -s 5.00502/BeOS-BePC/CORE/libperl.so . (substitute 5.00502 with the appropriate filename) BeOS Release-specific Notes R4 x86 Dynamic loading finally works! Yay! This means you can compile your own modules into perl. However, Sockets and Errno still don't work. (Hopefully, sockets will at least work by R5, if not sooner.) R4 PPC I have not tested this. I rather severely doubt that dynamic loading will work. (My BeBox is in pieces right now, following a nasty disk crash.) You may have to disable dynamic loading to get the thing to compile at all. (use `./Configure` without -d, and say 'no' to 'Build a shared libperl.so'.) Contact Information If you have comments, problem reports, or even patches or bugfixes (gasp!) please email me. 28 Jan 1999 Tom Spindler dogcow@isi.net Update 2002-05-30 The following tests fail on 5.8.0 Perl in BeOS Personal 5.03: t/op/lfs............................FAILED at test 17 t/op/magic..........................FAILED at test 24 ext/Fcntl/t/syslfs..................FAILED at test 17 ext/File/Glob/t/basic...............FAILED at test 3 ext/POSIX/t/sigaction...............FAILED at test 13 ext/POSIX/t/waitpid.................FAILED at test 1 The reasons for the failures are as follows: o The t/op/lfs and ext/Fcntl/t/syslfs failures indicate that the LFS (large file support, files larger than 2 gigabytes) doesn't work from Perl (BeFS itself is well capable of supporting large files). What fails is that trying to position the file pointer past 2 giga- bytes doesn't work right, the position gets truncated to its lower 32 bits. o The op/magic failures look like something funny going on with $0 and $^X that I can't now figure out: none of the generated pathnames are wrong as such, they just seem to accumulate "./" prefixes and infixes in ways that define logic. o The Glob/t/basic indicates a bug in the getpw*() functions: they do not always return the correct user db entries. o The sigaction #13 means that signal mask doesn't get properly restored if sigaction returns early. o The waitpid failure means that after there are no more child processes, waitpid is supposed to start returning -1 (and set errno to ECHILD). In BeOS, it doesn't seem to. Disclaimer: I just installed BeOS Personal Edition 5.0 and the Developer Tools, that is the whole extent of my BeOS expertise, so please don't ask me for further help in BeOS Perl problems. jhi@iki.fi perl v5.8.0 2003-02-18 PERLBEOS(1)
All times are GMT -4. The time now is 08:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy