HDTenEightyP/NetNews huggingface dataset:
From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Subject: FAQ or DOCs on common tips for portint to linux available?
Date: Sun, 26 Jul 1992 17:15:48 GMT
Organization: Illinois State University

Hello again,

Does anyone know of a good source of information, tips, FAQs, etc.,
on how to port software to linux.  Specifically, I'm looking for
tips on what has worked for others when certain problems arise.

For example, while trying to compile tgif (an xwindows paint program)
I got the message "file.c:1236: `SIGBUS' undeclared (first use this function)"
Usually, I can get around this by adding -DSYSV to the CCOPTIONS line
in the makefile generated by xmkmf.  In this case it didn't work, which
indicates to me that a) I need to try adding other -D switches and/or
b) I need to write the linux equivelent code by hand.  Tips on how to
do both, or documentation (if it is available anywhere) would be greatly
appreciated.  

Another bit of strangeness occurred as I was trying to compile
xfishtank.  This time, the make failed on an undeclared structure
"vec", which was used in the following way:

init_signals()
{
    struct sigvec vec;

    vec.sv_handler = toggle_secure;
    vec.sv_mask = 0;
    vec.sv_onstack = 0;

    sigvec(SIGUSR1, &vec, &vec);
} /* I have removed the #ifdefed stuff for HP and MOTOROLA, leaving only
     the code which, by implication, is supposed to be generic */

Is anyone keeping a FAQ on such questions?  If not, I would be happy to
volunteer my services as my contribution to the linux project.  A repository
of "if this error occurs, common things to try (in this order) are ..."
might be useful.

Thoughts, comments?

Jean.
-- 
Jean Liddle                                 | == Bill Clinton for President ==
Computer Science, Illinois State University | 
e-mail:  jliddle@ilstu.edu                  | - Carol Mosley Braun for Senat -
Newsgroups: comp.os.linux
From: weiler@crabapple.cis.ohio-state.edu (Jerry Weiler)
Subject: Re: yacc and lex
Originator: weiler@crabapple.cis.ohio-state.edu
Organization: NAIVE - New And Improved Virtual Environment
Date: Wed, 22 Jul 1992 02:37:19 GMT

In article <1992Jul21.164738.1@mcclb0.med.nyu.edu> ramirez@mcclb0.med.nyu.edu writes:

> I would like to know if anybody has ported yacc and lex
> over to linux. If yes, please let me know where I can find it.

You should use bison and flex. bison is the GNU replacement for yacc
and flex is the GNU replacement for lex. They're faster, more flexible
and all around better. Bison and flex should be able to handle any
grammer yacc and lex do (any well written one, that is)

they're available on tsx-11, banjo, and mirror sites. source can be
obtained from prep.ai.mit.edu. I dunno about where to find yacc and
lex. if you're still interested in 'em, try archie.
From: news@solitary.Stanford.EDU (System test)
Subject: please help: I killed my hard drive with efdisk
Organization: Stanford University, California
Date: Wed, 22 Jul 1992 06:16:46 GMT

Simply by changing the id tags on my Linux partitions with efdisk
I seem to have made the entire disk unreadable.  The partitions
were originally set up with pfdisk and I'd set the id number to 
some "unknown" type just to hide them from DOS.  Today I was playing
around with the new efdisk which came on the 0.96c root disk trying
to figure out what all I'd have to do to have the new extended file
system.  (Never did figure that out: it'd make a good FAQ.)  In
the process I saw that there was a nifty 't' option to change the id
type, so I figured I set 'em all to the official Linux number.

Big mistake: when I rebooted the machine (after syncing) I got hard
drive installation errors in the boot process.  I'd had the system
configured with two IDE drives, DOS on the master, 4 Linux partitions
on the slave, using bootlin on the DOS disk to boot Linux.

After ignoring the hardware boot errors, I managed to boot Linux from
a floppy.  After resetting the hard drive controller a number of times
Linux succeeded in reading the recalcitrant drive.  And I promptly made
things worse by restoring the old id types, this time with pfdisk.

Now, no matter what I try, I can't read the drive (Maxtor 120 MB IDE,
by the way).  When I boot Linux from a floppy it repeatedly attempts 
and fails to reset the hard drive controller:

