HDTenEightyP/NetNews huggingface dataset:
From: chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko)
Subject: Re: [386BSD] Disklabel help and large drives (1.7 gig)
Organization: Technical University of Graz, Austria
Date: Fri, 11 Dec 92 18:02:46 GMT

In article <1992Dec10.171917.20431@decuac.dec.com> darryl@sai.com writes:
>
>I know this is a FAQ which I have read, but I can't seem to partition
>my disk to anything but the default.  What am I doing wrong?   Do
>I need a disktab entrie to match my disk, before disklabel will work?
>Does the partition relate to fdisk format?
>
I had this problem, too. The error message was something like 'partition
c extends past end of drive'. I simply gave disklabel a bigger number
of cilynders than is actually on drive, that cured the problem.
I think disklabel verifies that nsectors*ntracks*ncylinders >= nblocks,
which is wrong for some drives.
No, you don't need a disktab entry.
No, the disklabel has nothing to do with fdisk.
>
>Also does 386BSD have any problem supporting drives larger than 1 gig?
>
It seems so. I tried yesterday to hook up a 2 Gig disk and make a
filesystem on a 1.9 Gig partition. When I then mounted the partition
and copied some files over (dump | restore), it destroyed the file
system (root directory inode was mangled). The other partition was not
affected, so I guess there was some wraparound inside the partition.
This was with the Seagate ST01 SCSI driver.

							Christoph
-- 
.signature: No such file or directory
Newsgroups: comp.unix.bsd
From: ghelmer@dsuvax.dsu.edu (Guy Helmer)
Subject: AT&T StarLAN NIC driver?
Organization: Dakota State University
Date: Sun, 13 Dec 1992 17:23:27 GMT

I thought I remembered seeing an AT&T StarLAN driver go by a while ago,
but I didn't keep it and now I can't seem to find it on any of the 386bsd
ftp sites.  If it exists, could someone please send it to me?  Thanks.

-- 
Guy Helmer, Dakota State University Computing Services - ghelmer@dsuvax.dsu.edu

Newsgroups: comp.unix.bsd
From: veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: More on pccons/XFree86 problems (keyboard hangs)
Date: 14 Dec 92 14:41:31 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.fb9dv.uni-duisburg.de
NNTP-Posting-Host: du9ds3.fb9dv.uni-duisburg.de
Keywords: 386BSD X11 XFree86 console pccons

In <1992Dec14.115444.12691@news.tu-graz.ac.at> chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko) writes:

>In article <1992Dec13.172900.451@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>>  Try it out yourself, inside of an X window, do a :
>>
>>     kill -1 `cat /var/run/syslog.pid`
>>
>>  and your keyboard will lock up.
>>
>>
>>I will probably try and examine the stock pccons.c to determine where
>>the problem can be corrected... but if someone has an idea/fix, feel
>>free to beat me to it...
>>
[...correct explanation of the problem follows...]

In this moment, I have no access to my 386bsd system, but if the problem
occurs with codrv, there will be a fast fix for the current version.
However, I doubt, that the problem will occur exactly as described, because
codrv in X-Windows mode does not access the /dev/console device, like the
original pccons did, but an independent /dev/kbd, which cannot be locked
by closing. The effect of killing may influence the behavior of the shell
that started xinit, but there are some modifications in codrv which regenerate
the console attribute (TIOCCONS settable) and thus should not hang a
process on /dev/console. Anyway, I'll check it.

>I don't know if any of the replacement pccons (or codrv) drivers fix this.


>							Christoph
>-- 
>.signature: Connection timed out

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.fb9dv.uni-duisburg.de
|__|  /  University of Duisburg  |
|  | /   Dept. of Electr. Eng.   |          "Understand me correctly:
|  |/    Inst. f. Dataprocessing |     I'm NOT the WIZARD OF OS" (Holger)
From: julian@tfs.com (Julian Elischer)
Newsgroups: comp.unix.bsd
Subject: Re: boot string; boot & root floppy set (was Re: Occasional system hangs)
Date: 14 Dec 92 22:34:52 GMT
Organization: TRW Financial Systems

In article <Bz9MIu.8A3@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
>In article <1992Dec14.175811.8493@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>>Another useful approach (that would require full acceptance of Julians
>>boot blocks -- as in replacing the wdboot code as well) would be to
>>allow "arguments" on boot to the kernel, like "NOFPU" and "10BITIO" for
>>people with bad FPU's or single sigma 386's.  Of course this would also
>>require the ability to put these flags in a file somewhere so the
>>kernel could have them "on" by default.
>
>Yeah, SCO has gotten a lot of mileage out of their "boot string" and the
>ability to type in command options at boot time, like to select the
>default tape drive, boot into a certain mode, boot a different kernel,
>and so forth.
>
the new bootblocks allow the use of boot modes and differnet drves, kernels etc.

