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 [ 01 | November | 2003 ]

>> Next Message >>


Date: Sat, 1 Nov 2003 11:38:41 PDT7
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: Boot systems, was Next Help Desk | SC

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.
=====================================================

> >>A word of caution about System Commander and OS/2.... If you're using the
> >>latest versions of OS/2 and/or eComStation (the ones that use LVM), System
> >>Commander is totally incompatible. If you install SC, you CANNOT boot to
> >>eComStation because the MBR is now incompatible with LVM.

Ray replied:

> Maybe I just haven't been listing, but I am still waiting to hear
> something that LVM does for us that helps. Mostly what I hear is
> gotchas. It seems to be a solution looking for a problem. Mostly it
> seems to be a way to play with drive letters. What problem does that solve?

It's kind of irrelevant whether we happen to like it or not, whether it solves
any particular problem or not. The simple fact is that if one wants to use ECS
(or MCP-level Warp of the past couple years), they require LVM. Period.
No choice in the matter. And I take the position that an OS/2 user probably
_does_ want to use ECS, because it offers the best matchup to contemporary
h/w and drivers, such as USB.

> I see two ways to manage a computer.
>
> The other, is set it up so you can alter anything to your hearts
> content, destroy it at will, and return to a predetermined state almost
> instantly. A primary element of that system is a spare, plug-in HDD.

If I was doing this today from scratch, your approach makes some sense
to me. But my system is all-SCSI, 2 h/d, and more trouble to configure
properly than most, so I'm disinclined to retrofit around this idea at this
point. Maybe on some future system.

But now, I have to live with LVM and accomodate it. If I have to get an
earlier version of SC, so be it. If that won't do the job, then Air-Boot or
one of the others. I'd like to do this stepping on as few banana peels as
possible, because I've already gone skidding on a few, after years of relative
stability.

Jordan

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

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".

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


>> Next Message >>

Return to [ 01 | November | 2003 ]



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.