HDTenEightyP/NetNews huggingface dataset:
From: wang@saturn.sdsu.edu (Luqing Wang)
Newsgroups: comp.unix.wizards
Subject: ??? about i-nodes and file system
Date: 22 Aug 92 16:42:16 GMT
Organization: San Diego State University, College of Sciences
X-Newsreader: Tin 1.1 PL5

Dear netters,

Right now I am worrking on a project which require to deal with a file's
disk block number directly. Is there any existing system calls which can
get a file inode structure, and the disk blocks allocated to a file?

I did this using ram i/o(treat disk as a file); First get the inode number 
of the file, then compute  the disk absolute address of the inode, then
read in the disk inode structrre. From the inode , one can easily find the 
disk block allocateion. However, this method has a deadly drawback, it
totally bypassed the unix file system, if the kernel has not write the 
recnet change of the file's inode information to disk, the program will 
get wrong infromation.

Any idea to get around this ?  Or is there a way to force the unix OS to
write all bufferd information(inodes information) to disk? I tried to use
sync from console, it does not work. Only thing I found worked so far is 
to shutdown the system, then reboot, this will force the system write most 
recent change to the disk. Obvious I can not do this in a program.

I am working SUN OS4.1

Any suggestionis highly appreciated.

Luqing



--
  .-.  ^^*^^        ;;;_         ||     %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
 ( o )             ~~&_/~*       ||       San Diego State University
;.   &   \     _ *___~.~.~. ^ __ ||     Internet: wang@saturn.sdsu.edu
Y/  $$$  \&/  _-_-_- _-==- ***  - +++   ||||||||||||||||||||||||||||||| 
Newsgroups: comp.unix.wizards
From: pooh@corner.asd.sgi.com (Drew Olbrich)
Subject: Re: CMU Coke Machine [Re: Torek a hack? [Re: What must I learn...]]
Reply-To: pooh@corner.asd.sgi.com (Drew Olbrich)
Organization: sgi
Date: Mon, 17 Aug 1992 23:01:31 GMT

pds@lemming.webo.dg.com (Paul D. Smith) writes:

> However, the machine was in the grad CS lab as I mentioned yesterday;
> you needed a special key (or a friendship with someone with such a key
> :) to get in.  For a while they also had an M&M machine in there which
> distributed a huge handful of M&M's for $.10.

I am happy to report that the M&M machine is still functional.
It still costs ten cents, too.

Drew Olbrich
pooh@corner.asd.sgi.com
Newsgroups: comp.unix.wizards,comp.unix.bsd
From: gray@pecan.cns.udel.edu (Scott Gray)
Subject: Re: Have $8000, what to buy?
Organization: University of Delaware, Newark
Distribution: comp
Date: Wed, 12 Aug 1992 02:26:54 GMT


>I want a Unix machine.  Now.
>
>I want BSD features.  I want full networking.  I want X11R5.  I want color.  I
>want at least 1.2Gb of disk, and 16Mb of memory.  I have $8000, and won't be
>able to add much more for at least a year.
>
>I may qualify for Sun's developer discount.  I'm willing to go 3rd party for peripherals.
>
>What should I buy?  Sparc IPC?  Iris Indigo?  A HP?  A PC (shudder) with BSDI?
>A NeXT?  A Mac with A/UX?  I only know that I can pick up an IPC for about
>$5000 after discount, and then use $3000 for buying peripherals.  Who else has
>deals like that?
>
>Personality features:  I want a programmer-friendly machine, (i.e. doesn't
>have to be user-friendly.)  I like machines with nifty goo-gaws like sound.  I
>want something I can grab stuff off then net and build with minimum headache.
>I want something reliable.
>
>Enlighten me.

After having didled with several versions of unix/hardware I will warn you
that you really have to be careful when looking at something like and
HP or Sparc, there are a lot of hidden costs.

For example, if you want to get HP-UX (which, by the way, I like quite a bit)
you also have to pay for software maintenance in order to get the upgrades,
patches, etc.  I don't know if there are personal discounts for the
average joe, but I do know that for a company this can be several thousand
dollars a year.  Also, if you are thinking HP with VUE, keep in mind that
VUE does not run very well at all in 16MB of memory, you really need around
32MB, and that stuff ain't cheap.

