Linux-Development-Sys Digest #986, Volume #7     Thu, 29 Jun 00 22:13:11 EDT

Contents:
  Re: Confirm this bug: CodeWarrior does not support spaces in paths? (Nate Eldredge)
  Re: Good Basic compiler for linux? (Stefaan A Eeckels)
  Re: Bash Script Error Tolerant (Stefaan A Eeckels)
  Re: Good Basic compiler for linux? (Kaz Kylheku)
  Re: Confirm this bug: CodeWarrior does not support spaces in paths? (Jan Panteltje)
  how to bulid  .so object file? ("jacky cui")
  Re: Good Basic compiler for linux? ("AndyD")
  Re: Good Basic compiler for linux? (Christopher Browne)
  Raw disk access on Linux (Myke Morgan)
  linux programming help needed ...... ([EMAIL PROTECTED])
  Recv errno = ECONNRESET (Bhavin Shah)
  Re: Raw disk access on Linux (Christopher Browne)
  Re: Recv errno = ECONNRESET (Kaz Kylheku)

----------------------------------------------------------------------------

From: Nate Eldredge <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Confirm this bug: CodeWarrior does not support spaces in paths?
Date: 29 Jun 2000 14:40:24 -0700

John Gluck <[EMAIL PROTECTED]> writes:

> > Should I mandate 8.3 filenames, in all caps? Hey, no "reasonable"
> > developer uses long filenames, or mixed case..
> 
> No there are very few operating systems in current use that require
> that.  I think the only ones that used to use that were on 8 bit
> micros. Things like CP/M 80 Anyway, that was in the days when 64K of
> RAM was huge and a floppy disk was 8 inches storing the inrcedible
> quantity of 128K bytes of data. But I think we've left that century
> and are adapting to the new freedom afforded by megabytes of RAM and
> gigabytes of disk storage not to mention 32 bit and even 64 bit
> computers.

Hello?  MS-DOS?  It certainly ran on things far beyond 8-bit micros
(it runs fine on my K6-3) and it isn't completely dead yet.

Also, there are other places where this restriction is needed.

- CDROMs for systems without Rock Ridge (yes, ISO-9660 supports 32
  char filenames, but nobody seems to use them or support them well)

- Under Windows NT, some toolchains (like DJGPP) can't use long
  filenames, due to brokenness in NT.

So if you are interested in portability, it is wise to consider making
your filenames 8.3 clean.  (i.e. thisfilehasalongname.c is okay, as
long as you don't also have thisfilehasastupidname.c (they will both
truncate to thisfile.c)).

-- 

Nate Eldredge
[EMAIL PROTECTED]

------------------------------

From: [EMAIL PROTECTED] (Stefaan A Eeckels)
Subject: Re: Good Basic compiler for linux?
Date: Thu, 29 Jun 2000 23:31:39 +0200

In article <EXL65.3879$[EMAIL PROTECTED]>,
        "AndyD" <[EMAIL PROTECTED]> writes:
> 
> 
> Not everyone see`s Linux as an excuse to write code.
No. But people suggesting that other fill a void that only
exists in their mind is bound to ruffle a few feathers.

> The point I was trying to make is that Linux is increasing being seen as an
> alternative to Windows, yet there are gaps in the programs available.
Yes. None of the Microsoft programs are available on Linux. What
a big surprise.
> 
> Visual Basic is used by a great number of IT departments to create a quick &
> dirty tool to do a job. As Linux does not have VB those departments keep on
> using Windows.
They can use Tcl/Tk or Python or Perl. Of course, if they insist on
VB they will have to stick with Windows. The point is that much better
tools _are_ available on Linux. Even if anyone would be daft enough
to write a VB-like thing on Linux, it's bound to be incompatible with
the genuine abortion. Ergo, your departments won't switch, because it
ain't 100% compatible. 

> Whenever a *user* mentions this to a Linux bod they are told - "Windows
> sucks, BASIC sucks - use C ( like me `cos i`m a kewl coder ) or if you want
> it write it yourself"
No. They're told (if they want to listen) to use one of the slew 
of superior alternatives. But they don't want to listen, usually.

> If you want a new tyre for your car, do you expect to get rubber, matting &
> carbon and make one yourself or would you just buy one?
No. But if you insist on a particular brand of tyre, and they don't
make one for your model, you're rather foolish not to use the tyre
from a different supplier.

> Expecting someone wanting to write a simple "hello world" type program to
> implement a programming language first is just silly.
That's right. Just use Tcl. Or Python. Or Perl. Or Rebol. 

> Linux is excellent but time & time again, if you identify a need you are
> told "do it yourself"
Only if that need happens to be VB, or Word, or Excel. Mind you,
since we got free StarOffice, Linux has its own bloatware, which
should do wonders for its acceptance in departments that program
in Visual Basic ;-)

HAND,

-- 
Stefaan
-- 
--PGP key available from PGP key servers (http://www.pgp.net/pgpnet/)--
Ninety-Ninety Rule of Project Schedules:
        The first ninety percent of the task takes ninety percent of
the time, and the last ten percent takes the other ninety percent.

------------------------------

From: [EMAIL PROTECTED] (Stefaan A Eeckels)
Subject: Re: Bash Script Error Tolerant
Date: Thu, 29 Jun 2000 23:33:33 +0200

In article <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED] (Kaz Kylheku) writes:
> On Thu, 29 Jun 2000 19:26:16 +0200, Alberto <[EMAIL PROTECTED]> wrote:
>>Hi Guys!
>>
>>I've got a question about Bash Scripts.
>>I would like to know whether it is possible to set Linux in such a way it
>>won't stop when a syntax error occurs in a script. The ideal behaviour for
>>the application I've in mind would require Linux just ingnoring the wrong
>>instruction (whatever type of, flow control included) and continuing the
>>execution of the script from the next instruction.
>>Does anyone of you how to do it?
> 
> The way you do might do this is to put the suspicious script into its own
> file.  Then you detect the failed or abnormal termination of that script
> in a higher level script.
As long as you don't source the file :-)

-- 
Stefaan
-- 
--PGP key available from PGP key servers (http://www.pgp.net/pgpnet/)--
Ninety-Ninety Rule of Project Schedules:
        The first ninety percent of the task takes ninety percent of
the time, and the last ten percent takes the other ninety percent.

------------------------------

From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: Good Basic compiler for linux?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 29 Jun 2000 22:06:38 GMT

On Thu, 29 Jun 2000 20:40:10 GMT, Bob Hauck <[EMAIL PROTECTED]> wrote:
>On Thu, 29 Jun 2000 18:48:56 +0100, AndyD <[EMAIL PROTECTED]> wrote:
>
>>The point I was trying to make is that Linux is increasing being seen as an
>>alternative to Windows, yet there are gaps in the programs available.
>
>There are always gaps.
>
>
>>Visual Basic is used by a great number of IT departments to create a quick &
>>dirty tool to do a job. As Linux does not have VB those departments keep on
>>using Windows.
>
>Nothing has VB but Windows since it is a proprietary language.  An IT
>department that uses a proprietary language for critical functions is
>vendor-locked by definition.  Even if that language isn't from
>Microsoft.

Another observation is that when people say VB, they really mean the language
plus all of the proprietary interfaces that it is used to glue together.  An
implementation of just the core language is meaningless, because VB is used as
a means of accessing all kinds of proprietary application and middleware
interfaces. So even if you have enough of the language on another platform to
make all the UI appear, what good is that if, say, the functions that access
some data store through a proprietary COM interface are not there?

-- 
#exclude <windows.h>

------------------------------

From: [EMAIL PROTECTED] (Jan Panteltje)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Confirm this bug: CodeWarrior does not support spaces in paths?
Date: Thu, 29 Jun 2000 22:13:14 GMT

>But you are correct. Not all environments allow spaces in paths.
>You can get away with it in linux (at least when you mount a vfat) but it's a pain
>to type in constructs like:
>
>cd '/something/If only this name was one word'
>
>
>--
>John Gluck  (Passport Kernel Design Group)
You can also do (in ext2)
mkdir 'this is more then one word'
Jan



------------------------------

From: "jacky cui" <[EMAIL PROTECTED]>
Subject: how to bulid  .so object file?
Date: Thu, 29 Jun 2000 16:30:40 +0800

thanks

--
Best wish to you

Jacky




------------------------------

From: "AndyD" <[EMAIL PROTECTED]>
Subject: Re: Good Basic compiler for linux?
Date: Thu, 29 Jun 2000 23:26:07 +0100


Alexander Viro <[EMAIL PROTECTED]> wrote in message
news:8jg67g$[EMAIL PROTECTED]...
> In article <EXL65.3879$[EMAIL PROTECTED]>,
> AndyD <[EMAIL PROTECTED]> wrote:
>
> >> So what stops you from implementing it, if you think that it's worth
> >doing?
> >
> >Not everyone see`s Linux as an excuse to write code.
>
> Excuse me, what the fuck? You are saying "<something> is needed".
Wonderful,
> but what makes you think that you've got a right to demand something from
> anybody? You want it - _you_ go and do it. Or pay somebody for doing the
work.
> "For free" means "what _I_ want to do" and if you want something
different -
> you'd bloody better do it yourself, pay somebody for work or sod off.
>