>Another useful thing would be to have a "boot and root" floppy set, where
>booting would pull the kernel off of one floppy but then pause for you to
>insert a second floppy with the "real" root filesystem on it.  It would 
>free up about 400K on the floppy for more useful programs, if it wouldn't 
>be too hard to do.

The new boot blocks also support this too. They only do it if they think
you are booting off a floppy though. (may be commented out on some versions)

>-- 
>-- Email info@NeoSoft.com for info on getting interactive Internet access.
>"Turn on your hot tub by email now.  Ask me how."

julian
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v
Newsgroups: comp.unix.bsd
From: cdillon@muse.cs.mu.OZ.AU (Craig Dillon)
Subject: Floppies and swap
Summary: I *really* need some help...
Keywords: Floppies and Swap
Organization: Computer Science, University of Melbourne, Australia
Date: Tue, 15 Dec 1992 08:31:39 GMT

Hi All, vegie problem stations again.

I got XFree86 working, but now have had absolutely no luck in either
of the following two:

(1)     Getting a swap partition set up (I am from System V, so have
	not a clue about BSD). Swapon bewilders me and I have played
	around with fdisk and mount and /etc/fstab alot to no avail.

(2)     Making floppies writeable. mount -u /dev/fd0a doesn't work.

Also, what purpose is the fixit disk?

Anyway, would love some help from someone who knows. 386BSD is great,
just not all that wonderful for people who aren't super-gurus to
begin with.

Cheers,
Craig.

Newsgroups: comp.unix.bsd
From: ashley@gidday.enet.dec.com (STEPHEN ASHLEY)
Subject: 386bsd how2 get modem 2 dial
Organization: Digital Equipment Corporation
Date: 18 DEC 92 16:08:05 AES


	Help Help Help.

I have got 386bsd up with the bin01 and etc01 stuff loaded
ok. The problem is with tip, I have got Terrys hint and tips
and it states that if tip has a problem then you need to
recompile tip. How do I get my modem to dial with out tip?
Cos I have to get to the server system to get the src01
stuff down to patch and recompile tip!! 

It appears I'm in a "catch 22" can't do one with out the
other. The only other soution is to dial out from the
server system to my machine and try to uucp the src01 down
that way. I would prefer not to do this and would like to
hear any other soutions net can offer.

Email your replies please.

	Thanks
Stephen Ashley,
Alice Springs Out Back Australia.

Newsgroups: comp.unix.bsd
From: gtoal@ibmpcug.co.uk (Graham Toal)
Subject: Re: tip & screen
Organization: The IBM PC User Group, UK.
Date: Mon, 14 Dec 1992 01:53:58 GMT

In article <tlukka.724239227@snakemail.hut.fi> tlukka@lk-hp-8.hut.fi (Tuomas J. Lukka) writes:
>Has anyone hacked screen to work on 386BSD? I get it to compile
>but have not yet gotten it to actually work.

Yes, there's a working copy (I'm using it now) on rachel.ibmpcug.co.uk
in /usr/local/src

G
-- 
Newsgroups: comp.unix.bsd
From: hackney@moxie.hou.tx.us (Greg Hackney)
Subject: Re: 386BSD - Bug in UFS file system + proposed fix
Organization: Home
Date: Thu, 17 Dec 1992 14:01:23 GMT

terry@cs.weber.edu (A Wizard of Earth C) writes:

> This fix seems a bad thing.

The fix we proposed for ufs_vnops.c, is identical to 386BSD's sister code
residing in nfs_vnops.c. I'm not sure why ufs_vnops.c got changed to
something different.

> In particular, you *don't* want to allow a
> file which is world read or world execute to be read/executed by someone
> who is a member of a group denied access.

Did you try the code? On my system, group denied access works properly.

> Perhaps the reason you are having NFS problems is because unknown users
> and root users from a remote system are translate to UID -1 and -2 unless
> you specify that root access is allowed on the remote machine in the
> /etc/exports file

Nope. The 2 systems are identical stock 386BSD systems with identical
password files. We've tried /etc/exports with and without root=0.

> (your example seems to indicate you were logged in as
> root when you tried this).

Nope. We've tried all sorts of logins.

>Admittedly, there are some permission comparison problems, but these are
>pretty well isolated, and will probably be more tha a one or two line fix.