Personally, I would go with a really killer pc, such as a 50Mhz EISA 486
with lots-o-memory and a monster harddrive.  386BSD is pretty cool and
really does perform relatively well (especially in comparison to AU/X).
And don't forget a really fast graphics adapter with lots-o-memory as well.

Hope this helped...
Later,
	Scott
-- 
-------------------------------------------------------------------
                          It is accomplished
-------------------------------------------------------------------
From: dymm@gofish.NoSubdomain.NoDomain (David Dymm)
Newsgroups: comp.unix.wizards
Subject: AFS, Unix, and Unix Security Training
Keywords: AFS Unix Security Training
Date: 19 Aug 92 20:56:56 GMT

Folks, I would like some information on formal training in
the following areas:

1)  Unix security

2)  Unix internals

3)  AFS ingternals (Transarc has only a beginning course)

Any help that you could give me would be greatly appreciated.


    david dymm

    dymm@cards.com
    304 367-0770

    EWA
    1401 Country Club Road
    Fairmont, WV  26554
Newsgroups: comp.unix.wizards
From: chrism@col.hp.com (Chris Magnuson)
Subject: BOOKS FOR SALE!!
Date: Sat, 15 Aug 1992 16:50:51 GMT
Organization: HP Colorado Springs Division


   What follows is a list of more books for sale.  Terms are the same as before,
shipping is $4 additional, books are hardcover (unless noted), etc.  Best
offer, etc.

   Topics include electronics, DSP (digital signal processing), software
engineering, computer languages and data structures, and realtime
programming.

Chris Magnuson
chrism@col.hp.com
Software Engineer
Hewlett-Packard


*************************
Digital Signal Processing
*************************

  Theory and Application of Digital Signal Processing, Rabiner and Gold, ISBN
0-13-914101-4, 762 pages, $20.


******************
Software/Languages
******************

  A Book on C, Kelley and Pohl, ISBN 0-8053-6860-4, 362 pages, $8 (softcover).
  "Good beginning-intermediate C programming text."

  Compiler Design in C, Holub, ISBN 0-13-155045-4, 924 pages, $30.
  "Good implementation book on compiler writing and theory."

  Data Structures Using Pascal, Tenenbaum and Augenstein, Second Edition, 
ISBN 0-13-196668-5, 774 pages, $20.
  "The most used book on dta structures at the university level."

  Structured Design, Yourdon and Constantine, ISBN 0-13-854421-9, 473 pages,
$15.
  "The classic software design text."

  An Implementation Guide to Real-Time Programming, Ripps, ISBN 0-13-451873-X,
262 pages, $15.
  "Just like it says...implementation-oriented realtime book."

  Software Engineering: A Practitioner's Approach, Second Edition, Pressman,
   ISBN 0-07-050783-X, 567 pages, $13.
  "I hate to part with this one...McCabe/Halstead/metrics, data flow and
   design...just about everything you can think of including object-oriented
   design."

***********
Electronics
***********

  Circuit Theory Fundamentals and Applications, Budak, ISBN 0-13-133975-3,
590 pages, $10.
  "The best book there is for learning circuit theory from."

  Illustrated Encyclopedic Dictionary of Electronics, Douglas-Young, ISBN
0-13-450791-6, 606 pages, $10.
  " Good reference."

  Basic Electronics, Grob, Third Edition, ISBN 07-024917-2, 763 pages, $5.
  "Has a variety of topics, including tubes!"

  Electronic Devices and Circuits: Discrete and Integrated, Ghausi, ISBN
0-03-062481-9, 808 pages, $10.
  "Hot book on designing electronic circuits, from diodes through
   op-amps."

  Micro-Electronic Circuits, Sedra and Smith, ISBN 0-03-056729-7, 927 pages,
