SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 24 | May | 2004 ]

<< Previous Message << >> Next Message >>


Date: Mon, 24 May 2004 20:25:01 PDT7
From: Sheridan George <s-geo@usa.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: New System Configuration

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Gary Granat wrote:

> difference between physical partitions and volumes. For now, I'm just looking
> at space allocations (which probably corresponds most closely to LVM volumes).
> I know how I want to allocate my space:
>

Gary,

I'm not clear on what you are intending by the partitioning you described so I'll tell you how I
have partitioned my hard drives under LVM. Maybe that will answer some of your questions.

I have two 120 gig drives; one as "primary" worker and the other as a backup. (I use dsync in a
manual mirroring method.)

Disk 1:
boot manager
C: is 10 gigs JFS and holds applications
D: is 50 gigs JFS and holds data
E: is 1 gig HPFS and holds eCS 1.1
L: is 1 gig fat16 and holds log files
N: is 1 gig fat16 and holds memory dump on a crash (must be at least as big as RAM)

Disk 2:
M: is 1 gig HPFS and holds eCS 1.1 mirror
P: is 10 gigs HPFS and holds applications mirror
Q: is 50 gigs HPFS and holds data mirror

The rest of the space on both drives is free space. And, yes, you can allocate it and deallocate it
as necessary. I did that when I had a bad crash and decided to redo my partition allocations. I
allocated some space from free space, saved files there, redesigned my partitions, restored the
saved files, reinstalled eCS via the mirror, and then returned the "save" partition to free space.

The drive lettering was assigned by me not by LVM.

I can boot to either E: or M:. This is not ideal though. Drive M: is a mirror of E: and that means
I have to fiddle with config.sys to boot properly in M:. I intend to create a true maintenance
partition on disk 1. Maybe on disk 2 also now that I think of it just in case drive 1 goes south.
(I've had a computer of one kind or another since 1977 and have not had a hard drive fail with out
notice, though.)

Sheridan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 24 | May | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.