HDTenEightyP/NetNews huggingface dataset:
From: steffen@gfz-potsdam.dbp.de
Subject: Re: Newbie Linuxer
Reply-To: steffen@gfz-potsdam.dbp.de
Organization: The Internet
Date: Tue, 28 Jul 1992 07:50:59 GMT

RFC-822-Headers:
X-Mailer: ELM [version 2.3 PL11]

==================
X-Mn-Key: normal

Hi,

first : welcome to the growing Linux community !
Another one made the final step away from DOS ...

To your questions (I'm new - 5 weeks reading c.o.l., 2 weeks experience
with 0.96c[pl2], so my answers may be incomplete or incorrect, but I hope
they will help you) :

[questions omitted - see Digest #524]

1. To boot DOS from HD, you have to mark your DOS partition as bootable
(this has nothing to do with laceup's asterisk !). Give Shoelace a '1' at
the Boot: prompt, this will do.
   To boot Linux from HD, in addition to the shoelace installation (the
laceup command -w 2 only marks the standard partition to boot from !) you
have to modify your boot image - if you recompile the kernel, this may be
done by editing the Makefile (ROOT_DEV), the Image should be in /etc then...
2. Get rid of the /etc/nologin file, this is left by a shutdown. Insert
a line like 'rm -f /etc/nologin to your /etc/rc startup file.
3. For automated selection of terminal resolution, get Digest # 490 from
tsx-11. It's somewhere in .../Volume2 in compressed form (digest490.Z) -
maybe you should ask archie for help...
4. mtools usually works on /dev/fd0 autodetecting; for formatting you have to
choose the correct device (fd0h1440 or so, have a look into your /dev dir.)
I didn't format disks with a DOS fs under linux ...
You will never need mkfs for this ! mkfs is for Linux file systems. If you
want to tar to a disk, you have only to format it.
Try dosfs built into 0.96cpl2 (get patch dosfs.6 !), its very nice - you
will never need mtools again. (But formatting is a problem i've not solved yet,
may be I'm overlooking something.)
5. The numbering of the com port depends on your kernel version, try /dev/ttysx
with x=0...4 (0 or 1 may be com1 and so on).
X should run with 4 chipsets : ET3000, ET4000, GVGA, PVGA1 (I type this off
my head, so it may be mis-spelled) - check your Paradise card (get whatvga.pas
somewhere in X386kit, I believe) for the chip set ! (& read the X channel)
There should be a possibility to run X in LOW resolution (640x400), you need
256 colors up to now (16 color modes are in work, I think).
---> If you get your card running with X, let me know the paarmeters - thanx !
Check your mouse response with /tst/mouse/mouse. There are different types
of Logitechs around. (Behaving like Microsofts - or not...)
6. !!!! What is that : Nethack ??? All speak about it, but I still don't know
what it is for !
7. Ghostscript has just been ported (should go without problems, -DSYSV should
help). GhostView - ??? There is also zsh, tcsh ... look at tsx-11 or banjo.
(Brute force : get a 'ls -ltR' to a file and search inside, it's faster than
archie !)

Good luck !
--
Steffen Grunewald | IP : steffen@gfz-potsdam.dbp.de | Phone : (+49)331-310526
GeoForschungsZentrum Potsdam,  Telegrafenberg A3,   O-1561 Potsdam,   Germany
#include <disclaimer.h>     /* >>> I don't like Mondays - and .sig's ! <<< */
From: drew@juliet.cs.colorado.edu (Drew Eckhardt)
Newsgroups: comp.os.linux
Subject: Re: Graphics library and mouse support in GCC ?
Keywords: Graphics GCC
Date: 28 Jul 92 03:00:54 GMT
Organization: University of Colorado at Boulder

In article <bibhas.712287107@femto.engr.mun.ca> bibhas@pico.engr.mun.ca (Bibhas Bhattacharya) writes:
>I will be very much interested to know the graphics library and mouse
>support with GCC. What could be the equivalent of the QUICK C interrupt

A vgalib is available from the FTP sites that supports VGA/SVGA graphics under
Linux.  You can also use X (if you have suitable hardware) and any of the 
X libraries.  MGR is available too. 

As far as mouse support, one of the windowing systems will handle that for
you, otherwise your on your own.  The code in the selection package, or 
MGR will show you how to digest the packets from the mouse.
 
>caller function int86() and others.

There is none.  The DOS/BIOS model is completely different from the Unix 
paradigm.  All system calls are interfaced by name through library 
routines. You want to write to a device, call write(2).  You want to do 
non-blocking I/O, use select(2).  Anything in section 2 of the manual is a 
syscall, and is analogous to DOS/BIOS intXX's.  

If you were persistant, you could bypass the library interface and 
use the native syscall mechanism, but this would be messy and non
portable.

Every Unix understands read(), nobody else will understand the int 0x80 
Linux uses for the syscall interface, or the call gates that other i386 
Unices may use.
  
You cannot call BIOS routines from protected mode, and without DOS running,
you can't make any DOS calls.

If you want to program under Linux, the GCC libraries are ANSI C, plus
a standard Unix unistd lib that is a hybrid of BSD/SYSV/POSIX.  Libc, libm,
and friends will be documented in any 'C' programming book, a Unix programming
book will cover the unix specific syscalls.

Also, assorted libraries like dbm, and crypt are available.

There are inumerable books on programming X11 on levels ranging from
raw xlib or xt, to the Widget sets and C++ class libraries.

MGR has man pages, as far as the Linux specific things like vgalib,
some documentation is there, but you're pretty much on your own.  

Linux was developed by hacker types
for hackertypes.  Hackers write in  awk, yacc, and even machine code  
(hexadecimal when necessary), not english, so the source code is the 
documentation, and something readable to mortals is not always readily 
available.
From: hlu@phys1.physics.wsu.edu (Hongjiu Lu)
Newsgroups: comp.os.linux
Subject: Re: localeconv()
Date: 27 Jul 92 21:09:29 GMT
Organization: Washington State University

In article <1992Jul27.124114.5363@athena.mit.edu>, J.Jagger@sheffield-city-poly.ac.uk writes:
|> Hi,
|> I was messing around with locale.h and localeconv() does not
|> appear to be in libc.a (or in any other .a file). I'm using the
|> MCC 0.96c version if this is of any help. It is an ANSI function.
|> 
|> Also I ran paranoia on Linux last night (it stresses the darker
|> corner of maths implementations). There were two things it found.
|> 1. (-0.0-----0e00) ^ (0.0-----0e00)
|>    yielded 0.0.....0e00 and not 1.0.....0e00
|> 
|> 2. (2.0------0e00) ^ (1.0-----0e00)
|>    yielded 1.9-----9e00 and not 2.0-----0e00
|>    (important in financial calculations apparantly).
|> 
|> Keep up the great work.
|> JJ
|> 

locale stuffs are taken from glibc 1.03, which is incompleted.


-- 
H.J.
Gcc/libc maintainer for Linux.
From: dennisf@miles.com (Dennis Flaherty)
Newsgroups: comp.os.linux
Subject: Re: SVGA modes in setup.S (Was: Kernel mucking (Was: New Linux Install: Summary))
Date: 29 Jul 92 15:05:58 GMT
Organization: Miles, Inc.  Diagnostics Divis.

In article <1992Jul28.182905.6379@ifi.uio.no> janl@ifi.uio.no (Jan Nicolai Langfeldt) writes:
> 
> In article <1992Jul28.145636.6862@sura.net>, vargish@sura.net (Nick Vargish) writes:
> > -->3. I remember seeing a clue on how to disable the initial "Hit <ENTER>
> >    to see SVGA modes, any other key to continue" [sic.] messgae. 
> > 
> > I was told, "hack the kernel." Haven't done this yet, but I'm thinking
> > about it.
> 
> I used a hour the other day to first disable the "Hit <ENTER>"
> message/readkey then select the desired video mode correctly. All this
> happens in /usr/src/linux/boot/setup.S. Just search for "chsvga" and
> you'll find the relevant code. Note that the "getkey" routine is kinda
> weird and seem to return something related to scancodes...
> 
> Now, anyone want to colaborate on _understanding_ the vga mode
> selection process and write patches so mode can be configured in linux
> Makefile (like keyboard is configured)?

I did this a long time ago, but since it was never worked into the official
distribution, this question keeps popping up from time to time.  You should
be able to find svga_mode.patch on tsx-11, although it's been so long since
I've built a kernel that I wonder if the patch works anymore.

-- 
Dennis T. Flaherty     dennisf@Miles.com
Miles, Inc.            dflahert@chekov.helios.nd.edu
Diagnostics Division
My doctor says Mylanta, but my boss says Alka-Seltzer!
From: unixsys@ssg.com (Rick Emerson)
Subject: Re: RFD: comp.unix.* reorganization
Organization: System Support Group
Date: Tue, 21 Jul 1992 21:29:08 GMT

peter@taronga.com (Peter da Silva) writes:

> 
> It appears I've caused some distress with a comment I made on news.groups.
> Just to avoid further flames, let me repeat it emphasising one particular
> phrase that seems to have been underemphasised in the original:
> 
> >>Actually, I was going to suggest pulling comp.os.{minix,linux,coherent} int
> >>the comp.unix world, IF THAT'S OK WITH THE READERSHIP OF THOSE GROUPS. That
>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>because Unix isn't an operating system: it's a family of operating systems
> >>with a common core API... and as far as I'm concerned MINIX, LINUX, and
> >>Coherent *are* Unix.

As one who took some exception to the proposal, I consider it bad form to
even raise the topic in news.groups before raising it here (and on the other
groups, for that matter, but I don't read them so how can I comment on
that?).  In one area there are readers who're debating adding three new
flavors of unix to comp.unix.xxx while at least this newgroup hasn't even
decided about how (or *if) comp.os.linux should be partitioned.  
 
> Of course I wouldn't take any such proposal to the RFD stage without asking
> the people involved first. That means discussion in comp.os.linux, .minix,
> and .coherent.

Um, rather late in doing that, aren't you?  

What is gained by moving to comp.unix.linux?  I suppose there's a certain
amount of cachet in replacing .os. with .unix.  On the down side, the
readership has to adjust to a new group while monitoring the old group.  

Alt.bbs.waffle voted to move to comp.bbs.waffle and, despite the move to the
more "respectable" comp.xxx, alt.bbs.waffle still carries some traffic. 
Xxx.bbs.waffle on its best day carries perhaps 1/4 of the traffic here and
the move has caused problems.  

I don't see the justification for moving this newsgroup.  

Rick


| Richard B. Emerson     | Replies may be sent to:                         |
| System Support Group   |         unixsys@ssg.com  -or-  rick@ssg.com     |
| Post Office Box 180    |-------------------------------------------------+
| Lansdale, PA 19446 USA |     "If I knew what I was doing,                |
| Voice: 215.855.1607    |      I wouldn't do it." - Me                    |
From: djansa@aphrodite.cs.wisc.edu (Dean Jansa)
Newsgroups: comp.os.linux
Subject: SC - The Saga
Date: 31 Jul 92 15:15:17 GMT
Article-I.D.: spool.1992Jul31.151517.24836
Organization: University of Wisconsin, Madison -- Computer Sciences Dept.

Ok, Ok...  I got a great response to the sc project.  But, it turns
out I have a old version.  A few people mailed me and told me they
have it working for Linux.  So my response is:  I'll grab the new
release, I will not take out anything, just add Linux #ifdefs if
they are needed anywhere.

All those who have sc going, please share it with us.  A ton of people
want it, I didn't know I was beating a dead (ok, slow moving) horse.

Now, about that Dbase IV clone I was working on...... <grin>

Thanks,
Dean Jansa
Newsgroups: comp.os.linux
From: smace@nyx.cs.du.edu (Scott Mace)
Subject: acct logging for Linux?
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Fri, 31 Jul 92 01:05:45 GMT


Is there a way to do logging in /var/adm/acct for the linux kernel?
Also is there a way to log errors from the kernel?
Is there a way to enable logging in /var/adm/message?

Thanks,
Scott Mace
--
*********************************************************************
*    Scott Mace                internet:    smace@isis.cs.du.edu    *
*********************************************************************
Newsgroups: comp.os.linux
From: caffrey@salem.salem.ge.com
Subject: help with  Maxtor M7080S and ST01.
Reply-To: caffrey@salem.salem.ge.com
Organization: The Internet
Date: Thu, 30 Jul 1992 13:36:34 GMT

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

I just received a new Maxtor M7080S scsi disk and am unable to
get it to work. I am using an ST01 controller which I have been 
using for the past few months with a seagate ST157N with no problems
( except that it was slow ).

The Maxtor seems to work in MSDOG I can partition(FDISK) and format 
the disk. From DOS I set up a 50 and 30 mg partition.

During Boot up the ST01 reports that it finds a disk, but linux  
reports 0 Disks 0 tapes total.

Regards

Paul Caffrey
Newsgroups: comp.os.linux
From: corywest@rice.edu (Cory West)
Subject: An interesting discovery about boot devices.
Organization: Well, none really, but I know where my socks are!
Date: Wed, 22 Jul 1992 05:40:40 GMT


	I'm not sure if this is common knowledge, but I just
'discovered' it on my own a couple of days ago and I have been
reading this group and all related documentation for a good,
solid six weeks:

	If you set the major and minor numbers of your boot 
device to 0 0 in the kernel (I did with with a binary editor
at the proper offset), when Linux boots, it _asks_ you what
to use as a boot device.  This is handy because if you have a
tiny DOS partition and use BOOT.SYS and BOOTLIN, you can 
boot from floppy or hard disk without having two different kernel
image files around.

	Anyway, I just thought that was interesting and thought
someone else might find it useful.

P.S.  Since there's a way to set or not set your boot device major
and minor numbers, is there also a way to set the default video
mode so that the kernel doesn't ask you what video mode it should
use?  That would be handy for a totally autobooting kernel (with
shoelace or something like that) for those infrequent remote reboots.


			Cory West, corywest@rice.edu
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Newsgroups: comp.os.linux
Subject: Re: mtools, compiling problems
Date: 30 Jul 92 12:31:43 GMT
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH

In article <1992Jul29.233928.9415@muddcs.claremont.edu> jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) writes:
> Actually, got_signal is ifdef'ed out of some of the files, and I've
> never been able to get it to compile without removing the ifdef's.

Well, it's not that bad. You only have to remove the  static  from line 26,
static int got_signal();
in mmd.c. gcc 1.40 didn't complain about that, but gcc 2.2.2 is a bit
pickier (like almost any other cc too).

There are still lots of warnings, but they can be ignored.

- Werner

-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
Newsgroups: comp.os.linux
From: farrow@ucsu.Colorado.EDU (J. Scott Farrow)
Subject: Will X11 run with my Oak "Extended" VGA controller?
Reply-To: farrow@fido.Colorado.EDU
Organization: University of Colorado, Boulder
Date: Wed, 22 Jul 1992 16:07:15 GMT

from the X11 README.base v1.1
------------

Requirements
------------

o Super VGA card which contains one of the following chips:
        ET4000
        ET3000
        PVGA1
        GVGA
  Note: even though the provided documentation makes references to other
  chips, they are not supported in this release. The document was gleaned
  from a variety of sources, some of which were running commercial products.

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

My system has a builtin Oak "Extended" VGA controller that supports 800x600
and 1024x7?? modes. I have no idea which chip it uses - does anyone know
if X11 will work with this controller?

Thanks,

Scott



--
--------------------------------------------------------------------------------
J. Scott Farrow - Student Programmer/Operator, University of Colorado at Boulder
Computing and Network Services, Campus Box 455, Boulder, CO 80309-0455  USA 
InterNet: farrow@spot.colorado.edu, Phone: (303) 492-4428
Newsgroups: comp.os.linux
From: kenc@sol.acs.unt.edu (Ken Corey - Operator)
Subject: Gads
Organization: University of North Texas
Date: Wed, 22 Jul 1992 05:01:18 GMT

unixsys@ssg.com (Rick Emerson) writes:
>I dunno.  In my case, the problem went away on its own (which means I
>stopped doing some undefined stupid thing) and I've been bopping in and out
>of XWS all day without a complaint from my mouse on /dev/ttys0.  The modem
>on /dev/ttys1 has been working pretty well, too.  
>Maybe you have a hardware problem?  Have you checked to see what ports Linux
>finds on start-up?

Jeez.  I finally figured it out.  You know...it's just when you start to
think that you know what's going on when something knocks you on your bum...

Turns out that I had put a line in my inittab so that I could log into Linux
from my Macintosh.  The only REALLY bad thing was that I soon took a rather
long break from Linux after that, and forgot about it.  So, all this time
I've been putzing with trying to fix things, it turns out nothing was
broken...getty kept spawning itself at my ttys1 port, changing the speed to
9600 if I reduced it, duplicating characters sometimes, and stealing
characters other times.  (Yikes, how embarassing!)

If any newbies are reading this: the moral is check your inittabs...;)

I'd looked at 1/2 of the stuff in /etc, just not the proper half....

So, it WAS a hardware problem: Linux is okay, but there's a loose nut behind
the keyboard...*wink*

Thanks to those who tried to help.

Happy Linuxing!
From: ssarkar@almaak.usc.edu (Subrata Sarkar)
Newsgroups: comp.os.linux
Subject: Jgraph doth not work
Date: 30 Jul 1992 00:21:50 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: almaak.usc.edu

I installed the MCC interim release today.  Things are GREAT!
I grabbed jgraph.Z from princeton.edu (a sharfile).

It compiles ok.  On roughly half the example files, when jgraph
runs, he emits strange errors about parsing tokens.

Has someone made jgraph.  (Shudder) Does this mean something about
gcc is amiss?

Thanks,

	-Subrata

Newsgroups: comp.os.linux
From: haldane@dcs.warwick.ac.uk (Steve Sykes)
Subject: TCP/IP
Organization: Department of Computer Science, Warwick University, England
Date: Thu, 23 Jul 1992 01:34:36 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: janl@ifi.uio.no (Jan Nicolai Langfeldt)
Subject: .login, .profile bash and stuff (some answers) (Was: Minor problems with Linux)
Organization: Folkeaksjonen for (tungt) eple cider p} Inf. stua
Date: Mon, 27 Jul 1992 17:29:18 GMT
Originator: janl@maud.ifi.uio.no