$15.
  "Another hot book...diodes, op-amps, FETs, transistors, etc."
  
  Analog-Digital Conversion Handbook, Third Edition, Sheingold, Ed., ISBN
  0-13-032848-0, 670+ pages, $10.
  "Want to know how analog-digital and digital-analog conversion works?"

  Microprocessor Architecture, Programming, and Applications, Gaonkar,
ISBN 0675-201594-05, 655+ pages, $10.
  "Designing with microprocessors is very 90's-ish."

  Analysis and Design of Analog Integrated Circuits , Second Edition, Gray
   and Meyer, ISBN 0-471-87493-0, 771 pages, $15.
  "Transistors, diff amps, op-amp stages, FETs..."

Newsgroups: comp.unix.wizards
From: bazyar@teal.csn.org (Jawaid Bazyar)
Subject: Re: cd'ing to a dir from a process & staying there
Organization: Colorado SuperNet, Inc.
Date: Thu, 20 Aug 1992 16:51:07 GMT

mpalmer@encore.com (Mike Palmer) writes:

>I have a ksh solution using an alias, a script & the program, but I'd like
>to do it just with a program, or at least a script & program than will work
>under csh & ksh.

  This solution is probably the easiest.  Unix separates process protection
information on purpose, and things like this unfortunately violate that,
at least in the way that micro programmers are used to.

  Under csh you can have an alias:
alias ncd cd `program`

  No script required.
I don't know about ksh (never used it voluntarily).

  The other thing to do would be to do some kernel work to not only handle