HD-controller reset
HD-controller times out, c=d0
HD-controller still busy
HD-controller reset failed: ff
controller_ready: status = ff
HD-contoller reset

and this repeats over & over.

Please, please someone tell me I didn't just toast my drive (which I
only bought a few months ago specifically for Linux).  What incantations
must I perform to make it whole again?  It'd be nice not to have lost
its contents, but just to be able to use it again would make me
deleriously happy.  Did I destroy the MBR?  If so, how can I restore it
without even being able to control the drive with the HD controller.
In the meantime I'm stuck with DOS on the other drive :-(

Thanks.

Don Taber
news@solitary.stanford.edu
From: steve@Nyongwa.CAM.ORG (Steve M. Robbins)
Newsgroups: comp.os.linux
Subject: getty_ps on banjo
Date: 21 Jul 92 20:38:21 GMT
Organization: Chiral Symmetry Breakers of Montreal

It was suggested that I put the new getty_ps sources on banjo.concert.net
as well as on tsx-11.mit.edu, so I did.

In pub/Linux/Incoming:
	gettyps202.tar.Z		- the complete source
	gettyps200-202.tar.Z		- diffs to update the original source

Steve

-- 
Steve Robbins  --  steve@nyongwa.cam.org
Nietzsche is dead - God
Newsgroups: comp.os.linux
From: mod32@cs.rug.nl ( )
Subject: Re: QIC-02 tape driver?
Organization: Dept. of Computing Science, State University of Groningen
Date: Wed, 29 Jul 1992 14:47:36 GMT

In article <NEGAARD.92Jul27123006@fungus.aero.org> negaard@aero.org (Eric Negaard) writes:
>I thought I remembered seeing a message from someone who is working
>on a QIC-02 driver, but I can't find it now.  Is anyone working
>on this beast?  Do you need beta-testers? :-)  Or, more seriously,
>do you need help?
>
>			Eric Negaard


Yes, I'm working on it. A new release should be out RSN. Beta-testers
are always welcome ;-) There are some minor buglets left, so if you're
feeling bored ...

-Hennus Bergman

Newsgroups: comp.os.linux
From: barr@hardy.u.washington.edu (David Barr)
Subject: sgtty.h
Organization: University of Washington
Date: Wed, 29 Jul 1992 16:58:49 GMT

I was trying to compile cxterm (Chinese xterm) and it tried to include
<sgtty.h>, which I do not have on my system.  Taking the include
statement out of cxterm resulted in a whole lot of undefined stuff.
So, do I need to get a copy of sgtty.h, or what?  If so, where?

David
Newsgroups: comp.os.linux
From: haldane@dcs.warwick.ac.uk (Steve Sykes)
Subject: TCP/IP current status
Organization: Department of Computer Science, Warwick University, England
Date: Thu, 23 Jul 1992 01:27:22 GMT



Hi guys! (OK gals too, but I think 'guys' is gender-wide!!!!)

I have suddenly needed to become aware of the current state of kernel
TCP/IP support under linux.  I've seen the odd mention since dec'91
but nothing lately.  AND...Ican't find out who and where the latest
on this thread of development is.

If you are working on TCP/IP support, (I want to be able to port
ftp etc etc etc) drop me some e-mail.  ka9q is swell, but I'd really
like to be a *complete* part of the internet :-)

Thanks

summary posted as and when!

Laurence Culhane
From: tlhilde@roby.ecn.purdue.edu (Troy Hildebrand)
Newsgroups: comp.os.linux
Subject: ST-02, ST-51 disk controllers coexisting?
Date: 29 Jul 92 05:11:45 GMT
Organization: Purdue University Engineering Computer Network

Hello,

     I am trying to install Linux on my 386sx16, 2M, with an ST02