The original person posting the enquiry stated he was looking for a
commercial solution to which he was willing to pay.

> I manage a small team of VB programmers and I am looking for a Basic
> Compiler and IDE for Linux. I have seen Xbasic and some others but they
are
> quite the quality I am looking for. I need a complete commercial package
> with available support. Anyone know of such a product?

I was identifying a business opportunity & shortcoming in linux at the
moment, but you seem to have gone off at a self righteous tangent. If I
asked someone for code I DO put my money where my mouth is.

Look! I even managed to say all that without sounding like a little thug.

-AndyD



------------------------------

From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: Good Basic compiler for linux?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 29 Jun 2000 23:40:50 GMT

Centuries ago, Nostradamus foresaw a time when AndyD would say:
>Not very helpful...
>
>I don`t think the person posting the message was ASKING for your opinion on
>BASIC or wished to see a list of your programming conquests.
>
>Visual Basic is used by a great number of people & if linux has a comparable
>application it would help it be adopted more in the real world.
>
>A large number of people make a living programming in a variety of BASIC`s
>and I for one would like to see a modern implementation of the language on
>LINUX.

Precisely _why_ do you want a "modern implementation"?

a) So that you can run the same code that you wrote for Windows?

   If this be the case, then you _should_ have said "implementation
   that provides an environment that is bug-for-bug-compatible with MS
   VB."

   By the way, were you including Win32, COM, and ADO on the list of
   things to be "bug-for-bug" compatible with?

b) So that you can create analagous applications?

   If this is the case, then I see little point to bothering with
   something as ill-defined and ill-built as BASIC.  There may be both
   ANSI and ISO standards for BASIC, but only Kemeny and Kurtz ever
   seriously deployed standards-compliant versions of it.  Indeed, the
   reason for the deployment of the ANSI standard was that Kurtz was
   so appalled by what had been done to their language that he became
   chair of the standards committee.

   The only option I'd _consider_ suggesting would be that of
   TrueBASIC, but it does not exist for any Unix variation.

   There are _already_ ample options for _other_ languages, that
   represent nicer languages, and that provide vastly more robust
   designs than Microsoft has deployed with VB.

   Leaping to mind are:
    - Python, Perl, Tcl/Tk
    - IBM Visual Age for Java
    - Applix SHELF
    - Smalltalk

People keep giving a third answer:

c) You don't want BASIC; you want to code in C.

Which is so desparately different an option that this is really quite
a _silly_ suggestion.  You're looking for an "environment with bucket
seats," something that _doesn't_ require that the developer spend
effort fighting with pointers, which rules out C and C++.

Of course, this leaves out the most important issue:

   Who is it that you expect to build this for you?

If you think that a "Visual BASIC"-like environment is _really_ so
valuable, then it probably makes sense for you to either put in the
effort to write it, or to invest the wherewithal to allow someone else
to write it.

When so many people seem to consider the availability of "VB for
Linux" to _NOT_ be the "bee's knees," you should be asking yourself
if:

  a) They're all idiots, 
  b) They're _so_ anti-Microsoft as to be _totally_ irrational
     (and some of the responses _have_ displayed this), or
  c) Perhaps you are overestimating the value of creating a "VB clone"
     when there already exist _so many_ other tools.
-- 
[EMAIL PROTECTED] - <http://www.ntlug.org/~cbbrowne/languages.html>
As of next Wednesday, CLU will be flushed in favor of SNOBOL.
Please update your programs.

------------------------------

From: [EMAIL PROTECTED] (Myke Morgan)
Subject: Raw disk access on Linux
Date: 30 Jun 2000 01:39:08 GMT

Will raw disk access happen the way I "expect it" to? Namely, can I open 
a block device, for example /dev/hdb, and expect to be able to read, write, 
seek, etc. properly? I have a Solaris program I am trying to port and it 
uses raw access to the disk drives to do a "custom filesystem" for lack 
of better description. I am using the open64, write64 functions. Perhaps 
thers are some ioctl's I have to do on that descriptor first, like 
turning off buffering or something, since I take care of all that in my 
program.

For reference, I am running RedHat 6.2, kernel 2.2.14-5.0smp with two
CPU's. The program seems to run fine on a RedHat 6.1/kernel 2.2.12-20smp I
am suspicious of perhaps the ide driver (I only have IDE drives to test
for now) because it seems quite a bit more stable when I substitute an
actual filesystem file instead of the disk device: ie /tmp/filename
instead of /dev/hdb. 

I was looking in the patch logs from 2.2.12 -> 2.2.14 and 2.2.13 mentions 
a SMP/IDE fix,  but that puzzles me since it works on the old version, 
but not the new.

