Subject: Linux-Activists Digest #47
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Thu, 9 Apr 92 19:00:28 EDT

Linux-Activists Digest #47, Volume #2             Thu, 9 Apr 92 19:00:28 EDT

Contents:
  Bash 1.12 (thomas dunbar)
  gcc-2.1 header files (Joseph Knapka)
  __ctype undefined symbol error (Joseph Knapka)
  <assert.h> in gcc2.1 (Joseph Knapka)
  Unsubscribe (David Fenyes)
  Patch to preset the SVGA mode (Dennis Flaherty)
  Wish list... (Todd Radel)
  Re: Non-destructive repartitioning (was Re: What is linux?) (William Michael Lye)
  Re: <assert.h> in gcc2.1 (David Engel)
  Another bug? [was Re: linux-0.95c known bugs] (Joel M. Hoffman)
  Re: HELP! Problems with rootimage. (Jim Winstead Jr.)
  Re: Binaries considered harmful (Joe Smith)
  New things at tsx-11 (Michael K. Johnson)
  Re: HELP! Problems with rootimage. (Farhan H Garib)
  Re: HELP! Problems with rootimage. (Bowen (Laughing Cheetah))
  Re: gcc-2.1 header files (Hongjiu Lu)

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

From: thomas dunbar <[email-masked]>
Subject: Bash 1.12
Reply-To: [email-masked]
Date: Thu, 9 Apr 1992 16:17:13 GMT

Bash 1.12 in at hpb.mcc.ac.uk in dir pub/linux/mcc-bin

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

From: [email-masked] (Joseph Knapka)
Subject: gcc-2.1 header files
Date: 7 Apr 92 14:55:23 GMT

H.J. asked me to forward this exchange to the newsgroup:

I said:
>> Kernel build of .95c went fine, but when compiling ps, I get
>> "undefined symbol __ctype referenced from text segment" while linking
>> ps.o. This is with very latest gcc-2.1, libraries, and binutils from
>> banjo. I linked xxx/src/linux/lib/ctype.o and got it to compile, and
>> (seems that) everything works. Did I do the right thing?
>> 
>

H.J. said:
>No. Please get my 2.1ps.tar.Z, 2.1kernel.tar.Z and apply Linus's second
>patch first. When compile any application, do not use ANY header files
>from ./linux/include.

Joseph

P.S.: but I'd already applied .95c, 2.1kernel, and ps patches. Still
waiting for a reply...

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

From: [email-masked] (Joseph Knapka)
Subject: __ctype undefined symbol error
Date: 7 Apr 92 17:55:22 GMT

Hi, all. I was having trouble compiling ps after applying Linus' and
H.J.'s patches to the .95a kernel. Turned out I hadn't rooted out all
traces of gcc-1.40 --- that part of the FAQ is to be taken very seriously!
Here's H.J.'s message:

        __ctype is from the header files of gcc 1.40. Please backup and remove
        any files related to the previous compilers before you install gcc 2.1.
        There is no __ctype anywhere in the header files for gcc 2.1.
        
        BTW, they are in my FAQ. PLEASE READ IT WORD BY WORD AND FOLLOW THE
        INSTRUCTIONS.
        
        Could you please forward my msg to news groups?
        
        H.J.
        -- 
        School of EECS                          Internet: [email-masked]
        Washington State University             BITNET:   [email-masked]
        Pullman, WA 99164                       Phone:    (509) 335-6470 (O)
        USA                                               (509) 334-6315 (H)

Thanks for your help, H.J. -- the fault was entirely mine.

For those who are installing 2.1 for the first time, "Remove all other
compilers" means "rm +recursive /usr/include /usr/lib /usr/local/lib
(and anything else that looks suspicious)."  Took me a while to catch
on to that :)

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

From: [email-masked] (Joseph Knapka)
Subject: <assert.h> in gcc2.1
Date: 8 Apr 92 13:39:22 GMT

Has anyone had trouble using assert under gcc-2.1? The problem I'm
having (and it only takes a trivial bit of code to demonstrate) is
that while #define-ing NDEBUG turns off assertions as advertised, it
seems that subsequently #undef-ig NDEBUG and re-#include-ing
<assert.h> *fails* to turn them back on.  Am I hallucinating, or is
there really a problem?

Thanks for any assistance,

Joseph

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

From: David Fenyes <[email-masked]>
Subject: Unsubscribe
Reply-To: [email-masked]
Date: Thu, 9 Apr 1992 17:17:24 GMT