controlling an (80 Meg) ST-296N and an st-51 controlling a 74Meg MFM
drive (i'm not sure what kind, but the ST-51 bios recognizes it).

Neither of the drives are in the ROM Bios (Phoenix), because the
controllers take care of it.  The Problem is, when I boot linux from
floppy, it recognizes the SCSI drive, but not the MFM drive.  And
then later, it gives a warning, "READ CAPACITY FAILED" or something
about the SCSI drive.

I would like to keep the SCSI drive for use under dos, and install
linux onto the MFM drive (64 meg now, with extra partition for swap).
Does anyone see a problem with this setup?  Will I be able to boot
selectively ie, either OS, without hassle?

Help me get this OS onto my system soon!  THANKS.

Troy

--
tlhilde@en.ecn.purdue.edu
From: laakkone@klaava.Helsinki.FI (Tero Laakkonen)
Newsgroups: comp.os.linux
Subject: tlA: /bin/arch solved.
Date: 23 Jul 92 17:07:23 GMT
Organization: University of Helsinki

thanks to everybody who e-mailed me about my /bin/arch problem. i
thought it was a rather dumb question when i sent it to c.o.l., 
because it is so easy to write a script to "echo i386"...

so, i want to apologise for my dumb question.

nevertheless, i thought that "echoing stuff" like that isn't a very
satisfactory way of doing things (even for "hackers"). 
so i just wanted some better opinions.

and i got one. somebody pointed out to me that "/usr/bin/uname -m"
does exactly the same as /bin/arch does...

so here's my /bin/arch for linux:

---cut here------cut here------cut here------cut here------cut here---
# !/bin/sh
/usr/bin/uname -m
---cut here------cut here------cut here------cut here------cut here---

";-)"

-tero
From: nafpliot@ux2.cso.uiuc.edu (Nick Nafpliotis - IlliGAL)
Subject: Who is handling TeX for Linux?
Organization: University of Illinois at Urbana
Date: Fri, 24 Jul 1992 05:40:47 GMT

I was looking to get TeX for Linux, and I have gotten all the necessary files,
etc.  However I am interested not only in LaTeX, but SliTeX, BibTeX, and 
METAFONT.  Therefore, I was wondering if they were available and I just
couldn't find them on the various ftp sites, or if the person who did the 
port has the format files for SliTeX and the binaries for BibTeX and 
METAFONT as well.   I am also interested in knowing if the TeX available
is a BIG version of TeX or not.    If not, then I will be compiling the 
whole TeX distribution  and would be willing to put it up for 
ftp if enough people are interested (and if I can get it done.)  

Thanks,

Nick 

----------------------------------------------------------------------------
Nicholas Nafpliotis                       nafpliot@ux2.cso.uiuc.edu
Illinois Genetic Algorithms Laboratory
Department of General Engineering
University of Illinois at Champaign/Urbana 

Newsgroups: comp.os.linux
From: nhc@cbnewsj.cb.att.com (n.h.chandler)
Subject: Re: Two Hard drives?
Organization: AT&T
Date: Thu, 23 Jul 1992 03:40:14 GMT
Summary: Linux BOOT.SYS BOOTUTIL

In article <1992Jul22.233242.22228@rs6000.cmp.ilstu.edu>, jliddle@rs6000.cmp.ilstu.edu (Jean Liddle) writes:
> In article <Brt6Lz.7Fp@news.udel.edu> radel@bach.udel.edu (Todd Radel) writes:
> >OK, folks, here it is:  How to keep Linux entirely (err, almost) on a 
> >second hard disk and still be able to boot without a floppy.  Here's
> >what you do:
> >
> > [ ... ]
> >
> >1. Backup everything. 
> >2. Repartition your primary hard disk (drive C:) and add a 1mb partition
> >   somewhere.  My 119mb drive looks like this:
> >
> >	DOS partition	/dev/hda1	118mb
> >	Linux boot	/dev/hda2	1mb
> >
> 
> This week I completely repartitioned my hard drives, giving LINUX the
> Lions Share of space.  To be on the safe side, I mirrored my entire
> bootable Linux installation on a partition on the second hard drive and
> recompiled the kernel with my ROOT device set to sdb2.  Using mcopy
> I copied the resulting Image to the C: drive, from which bootlin4 can
> execute it.  I rebooted and Linux worked fine from D:, with absolutely
> no reference to anything on C: beyond the initial BOOT.SYS and BOOTLIN
> calls.  If your using DOS on your C: drive anyway, this approach would
> let you avoid having to create an extraneous 1 MB parition.
> 
> Using this approach I was able to mess around with the partitioning
> scheme on /dev/sda with no fear of reprisal, beyond having to reinstall
> my DOS stuff from floppy backups.  Worked like a charm.
> 
> Jean.
> -- 

Same here!!  This arrangement also allows easy testing of new images.
One can move the new kernel image to C, modify the CONFIG.SYS file
to add another menu item for the new kernel image.  If the new image
bombs, reboot the system and select the original kernel.

Neville Chandler
nhc@mtdcr.att.com
Newsgroups: comp.os.linux
From: mhbrekke@iastate.edu (Monty H. Brekke)
Subject: Rebooting and bad cache
Organization: Iowa State University, Ames, IA
Date: Wed, 29 Jul 1992 03:16:59 GMT

Has anyone else received a bad cache memory error after rebooting Linux?
Every time I reboot, my BIOS tells me that my cache memory is bad, and that
I should disable it. This message comes up just before the Shoelace menu
appears and only after I have rebotted from Linux. Rebooting from DOS does
not seem to produce this error. Also, if I shutdown and then C-A-D instead of
typing reboot, the error does not appear. Disabling the external cache seems
to fix the problem.

My system configuration is as follows:

486-33
AMI BIOS/OPTi chipset
256K external cache
16MB memory
1.44MB 3.5 inch floppy drive on /dev/fd0
1.2MB 5 inch floppy drive on /dev/fd1
Quantum 244MB hard drive partitioned as follows:
	~100MB DOS partition on /dev/hda1
	~64MB Linux root partition on /dev/hda2
	~50MB Linux partition on /dev/hda3, mounted as /home
	~20MB Linux swap partition on /dev/hda4
Colorado Memory Systems 250MB tape drive

Any help would be greatly appreciated. Thanks in advance.

Monty
-- 
Internet : mhbrekke@iastate.edu
Newsgroups: comp.os.linux
From: kenc@sol.acs.unt.edu (Ken Corey - Operator)
Subject: Anyone use the cscript utility?
Organization: University of North Texas
Date: Thu, 23 Jul 1992 22:36:28 GMT

I got this little tiny utility to capture whatever happens to a file, while
it's happening.  It works great at school on Solbourne's MP version of
SunOS, but works sporadically, and in fits and starts on Linux.  It uses
pipes, so might be a test of capability for Linux...

-Ken
From: as@prg.ox.ac.uk (Andrew Stevens)
Newsgroups: comp.os.linux
Subject: Re: tlA: /bin/arch solved.
Date: 25 Jul 92 15:04:02 GMT
Organization: Oxford University Computing Laboratory, UK

In article <bjl.711923672@freyr> B.J.Lippolt@research.ptt.nl writes:
>laakkone@klaava.Helsinki.FI (Tero Laakkonen) writes:
>
>>and i got one. somebody pointed out to me that "/usr/bin/uname -m"
>>does exactly the same as /bin/arch does...
>
>Is there a way to distinguish between a 386 and a 486? I have a 486,
>but 'uname -m' says 'i386'. But when I compile with 'gcc -m486' I'll
>get code which doesn't run on a 386.

Surely this is not the case.   As I understood it the user-level instruction
sets of the 386 and 486 are identical.  The -m486 flag just tweaks
code generation to use instruction sequences better suited to the 486's
instruction timings instead of sequences best suited to 386 instruction
timings.


Andrew
        Andrew Stevens                  
      Programmming Research Group       JANET: Andrew.Stevens@uk.ac.oxford.prg
     11 Keble Road, Oxford, England     UUCP:  ...!uunet!mcvax!ukc!ox-prg!as
     OX1 3QD   +44 0865 272563
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Anyone done bc?
Date: 22 Jul 92 20:18:24 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

Last night using linux I realized how much I use bc. Has anyone done a
port, or is there even a free version? Seems there was a GNU version,
but it may only have been dc.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
	It never ceases to amaze me that otherwise rational people, able to
	understand calculus, compound interest, and the income tax form, can
	continue to believe that poker is a game of chance.
From: Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin)
Newsgroups: comp.os.linux
Subject: Problems with Alpha.5 DOSFS
Date: Mon, 20 Jul 1992 08:13:54 -0800