Any help is appreciated, and I can attempt to supply a more coherent 
explination if necessary also.

myke




--
I proclaim you, FOUR!


------------------------------

From: [EMAIL PROTECTED]
Subject: linux programming help needed ......
Date: Fri, 30 Jun 2000 01:28:58 GMT

hello all,

I am developing a webmail system on linux. I need to add a user into the
system by cgi(written in GNU C), of course, I executed useradd program
and passwd, the problem occurred when I tried to send the password to
passwd using a pipe.  my program goes like this

  pipe_out = popen ("passwd username", "w");
  fprintf (pipe_out, "password\npassword\n");
  pclose(pipe_out);

but passwd said "conversation error". anoy way it doesn't work.  So
anyone know how to handle this kind of problem? or in an alternative
way to work the task out.

thanks
nick


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

From: Bhavin Shah <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development,linux.redhat.development
Subject: Recv errno = ECONNRESET
Date: Thu, 29 Jun 2000 18:41:50 -0700

Hi,

I'm trying to recv a buffer with a fairly large
size (approx. 16k).  However, I'm getting an
error using 'recv' and errno is Connection
reset by peer.  

How do I go about fixing/handling this error so
I can still recv the entire thing?  Thanks in
advance.

Bhavin 



------------------------------

From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: Raw disk access on Linux
Reply-To: [EMAIL PROTECTED]
Date: Fri, 30 Jun 2000 01:53:47 GMT

Centuries ago, Nostradamus foresaw a time when Myke Morgan would say:
>Will raw disk access happen the way I "expect it" to? Namely, can I open 
>a block device, for example /dev/hdb, and expect to be able to read, write, 
>seek, etc. properly? I have a Solaris program I am trying to port and it 
>uses raw access to the disk drives to do a "custom filesystem" for lack 
>of better description. I am using the open64, write64 functions. Perhaps 
>thers are some ioctl's I have to do on that descriptor first, like 
>turning off buffering or something, since I take care of all that in my 
>program.
>
>For reference, I am running RedHat 6.2, kernel 2.2.14-5.0smp with two
>CPU's. The program seems to run fine on a RedHat 6.1/kernel 2.2.12-20smp I
>am suspicious of perhaps the ide driver (I only have IDE drives to test
>for now) because it seems quite a bit more stable when I substitute an
>actual filesystem file instead of the disk device: ie /tmp/filename
>instead of /dev/hdb. 
>
>I was looking in the patch logs from 2.2.12 -> 2.2.14 and 2.2.13 mentions 
>a SMP/IDE fix,  but that puzzles me since it works on the old version, 
>but not the new.
>
>Any help is appreciated, and I can attempt to supply a more coherent 
>explination if necessary also.

The problem with expectations will be based on just _how_ raw you want
your disk accesses to be.

The RDBMS vendors generally want access to be _completely_ raw, with
_no_ possible involvement of cacheing, so that they can manage their
own caches.

On Linux, the access to disk via /dev/hda, /dev/sdc, and so forth, 
_are_ going to be cached.

Stephen Tweedy apparently has a patch to allow creating accesses for
block devices that _don't_ cache.  You may want to look at one of the
Linux kernel patch sites for info on that, although if you're finding
that doing the "nearly direct" access via /dev/hd?? is suitable, that
may be quite good enough.
-- 
[EMAIL PROTECTED] - <http://www.hex.net/~cbbrowne/linuxkernel.html>
All syllogisms have three parts, therefore this is not a syllogism.

------------------------------

From: [EMAIL PROTECTED] (Kaz Kylheku)
Crossposted-To: comp.os.linux.development,linux.redhat.development
Subject: Re: Recv errno = ECONNRESET
Reply-To: [EMAIL PROTECTED]
Date: Fri, 30 Jun 2000 02:00:27 GMT

On Thu, 29 Jun 2000 18:41:50 -0700, Bhavin Shah <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I'm trying to recv a buffer with a fairly large
>size (approx. 16k).  However, I'm getting an
>error using 'recv' and errno is Connection
>reset by peer.  
>
>How do I go about fixing/handling this error so
>I can still recv the entire thing?  Thanks in
>advance.

Umm, the error means that the other side has turfed the socket.  There is
nothing you can do on your end to suck the data out of a host that doesn't want
to talk to you.

Maybe the remote host is dropping the connection because of host access
controls. That is, it picks up the connection, then sees that it's from an
unwanted host and drops it right away.

Or maybe something you sent in the other direction caused the other
host to bail.

-- 
#exclude <windows.h>

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.development.system) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Development-System Digest
******************************

Reply via email to