Linux-Misc Digest #796, Volume #21 Mon, 13 Sep 99 20:13:11 EDT
Contents:
New Documentation License--Comments Requested (Richard Stallman)
Re: dosemu (Reinhard Karcher)
Re: Unable to load interpreter (Humphrey Zhang)
Re: Swapping harddrives, this is confusing, I need help ("Art S. Kagel")
Re: General Rant from a Linux Newbie (Todd Knarr)
One more Stupid C question (me)
Re: MP3 players (Radovan Garabik)
mp3 to wav or cdda? (me)
Re: How can I disable su? ([EMAIL PROTECTED])
Re: How can I "capture" HTTP request in apache? (Leslie Mikesell)
Re: YALNQ: yet another linux noobee question (Mike Detlefsen)
Re: How can I disable su? (steve mcadams)
Re: What is RAMDAC? (Thomas Ruedas)
----------------------------------------------------------------------------
From: Richard Stallman <[EMAIL PROTECTED]>
Crossposted-To: gnu.announce,gnu.misc.discuss
Subject: New Documentation License--Comments Requested
Date: Sun, 12 Sep 1999 03:59:40 -0400
Reply-To: [EMAIL PROTECTED]
I am working on a new license to use for GNU documentation. Here is a
draft of it. Please don't use it yet; I have not finished checking
it. But please do give me constructive comments for improving the
details of it. I can make use of them to improve version 1.0.
GNU Free Documentation License Version 0.9
DRAFT
0. PREAMBLE
The GNU Free Documentation License is a form of copyleft designed for
books, such as reference manuals and tutorials. We designed it in
order to use it for documentation about free software, but it can be
used regardless of the subject matter. It can also apply to textual
works that are not released in book form. It gives users the right to
copy, redistribute and modify the work, just as users have the right
to copy, redistribute and modify free software.
1. APPLICABILITY
This License applies to any manual or other work which contains a
notice placed by the copyright holder saying it can be distributed
under the terms of this License. The "Manual", below, refers to any
such manual or work. Any member of the public is a licensee, and is
addressed as "you".
A "Modified Version" of the Manual means any work containing the
Manual or a portion of it, either copied verbatim or with
modifications and/or translated into another language.
The "Invariant Sections" are certain appendices or front-matter
sections of the Manual, which deal exclusively with nontechnical
matters (such as the political views, histories or legal positions of
the authors), and whose titles are listed as Invariant Sections in
the notice saying that the Manual is released under this license.
The "Front-Cover Texts" are certain short passages of text are listed as
Front-Cover Texts or Back-Cover Texts in the notice saying that the
Manual is released under this license.
A "Transparent" copy of the Manual means a machine-readable copy,
represented in a format whose specification is available to the
general public, in which the text may be viewed straightforwardly with
ordinary text editors, and which is suitable for input to text
formatters or for automatic translation to a variety of formats
suitable for input to text formatters. Examples of suitable formats
for transparent copies include Texinfo input format, LaTeX input
format, SGML, and standard-conforming HTML. A copy that is not
"Transparent" is called "Opaque".
The "Title Page" means, for a printed book, the title page; for works
in other formats where there is no title page as such, it means the
text near the most prominent mention of the work's title, preceding
the beginning of the body of the text.
2. VERBATIM COPYING
You may copy and distribute the Manual, in any medium, either
commercially or noncommercially, provided that this license is
reproduced in all copies, and you add no other conditions whatsoever
to those of this license. You may accept compensation in exchange for
copies, but you may not technically obstruct the reading or further
copying of the copies you make or distribute.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
It is requested, but not required, that you give the authors of the
Manual thirty days (or more) advance notice of your plans to
redistribute any large number of copies, to give them a chance to
provide you with an updated version of the Manual.
3. COPYING IN QUANTITY
If you publish or distribute printed copies of the Manual numbering
more than 100, and the Manual's license notice requires Cover Texts,
you must enclose the copies in covers that carry, clearly and legibly,
all these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. If the required texts for either
cover are too voluminous to fit legibly, put the first ones listed (as
many as fit reasonably) on the actual cover, and continue the rest
onto adjacent pages.
If you publish or distribute Opaque copies of the Manual numbering
more than 100, you must state in or with each copy a publicly
accessible computer network location containing a Transparent copy of
the Manual, no more and no less, which the general network-using
public has access to download at no charge. You must take reasonably
prudent steps, when you begin distribution of Opaque copies in
quantity, to ensure that this Transparent copy will remain thus
accessible at the stated location until at least six months after you
last distribute an Opaque copy.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Manual under the
conditions of section 2 and 3 above, provided that you release the
Modified Version under precisely this license, with the Modified
Version filling the role of the Manual, thus licensing use of the
Modified Version to whoever possesses a copy of it. In addition, you
must do these things in the Modified Version:
A. Mention the Manual's title on the Title Page.
B. Add something to the title, or a subtitle, stating that the version has
been modified, and distinguishing it from the Manual you started with.
C. Mention on the Title Page at least one name of a person or entity
responsible for authorship of the modifications in the Modified
Version and/or publication of the Modified version, and describe
that entity's relationship to the Modified Version.
D. Retain on the Title Page or its continuation the authors' and publishers'
names listed on the Manual's Title Page.
E. Preserve all the copyright notices of the Manual.
F. Add an appropriate copyright notice for your own work.
G. Include after them a notice stating giving the public permission to
use the Modified Version under the terms of this license,
in the form shown in the Addendum below.
H. Preserve in that notice the full list of Invariant Sections,
and the full list of required Cover Texts, given in Manual's notice.
I. Include an unaltered copy of this license.
J. Preserve the network location, if any, given in the Manual for
public access to a Transparent copy of the Manual, and likewise
those network locations given in the Manual for any earlier
versions it was based on.
K. If the Manual has an Acknowledgements and/or Dedications section,
preserve therein all the substance of each of the contributor
acknowledgements and/or dedications stated therein.
L. Preserve all the Invariant Sections of the Manual,
unaltered in text and in their titles.
If the Modified Version includes new front-matter sections (or
appendices) which deal exclusively with nontechnical matters, and
contain no material copied from the Manual, you may at your option add
the section titles of any or all of these sections to the list of
Invariant Sections in the Modified Version.
You may add up to five words of Front-Cover Text and up to 25 words of
Back-Cover Text to the end of the list of Cover Texts in the Modified
Version.
The author(s) and publisher(s) of the Manual do not by this license
give permission to use their names for publicity or to assert or imply
endorsement of any Modified Version.
5. COMBINING MANUALS
You may combine the Manual with other manuals released under this
license, under the terms of section 3 above as for modified versions,
provided that you include all of the Invariant Sections of all of
the original manuals, unmodified, in the combination, and list them
all as Invariant Sections in your combined work.
The combined work need only contain one copy of this license, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end, in parentheses, the name of the original author or
publisher of that section if known, otherwise the name of an author or
publisher of the manual that section came from; and make the same
adjustment in the list of Invariant Sections in the license of the
combined work.
6. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Manual or its derivatives with other separate and
independent documents or works, in or on a volume of a storage or
distribution medium, does not as a whole count as a Modified Version
of the Manual, provided no compilation copyright is claimed for the
compilation. In such a case, this license does not apply to the other
self-contained works thus compiled with the Manual, if they are not
derivative works of the Manual.
7. TRANSLATION
Translation is considered a kind of modification, so you can
distribute translations of the manual under the terms of section 4.
This implies that translation of the Invariant Sections requires
special permission from their copyright holders. You may include a
translation of this license provided that you also include this
license in the original English version. In case of a disagreement
between the translation and the English version of this license, the
English version will prevail.
8. TERMINATION
You may not copy, modify, sublicense, or distribute the Manual
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Manual is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
9. ADDENDUM: How to use this license for your manuals
To use this license in a manual you have written, put the following
notice on the page after the title page:
Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this
manual under the terms of the GNU Free Documentation License,
Version 1.0 or any later version published by the Free Software
Foundation, with the Invariant Sections being LIST THEIR TITLES,
Front-Cover Texts being LIST, and Back-Cover Texts being LIST.
A copy of the license is included in the section entitled "GNU
Free Documentation License"
If you have no Invariant Sections, write "with no Invariant Sections"
instead. If you have no Front-Cover Texts, write "no Front-Cover Texts"
instead of "Front-Cover Texts being LIST". Likewise for Back-Cover Texts.
------------------------------
From: [EMAIL PROTECTED] (Reinhard Karcher)
Date: 10 Sep 99 17:09:16 GMT
Subject: Re: dosemu
Michael B. <[EMAIL PROTECTED]> wrote:
>Would this be the correct place for answers to problems with
>DOSEMU running under Linux? If not, can someone please direct
>me to the proper location.
Hi Michael,
I don't know of any newsgroup, but there is a mailinglist:
[EMAIL PROTECTED] You can subscribe the list and
ask your questions. But be warned, you have to supply much more
information: version of dosemu, version of linux, those parts
of dosemu.conf, that are related to your problem, a description
of your problem, errormessages etc. But perhaps you did know all
these points.
Greetings
Reinhard
------------------------------
From: Humphrey Zhang <[EMAIL PROTECTED]>
Subject: Re: Unable to load interpreter
Date: Mon, 13 Sep 1999 13:41:38 -0400
I did the search, and found this message. Could you please spend a few
minutes
to give me a hint about the nature of the problem or further leads to the
already asked
question and its answers?
Thank you very much.
Jun
Andrei A. Dergatchev wrote:
> Can you search www.deja.com ?
> It was asked already and you may find useful answer.
>
> On Fri, 10 Sep 1999 13:49:19 -0400, Humphrey Zhang
> <[EMAIL PROTECTED]> wrote:
>
> >This is Mandrake 6.0, kernel of which has been upgraded to 2.2.10. Each
> >time
> >the system boot, after the line
> > INIT: version 2.76
> >there is a line read exactly like the subject of this message. The
> >system doesn't have
> >major problems after coming up, but, what is it?
> >
> >Jun
> >
------------------------------
From: "Art S. Kagel" <[EMAIL PROTECTED]>
Subject: Re: Swapping harddrives, this is confusing, I need help
Date: Mon, 13 Sep 1999 14:23:28 -0400
Reply-To: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
>
> Hi,
>
> Here's my very basic setup:
> 8 Gig drive-Totally 95
> 1.2 Gig drive-Linux
> 2 Gig drive-Blank 95 partition
>
> Here's what I need to do:
> 1. Copy 95 drive to the 95 partition (all the files should fit in the
> two Gigs.
> 2. Reformat and repartition 8 Gig drive.
> 3. Copy linux to the new 8 Gig drive.
>
> Here's what I need to know:
> 1. Dos command to copy entire directory sturcture. I've tried the
> normal copy c:\*.* d:\ and it only copies files, not directories
XCOPY /s c:\*.* d:\
> 2. The linux command to do basically the same thing
There are several idioms for doing this using tar or cpio. This is my
favorite:
cd old_fs_root; tar cf - * | (cd new_fs_root; tar xvf - )
> 3. Linux command to make a LILO boot disk.
Edit the LILO config file and run lilo.
> Basically, I am degrading windows to the 2 Gig drive and giving myself
> more space for linux. I'll prolly be using the 1.2 Gig drive for either
> another linux dist or FreeBSD. I will be doing a lot of drive switching
> during this process so I think I know how to deal with LILO. I just
> need someone to help me with those commands, stupid questions, I know.
> TIA.
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
Art S. Kagel
------------------------------
From: Todd Knarr <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy
Subject: Re: General Rant from a Linux Newbie
Date: 13 Sep 1999 19:35:20 GMT
In comp.os.linux.misc <[EMAIL PROTECTED]> Philip Brown
<[EMAIL PROTECTED]> wrote:
> To stick with the plane analogy:
> There have been crashes due to pilot error.
> There have been crashes due to MECHANICAL failure.
> How many crashes have their been due to systems failure/error?
> Not a whole lot.
No, but I've heard and seen reports on several where the flight control
system malfunctioned. One common thread in all of them: the pilot could
have recovered from the situation and brought the plane down safely had
he had a way to override the flight control system, but the designers
of the aircraft gave the flight-control system the ability to override
the pilot instead. One, IIRC, involved an Airbus plane. A sensor malf
told the flight computer the plane was descending right after takeoff,
so the computer started to pull up. That put the plane dangerously close
to a stall. The pilot tried to bring the nose down, which the computer
interpreted as increasing the dive and it countered by pulling the nose
up even more. Result: one fully-loaded airliner falling out of the sky
and making a big hole in the ground even though the plane itself was in
perfect flying condition and the pilot's actions would have prevented
the accident.
The same thing happens with computer software too. The system hides
things so thoroughly that you can't get at it to fix the problem even
when you know exactly what the problem is and how to fix it.
--
Safety hint, dude ... never, ever get up to go to the john at night unless
you can actually feel your body.
-- Sonya Marie Gildencrantz
------------------------------
Date: Tue, 14 Sep 1999 00:53:40 +0200
From: me <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.questions
Subject: One more Stupid C question
Hi
Firstly....thanks to everyone who responded to my original message ie.
(Stupid C question). I adjusted the code and removed all the C++ bits so
everything's fine now and the program works.
There's just one thing that bugs me. When i declare a string in any
block, it gets assigned to a negative memory address. eg.
main()
{
......
.......
{
char s[80];
........
.......
}
......
}
For some reason......'s' gets assigned a memory address like -1038473945
or something. I'm forced to use malloc to correct this problem. It
doesnt seem to happen with other datatypes. Why does this happen???
just curious
ali ([EMAIL PROTECTED])
------------------------------
From: [EMAIL PROTECTED] (Radovan Garabik)
Subject: Re: MP3 players
Date: 13 Sep 1999 19:38:37 GMT
saken <[EMAIL PROTECTED]> wrote:
: which mp3layer is the easiest/best 2 use? linuxberg recommended 2
: xmms and mp3studio, are there better ones or are these good or what?
: --saken
I'd say mpg123
--
-----------------------------------------------------------
| Radovan Garabik http://melkor.dnp.fmph.uniba.sk/~garabik |
| __..--^^^--..__ garabik @ fmph . uniba . sk |
-----------------------------------------------------------
------------------------------
Date: Tue, 14 Sep 1999 01:17:12 +0200
From: me <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.admin,comp.os.linux.help,comp.os.linux.questions,comp.os.linux.x
Subject: mp3 to wav or cdda?
hi
i'm looking for an application to convert mp3's to wav or cdda (or some
similar) format so that i can create audio CD's from mp3's.
anyone know of anything?
ali
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: How can I disable su?
Date: Mon, 13 Sep 1999 22:59:55 GMT
I read the other responses sent so far, and none seemed to answer the
question directly, and
'simply,' so here is a direct, and simple answer:
chgrp admin /bin/su
chmod 750 /bin/su
Now, all you need to do is add each user you'd like to have access to
the 'admin' group (or any other group you choose to create.. admin was a
simple example) You can take the time to man su and suauth as another
post suggested, and you'd get another answer. This one however, is
simple and gets the job done, and is somewhat secure.
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> Dear Gurus
>
> How can I allow only certain users to have access to su?
> I have seen this works on an acount I have access to and
> I would like to do it on linux box.
>
> Thanks in adavnce
>
> please cc to [EMAIL PROTECTED]
>
--
| Bill Bartlett |
| Metro One Telecommunications
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Leslie Mikesell)
Subject: Re: How can I "capture" HTTP request in apache?
Date: 13 Sep 1999 17:54:34 -0500
In article <[EMAIL PROTECTED]>,
nodd <[EMAIL PROTECTED]> wrote:
>i have one linux box(redhat 6.0), and manage apache 1.3.6 web server
>in that box.
>
>My job is make some scripting in PHP3, and need to send "perfectly
>same" HTTP request to certain site (not bad purpose...)
If all you need to do is to make the web requests that hit
one site (or part of it) transparently get passed to a
different site, you can use the ProxyPass directive in
apache. ProxyPass by itself will map a whole subdirectory
but you can use mod_rewrite with the [p] rule to be
more selective. Look at the documentation in the modules
section or on www.apache.org.
Les Mikesell
[EMAIL PROTECTED]
------------------------------
Crossposted-To: alt.sci.seti
Subject: Re: YALNQ: yet another linux noobee question
From: [EMAIL PROTECTED] (Mike Detlefsen)
Date: Mon, 13 Sep 1999 22:29:41 GMT
John Girash <[EMAIL PROTECTED]> wrote:
> They could at least have the provision to put the client to sleep if it's not
> currently needed, and to check in ~once/day to see if a new data stream's up.
Sounds like a good idea to me.
--
Sorry, but it's a bogus address in the header.
Score one for the spammers.
------------------------------
From: steve mcadams <[EMAIL PROTECTED]>
Subject: Re: How can I disable su?
Date: Mon, 13 Sep 1999 13:00:30 -0600
couldn't you just move the real su to a directory that only the desired users
have execute privilege for, then write a front-end to call it? seems like
that might be easier to manage than having a list. just a thought.
"Art S. Kagel" wrote:
> You have to make a version of su that checks the userid against a list of
> valid user ids. Then compile the new program, make it suid root and
> install it in place of su. Get the source from the distribution.
------------------------------
Date: Mon, 13 Sep 1999 23:06:15 +0200
From: Thomas Ruedas <[EMAIL PROTECTED]>
Subject: Re: What is RAMDAC?
RAMDAC: Random Access Memory Digital Analog Converter
see http://www.ciw.uni-karlsruhe.de/abklex.html
--
============================================
Thomas Ruedas
Institute of Meteorology and Geophysics,
J.W. Goethe University Frankfurt/Main
Feldbergstrasse 47 D-60323 Frankfurt/Main, Germany
Phone:+49-(0)69-798-24949 Fax:+49-(0)69-798-23280
e-mail: [EMAIL PROTECTED]
http://www.geophysik.uni-frankfurt.de/~ruedas/
============================================
------------------------------
** 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.misc) 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-Misc Digest
******************************