Hello,

Please unsubscribe me from the mailing list--

Thanks :-)  And I'm grateful for the wonderful service you've 
provided :-)

David.
--
David Fenyes                                 [email-masked]
University of Texas Medical School           Houston, Texas

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

From: [email-masked] (Dennis Flaherty)
Subject: Patch to preset the SVGA mode
Date: 9 Apr 92 16:49:27 GMT

If you are tired of hitting RETURN and selecting the
same SVGA mode every time you boot Linux, apply this
patch and rebuild the kernel.  It allows you to preset
the mode in the Makefile, so that the setup program
proceeds as if you had hit RETURN and your favorite number.

Dennis

*** Makefile~   Mon Apr  6 15:41:45 1992
--- Makefile    Thu Apr  9 10:39:19 1992
***************
*** 44,49 ****
--- 44,53 ----
  AS86  =as86 -0 -a
  LD86  =ld86 -0
  
+ # If you want to preset the SVGA mode, uncomment the next line
+ # and set SVGA_MODE to whatever number you want.  I use #2.
+ #SVGA_MODE=   -DSVGA_MODE=\#2
+ 
  AS    =as
  LD    =ld
  #LDFLAGS      =-s -x -M
***************
*** 124,130 ****
        $(LD86) -s -o boot/setup boot/setup.o
  
  boot/setup.s: boot/setup.S include/linux/config.h
!       $(CPP) -traditional boot/setup.S -o boot/setup.s
  
  boot/bootsect.s:      boot/bootsect.S include/linux/config.h
        $(CPP) -traditional boot/bootsect.S -o boot/bootsect.s
--- 128,134 ----
        $(LD86) -s -o boot/setup boot/setup.o
  
  boot/setup.s: boot/setup.S include/linux/config.h
!       $(CPP) -traditional $(SVGA_MODE) boot/setup.S -o boot/setup.s
  
  boot/bootsect.s:      boot/bootsect.S include/linux/config.h
        $(CPP) -traditional boot/bootsect.S -o boot/bootsect.s
*** boot/setup.S~       Mon Apr  6 13:32:48 1992
--- boot/setup.S        Thu Apr  9 10:36:55 1992
***************
*** 245,250 ****
--- 245,251 ----
        mov     es,ax
        lea     si,msg1
        call    prtstr
+ #ifndef SVGA_MODE
  flush:        in      al,#0x60                ! Flush the keyboard buffer
        cmp     al,#0x82
        jb      nokey
***************
*** 259,264 ****
--- 260,266 ----
        mov     ax,#0x5019
        pop     ds
        ret
+ #endif
  svga: cld
        lea     si,idati                ! Check ATI 'clues'
        mov     di,#0x31
***************
*** 497,502 ****
--- 499,507 ----
        call    prtstr
        pop     si
        add     cl,#0x80
+ #ifdef SVGA_MODE
+ nonum:        mov     al,SVGA_MODE            ! Preset SVGA mode 
+ #else
  nonum:        call    getkey
        cmp     al,#0x82
        jb      nonum
***************
*** 508,513 ****
--- 513,519 ----
  zero: sub     al,#0x0a
  nozero:       sub     al,#0x80
        dec     al
+ #endif
        xor     ah,ah
        add     di,ax
        inc     di

-- 
Dennis T. Flaherty     [email-masked]
Miles, Inc.            [email-masked]
Diagnostics Division
My doctor says Mylanta, but my boss says Alka-Seltzer!

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

From: [email-masked] (Todd Radel)
Subject: Wish list...
Date: 9 Apr 92 17:42:25 GMT

Does anyone have any of the following compiled for Linux?

- System information (e.g. du, df, users, uptime, etc.)
- Mail system (mail, rmail, sendmail, etc.)
- Any type of BBS or Muck software

Also, how close is the port of X-Windows coming to reality?  If someone gets
X working, I'll format my DOS partition!

Cheers,
Todd
 
-- 
* Todd Radel                      Sysop, Dickinson Domain BBS                *
| CIS/English                     FidoNet: 1:150/160; VirtualNET @3023       |
| University of Delaware          REGISTERED Alpha Colony VI!                |
*         "You don't need to be crazy to be a sysop, but it helps!"          *

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

From: [email-masked] (William Michael Lye)
Subject: Re: Non-destructive repartitioning (was Re: What is linux?)
Date: 9 Apr 92 15:29:33 GMT

[email-masked] (Anthony Frey) writes:

>In article <[email-masked]> [email-masked] (Adam Justin Thornton) writes:
>>Using pfdisk, it's actually not that bad.  Use a disk optimizer to put all your
>>stuff on the front of the disk.  Use pfdisk to create your partitions, making 
>>sure that the DOS partition is bigger than all the stuff you now have in it.
>>If it's your boot partition, use Norton or something to edit the boot record so
>>that the whole filesystem believes it's the right size.
>>
>>Then boot from linux and mkfs on your new partition(s).  No problem.
>>
>>Adam
>>

>Hi everyone,

>I think this non-destructive partitioning is the route I want to take. I've
>done most things up to the point of running pfdisk and I feel fairly confident
>of what I'm doing but there's one thing that's hanging me up. I guess this is
>kind of a DOS question but there's probably more repartitioning going on here
>than the average DOS newsgroup.

>I'm running DOS 5.0 and Norton for DOS 5.0 and the Norton optimizer reports the
>very last few clusters of the hard disk as being unmovable and owned by a file
>called 'image.idx'. I believe this has something to do with an extra copy of
>the DOS 5.0 boot image. The question is, does DOS absolutely need this file in
>that particular location, or might it possibly create a new image in the last
>few clusters of a new partion? If not, can this file be moved and how?

>I've got an extra 40meg free on my hard drive that's got Linux written all
>over it. Thanks! 
>-- 
>-----------------------------------------------------------------------------
>Anthony Frey
>[email-masked]                          "Building stereotypes
>                                               for the 90's"

You can just delete this file.  It would be out of date once you do your
partition editing anyways.  Use "attrib -hr image.idx" to make the file
writable and visible, and then delete it.  Check your autoexec.bat file and
comment out the line that creates this file (probably mirror) until you've
finished re-arranging your disk.  Once you've done your magic, and made sure
that everything is working ok (use NU to write garbage to the last logical 
sector of the new, smaller partition, and then use absolute sector read to
find it and check your math is correct) you can remove the comment.  One
thing in the original message you should know about.  If you've got multiple
DOS partitions, only one of which is bootable, you should know that all
partitions have boot code in them even if it is code that says "Non-system
disk" or something similar.  You'd have to massage the sector count in all
partitions' boot records.

Good luck!

-- 
Bill Lye, [email-masked]
SFU claims these views....NOT!

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

From: [email-masked] (David Engel)
Subject: Re: <assert.h> in gcc2.1
Date: 9 Apr 92 17:58:59 GMT

[email-masked] (Joseph Knapka) writes:
: Has anyone had trouble using assert under gcc-2.1? The problem I'm
: having (and it only takes a trivial bit of code to demonstrate) is
: that while #define-ing NDEBUG turns off assertions as advertised, it
: seems that subsequently #undef-ig NDEBUG and re-#include-ing
: <assert.h> *fails* to turn them back on.  Am I hallucinating, or is
: there really a problem?

You're right!  You need to delete the #ifndef _ASSERT_H/#define _ASSERT_H
and associated #endif stuff from include/assert.h.

David
-- 
David Engel                        Optical Data Systems, Inc.
[email-masked]                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081

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

From: [email-masked] (Joel M. Hoffman)
Subject: Another bug? [was Re: linux-0.95c known bugs]
Date: Thu, 9 Apr 1992 20:02:44 GMT

In article <[email-masked]> [email-masked] (Linus Benedict Torvalds) writes:
>Well, only one known bug so far, but a couple of problems. I thought I'd
>mention them before anyone else does, and we'll call them "features" :^)

More than once, I've gotten a message about mis-linked processes.  I
usually get it when I'm compiling from one VC and using Kermit
interactively on another, but most of the time I'm compiling and using
Kermit....