If no one else is having these (major) permissions problems when
using NFS across 2 386BSD systems, then we need to go back and dig
deeper into why the modes aren't working. Are you saying that it works
properly for you?
--
Greg Hackney

Newsgroups: comp.unix.bsd
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: 386BSD install program - where is it?
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Fri, 18 Dec 1992 16:38:42 GMT

In article <1992Dec17.134832.9812@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes:
>gab10@griffincd.amdahl.com (Gary A Browning) writes:
  [ someone ask ]
>>> Where is the source code located for the 'install' program that's on
>>> the
>>> 386BSD dist.fs floppy?

>>The source for it was never released.

>I wonder why? It sure would be nice to have to make a customized
>installation process!

It would be particularly useful when running into install problems, 
as I did last week when playing with my new RLL card. Wierdly enough,
the size of the drive affected whether or not INSTALL would work...
It locked up on the larger drive (Micropolis 1325, about 100M RLL) but
worked OK on the smaller (Qume 540, ~48MB RLL). Having source, or an
install script instead of executable, would have made life easier. 

(Yes, I did finally get the larger drive booting, but most of the /dev
entries were missing, and some directories and permissions were missing.
And rogue still fails to update the score file. :-) )

-- 
Gary Heston    SCI Systems, Inc.  gary@sci34hub.sci.com   site admin
The Chairman of the Board and the CFO speak for SCI. I'm neither.
"Data sheet: HSN-3000 Nuclear Event Detector. The [NED] senses the gamma
radiation pulse [from a] nuclear weapon." As if we wouldn't notice...
Newsgroups: comp.unix.bsd
From: rp@llex.ll.mit.edu ( Richard Pavelle)
Subject: Emacs will not load on one machine in cluster
Originator: rp@llex
Organization: MIT Lincoln Laboratory
Date: Mon, 14 Dec 92 22:21:22 GMT


About a week ago local domain name changes were made on our
Sparc cluster (we are running SunOS Release 4.1.1).
Since that time I am unable to run emacs on one particular
machine, the others are ok. When I try to load emacs I lose
all response to the operating system. No command works and I
must get back to the terminal concentrator and start over.

I have checked in my .login and .cshrc and see nothing odd.
I disabled my .emacs and still have the problem.

I am not very familiar with unix so if you have a suggestion
please take this into account. Of course, it may not be a 
unix problem.

 
Xref: sparky comp.unix.bsd:10443 comp.os.linux:21119
From: davis@csrg2.ee.iastate.edu (Jim Davis)
Subject: 386BSD vs Linux: major differences?
Organization: Iowa State University, Ames IA
Date: Sun, 20 Dec 1992 02:17:43 GMT

Although I use UNIX at work everyday, I am interested in tinkering with
UNIX at home.  It seems like 386BSD or Linux would fit my modest needs.
I have been reading comp.unix.bsd and comp.os.linux for about a month; 
both groups seem to be very active and doing an excellent job of 
porting software and providing support to users.  But I have wondered
why there are two efforts to provide a free UNIX...is it just coincidence
that two groups developed a distribution at about the same time?  or did
they have different goals?  or is this a BSD vs. System-V thing?
Without starting a flame war or anything like that, I would appreciate
hearing about the major differences between BSD and Linux.

"thanks in advance"

Jim Davis
davis@iastate.edu


Newsgroups: comp.unix.bsd
From: amurai@specgw.spec.co.jp (Atsushi MURAI)
Newsgroups: comp.unix.bsd
Subject: Re: Help installing from 3.5 inch a: drive
Date: 9 Dec 92 04:02:40 GMT
Organization: System Planning and Engineering Corp., Tokyo, Japan
X-Newsreader: Tin 1.1 PL5


Don Osburn (dosburn@cwis.unomaha.edu) wrote:
: 
: This is a repost of a request for help that apparently got fluked by 
: the mail system.  I did a binary download of the dist.fs and fixit.fs
: binary image, and the rawrite.exe program to my c: drive.  Then I used
: rawrite to write the dist.fs image to a 3.5 inch floppy to attempt an
: install.  (My a: drive is 3.5 inch.)  When I booted the system with the
: disk, it just hangs with the a: drive spinning infinitely.  ( I waited 
: about 10 minutes.)  After some discussion, I have come to the conclusion
: that the image will only work on 5.25 inch media, and that this must be
: the boot drive.  IS THIS CORRECT, and if so, does anyone know where I
: can get an image for 3.5 inch media, or must I change the cabling to 
: install.  My system is a Tandon 80386SX with 4MB memory, and 105MB hard
: drive.  It is pretty much a standard intel pc, (at least so far.)  If
: anyone can offer assistance on installing the system I would greatly
: appreciate it. :-)  Thanks in advance.
: Don