I put up patch 2, and the DOS file system works great!  However, I do
have one problem.  When using JOE (as released with the Winstead root, I
think?), I show control-M's on the end of each line and a control-Z at
the end of the file, when I edit files with extensions not listed as
binary in misc.c.  I have mounted the file system using smount, with all
three modes (binary, text, auto) and all behave the same.  The
extensions in question are .CFG, .BAT, .BTM and many more....

HELP!  [grin]

Rob L.

P.S.  I want to thank the developer(s) and other alpha-testers.  This is
nice stuff.  Oh, by the way, I'm using the smount utility from the
Alpha.5 archive.

Rob


 * Origin: Via the Annex in Victoria, TX (1:3802/217)

Newsgroups: comp.os.linux
From: smace@nyx.cs.du.edu (Scott Mace)
Subject: Ctrl-Alt-Del in linux, doesn't work.
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Fri, 31 Jul 92 01:08:57 GMT


Ctrl-Alt-Del doesn't reboot my system.  It disables the keyboard and
locks everything up.  I am running 0.96c patch level 2, and have AMI
BIOS., 386DX-33, Adaptec AHA-1542B,...

Thanks, 
Scott Mace
--
*********************************************************************
*    Scott Mace                internet:    smace@isis.cs.du.edu    *
*********************************************************************
From: rohrer@fncrda.fnal.gov (Keith Rohrer)
Newsgroups: comp.os.linux
Subject: Re: Problems with X as non-root
Keywords: X tty
Date: 22 Jul 92 16:16:55 GMT
Followup-To: rohrer@fncrd0.fnal.gov
Organization: Fermilab