This is actuall pieces of the bash man page:

Nicolai

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

--------------------
INVOCATION
     A login shell is one whose first character of argument  zero
     is a - , or one started with the -login flag.

     An interactive shell is one whose standard input and  output
     are   both   connected   to   terminals  (as  determined  by
     isatty(3)), or one started with the -i flag.  PS1 is set and
     $- includes i if bash is interactive, allowing a way to test
     this state from a shell script or a startup file.

     Login shells:
       On login:
             if /etc/profile exists, source it.

             if ~/.bash_profile exists, source it,
               else if ~/.bash_login exists, source it,
                 else if ~/.profile exists, source it.
       On logout:
             if ~/.bash_logout exists, source it.

     Non-login interactive shells:
       On startup:
             if ~/.bashrc exists, source it.

     Non-interactive shells:
       On startup:
             if the environment variable ENV is non-null, expand
          it and source the file it names.



FILES
     /bin/bash
          The bash executable
     /etc/profile
          The systemwide initialization file, executed for  login
          shells
     ~/.bash_profile
          The personal initialization file,  executed  for  login
          shells
     ~/.bashrc
          The individual per-interactive-shell startup file
     ~/.inputrc
          Individual Readline initialization file
From: rmk@rmkhome.UUCP (Rick Kelly)
Newsgroups: comp.os.linux
Subject: Re: BSD Unix aka Freedom is a myth....
Date: 24 Jul 92 04:52:00 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats

In article <1992Jul22.215906.10708@murdoch.acc.Virginia.EDU> lfoard@Turing.ORG (Lawrence C. Foard) writes:
>In article <1992Jul21.112705.6276@cs.cornell.edu> murthy@cs.cornell.edu (Chet Murthy) writes:
>>Y'know, Doug Comer's XINU, Linus Torvalds' Linux, Tanenbaum's Minix,
>>and I'm sure there are others, all stand as good arguments that the technology
>>if UNIX isn't just an AT&T invention anymore - the V sytem, Mach,
>>ad a zillin other ways of implementing the core of UNIX exist.
>>
>>I think that even if BSDI fails, even if 386BSD fails, and even
>>if the entire Berkeley net2 distrib gets nuked,
>>free unix is perhaps 2 years away - in 2 years, linux will be stable.
>>In two years, the GNU Hurd will be stable.  And AT&T can 
>>do almost nothing abot that, eh?
>
>I'm somewhat concerned about the possibility that some Linux developers
>might be familiar with AT&T code. For legal reasons it might be best
>to make sure that all Linux kernel code is developed by people with
>no prior experience with AT&T code.
>
>>But you're right - I'm pissed, too.  From what I heard of the history,
>>BSD started with V6 unix, a developed a _whole_ _lot_
>>of what currently constitutes UNIX.  To claim that AT&T did ti all is
>>goinga bit far.
>
>The unfortunite thing is that money makes right in court. Atleast Linux
>is an international effort and may be harder for AT&T to stop.


And when you consider how Linus has been tainted by the MINIX sources, then
consider that AST might be out hiring lawyers. :-) :-) :-)

Of course, Linus could then turn around and sue AST for attempted brain
damage. :-) :-) :-)

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Newsgroups: comp.os.linux
From: esaffle@gmuvax2.gmu.edu (Ed Saffle)
Subject: Re: Problem compiling the kernel.
Organization: George Mason University, Fairfax, Va.
Date: Tue, 21 Jul 1992 15:44:53 GMT

In article <1992Jul21.124846.2263@rhrk.uni-kl.de> herfert@arctecserv-1.informatik.uni-kl.de (Michael Herfert) writes:
>I use Linux 0.96c and GCC 2.2.2.
>Compilation of the kernel is succesfull but when running there come error messages like:
>  getwd: can not access parent directory
>Any help ?

This is the same kind of thing that happened when I first tried the linux
boot & root images after rawrite'ing then to disks...maybe if someone comes
up with an answer to this one, it would also be valid toward my problem.

ed
Newsgroups: comp.os.linux