more than one cwd (perhaps 8 or 16? They're very useful in GS/OS) but
to provide specific means for children to pass changed prefixes back to
their parents.  However, this starts moving Unix into the world of
"Big Government/Liberal" operating systems. Hmm.

-- 
 Jawaid Bazyar              |   Ask me about the GNO Multitasking Environment
 Procyon, Inc.              |   for the Apple IIgs!   
 bazyar@cs.uiuc.edu         |   P.O Box 620334
 --Apple II Forever!--      |   Littleton, CO 80162-0334   (303) 933-4649
From: hayhurb@cards.com (Brett Hayhurst)
Newsgroups: comp.unix.wizards
Subject: TEST
Date: 21 Aug 92 16:50:20 GMT

This is a test.
Newsgroups: comp.unix.wizards
From: fitzgb@mml0.meche.rpi.edu (Brian Fitzgerald)
Subject: Intro to comp.unix.wizards - read before posting! (weekly announcement, last change: Jul 31 10:30)
Followup-To: poster
Organization: Rensselaer Polytechnic Institute, Troy NY
Date: Sun, 16 Aug 1992 10:00:36 GMT
Expires: Tue, 15 Sep 1992 10:00:22 GMT

Please take a moment to read this before posting to comp.unix.wizards
for the first time.

comp.unix.wizards is for in-depth discussion of advanced unix topics.

Elementary questions do not belong in comp.unix.wizards.  Although some
socket questions (for example) are appropriate, "How do I program with
sockets?" is not.

Crossposting to comp.unix.wizards and comp.unix.questions is
inappropriate.  Plenty of wizards read comp.unix.questions and answer
questions there.

A wizard is someone who can rewrite the entire system from scratch.  If
you are not a wizard, you are welcome to follow along the discussions
anyway.  You'll learn quite a bit about how UNIX works.  Caution: post
to wizards only if you are yourself a wizard.

For a list of answers to frequently asked questions (FAQ), please refer
to comp.unix.questions (or comp.lang.c, news.answers, etc...).  "How do
I delete a file whose name starts with a '-' ?" is an example of such a
question.  Please do not ask or answer FAQ's on the net.

Write to Unix-Wizards-Request@BRL.MIL (Subject: subscribe.  Any
message.) if you want a daily digest of this newsgroup mailed to you.

To unsubscribe from the unix-wizards mailing list, send mail to
Unix-Wizards-Request@BRL.MIL Subject: unsubscribe.  It is incorrect to
post such requests to the list, or to mail them to me, though others
may mistakenly do so.

E-mail comments about this posting are welcome.  From time to time I'll
summarize them.

Brian
--
These opinions are mine, and do not necessarily reflect those of any
academic department or computing service at Rensselaer.
Newsgroups: comp.unix.wizards
From: mpalmer@encore.com (Mike Palmer)
Subject: cd'ing to a dir from a process & staying there
Date: Thu, 20 Aug 1992 12:34:46 GMT
Organization: Encore Computer Corporation

Can anyone suggest a way for a process to cd to a dir & stay there when the \
process exits.

I have a ksh solution using an alias, a script & the program, but I'd like
to do it just with a program, or at least a script & program than will work
under csh & ksh.

Any ideas gratefully accepted.
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.wizards
Subject: Re: flock(2) emulation?
Date: 15 Aug 92 00:06:21 GMT
Organization: Auspex Systems, Santa Clara

>If I recall the history correctly:

Not completely.

>first was lockf(3) - a library that provided advisory record locking.
>Then it was rolled into the OS

(Presumably meaning "rolled into the kernel"; the kernel isn't all there
is to the OS....)

Actually, the original "lockf()" *was* in the kernel.

> as flock(2),

"flock()" was a *separate* locking mechanism, which showed up in 4.2BSD
(maybe earlier; I don't know if Berkeley invented it or not).

>and lockf(3) became simply calls to flock.

It sounds as if you're thinking of System V-style locking with
"fcntl()"; AT&T put that in some SVR2-vintage release, and made
"lockf()" a library routine wrapped around it.

>This enabled manditory record locking
>(write(2) returns EAGAIN or blocks if it would overwrite a locked
>region of the file).

The "lockf()" implementation by John Bass (which was, I think, the first
one; published in an issue of ";login:", as I remember) had mandatory
record locking - it was, I think, the *only* kind of locking it had. 
Other byte-span locking implementations may have done only advisory
locking, or have done both (the AT&T "fcntl()" locking did both).

>As mentioned in this newsgroup, the library probably kept a file
>containing
>- the file being locked (by major number/minor number/inode)
>- the region locked and the PID
>that way, all processes can access the global file and
>inspect each other's locks.

Nope.  The original implementation kept such a database, but it kept it
in the kernel, rather than in a file.

>The problem with advisory record locking is that a 'rude'
>program that doesn't respect the locking can destroy the file.
>Manditory record locking (having a file with the "get GID bit" set)
>enforces the lock by blocking writes on locked portions.

The problem with mandatory record locking is that a "rude" program can
lock a file and never unlock it; for example, it could stick a read lock
on, say, "/etc/passwd" and hang onto it forever.  That's why it's not
the default....

Many OSes offer, from what I can tell, only advisory locking;
admittedly, they're OSes not used much for commercial data processing,
such as IBM's MVS and VMS. :-)

In other words, the lack of mandatory record locking isn't necessarily
crippling; OS/360 and successors seem to have gotten along without it. 
Of course, in those OSes, those files that require locks are generally
accessed through a library that does the locking for you, so you
probably have to do a lot more work to write such a rude program.

Frankly, if there's some UNIX programmer who can't manage to get locking
right, I wouldn't trust them to access such a file *except* through e.g. 
some ISAM package; said package would, presumably, not only manage the
index, etc., better than said programmer's code could, it would also
manage locks better than their code could.

As I remember, AT&T's documentation recommends *against* using mandatory
locking....
Newsgroups: comp.unix.wizards
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: csh bashing
Organization: Weber State University  (Ogden, UT)
Date: Fri, 14 Aug 92 06:39:47 GMT

In article <1992Aug13.043302.9796@news.acns.nwu.edu> navarra@casbah.acns.nwu.edu (John Navarra) writes:
>In article <BswF58.17C@csfb1.fir.fbc.com> uunet!csfb1!jbrock writes:
>>Seriously.  It's nice to know which tools knowledgeable people respect
>>and which they don't.  But what about ksh?  It's hardly figured in
>>the proceedings and I'm feeling left out!  Is it worthy?  Considered
>>harmful?  Beneath consideration?
>
>	It's not that we aren't considering ksh, but that we are arguing
>over the merits of programming in csh vs NOT programming in csh.

If this is literal (which I rather think it isn't), then, as opposed to what
I might answer for "programming in csh vs programming in *anything but* chs",
I'd have to say that programming in csh was much better than not programming,
but it certainly wouldn't be my first choice.  8-).


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
Newsgroups: comp.unix.wizards
From: thf@zelator.in-berlin.de (Thomas Funke)
Subject: Re: Have $8000, what to buy?
Reply-To: thf@zelator.in-berlin.de (Thomas Funke)
Organization: NNU Corp. - NeXT is Not UN*X
Date: Sun, 16 Aug 1992 11:12:28 GMT

In article <1992Aug11.164928.2658@tfs.com> paigen@tfs.com (David Paigen)  
writes:
> 
> Stay away from A/UX. It is slow (or used to be) and not really BSD. Ditto
> for the NeXT, a flashy machine for users, an "insanity machine" for
> seasoned unix people.  Doesn't even pretend to be real unix.  HP-UX is

That's a very superficial comment which is totally false. I'm doing  
development for "traditional" unix-machines (AIX/DEC/Sun/Siemens) and use  
NeXT for cross-development, just because it gives you much less headaches  
than the others. NeXT gives you a BSD-System. You can also have X/Motif if  
you have to use it for your target platform. It's stable and FAST,  
(compilations 30-50% faster than RS6000/320 for example, even if the latter  
has the double amount of "MIPS"). Sure, you can't use all that great SW  
which NeXT gives you for free, like a great Interface-Builder, if you want  
to be "compatible". Nevertheless, almost all available free/PD-Software can  
easily be installed on NeXT, too. 

-- 
------------------------------------------------------------------
Thomas Funke  ** E-mail: thf@zelator.in-berlin.de
NeXT-Developer * Unix-Consultant
------------------------------------------------------------------
From: jhd@irfu.se (Jan D.)
Newsgroups: comp.unix.wizards
Subject: Re: flock(2) emulation?
Date: 16 Aug 92 14:02:35 GMT
Organization: Swedish Institute of Space Physics, Uppsala, Sweden

In article <19480@fritz.filenet.com> scotth@fritz.filenet.com (Scott Hopson) writes:
>In article <BsrzAp.7KD@ef2007.efhd.ford.com> Mike O'Connor <mjo@fmsrl7.srl.ford.com> writes:
>>In article <1992Aug7.173126.25686@htsa.aha.nl> miquels@htsa.aha.nl (Miquel van Smoorenburg) writes:
>>
>>:And for BSD or HPUX etc it makes no sense to implement a flock or lockf
>>:emulation, since you already have the Real Thing (TM).
>>
>>H-pukes doesn't have flock().
>
>no but HPs do have lockf()
>
That doesn't help much, since a lot of programs use flock(). You can't
fully emulate flock() with lockf() (shared locks). Nor can you do it
with fcntl() since it differs from flock() with repect to fork().

	Jan D.
Newsgroups: comp.unix.wizards
From: paigen@tfs.com (David Paigen)
Subject: Re: Have $8000, what to buy?
Organization: TRW Financial Systems
Distribution: comp
Date: Thu, 13 Aug 1992 19:28:06 GMT

rg@msel.unh.edu (Roger Gonzalez) writes:

>-> >I want a Unix machine.  Now.
>-> 
>-> >I want BSD features. I want full networking. I want X11R5. I want color.

I write:

>-> As much maligned as the PC is (with good reason), it gives the best bang
>-> for the buck.  $2K will buy you a 486/50 (at least here in silicon
>-> valley).  Another $2K for a big monitor and a big disk leaves you $4K
>-> to hang the kitchen sink off of it.  Add a SoundBlaster.  Add an X-10
>-> interface.  Add analog<=>digital converters.  Add an NTSC board.  Plus,
>-> you would get source to your OS.

meunier@quasar.enst.fr (Sylvain Meunier) writes:

>Ok for computer but which Unix OS will you chose ? A good OS with full
>compatilility with other OS ...

Rodger said he wanted BSD, so that rules out sVr4.  386BSD costs nothing,
BSDI's BSD/386 costs $1000.  I would suggest BSDI, it might be more
stable.  Note the 'might'.  Also note that I have not played with either.

I will be installing 386BSD this weekend, barring any major problems.

----------------------->"Lay on, McDuff,    14th c. ideals in a 21st c. world
David Paigen            and damn'd be he        N: PLO Bush IRA CIA KKK
TRW Financial Systems   who first cries,        S: terrorism pipe bomb kill
paigen@tfs.com          'hold, enough!'"        A: assasination maim
From: mikes@Ingres.COM (Mike Schilling)
Subject: Re: flock(2) emulation?
Date: 17 Aug 92 17:21:16 GMT

Try herd(3). After the Millenium, pride(3) might apply.
Xref: sparky comp.unix.wizards:3583 comp.unix.bsd:4043
From: meunier@quasar.enst.fr (Sylvain Meunier)
Newsgroups: comp.unix.wizards,comp.unix.bsd
Subject: Re: Have $8000, what to buy?
Date: 12 Aug 92 16:42:08 GMT
Reply-To: meunier@inf.enst.fr
Followup-To: comp.unix.wizards
Distribution: comp
Organization: Telecom Paris, France

In article <1992Aug11.164928.2658@tfs.com>, paigen@tfs.com (David Paigen) writes:
-> rg@msel.unh.edu (Roger Gonzalez) writes:
-> 
-> >I want a Unix machine.  Now.
-> 
-> >I want BSD features.  I want full networking.  I want X11R5.  I want color.  I
-> >want at least 1.2Gb of disk, and 16Mb of memory.  I have $8000, and won't be
-> >able to add much more for at least a year.
-> 
-> >What should I buy?  Sparc IPC?  Iris Indigo?  A HP?  A PC (shudder) with BSDI?
-> >A NeXT?  A Mac with A/UX?  I only know that I can pick up an IPC for about
-> >$5000 after discount, and then use $3000 for buying peripherals.  Who else has
-> >deals like that?
-> 
-> After having spent 5 years contracting on almost every workstation class
-> unix platform, I'll add my $0.02 here.
-> 
				.
				.
				.

-> 
-> As much maligned as the PC is (with good reason), it gives the best bang
-> for the buck.  $2K will buy you a 486/50 (at least here in silicon
-> valley).  Another $2K for a big monitor and a big disk leaves you $4K
-> to hang the kitchen sink off of it.  Add a SoundBlaster.  Add an X-10
-> interface.  Add analog<=>digital converters.  Add an NTSC board.  Plus,
-> you would get source to your OS.
-> 

Ok for computer but which Unix OS will you chose ? A good OS with full
compatilility with other OS ...

-> Sun is my second choice.  With a budget of $20K or more it would be my
-> first choice.  But not when spending less than $10K.  I wouldn't buy
-> any of the other machines you mentioned even with someone else's money.
-> 
-> But that is only an opinion.
-> 
-> ----------------------->"Lay on, McDuff,    14th c. ideals in a 21st c. world
-> David Paigen            and damn'd be he        N: PLO Bush IRA CIA KKK
-> TRW Financial Systems   who first cries,        S: terrorism pipe bomb kill
-> paigen@tfs.com          'hold, enough!'"        A: assasination maim

-- 

	S. Meunier		E-Mail: meunier@inf.enst.fr
Newsgroups: comp.unix.wizards
Newsgroups: comp.unix.wizards
From: mounty@cix.compulink.co.uk (Michael Mounteney)
Subject: NFS Syncing                             
Cc: mounty@cix.compulink.co.uk
Reply-To: mounty@cix.compulink.co.uk
Date: Tue, 18 Aug 1992 07:41:50 +0000

Apparently some time ago there was a fix described here to circumvent NFS's
infuriating habit of syncing all writes to disc without putting them in the
normal system cache.  Needless to say, this makes creating new files with a
PC-NFS client _pretty_ slow.  Can anyone enlighten me about what the fix is?

I am running SunOS 4.1.1 and PC-NFS 3.5.
Xref: sparky comp.unix.wizards:3598 comp.unix.programmer:4280