All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Andrew - Sun MDE <David.Andrew@East.Sun.COM>
To: ultralinux@vger.kernel.org
Subject: Suggestion for linux install
Date: Thu, 30 Jul 1998 15:35:08 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531100@msgid-missing> (raw)

Hi folks,

As I was installing Linux on my Ultra5, the script stopped and told me that it 
could not find a binutils file.  There was one in the RPMS, but it was a later 
rev than the script wanted.  I don't know why the script decided it needed that 
particular rev, but the only alternative offered me was "ok", so no binutils was 
loaded.  Fortunately I did not need binutils for my installation at this time.  
I loaded the .106 kernel and everything dated up to June 24 into my server for 
this install.

My suggestion is that when the script detects that a file is missing, it should 
also permit the installer to enter a file name to load in place of the one it is 
asking for (or to continue as now).  This would eliminate the necessity of 
installing the file later, and could complete the install with all the correct 
stuff. 

By the way, the comps file dated April 16, which chooses what packages to load, 
wanted gtk and did not recognize gtk+ files, so I edited comp to choose gtk+. 
Also, several functions required glib, which is not called out in the comps 
file. Is there a new comps file coming/needed?


David Andrew                Tel:  978-442-2316   Internal:   22316
Market Development Engineer - I/O Technologies   FAX:  978-442-1520	
Sun Microsystems, 2 Omni Way - M/S UCHL02-102,   Chelmsford, MA 01824	 
e-mail:  david.andrew@sun.com

                 reply	other threads:[~1998-07-30 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ultrasparc-90222358531100@msgid-missing \
    --to=david.andrew@east.sun.com \
    --cc=ultralinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.