Linux-Development-Sys Digest #354, Volume #6 Sun, 31 Jan 99 08:15:51 EST
Contents:
Re: Parallel C for Linux (Adam P. Jenkins)
Re: /dev/lp? with 2.2.1? (Jens Kristian S�gaard)
Tired of DNS servers that suck? (Todd Graham Lewis)
Re: Why I'm dumping Linux, going back to Windblows ([EMAIL PROTECTED])
Re: Why I'm dumping Linux, going back to Windblows ([EMAIL PROTECTED])
Kernel 2.2.1 trouble: IDE; eexpress; Quake2 (Samuel Scarano)
Re: Debugger ? ("Douglas Cook")
Re: COM for Linux? ("Ayal Pinkus")
Help new Red Hat user ("Mike Hendrick")
Re: Why I'm dumping Linux, going back to Windblows ([EMAIL PROTECTED])
Re: Why I'm dumping Linux, going back to Windblows (Isaac To)
----------------------------------------------------------------------------
Subject: Re: Parallel C for Linux
From: [EMAIL PROTECTED] (Adam P. Jenkins)
Date: 31 Jan 1999 01:59:59 -0500
Nix <$}xin{[email protected]> writes:
> [EMAIL PROTECTED] (Petter Reinholdtsen) writes:
>
> > This is the normal GNU make. Use 'make -j <num>' to compile <num>
> > files in parallell.
>
> And watch it get its dependencies in a tangle :(
>
> make -j on a multiprocessor system (or with the Custom libs across a
> network) is not exactly perfect yet. :(
It works fine for me. I can compile kernel 2.0.36, modules and all,
in around 2 minutes on a dual pentium machine with "make -j2 zImage".
If you don't set up the dependencies in your makefile, make won't be
able to figure this out for you. The problem is just more likely to
manifest when you run make in parallel mode.
--
Adam P. Jenkins
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Jens Kristian S�gaard)
Subject: Re: /dev/lp? with 2.2.1?
Date: 30 Jan 1999 04:19:19 +0100
jacques <[EMAIL PROTECTED]> writes:
> has anybody figured out how to restore printing
> after upgrading to 2.2.1. I know that lp1 moved to
Put this in /etc/conf.modules:
alias parport_lowlevel parport_pc
options lp parport=0
--
Jens Kristian S�gaard,
[EMAIL PROTECTED]
------------------------------
From: Todd Graham Lewis <[EMAIL PROTECTED]>
Crossposted-To: comp.unix.admin
Subject: Tired of DNS servers that suck?
Date: Sat, 30 Jan 1999 19:30:22 -0500
This is a developer troll; the Dents project is looking for developers!
http://www.dents.org
Dents is an implementation of the server half of the DNS internet
protocol, as defined in RFC-1035 et al. Dents is a from-scratch
implementation; i.e., it shares no code with any other DNS server.
There really is only one other DNS server: named. The Dents team aims
to advance the state of the art by by building a better mousetrap,
so to speak. We aim for Dents to be the premiere name server on the
Internet. How do we plan on doing this? Through better technology and
better licensing.
The better licensing part is easy: Dents is releases under the GPL,
so you can be sure that your contributions will not be hijacked by some
corporate marauder looking to turn a quick buck on top of your hard work.
The better technology portion has two parts:
First, Dents employs a modular design which allows users to develop
and use new resolver mechanisms with ease. Want for your domain to
be stored in an Oracle database and have queries into your name server
answered based on data in that database? You can do it by writing an
Oracle driver. Want to tie into your DHCP server so that your DNS data
is consistent with what your DHCP server says? Just write a driver
which uses a shared memory segment with your DHCP server.
This module system is still fairly young, but it is at the point where
people can start writing drivers which can pretty certainly be used for
a long time. I personally hope to have a PostgreSQL driver finished
soon, and Dents' other inventor, Johannes Erdfelt, is working on an
algorithmic driver which will allow you to generate in-addr.arpa answers
on the fly rather than having to generate huge static zone files for
your reverse zones.
Second, Dents has a dynamic control facility which allows administrators
to direct the operations of a running server without restarting it.
Inspired by xntpdc from the U. Deleware NTP distribution and kadmin
from MIT's Kerberos distribution, this facility allows one to instruct
the server to add, drop, or reload a zone, modify its interface list,
and to query the server concerning stats. The control facility is
further extensible through the module system, so that module writers can
also export control functionality through the system control facility.
Dents is also optionally multithreaded, so that CPU-intensive backend
methods can make use of multiple CPUs. Further, we have a preliminary
named-compatibility mode which we are working on extending, which,
we hope, will allow very easy transition from named to Dents.
Dents is still in the fairly early stages of public development after
a very long private development cycle. The last remaining area of
instability in the source tree, our red-black tree, has been debugged
and is being fixed as I type this. We should be doing a new release
next week which will mark our first really stable version of the server.
If you need a server which you can immediately throw 10k zones onto, then
Dents is not for you, at least not yet. If, however, you enjoy playing
with neat code and are interested in DNS or are looking for a project
where you can flex your muscles, then you might want to take a look
at Dents. Dents is written in C and should run on any posix-ish system;
the primary development systems are Linux and Irix. We would appreciate
anyone who can help us to get and keep Dents running on other operating
systems, including Solaris, HP/UX, FreeBSD, Hurd, and AIX. (I should
be able to handle Digital Unix (or whatever it's called today) myself,
but if someone wants to take it from me, then I would be appreciative.)
The pace of development has become really breathtaking; we have very
high hopes of becoming competitive with named in short order, and we
aim in the long run to become the dominant name server on the Internet.
Right now, however, we need developers who have the time and skills
to help us along. If you are interested, then send me mail or subscribe
to our mailing list; we will match your skills to the work left to be
done. Right now, we need the people who can do the following:
- documentation.
- write drivers for various databases and other back ends. We don't know
what backends people will find useful, so feel free to implement anything
which you think will be useful.
- SNMP hackers. We want to implement the SNMP MIBs, but we need help
integrating these internal stats with SNMP servers.
- portability. If you have a favorite platform that you want to see well-
supported, then try to get Dents running on it! Report bugs back to us,
or, even better, send in patches. We take such patches seriously.
- admin-friendliness. I came up with the idea for Dents when I was an
admin frustrated with the cumbersomeness of named. The control facility
should offer all of the functionality needed for admins to employ Dents
as a useful tool, and it should make working with DNS a pleasure for admins,
not a chore. Easy access to stats, the ability to reload individual zones
without taking the whole server down, all of these features are aimed at
admin-friendliness. If you want to see features like these in a DNS server,
then join our project and tell us about them.
- general C hackery. We need more C hackers to get Dents to
production-quality and 100% named-compatibility as quickly as possible.
We are not stingy with CVS access; if you write code, then you get write
access to our CVS tree. We are not stingy with credit; every release
has in the announcements mention of everyone who made significant
contributions to that release, and anyone can add themselves to the
CREDITS file whenever they think that their contributions merit their
doing so. We want to make the Internet a better place by making a better
DNS server available to Internet admins. We want you to hack on Dents.
http://www.dents.org
echo "subscribe dents-list" | mail [EMAIL PROTECTED]
See you on the Dents mailing list!
--
Todd Graham Lewis 32�49'N,83�36'W (800) 719-4664, x2804
******Linux****** MindSpring Enterprises [EMAIL PROTECTED]
"Those who write the code make the rules." -- Jamie Zawinski
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 31 Jan 1999 00:20:56 -0800
In article <790kk4$1qg0$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
>
>The man pages should not be
>cluttered with the kind of thing that you only want to see
>once. They should be the place you look when you know what
>you want to do but you need to fine tune the options. If
>you turn the man pages into fluff for people that haven't
>learned the language, then you'll also have to re-write the
>real reference again for the people that need it.
>
If you call examples that help people understand how to use
something "clutter" and "fluff", then it is beyond hope to
continue to argue with you.
But your point now seems that examples are good, but don't belong
to a man page?
well, at least this is a progress.
I say examples do belong in man pages, since man pages are
the first thing one looks at to find how to use a command.
putting examples in a book, or some other document somehwere
on the net will not help someone at 3 a.m. trying to figure some
complex command. Sure, have a separate document or book if
you want, but this does not mean not to have the examples in
the man page as well.
Do what is practical and convienent for the users, and use
common sense.
>>
>>Look at VMS help and you'll see what I mean.
>
>Do people typically combine many tools in VMS with pipelines and
>command grouping as they do in unix?
>
Sure. In VMS you can do
$pipe show file/device | search sys$input my_file_name
In the above, 2 commands are used. the SHOW command, and the
SEARCH command. The SHOW command generates a list of open
files on the current device, and the SEARCH command searches
the resulting list for a specific name.
I can do $HELP SHOW to tell me about the SHOW command (with
examples), and I can type $HELP SEARCH to tell me about the
SEARCH command with examples.
why does combining commands prevent one from showing examples
of how each command byitself can be used?
>>
>>What we are trying to point, is that examples help one understand.
>>And without examples, many will not understand well.
>
>I don't disagree here - I just don't want to see them more than
>once, and I don't think everyone else would either.
>
I dont understand this about "not wanting to see them more
than once" ??
You do see the options more than once when you type man command,
dont you?
Think of examples as extension of the option list, or if you
dont want to see them at all, close your eyes when the page scrolls
down to the examples sections at the end of the page.
Kirk
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 31 Jan 1999 00:25:28 -0800
In article <790kk4$1qg0$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
>
>In article <78ur7u$[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
>>
>>>Perhaps we would understand if you gave an example that is somehow
>>>better than your description???
>Urk.. That's not a man page, that's a full-blown 150 page book!
Besides the point.
The point was that Examples sometimes are the best way to help
show how a command is used.
If something is good, then make this good thing available.
since man pages are the first thing people look at to use
a command, then it is only logical to put this good
thing where people will look first.
Kirk
------------------------------
From: [EMAIL PROTECTED] (Samuel Scarano)
Subject: Kernel 2.2.1 trouble: IDE; eexpress; Quake2
Date: 30 Jan 1999 05:04:43 GMT
Reply-To: srs25@ [you know the routine] cornell.edu
I just compiled & installed Linux 2.2.1 and I have had 3 problems so
far. The first has to do with my IDE hard disk. I got the following
messages:
Jan 29 22:30:49 tumbolia kernel: VFS: Disk change detected on device
ide0(3,64)
Jan 29 22:56:13 tumbolia kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Jan 29 22:56:13 tumbolia kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
The other is with my ISA Etherexpress card. I've been getting lots of
these:
Jan 29 23:02:03 tumbolia kernel: eth0: tx interrupt but no status
Previously, with Linux 2.0.33, I had no such errors; I'm assuming that
these are both new bugs, but is the new kernel simply more verbose than
the old one?
And finally, a problem some other people on slashdot have apparently
experienced, but not resolved: Quake 2 freezes the whole system.
I can't think of anything strange about my system that could have
anything to do with these (except of course for the mere existences of
that horrible etherexpress), but I'll give a run-down anyway: AMD K6, 48
megs, 2 popular IDE hard disks (6.4-gig WD "Caviar" as hda, 2-gig
Seagate "Medalist" as hdc), express. I'd feel silly giving my video card
& stuff. If anyone wants more info, email me (Use the address in my sig,
I'm not sure what will show up in the header).
I'd like to help, but I'm not much of a kernel hacker (although I did
fix a simple bug in the smbfs code, if anyone remembers :-), so I'm
going to just go back to 2.0.33 for fear of corrupting data on my hard
disk. (BTW, I've gotten two more pairs of those scary-looking (to me)
`dma_intr' messages.)
--
Samuel R. Scarano "Everything should be made as
srs25@[remove this text]cornell.edu simple as possible, but not
http://people.cornell.edu/pages/srs25/ simpler." -- Albert Einstein
------------------------------
From: "Douglas Cook" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.unix.bsd.freebsd.misc
Subject: Re: Debugger ?
Date: Sun, 31 Jan 1999 00:16:06 -0700
On this note, how do you pass a command line parameter to your program
into gdb? On the HP-UX, gdb passed all options after the exe name to
the program, but on FreeBSD it looks for a core-dump by the name of the
parameter.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Douglas Cook - MCP, BYU ITC Web Programmer
mailto:[EMAIL PROTECTED]
http://students.cs.byu.edu/~cookd/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
------------------------------
From: "Ayal Pinkus" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: COM for Linux?
Date: 31 Jan 1999 11:05:31 GMT
An upcoming Linux game sports a COM emulator. go
http://crystal.linuxgames.com/
It is now closely tied in with the game, but I believe there are some ppl
ripping it out of
the game so it can be used in other projects. Any way, the source code for
COM on Linux
is right there...
Nathan Myers <[EMAIL PROTECTED]> wrote in article
<78vvol$sb1$[EMAIL PROTECTED]>...
> Aaron Perrin<[EMAIL PROTECTED]> wrote:
> >Does anyone know if a Component Object Model (COM) port is available
> >for linux?
>
> A final note: http://www.quoininc.com/quoininc/COM_CORBA.html
>
> --
> Nathan Myers
> [EMAIL PROTECTED] http://www.cantrip.org/
>
>
------------------------------
From: "Mike Hendrick" <[EMAIL PROTECTED]>
Subject: Help new Red Hat user
Date: Sun, 31 Jan 1999 04:23:27 -0700
I'm new to lynux and trying to figure out what compiler is used in the red
hat version for c++ compiling comparible to xlC which I'm useing on a school
network to run example c++ programs. I would be grateful for any advice.
thanks
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 31 Jan 1999 00:31:02 -0800
In article <790fbn$r3e$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
>
>> An example helps one UNDERSTAND. this is something you or les dont
>> seem to understand.
>
>There are places for examples.
Where?
> But they will not solve The
>Documentation Problem. Problem being, broadly, that lots of people
>complain that Unix is too hard to use.
>
One of the reasons is lack of examples in man pages !!
(some people really do not seem to have any common sense left).
Kirk.
------------------------------
From: Isaac To <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 31 Jan 1999 16:27:13 +0800
>>>>> "Nick" == Nick Papadonis <[EMAIL PROTECTED]> writes:
Nick> Completely agree. It seems that in the UNIX world people try to
Nick> force away non-technical newbies. A lack of examples is further
Nick> proof of this.
Agreed that not all Unix program developers tries to attract non-technical
newbies. But I would rewrite your sentence like this:
A lack of examples in the man pages shows that UNIX world people do not
try to attract non-technical newbies using its man pages. Those who do
not provide alternative documentation would end up distracting
non-technical users.
This is then correct.
The man page system is not particularly good for new comers of any program.
It lack a lot of functionalities like cross-referencing, tables, graphics
illustrations, glossary, navigation support, etc. to enhance readability.
It is therefore incorrect to ask a newbie to turn to their man pages if the
"newbie" do not seems to understand the structures of a program. There are
a lot of other type of documenetation that fill in this gap. They are
usually in the form of "Quickstart", "readme", Postscript manual or even
"texinfo" files.
On the other hand, as a user of Unix for some years, I do think that there
is a need of manual pages free from little gems to "enhance readability".
Once the basics of a software is learnt, it is essential that one can get
information about a program as quickly as possible. Starting up a
postscript previewer and look for the relevant section within a 600+ pages
manual is absolutely a non-solution. What we need is a concise description
documenting the options, the resources, etc.: in short, those that will be
forgotten. That's where man pages comes in handy. For example, when I need
to sort a ls listing under the ctime, I just need to "man ls" and type
"/ctime" and when that failed, "/change" and "n" thrice to find "-c" is the
needed option.
Man pages is more a "Quick reference" than a "tutorial". Use a document in
the wrong way probably end up in frustration.
Isaac.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
