On Saturday 08 November 2003 23:41, Ben Rosenberg wrote: <snip>

Now if we could just get them to change SuSEconfig to suseconfig ..this mixed case crap should have gone away years ago. ;)

-- And SuSEfirewall2 to firewall2?

LW999

* Michael Galloway (mgx@ornl.gov) [031108 15:45]:

oh no, if they change it to suseconfig now it'll take me a year to relearn to type it again :-)

So do what I did a long time ago... cd /sbin && ln -s SuSEconfig suseconfig That way you get use to it. :) -- Ben Rosenberg ---===--- #147972 ---===--- mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.

On Sunday 09 November 2003 00:04, Kastus wrote:

Lowercase "u" in SuSE made perfect sense from grammar point of view, while making it uppercase makes no sense at all. It does not make "und" a noun.

I agree, SuSE makes much more sense than SUSE. C'eST La viE. Jake

On Sat, Nov 08, 2003 at 06:31:00PM -0800, Ben Rosenberg wrote:

No objection there. What I was talking about is that it's much easier to type suseconfig vs SuSEconfig. I guess it's a matter of preference. :)

Sure. I, personally, extensively use TAB key for command completion when in doubt. -Kastus

On Sat, 2003-11-08 at 23:41, Ben Rosenberg wrote:

* GarUlbricht7@netscape.net (GarUlbricht7@netscape.net) [031108 15:36]:

...

Jerry Feldman wrote: ---<text heavily snipped>---

...

I think there is some good and bad here....(snip)

This acquisition firmly puts SuSE into the US enterprise because of both Novell and IBM support.

The bottom line for SuSE is that it is a good move...(snip)

Jerry, i agree with your comments. However, i found it interesting that you used the old name for SUSE. Old habits, die hard, huh ???

But I suspect that SUSE honchos (and bankers) have been considering this for a while and that is one reason 9.0 is now "SUSE"

Now if we could just get them to change SuSEconfig to suseconfig ..this mixed case crap should have gone away years ago. ;)

They could just make the file system so it doesn't matter about the case of the file name, just like all the other great operating systems. Adam Leach ================================ http://www.ask-adders.com

On Thu, 2003-11-13 at 08:45, Carlos E. R. wrote:

The Sunday 2003-11-09 at 00:48 -0000, Adam Leach wrote:

...

...

Now if we could just get them to change SuSEconfig to suseconfig ..this mixed case crap should have gone away years ago. ;)

They could just make the file system so it doesn't matter about the case of the file name, just like all the other great operating systems.

But all of the other "great" operating systems are also case sensitive.

That is not a decision SuSE can make. Linux, as Unix, is case sensitive.

And... isn't Unix a "great operating system"? Or are you thinking of dos/windows as a "great operating system" :-)

-- Cheers, Carlos Robinson

-- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)

On Fri, 2003-11-14 at 09:59, Jerry Feldman wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Thu, 13 Nov 2003 15:37:36 -0500 Ken Schneider wrote:

...

On Thu, 2003-11-13 at 08:45, Carlos E. R. wrote:

...

The Sunday 2003-11-09 at 00:48 -0000, Adam Leach wrote:

...

...

Now if we could just get them to change SuSEconfig to suseconfig ..this mixed case crap should have gone away years ago. ;)

They could just make the file system so it doesn't matter about the case of the file name, just like all the other great operating systems.

But all of the other "great" operating systems are also case sensitive. Not entirely true. But, Unix and many other good operating systems have been case sensitive since their inception. However, many of the older mainframe operating systems are case insensitive.

But then I was referring to the "great" OS's (unix of course). -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)