No. Even My PC setup 3.5inch for A drive and 5.25inch for B drive, 
I can boot up [fixit|dist].fs without problem.
I suspect you might need to check BIOS setup, setup of dip switch of
Drive for Drive number and cable.

Good luck.

Atsushi Murai

-- 
$@B<0f!!=_(J (Atsushi Murai)                              Junet : amurai@spec.co.jp
SPEC                                                  Voice : (03)3833-5341
System Planning and Engineering Corp.
Newsgroups: comp.unix.bsd
From: pierson@midas.mgmt.purdue.edu (Brian Pierson)
Subject: LP setup question
Date: Tue, 15 Dec 1992 19:36:54 GMT
Distribution: NA
Organization: Purdue School of Management


Hello,

	I have just acquired a IBM proprinter for my 386BSD system. On 
startup, the system sees the printer on the parallel port but it
says that /dev/lp does not exist. I realize that I have to make 
the node so here is my questions:

1 What major,minor numbers should I be using for it? I could not 
find the numbers in the source.

2 Does any one have a printcap for the proprinter? I think I would
like to experiment with it but would like a fall back.

Any help will be useful thanks
 
Brian Pierson
pierson@midas.mgmt.purude.edu
From: scm@aiware.in-berlin.de (Harald Schmidt)
Newsgroups: comp.unix.bsd
Subject: [386bsd] login via modem (problem with gettytab/ttys)
Summary: 386bsd
Keywords: login
Date: 20 Dec 92 11:43:55 GMT
Organization: AIware

Hallihallo,

I got so many problems logging in via modem. If I dial the number,
the modem answers the correct string, but there is no login (hmm...).

My simple question is: can anybody send me the right entries for
all these config files (gettytab/tty/termcap??) and a few tips?

BTW: I would like to use the line for both login and uucp.

Thanks in advance and MC/HNY,

	Harald
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.unix.bsd
Subject: WD8003E ethernet card compatibility
Date: 16 Dec 1992 19:15:08 -0800
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: neuro.usc.edu
Keywords: AKCL Common LISP Kyoto Austin 386BSD

Has anyone managed to get 386BSD to work correctly with the WD8003E ethernet
card?  I ultimately gave up on using this card for my development machine many
months ago and bought an SMC/WD Elite16 Combo card instead which worked fine.
However, I have several machines with the old WD8003E card available at USC &
I'd like to be able to put 386BSD up on those machines using the WD8003E as a
primary network interface.  Are the WD8003E cards working with 386BSD + patch
now -- or are they still error prone?

Thanks, AJ

------------------------------------------------------------------------------
Alexander-James Annala
Principal Investigator
Neuroscience Image Analysis Network
HEDCO Neuroscience Building, Fifth Floor
University of Southern California
University Park
Los Angeles, CA 90089-2520
------------------------------------------------------------------------------

Newsgroups: comp.unix.bsd
From: deraadt@newt.cuc.ab.ca (Theo de Raadt)
Subject: Re: Almost Free Symbolic Links (source code)
Organization: little lizard city
Date: Thu, 17 Dec 1992 19:52:57 GMT

In article <id.J2UV.H5K@ferranti.com> peter@ferranti.com (peter da silva) writes:
   In article <39777@hoptoad.uucp> curt@hoptoad.uucp (Curt Mayer) writes:
   > this cruddy but complete hack answers one of the objections to symlinks:
   > that they are slow, and cost an entire frag. symlinks of less than length
   > 60 are stored in the inode itself.

   How about generalizing this to put ALL files < 60 bytes in the inode, not
   just symlinks?

Because it screws up the alignment all the way through the file. It's nice
to know that going a multiple of st.st_blocksize into the file and reading
a multiple of st.st_blocksize bytes is going to be faster.
 <tdr.
--

This space not left unintentionally unblank.		deraadt@newt.cuc.ab.ca
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Dumb Question: Why 512 byte block?
Organization: Weber State University  (Ogden, UT)
Date: Fri, 18 Dec 92 23:56:23 GMT

In article <1gt736INNjje@menudo.uh.edu> wjin@cs.uh.edu (W. Woody Jin) writes:
>In article <1992Dec18.030833.7395@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>>In article <1992Dec18.005050.20594@decuac.dec.com>, darryl@vfofu1.dco.dec.com (Darryl Wagoner) writes:
>>|> Why is everything in 1/2 k block instead the BSD standard of 1024 byte blocks?
[ ... ]
>>
>>If I have a set of 6 512 byte files, I will use up 3K of disk for them;
>>similarly, if I had a blocking factor of 1K, I would use of 6K (since the
>>smallest fragment usable by a file is now 1K.
>>
>>If I have 6 1.5K files, this translates to 9K of disk(512B) or 12K of disk(1K).
>>Obviously, if I have 6 1.6K files, both blocking factors take up 512K.
>
>I did not think that Fast Unix File System works this way.
>If you have 6 1.5K files using 1K blocks,
>   6 1k blocks will take each 1K from each file, and 
>   3 1k blocks will take 0.5k from each file.
>This was my understading from the famous FUFS paper.

You can't split blocks between files.  A block is, by definition, the
smallest possible allocation unit.  Thin about the case where you have
a 1 byte file and a 1 block - 1 byte file; what would you do when
adding one or two characters to the first (1 Byte)?  TReallocate?  Shift
and reallocate for the last byte of the second file?

But... you're right that it doesn't work the way I've shown... thought
for sure I'd get bombarded on this one:
>>Obviously, if I have 6 1.6K files, both blocking factors take up 512K.
should have read:
>>Obviously, if I have 6 1.6K files, both blocking factors take up 12K.

1.6K rounded to a both a 512b and 1K boundry is 2K, and 2k * 6 = 12k.

>>When you store a lot of little files on the disk, small blocks are wasteful
>>of disk space (for instance, 1024 empty files take 512K vs 1M of disk for
>>the smaller blocking factor).
>
>And choosing a disk block size is a performance issue rather than
>disk space issue. One should tune disk block size and fragment size
>to get the best performance.
>
>I thought that 386BSD uses this Fast Unix File System.

Consider the most ridiculous possible situation:  I have a 1G disk with
a 1G blocking factor (impossible without rewriting the buffering code).

How many files can I have on the disk? (Ignore the blocks allocated to inodes
and directoryies 8-P).

The answer is "1"... even if it only has 1 byte in it.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: tempel@sun490.fdu.edu (Philippe N. Tempel)
Newsgroups: comp.unix.bsd
Subject: Can't find the /dev/lp* files in 386BSD 0.1
Keywords: 386BSD /dev/lp
Date: 15 Dec 92 00:05:00 GMT
Organization: Fairleigh Dickinson University

The man page for lpd states that there should be /dev/lp* files.  I can't
find these at all.  Where can I get these?  It would be nice to print
things out once in a while...

Thanks,
Philippe
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: [386bsd] InterViews is available
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: comp.unix.bsd
Date: Sun, 13 Dec 1992 22:22:46 GMT

date: 12/13/92

	InterViews for 386bsd

As part of the 386bsd Desktop project, I have ported InterViews, an X-windows
object oriented package, which includes a graphical user interface
builder, a mac-draw like drawing program, a what-you-is-what-you-get
document preparation program and other features is now available for 386bsd.
man pages as well as documents which explain InterViews are included in
the package.

gcc-2.3.2 is required to compile ibuild generated programs or programs
which use the InterViews API. However gcc-2.3.3 is not reguired to run
InterViews' programs.

Hopefully, ibuild will pave the way for non-window experts to write X-oriented
applications. The traditional hello program took less than 15 minutes to create
with ibuild.

To install:

(1) tar iv-int.tar to a directory

(2) make soft link /usr/packages/iv3.1.3 to point to ../iv/installed
	(ln -s ../iv/installed /usr/packages/iv3.1.3)

(3) copy ../iv/installed/lib/all/app-defaults/* 
	to /usr/X386/lib/X11/app-defaults/


	----you are done----



Questions relating to InterViews should be posted to comp.windows.interviews.

InterViews is available at:

	sunvis.rtpnc.epa.gov:/pub/386bsd/incoming/iv-inst.tar.Z
	ref.tfs.com:/usr/othersrc/iv-hasty/iv//iv-inst.tar.Z


***Patches to build InterViews will be available soon.***

Any help in supporting or expanding InterViews will be appreciated!

InterViews is known to work with XFree86 and XS3 with twm. Although,
I don't expect any problems, InterViews has not been tested with olwm or gwm.


Credits:

Rich Murphey	from the XFree86 core team, provided the configuration 
		patches for InterViews

Julian Elischer allowed me to build InterViews on ref

Doug Rabson	provided the patches which allowed doc to work


Enjoy,
Amancio Hasty



-- 
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/incoming
Newsgroups: comp.unix.bsd