Solaris install through TFTP linux-server
Hi, I have been able to pick up a Sparcstation 4. In the long run I intend to use it as a Linux server (or maybe on of the BSDs). For now I would like to try Solaris. Never touched/never seen it. I spent many hours this evening to get the Openboot screen in a terminal on my Linux desktop. After that I spent quite some time on setting up networking to serve the SS the Debian boot image. I am happy to say that I can now install Debian once I acquire the complete base-system. I have already downloaded three ISO-images for a Solaris 9 install. I can't burn images to cd, so I to mounted the ISO-files from the harddrive with -o loop. Apart from a few scripts there is not much I can see. Is my download corrupt or is it impossible to read these images from Linux? I have read some of the Solaris docs concerning Install servers. As I understand it you need a Solaris system to create an Install server. Is that correct? Is it not possible to boot the Sparcstation and start the Solaris installation by using Linux as an Install server? I am sorry if I offend anyone on this list by asking these questions. It's just that I don't know about all the usual places in regards to Solaris and Sun hardware. Bob pgpjWi4jIfgWF.pgp Description: PGP signature
Re: question about uname on sparc
On Fri, Jun 28, 2002 at 06:47:30PM -0400, Ben Collins wrote: Kill it. Excellent. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question about uname on sparc
> It's something I inherited, and I have no idea why it's there. Is there > any need for it currently on the sparc port? If not, I'd like to get rid > of it in sid. On ultrasparc, uname returns "sparc64". Even though we use a 32bit userland, some configure scripts mistakenly assumed this meant "64bit userland". So I implemented this to fool those scripts on the buildd. It is ancient (I thought it was already removed), and is superceded by the sparc32/sparc64 personality changing programs that do it the right way (down to the kernel level). Kill it. -- Debian - http://www.debian.org/ Linux 1394 - http://linux1394.sourceforge.net/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
question about uname on sparc
(Please cc, I'm not on debian-sparc) shellutils currently applies this patch to uname: --- shellutils-2.0.11.orig/src/uname.c +++ shellutils-2.0.11/src/uname.c @@ -119,6 +119,9 @@ struct utsname name; int c; char processor[256]; +#if defined(__sparc__) && defined(__linux__) + char *fake_sparc = getenv ("FAKE_SPARC"); +#endif program_name = argv[0]; setlocale (LC_ALL, ""); @@ -188,6 +191,11 @@ error (1, errno, _("cannot get processor type")); #else strcpy (processor, "unknown"); +#endif + +#if defined(__sparc__) && defined(__linux__) + if (fake_sparc != NULL && (fake_sparc[0] == 'y' || fake_sparc[0] == 'y')) +strcpy(name.machine, "sparc"); #endif print_element (PRINT_SYSNAME, name.sysname); It's something I inherited, and I have no idea why it's there. Is there any need for it currently on the sparc port? If not, I'd like to get rid of it in sid. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No sparc buildlog at buildd.debian.org
Bill Allombert <[EMAIL PROTECTED]> writes: > My packages build fine or sparc, but the sparc buildlog no more appears at > buildd.debian.org, as it was previously. Whoops. Lossage during ~buildd reconstruction after an accident by parties who shall remain nameless. Fixed now. -- James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No sparc buildlog at buildd.debian.org
Hello, My packages build fine or sparc, but the sparc buildlog no more appears at buildd.debian.org, as it was previously. Is it a know temporary issue ? Should I report it to Ryan Murray ? Cheers, (Please CC answer to me) -- Bill. <[EMAIL PROTECTED]> FHS 5.3: As of the date of this release of the standard, system crash were not supported under Linux. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]