I'm using a patched .95a kernel, GCC 1.40, and the kermit binary from
tsx (running on a Dell 325D -- '386DX with 2M).

-Joel
([email-masked])

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

From: [email-masked] (Jim Winstead Jr.)
Subject: Re: HELP! Problems with rootimage.
Date: 9 Apr 92 19:54:45 GMT

In article <[email-masked]> [email-masked] writes:
>In article <[email-masked]>, [email-masked] (Timo Jaakko Sillanp{{) writes:
>> Am I doing something totally wrong? 
>> I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
>> uncompress it and write it to a floppy disk (1.44Mb) using
>> rawrite.exe. 
>
>the rootimage is (I think !) for a 1.2Mb floppy.  Try to find a rootimage for a 
>1.44 disk - this could be the problem ...

The root image is 1.2 megs because that is the only size that will fit
on both a 1.2 meg 5.25" disk _and_ and 3.5" 1.44 meg disk.  There are
not seperate 3.5" and 5.25" root images.

-- 
Jim Winstead Jr. (CSci '95)    | "Catch a fish!"
Harvey Mudd College            |  -Geddy Lee,
[email-masked] |   San Diego Sports Arena
Disclaimer: Mine, not theirs!  |   January 20, 1992

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

From: [email-masked] (Joe Smith)
Subject: Re: Binaries considered harmful
Date: 9 Apr 92 19:38:44 GMT

I'll probably regret this, but here goes...

What's the beef?  I think the discussion about distributing individual
binaries is clouding a more important issue.  It seems pretty clear to
me that linux, just like any Unix, needs a binary distribution to
bootstrap from.  The binary distribution needs to be
        * stable
        * easily downloaded & installed
        * complete(*)
        * as small as practical (say ~5-8 Mb)
This would allow newcomers to install a working system with known
features (& bugs) with a minimum of hassle and ftp/file transfer time.

I'd like to see this system include gcc(**), but that's certainly not
necessary.  From this platform, people could evaluate linux without
spending a couple of weeks moving this file and that patch, etc.  If
successful, they can then add binary accessory packages or source +
patches.  The distribution model used by commercial Unixes is not bad
- it just costs way too much, and you can't get source even if you
want it.

I don't know if Alan's ABC version will do this or not, but I hope
so.  Without a stable C compiler & development system it's probably a
waste of time to try and assemble a distribution, but now I think we
can.

<Joe
==============================
(*) What's complete?  Well, one example comes to mind: the MKS toolkit
is reasonably complete and fits into this size limitation.  Basically
it should have enough functionality to give a good look at Unix and
the capability to load additional packages.  Maybe the Byte benchmarks
would be a reasonable target capability.

(**) What would you do with such a system except software development:
I'm not holding *my* breath for Word Perfect for Linux :-)

--
 Joe Smith
 University of Pennsylvania                    [email-masked]
 Dept. of Biochemistry and Biophysics          (215) 898-8348
 Philadelphia, PA 19104-6059

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

From: [email-masked] (Michael K. Johnson)
Subject: New things at tsx-11
Reply-To: [email-masked] (Michael K. Johnson)
Date: Thu, 9 Apr 1992 21:55:28 GMT

OK, there are a few new things at tsx-11.mit.edu

Linus has made available another patch for linux, right after I
finally patched the source to .95c.  This one is called .95c+ (wait,
doesn't the unary operator look like '++'?...) and patches are
available in /pub/linux/patches, source in /pub/linux/source/system,
and bootimage in /pub/linux/images.  All the files have the
appropriate names with .95c+ in them.  Oh, yeah, there's also a
README.0.95c+ in /pub/linux/docs.

Jim Winstead has made available the system-0.95a.tar.Z he promised,
with source to many utilities.  It is in
/pub/linux/sources/system

Jim Lynch has ported kermit 5a, and it is available as
/pub/linux/binaries/usr.bin/kermit5A.tar.Z
It includes a readme -- read it.

Someone put a file xcomm.tar.Z in incoming, and it has been put in
/pub/linux/binaries/usr.bin/xcomm.tar.Z
I have not looked at it, and don't know if it belongs elsewhere.  I
don't know what it contains, other than from the name.

Which brings me to this:

NOTE:
Please, when you upload things to tsx-11.mit.edu, send mail describing
it to [email-masked], so that we know that it's there and
what it is.  Most people have been doing this, but a few haven't, so I
thought I would remind people just in case...

michaelkjohnson
[email-masked]

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

From: [email-masked] (Farhan H Garib)
Subject: Re: HELP! Problems with rootimage.
Date: 9 Apr 92 19:49:22 GMT
Reply-To: [email-masked] (Farhan H Garib)

In article <[email-masked]> [email-masked] writes:
>In article <[email-masked]>, [email-masked] (Timo Jaakko Sillanp{{) writes:
>> ...
>
>> Am I doing something totally wrong? 
>> I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
>> uncompress it and write it to a floppy disk (1.44Mb) using
>> rawrite.exe. 
>
>the rootimage is (I think !) for a 1.2Mb floppy.  Try to find a rootimage for a 
>1.44 disk - this could be the problem ...
>
>Tony
>
>                                                   _
>Tony Kew,   Oxford University Computing Services,  (_)xford,  England,  U.K.
>====================================================|=========================
>Janet:- [email-masked]                     --+--    Disclaimer :-
>Internet:- [email-masked] | Who is the more foolish?
>Earn/Bitnet:- tony%vax.oxford.ac.uk@ukacrl         |    The fool, or the
>Phone:- +44 (0)865 273268   Fax:- +44 (0)865 273275 |  man who follows him?
>==================================================\=|=/=======================
>                                                  \|/

I use 1.44MB floppies without a problem.

-Greg

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

From: [email-masked] (Bowen (Laughing Cheetah))
Subject: Re: HELP! Problems with rootimage.
Date: 9 Apr 92 20:49:12 GMT

In article <[email-masked]> [email-masked] writes:
>In article <[email-masked]>, [email-masked] (Timo Jaakko Sillanp{{) writes:
>> ...
>
>> Am I doing something totally wrong? 
>> I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
>> uncompress it and write it to a floppy disk (1.44Mb) using
>> rawrite.exe. 
>
>the rootimage is (I think !) for a 1.2Mb floppy.  Try to find a rootimage for a 
>1.44 disk - this could be the problem ...

The images I have seem to work without any difficulties for either 1.2MB or
1.44MB disks.  Since (to my understanding) they are raw images, it dosen't
really matter how big the disk is, just as long as the entire thing fits.

        -bg
-- 
________________________________________________________________________________
Bowen Goletz
Purdue University                  Midi 'n Music
[email-masked]         [email-masked]

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

From: [email-masked] (Hongjiu Lu)
Subject: Re: gcc-2.1 header files
Date: 9 Apr 92 18:54:02 GMT

In article <[email-masked]>, [email-masked] (Joseph Knapka) writes:
|> H.J. asked me to forward this exchange to the newsgroup:
|> 
|> I said:
|> >> Kernel build of .95c went fine, but when compiling ps, I get
|> >> "undefined symbol __ctype referenced from text segment" while linking
|> >> ps.o. This is with very latest gcc-2.1, libraries, and binutils from
|> >> banjo. I linked xxx/src/linux/lib/ctype.o and got it to compile, and
|> >> (seems that) everything works. Did I do the right thing?
|> >> 
|> >
|> 
|> H.J. said:
|> >No. Please get my 2.1ps.tar.Z, 2.1kernel.tar.Z and apply Linus's second
|> >patch first. When compile any application, do not use ANY header files
|> >from ./linux/include.

That is not totally right. Here again.

I am enclosing a program, conv. You run it under ./linux. That program will ensure only one set of header files is needed for compiling appplications and
kernel.

Before you run it, you have to have gcc 2.1 beta, mv, cp and sed
installed on your system.

Before you do anything, please backup gcc 2.1 and kernel sources. Here
goes.

Step 1: Apply Linus's second patch and then my 2.1kernel.tar.Z.

Step 2: Read conv and understand what it is doing. Then go to the
        toplevel of kernel source tree and do

        conv

Step 3: Edit the toplevel Makefile and add -DPRE_GCC_2 to CFLAGS.
        You have to get rid of "-nostdinc -Ixxxx" stuff since
        ./include has been moved to /usr/include.

Step 4: Type

        make

If you have any problem, please let me know.

H.J.
============CUT HERE======
#!/bin/sh
# you have to run this script under ./linux
INCS="a.out.h const.h asm linux"

# move ctype.h and string.h in kernel source, which are different from
# gcc 2.1 to ./include/linux.
mv ./include/ctype.h ./include/string.h ./include/linux

# copy those header files which don't exist in gcc 2.1 to /usr/include
for h in $INCS
do
  cp -r ./include/$h /usr/include/$h
done

# move ./include to ./include.kernel
mv ./include ./include.kernel

# change
#include <ctype.h>
#include <string.h>
# to
#include <linux/ctype.h>
#include <linux/string.h>
#
DIRS="boot fs init kernel lib mm"
for d in $DIRS
do
  for f in $d/*.c $d/*.h $d/*/*.c $d/*/*.h
  do
    if [ -f $f ]
    then
      sed 's,<ctype.h>,<linux/ctype.h>,' $f | sed 's,<string.h>,<linux/string.h>,' > 1
      mv 1 $f
    fi
  done
done

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

** 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-masked]

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

    Internet: [email-masked]

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    tupac-amaru.informatik.rwth-aachen.de	pub/msdos/replace

The current version of Linux is 0.95a released on March 17, 1992

End of Linux-Activists Digest
******************************