Have you tried chmod go+whatever /dev/tty0?  Or is /dev/tty0 a link?
One thought is that if the way it's set up is as a link to /dev/ttysomeodd,
where the user attempting to start X is not logged in on that device,
the tty to which tty0 is linked is owned by the user logged in on it
(or root, if there is no such user) and therefore probably not
writable by the user trying to start X...

	Keith
(rohrer@fncrd0.fnal.gov)
Newsgroups: comp.os.linux
From: janl@ifi.uio.no (Jan Nicolai Langfeldt)
Subject: Re: Problems compiling 0.96cpl1
Organization: Folkeaksjonen for (tungt) eple cider p} Inf. stua
Date: Tue, 21 Jul 1992 23:57:48 GMT
Originator: janl@maud.ifi.uio.no


In article <1992Jul21.201637.5864@constellation.ecn.uoknor.edu>, callison@uokmax.ecn.uoknor.edu (James P. Callison) writes:
> I'm having problems compiling 0.96cpl1...(surprise, surprise, surprise :-)
> I applied the patches to the 0.96c source (which, with the help of a few
> persons to whom I am truly grateful, I got to compile) using 
> 'patch </patch1' correctly, I think. However, patch kept saying "this

The correct way to do it is 'patch -p0 <patchfile', which should
abolish the problems you mention later in the post.

Nicolai

-- 
Nicolai Langfeldt, "Bugs made while you wait"             
Internet: janl@ifi.uio.no

Newsgroups: comp.os.linux
From: sevenup@netcom.com (Mark W. Moorcroft)
Subject: Re: New version of the SCSI drivers
Date: Thu, 30 Jul 92 02:37:27 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)

>>
>>
>>	The new bootimage won't even allow me to get far enough to run
>>efdisk and specify /dev/sd01. With the old bootimage I was able to
>>load the rootimage but efdisk would crash after I specify the above.
>>It would allow me to partition the disk (apparently?) but no drive
>>info was detected (sect,cyl,heads) so the disk was unusable anyway.
>>
>>

