All the obsession around "legitimizing" Linux seems to cater to a particular environment: Corporations. I.e. corporate users, commercial vendors.
I'm interested in legitimising Linux in those terms, granted - but only as a means to an end.
I want packaged software to be made available for Linux. I want hardware vendors and service providers to continue to respond to problem reports after I admit that I'm using Linux, rather than just going silent on me or saying "Lie-nooks? I don't think we support that."
I don't really care whether Linux is used by large corporations, per se. However, I do want to see more reports like the 3Com one - where the big players say "We want Linux support" and it happens. Without corporate acceptance of Linux, that kind of thing is just a dream.
Does this solve the glibc 2.1 problem?
on
egcs to become gcc
·
· Score: 1
ISTR the problem with glibc 2.1 was that it wasn't compilable with the 'official compiler' of the GNU project.
I assume that this will expedite the (re)release of glibc 2.1? (Or has it been released already - I haven't bothered to check).
I admin a network which has GNOME, KDE and WM+xterm users. I don't care which one they use - as long as I can set up mime types and new applications in a uniform manner.
Currently, I can't - I've set up a KDE Application link, and MimeType links, for Applixware, but GNOME doesn't use them. Until there's a uniform way of doing things like this, we can't expect commercial software to use it, and hence we can't expect things to 'just work' when we click on them.
Hopefully, with RedHat (or indeed anyone) taking an active part in development of both, this will be fixed quite quickly.
Has anyone done QT-emulating C++ bindings for GTK, and a QT-like theme?:)
I don't think that quoting this reply is too inappropriate...
Date: Fri, 12 Feb 1999 10:25:45 -0800 To: David Woodhouse <David.Woodhouse@mvhi.com>, ombudsman@computer.org, software@computer.org From: Ted Lewis <tedglewis@friction-free-economy.com> Subject: Re: Complaint re: 'Computer' magazine. Cc: aburgess@computer.org
David,
The April issue of Computer will reply to many of the issues raised by the open source community.
Grrr. When I hit 'preview',/. removed all the bloody > escapes, and replaced them with the real characters, which then didn't bloody work next time.
As the only changes to the ISDN code are cosmetic, it's a fairly safe bet that it still won't work. The ISDN link comes up and works for a few hours, but then fails, complaining HiSax: if_command 14 called with invalid driverId 0! until it's rebooted.
Slashdot Mirror
I'm interested in legitimising Linux in those terms, granted - but only as a means to an end.
I want packaged software to be made available for Linux. I want hardware vendors and service providers to continue to respond to problem reports after I admit that I'm using Linux, rather than just going silent on me or saying "Lie-nooks? I don't think we support that."
I don't really care whether Linux is used by large corporations, per se. However, I do want to see more reports like the 3Com one - where the big players say "We want Linux support" and it happens.
Without corporate acceptance of Linux, that kind of thing is just a dream.
ISTR the problem with glibc 2.1 was that it wasn't compilable with the 'official compiler' of the GNU project.
I assume that this will expedite the (re)release of glibc 2.1? (Or has it been released already - I haven't bothered to check).
Am I just being dim, or does it not say how much it costs?
I admin a network which has GNOME, KDE and WM+xterm users. I don't care which one they use - as long as I can set up mime types and new applications in a uniform manner.
Currently, I can't - I've set up a KDE Application link, and MimeType links, for Applixware, but GNOME doesn't use them. Until there's a uniform way of doing things like this, we can't expect commercial software to use it, and hence we can't expect things to 'just work' when we click on them.
Hopefully, with RedHat (or indeed anyone) taking an active part in development of both, this will be fixed quite quickly.
Has anyone done QT-emulating C++ bindings for GTK, and a QT-like theme? :)
As long as he can tell the difference, keep him.
I did. And I've even got it back from linux-kernel, after the obligatory 2-day delay.
But there's no point trying to fix it - we just need to put the latest CVS code into 2.2.
As the only changes to the ISDN code are cosmetic, it's a fairly safe bet that it still won't work.
The ISDN link comes up and works for a few hours, but then fails, complaining
HiSax: if_command 14 called with invalid driverId 0!
until it's rebooted.