home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp
- Path: sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!lynx!nmsu.edu!opus!jthomas
- From: jthomas@nmsu.edu (James Thomas)
- Subject: Disk partitioning/layout (Was: New 877 Installation)
- In-Reply-To: jthomas@nmsu.edu's message of Thu, 24 Dec 1992 21:06:11 GMT
- Message-ID: <JTHOMAS.92Dec28161410@navajo.nmsu.edu>
- Sender: usenet@nmsu.edu
- Organization: NMSU Computer Science
- References: <JTHOMAS.92Dec24140611@navajo.nmsu.edu>
- Date: Mon, 28 Dec 1992 23:14:10 GMT
- Lines: 35
-
- In article <JTHOMAS.92Dec24140611@navajo.nmsu.edu> I write:
-
- jim> ... (I suppose I should be thankful that it has partitions - not
- jim> like the 700's; but as per previous discussions we want to be able to
- jim> set the sizes ourselves :-) . ...
-
- I would like to bring up this apparently dead horse (at least according to
- HP) again :-(
-
- a) I would like to be able to define the partition sizes. For example, a
- stock 48M swap partition may have been OK in the "old" days, but systems
- have more memory now. The 877 we got was ordered with 128M of memory (gee,
- somewhere between 3200 and 6400 times the memory in the 1620 I started on
- ... :-) . It was set up with a 1106M primary swap space - not enough for a
- full dump, for example. Suppose I want 145M of primary swap? The choices
- are 106M, 128M, and 980M. Not very appropriate. What do I do when HP
- tells me they can't support the system because I can't give them a complete
- system dump ?? :-) :-)
-
- Note that in the above there was not a reasonable way to divide such a disk
- in half (it's a 1.4G - these partitions were set up when 300M was a HUGH
- disk - they are no longer reasonable except for the LIF partition which
- seems to have shrunk from the 6M it used to be :-) . Multiple people have
- listed reasons why they wanted that ability. The swap space argument is
- new, I think.
-
- b) Back 20 years ago, I could tell TOPS-10 where I wanted its equivalent
- to the inode table. That is still missing in unix. If I set a disk up
- with only section 2, I would like to be able to say that the inode table
- should be put smack in the middle (if I don't want a single file,
- contiguous though unix also can't particulary do that anyway). That
- way seeks are minimized when the relatively common requirement to find some
- inode information happens.
-
- Jim
-