>1.  you need to patch the bootimage so that the bytes at offset 508 / 509
>	are 0 so that it doesn't try mounting root from partition one 
>	of a "normal" hardisk.  This was a mistake, a new image 
>	will be put out "some time" that fixes this.  I think 
>	I'll have an all night debugging session with the HP700 port
>	of BSD, so it won't be too soon.

Done (with pboot.exe)



>2.  As far as partitioning with something under Linux : 
>
>	Use a DOS partitioning program.  Some of the Linux
>	partitioning programs are unhappy with not having the 
>	(unavailable) disk geometry.
>
>	pfsdisk works, but note that shoelace will not work if the 
>	geometry in the partition table does not match what
>	the BIOS says.


I have now tried the partitioning utilities from 3 seperate ftp sites,
and 2 under DOS. I have used the disk geometry info reported to DOS,
and also the actual figures. I am coming to the conclusion that until
Linux is equipped with the ability to detect my disk geometry I will
not be able to mkfs :-(
	I would like to thank Drew Eckhardt for sending me direct mail
to address this issue. There is much conflicting info on configuring
SCSI systems at the various ftp sites and I have no idea how to
proceed ?  (SCSI disk 1 = /dev/sdb, or /dev/sd1, or /dev/sd01, or ...)

system=

386/16 w/4 meg
1542b SCSI host
2 80 meg drives and one 60 meg tape (all SCSI)
Paradise plus 16 VGA board


??????????????????????????......



-- 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Mark W. Moorcroft -- sevenup@netcom.COM -- C.I.S. 70741,325
-------------------------------------------------------------
  "I speak for myself and those who agree with me !"   ;-)
From: lynch@ccwf.cc.utexas.edu (Tom Lynch)
Newsgroups: comp.os.linux
Subject: X11 programs porting HELP needed
Date: 29 Jul 92 19:19:39 GMT


Summary: How/where can one get files to port programs such as XFIG?

I downloaded (ftp) one of the X11 contrib splits from a stanford machine
with the intent to PORT XFIG.  I used cat to put the peices 
together:


       cat contrib-1* >c1.tar

and then untared it and got a checksum error.  I used a binary
mode transfer.   I have never done this before.  Question: is
this the right method to use, and there is just glitch, or am I
way off?  Any help appreciated.

p.s. I have now ported Ghostscript, Ghostview, and Gnuplot, is anyone
needs help with these.  Also, thanks to everyone who answered
questions to help with these ports!

p.s.s. does anyone know what unidraw is?  is it better than xfix?

-tom
lynch@ccwf.cc.utexas.edu
From: barr@hardy.u.washington.edu (David Barr)
Newsgroups: comp.os.linux
Subject: Re: olvwm
Date: 28 Jul 92 15:45:29 GMT
Organization: University of Washington

lhanson@moose.uvm.edu (lhanson) writes:

>not been successful (fatal errors in olwm.c).  The Makefile also
>requires flex; where are the current sources for flex?

>Lee

Flex is with the rest of the GNU stuff at prep.ai.mit.edu in pub/gnu.

David
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: Setuid?
Date: 21 Jul 1992 23:53:56 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

smp@myamig2.myamiga.mixcom.com (Steve Palm) writes:

>probreak@matt.ksu.ksu.edu (James Michael Chacon) writes:
>: 
>: >  What's 'setuid' and what does it do?
>: 
>: The setuid bit is done by doing a chmod 6xxx (where x are your normal values)
>: on the files involved. The setuid bit will allow the program to run under

> Wouldn't a setuid be a chmod 4xxx?  I thought 6xxx was setuid/setgid.

>Steven M. Palm
>smp@myamiga.mixcom.com   or   smp@myamig2.myamiga.mixcom.com (LINUX SITE)
>Milwaukee, WI

I know, my mistake. After I posted the message I realized the mistake, but 
since it wasn't going to damage anything I didn't kill it.


-----------------------                              ---------------------------
-----------------------       James Chacon           -probreak@matt.ksu.ksu.edu-
-----------------------                              ---------------------------

-