Files
oldlinux-files/ftp-archives/tsx-11.mit.edu/1996-10-07/mail-archive/linux-devel/Volume2/digest128
2024-02-19 00:24:15 -05:00

739 lines
29 KiB
Plaintext
Raw Blame History

From: Digestifier <Linux-Development-Request@senator-bedfellow.mit.edu>
To: Linux-Development@senator-bedfellow.mit.edu
Reply-To: Linux-Development@senator-bedfellow.mit.edu
Date: Tue, 6 Sep 94 08:13:06 EDT
Subject: Linux-Development Digest #128
Linux-Development Digest #128, Volume #2 Tue, 6 Sep 94 08:13:06 EDT
Contents:
Re: DOSEMU 0.53pl17 and keyboard (Pekka J Taipale)
cat /proc/interrupts doesn't show printer ints. (andrei@labomath.univ-orleans.fr)
Re: WARNING about shadow-mk package (Joe Zbiciak)
Re: Future of linux -- the sequel (Conrad Steenberg)
BUG SCSI 1.1.37 to 1.1.49 more info. (BARRY TITMARSH)
Re: WARNING about shadow-mk package (Patrick Reijnen)
Re: WARNING about shadow-mk package (Patrick Reijnen)
Re: Any interest for DCF77 clock code? (David Kastrup)
Re: Future of linux -- the sequel (Shannon Hendrix)
Re: Kernel change summary 1.1.45 -> 1.1.46 (John McClary Prevost)
Re: Fortran Compiler for Linux?? (Sakari Mattila)
Looking for term2.x applications (Andrew Davison)
Re: Netware Client (Volker Lendecke 29121346)
Adaptec 2742AT (Bernd Bartmann)
----------------------------------------------------------------------------
From: pjt@snakemail.hut.fi (Pekka J Taipale)
Subject: Re: DOSEMU 0.53pl17 and keyboard
Date: 06 Sep 1994 06:52:01 GMT
In article <34g893$s2v@flood.xnet.com> genanr@amiserv.xnet.com (Andrew Ryan) writes:
> I can't get DOSEMU 0.53pl17 to work right. After dos 6.2 boots and
>I get the date prompt my keyboard is all screwed up. I have linux 1.1.49.
>Does anyone else have this problem? Is there a fix?
I had a similar problem, until I changed rawkeyboard to on in
/etc/dosemu.conf. Odd enough. One would think that having rawkeyboard
off would give less problems, but not so.
Of course, you might have another problem...
--
Pekka.Taipale@hut.fi
------------------------------
From: andrei@labomath.univ-orleans.fr
Subject: cat /proc/interrupts doesn't show printer ints.
Date: 6 Sep 1994 02:10:53 -0500
Hello All,
The Subject says it all. I am *almost* sure my printer uses INT7, as I set it
by tunelp, and it works, and if I set it to another value, it doesn't. Kernel
version is 1.1.49. Could someone hint if one can do something to make the
printer interrrupts counter displayable? Many thanks,
Andrew Yakovlev.
------------------------------
From: im14u2c@cegt201.bradley.edu (Joe Zbiciak)
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
Subject: Re: WARNING about shadow-mk package
Date: 6 Sep 1994 02:10:30 -0500
=====BEGIN PGP SIGNED MESSAGE=====
This post is in regards to the login.secure program included in
the shadow-mk package authored by Mohan Kokal. I, Joseph R.M. Zbiciak,
am the sole author of this program, and would like to dispell any
rumors labeling it as the tool of a "cracker."
Included in this post is the source code for my /bin/login replacement.
The binary included in the shadow-mk package distributed by Mohan Kokal
was apparently compiled under GCC 2.4.5, using libc 4.4.4. I base this
statement on the fact that the binary was indeed compiled by me on my
personal Linux box, "asylum," prior to June 9th. On June 9th, I upgraded
to GCC 2.5.8, and libc 4.5.26.
Inspection of the login.secure binary will reveal that it was indeed
linked with libc 4.4.4.
Therefore, I seek corroboration of the following, since I cannot
do this myself (my system has no room to dl libc 4.4.4 and gcc 2.4.5 to
try this):
The login.secure binary was most probably compiled as follows:
gcc -o login.secure -s -N -O6 -fomit-frame-pointer -m386 login1.c
(as I said, under GCC 2.4.5, and libc 4.4.4)
Using GCC 2.5.8 and libc 4.5.26 yeilds an executable of 1328 bytes
with these options.
Let me remind you that the /bin/login on my system has been and continues
to be the login.secure binary that was included in shadow-mk. (Size:
1124 bytes. CRC: a4abbb26)
I have PGP-signed this post to ensure its authenticity. My public key
is available via finger. Please finger im14u2c@cegt201.bradley.edu.
Pipe the output to a file and run pgp -ka on the file to add the key
to your keyring. This key is primarily for private messages. I do not
yet have a well established key for business use. One will be forthcoming.
Please: I urge *ANYONE* that has any questions, problems, etc. relating
this program to CONTACT ME IMMEDIATELY. My email address is, once again,
im14u2c@cegt201.bradley.edu. Should that address fail, there's also
im14u2c@camelot.bradley.edu. Should both of those addresses fail for one
reason or another, email Mohan Kokal at magnus@cegt201.bradley.edu, with
instructions to forward the mail to me.
And again: I do apologize for any inconvenience this may have caused
anyone. The shadow-mk package is not insecure. The login.secure is
indeed what it was titled. I do hope that this post lays to rest any
suspicion about the shadow-mk package, its contents, and its author.
I also apologize to Mohan Kokal for not realizing that such a small piece
of code would cause such a large number of people to label him as a
cheap-and-dirty cracker.
Here's the source code:
==FILE: login1.c==
/* Preprocessor for /bin/login */
/* Corrects /bin/login security hole regarding -f */
/* Also disables -h for non-root users. */
/* (c) 1994, Joseph R. M. Zbiciak */
#include <strings.h>
#include <unistd.h>
#include <stdio.h>
main (int argc, char * argv[], char * envp[])
{
char **av=argv;
int ac=argc;
if (argc>1) {
while(--ac>0) {
if (**(++av)=='-' && strlen(*av)>1) {
*((*av)+2)=0;
if (*((*av)+1)=='h' && getuid()>100) {
fprintf(stderr,"You cannot specify a new host.\n");
exit (1);
}
}
}
}
execve("/bin/_login",argv,envp);
return 0;
}
==END OF FILE==
- --Joseph R.M. Zbiciak
Systems Administrator & Programmer
Texas Networking Systems, Inc.
DISCLAIMER: Neither this post, nor any other post made by me, reflects
the opinions of my various employers, unless EXPLICITLY
stated. All opinions stated herein are mine unless otherwise
noted.
:= Joe Zbiciak == im14u2c@ =:
:- - cegt201.bradley.edu - -:
If it works, Don't fix it. : - camelot.bradley.edu - :
:-Finger for PGP Public Key-:
:===========================:
=====BEGIN PGP SIGNATURE=====
Version: 2.3a
iQCVAgUBLmwUH/1glWhKqKRRAQHCAgP6AqTd3G9kzRm12GqiE29aL1VHjkYxb/hU
FW4F0+TEIM7RbUcbfFPilwtnb2n08btgcLW+92YZRGf4FmzteVLEMhecz/+wB9Wd
/Dr8rH5rUrJw2Lclx7ZmiLDLfBVHLahcRNQ/oH/itLg9UJXLzLKq8igEniIpyxgW
LevHNAnbWgM=
=VIIl
=====END PGP SIGNATURE=====
------------------------------
From: conrad@fskcds.puk.ac.za (Conrad Steenberg)
Subject: Re: Future of linux -- the sequel
Date: 6 Sep 1994 07:15:04 GMT
Rob Janssen (rob@pe1chl.ampr.org) wrote:
: In <34el3j$hsp@gazette.engr.sgi.com> erik@westworld.esd.sgi.com (Erik Fortune) writes:
: >In article <CvMKy4.3Bz@pe1chl.ampr.org>, rob@pe1chl.ampr.org writes:
{LOTS of stuff deleted...}
: However, this is not what the thread is all about. The point is that the
: original statement that an Indy makes a Pentium feel like a 4.77MHz XT
: was a gross exaggeration, and that still stands. The memo only shows that
{snip...}
: Rob
One of the original poster's questions is seemingly completely ignored, even
though it is much more relevant than whether chip X or system Y is faster/
cheaper than a Pentuim at Z MHz, so let me ask that question:
WHY is no one even CONSIDERING doing a multiprocessor kernel for Linux?
It doesn't matter which multiprocessor board, but the fact is that there
are multiprocessor 486 and Pentium motherboards out there... they are even
affordable (of all things ;-). OS/2 from IBM comes with a multiprocessing
kernel (SMP no less...) so it is not impossible, even though it may be
hard on a few programmers' sleep.
I think this should be considered an essential next
step in the development of a free, high performance OS that runs on just
about any PC hardware (i.e. Linux)
One could probably go on like this for ages, but it probably comes down to
the fact that the guys doing the slick programming doesn't have the slick
hardware...<sigh>. Maybe someone should volunteer sending a multiprocessor
board off to Australia to tempt a certain higly respected kernel programmer!
Cheers
Conrad
______________________________________________________________________________
|Conrad Steenberg | Space Research Unit | Eenheid vir Ruimtenavorsing |
| | Potchefstroom | Potchefstroomse |
| 99-2424 | University for CHE | Universiteit vir CHO |
______________________________________________________________________________
|"Hou hierdie spasie dop... |
| goed gaan maar weer voort." |
|"This will probably be modified as soon as someone comes up with something |
| witty worthwile repeating in the presence of a lady" |
_____________________________________________________________________________|
conrad@fskcds.puk.ac.za
(fiscds@pukrs1.puk.ac.za, fiscds@pukrs6.puk.ac.za)
------------------------------
Date: Tue, 6 Sep 1994 08:57:38 EST
From: BARRY TITMARSH <BTITMARS@ESOC.BITNET>
Subject: BUG SCSI 1.1.37 to 1.1.49 more info.
I have tested all kernels 1.1.36 to 1.1.49 last night.
on platform slackware 2.00
seems aha1542 stopped working with 1.1.36. ??
however with libs ....24 it did work Ok sortof.?
Idears.
1.1.37
kernel: Kernel logging (proc) started.
kernel: 16384 bytes for swap cache allocated
kernel: Console: colour EGA+ 100x40, 8 virtual consoles
kernel: Serial driver version 4.00 with no serial options enabled
kernel: tty00 at 0x03f8 (irq = 4) is a 16450
kernel: tty01 at 0x02f8 (irq = 3) is a 16450
kernel: lp_init: lp1 exists, using polling driver
kernel: lp_init: lp2 exists, using polling driver
kernel: Microsoft BusMouse detected and installed.
kernel: tpqic02: IRQ 5, DMA 1, IO 0x300, IFC Archive, $Revision: 0.4.1.4
$
kernel: tpqic02: Settings: IRQ 5, DMA 1, IO 0x300, IFC Archive
kernel: tpqic02: waiting looong in rdstatus() -- drive dead?
kernel: tpqic02: finished waiting in rdstatus()
kernel: tpqic02: tp_sense: status: 81d0, error count: 0, underruns: 0
kernel: tpqic02: DMA buffers: 20 blocks, at address 0x1ac200 (0x1ac018)
kernel: tpqic02: tp_sense: status: 81d0, error count: 0, underruns: 0
kernel: Calibrating delay loop.. ok - 6.60 BogoMips
kernel: Configuring Adaptec at IO:330, IRQ 11, DMA priority 5
kernel: scsi0 : Adaptec 1542
kernel: scsi : 1 hosts.
kernel: Vendor: SyQuest Model: SQ5110 Rev: CHC
kernel: Type: Direct-Access ANSI SCSI revision:
0
kernel: Detected scsi disk sda at scsi0, id 3, lun 0
kernel: Vendor: NEC Model: CD-ROM DRIVE:841 Rev: 1.0
kernel: Type: CD-ROM ANSI SCSI revision:
0
kernel: Detected scsi CD-ROM sr1 at scsi0, id 4, lun 0
kernel: Vendor: LMS Model: CM214 Rev: 0.12
kernel: Type: CD-ROM ANSI SCSI revision:
0
kernel: Detected scsi CD-ROM sr2 at scsi0, id 5, lun 0
kernel: scsi : detected 2 SCSI cdroms 1 SCSI disk total.
kernel: Scd sectorsize = 2048 bytes
kernel: Scd sectorsize = 2048 bytes
kernel: Memory: 14912k/16384k available (592k kernel code, 384k reserved,
kernel: Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
kernel: Swansea University Computer Society NET3.016
kernel: NET3 TCP/IP protocols stack v016
kernel: IP Protocols: ICMP, UDP, TCP
kernel: SLIP: version 0.7.5-NET3.014-NEWTTY (4 channels)
kernel: CSLIP: code copyright 1989 Regents of the University of Californi
a
kernel: eth0: WD80x3 at 0x280, 00 00 C0 02 BA 6A assigning address 0xd00
0
kernel: wd.c:v0.99-14 11/21/93 Donald Becker (becker@super.org)
kernel: Checking 386/387 coupling... Ok, fpu using irq13 error reporting.
kernel: Linux version 1.1.37 (root@dc0hk-sys2) #3 Mon Sep 5 22:25:36 MET
D
kernel: Partition check:
kernel: sda: sda1
kernel: hda: multiple mode not supported
kernel: hda: hda1 hda2 hda3 hda4
kernel: hdb: multiple mode not supported
kernel: hdb: hdb1 hdb2 hdb3
kernel: VFS: Mounted root (ext2 filesystem) readonly.
kernel: Adding Swap: 29576k swap-space
named<EFBFBD>54<EFBFBD>: Ready to answer queries.
named<EFBFBD>54<EFBFBD>: sysquery: query() contains our address (dc0hk-sys2.ampr.org:44
.
login: ROOT LOGIN ON tty1
kernel: SCSI host 0 timed out - aborting command
last message repeated 3 times
kernel: SCSI host 0 abort() timed out - reseting
kernel: Sent BUS DEVICE RESET to target 3
kernel: Sending DID_RESET for target 3
and now 1.1.39
syslogd: restart
named<EFBFBD>53<EFBFBD>: starting. named 4.9.3-BETA9 Sun Sep 4 14:10:48 MET DST 1994
kernel: Kernel logging (proc) started.
kernel: 16384 bytes for swap cache allocated
kernel: Console: colour EGA+ 100x40, 8 virtual consoles
kernel: Serial driver version 4.00 with no serial options enabled
kernel: tty00 at 0x03f8 (irq = 4) is a 16450
kernel: tty01 at 0x02f8 (irq = 3) is a 16450
kernel: lp_init: lp1 exists, using polling driver
kernel: lp_init: lp2 exists, using polling driver
kernel: Microsoft BusMouse detected and installed.
kernel: tpqic02: IRQ 5, DMA 1, IO 0x300, IFC Archive, $Revision: 0.4.1.4
kernel: tpqic02: Settings: IRQ 5, DMA 1, IO 0x300, IFC Archive
kernel: tpqic02: waiting looong in rdstatus() -- drive dead?
kernel: tpqic02: finished waiting in rdstatus()
kernel: tpqic02: tp_sense: status: 81d0, error count: 0, underruns: 0
kernel: tpqic02: DMA buffers: 20 blocks, at address 0x1ad200 (0x1ad0d0)
kernel: tpqic02: tp_sense: status: 81d0, error count: 0, underruns: 0
kernel: Calibrating delay loop.. ok - 6.60 BogoMips
kernel: Checking 'hlt' ... ok
kernel: Configuring Adaptec at IO:330, IRQ 11, DMA priority 5
kernel: scsi0 : Adaptec 1542
kernel: scsi : 1 hosts.
kernel: Vendor: SyQuest Model: SQ5110 Rev: CHC
kernel: Type: Direct-Access ANSI SCSI revision:
kernel: Detected scsi disk sda at scsi0, id 3, lun 0
kernel: Vendor: NEC Model: CD-ROM DRIVE:841 Rev: 1.0
kernel: Type: CD-ROM ANSI SCSI revision:
kernel: Detected scsi CD-ROM sr1 at scsi0, id 4, lun 0
kernel: Vendor: LMS Model: CM214 Rev: 0.12
kernel: Type: CD-ROM ANSI SCSI revision:
kernel: Detected scsi CD-ROM sr2 at scsi0, id 5, lun 0
kernel: scsi : detected 2 SCSI cdroms 1 SCSI disk total.
kernel: Scd sectorsize = 2048 bytes
kernel: Scd sectorsize = 2048 bytes
kernel: Memory: 14908k/16384k available (596k kernel code, 384k reserved
kernel: Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
kernel: Swansea University Computer Society NET3.016
kernel: NET3 TCP/IP protocols stack v016
kernel: IP Protocols: ICMP, UDP, TCP
kernel: SLIP: version 0.7.5-NET3.014-NEWTTY (4 channels)
kernel: CSLIP: code copyright 1989 Regents of the University of Californ
kernel: eth0: WD80x3 at 0x280, 00 00 C0 02 BA 6A assigning address 0xd0
kernel: wd.c:v0.99-14 11/21/93 Donald Becker (becker@super.org)
kernel: Checking 386/387 coupling... Ok, fpu using irq13 error reporting
kernel: Linux version 1.1.39 (root@dc0hk-sys2) (gcc version 2.5.8) #1 Mo
kernel: Partition check:
kernel: sda: sda1
kernel: hda: identity unknown
kernel: hda: hda1 hda2 hda3 hda4
kernel: hdb: identity unknown
kernel: hdb: hdb1 hdb2 hdb3
kernel: VFS: Mounted root (ext2 filesystem) readonly.
kernel: Adding Swap: 29576k swap-space
named<EFBFBD>54<EFBFBD>: Ready to answer queries.
named<EFBFBD>54<EFBFBD>: sysquery: query() contains our address (dc0hk-sys2.ampr.org:4
login: ROOT LOGIN ON tty1
kernel: scsi : aborting command due to timeout : pid 26, scsi0, id 4,
lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
kernel: scsi : aborting command due to timeout : pid 31, scsi0, id 3,
lun 0 Test Unit Ready 00 00 00 00 00
kernel: scsi : aborting command due to timeout : pid 31, scsi0, id 3,
lun 0 Test Unit Ready 00 00 00 00 00
kernel: SCSI host 0 abort() timed out - reseting
kernel: Sent BUS DEVICE RESET to target 3
kernel: Sending DID_RESET for target 3
the only version that functions correctly is
1.1.36 i have tested all kernels last night
from 1.1.36 to 1.1.49 and this bug is a fixed
constant in its faults from 1.1.37 to 1.1.49
however this fault is not seen when i used
libc-...24 im now useing libc....26
if that helps.
Barry..
------------------------------
From: patrickr@cs.kun.nl (Patrick Reijnen)
Subject: Re: WARNING about shadow-mk package
Date: Tue, 6 Sep 1994 06:47:34 GMT
In <34gcci$l7q@stratus.skypoint.com> gaj@skypoint.com () writes:
>Larry Doolittle (doolitt@recycle.cebaf.gov) wrote:
>: Bauke Jan Douma (bjdouma@xs4all.nl) wrote:
>: : If you are about to update you shadow programs with the shadow-mk
>: : package by Mohan Kokal, think again.
>: : Here's the snippet from the Makefile in that package where login is
>: : installed:
>: : install -m4755 login $(LOGINDIR)/_login
>: : install -m4711 login.secure $(LOGINDIR)/login
>: : -rws--x--x 1 root staff 1124 Jul 13 10:36 login.secure <- ?
>: If Mohan is the cracker you suggest, what he would hate the most
>: would be publishing the login.secure program.
>: If Mohan is innocent, the fastest way to clear his neame would be
>: to publish the login.secure program.
>: Either way, I suggest you uuencode login.secure (if it's not an
>: ASCII shell script :-) and post it to these newsgroups. A lot
>: of people here are competent with unassemblers.
>: - Larry Doolittle doolittle@cebaf.gov
>Grand suggestion, Mr. Doolittle! I second the motion. Lets get a look
>at this code & find out just exactly what is going on here, if anything.
>: : bjdouma@xs4all.nl (Bauke Jan Douma)
On comp.os.linux.admin the source code of login.secure was promised to be posted,
so there is no more reaseon for blaming people and warnings against using shadow-mk.
In the article in there it is also described what login.secure exactly does, so
anyone should be happy now :-)
Patrick Reijnen
--
************************* Patrick Reijnen *************************
* Department of Computer Science, Catholic University of Nijmegen *
* Email: patrickr@{sci,cs}.kun.nl *
* WWW: http://{atlas,zeus}.cs.kun.nl:4080/homepage.html *
------------------------------
From: patrickr@cs.kun.nl (Patrick Reijnen)
Subject: Re: WARNING about shadow-mk package
Date: Tue, 6 Sep 1994 06:48:26 GMT
In <Cvoo0A.748@eecs.nwu.edu> jseng@news.eecs.nwu.edu (John S. Seng) writes:
NO MORE REASON to look at a binary. The source code will become available.
>Well you guys can take a look at it here:
>begin 711 login.secure
>M!P%D`,@#``!X````"`````````````````````````#H?P(``+@M````NP``
>M``#-@*-<"PE@BT0D"*,T"PE@#[<%V`,``%#H0`,``(/$!.A0````4.B6`P!@
>M6[@!````S8#K]Y"0D)"0D)"0D)"0D`````!9;W4@8V%N;F]T('-P96-I9GD@
>M82!N97<@:&]S="X*`"]B:6XO7VQO9VEN``````!5B>6#[`175E.+70CH`P$`
>M`(MU#(/[`7Y<ZU60D)"0D(/&!(L6@#HM=4:)US#`_+G_____\J[WT8G(2(/X
>M`78PQD("`(L&@'@!:'4DZ`,&`&!F@_AD=AEH5````&C4!PE@Z)X#`&!J`>C?
>M`@!@D)"02X7;?ZN+11!0BT4,4&AT````Z+4"`&`QP(UE\%M>7XGL7<,`4XL5
>M0`0``(/Z_W49,=*#/40$````=`ZX1`0``(/`!$*#.`!U]XG0A<!T&(T<A4`$
>M``"0D(L#_]"#P_R!^T`$``!U\5O#``````````````!3NQ`$``"#/1`$````
>M=`V0BP.#PP3_T(,[`'7T:!@!``#H"@``8(/$!%O#``````"#/=`#````=0_'
>M!=`#```!````Z+C____#````4[@!````BUPD",V`A<!]#/?8H^`#``"X____
>M_UO#``!3N%8```"+7"0(S8"%P'T,]]BCX`,``+C_____6\,``%.X!````(M<
>M)`B+3"0,BU0D$,V`A<!]#/?8H^`#``"X_____UO#`````````````%.X6P``
>M`(M<)`B+3"0,S8"%P'T,]]BCX`,``+C_____6\,O;&EB+VQD+G-O`#H@8V%N
>M)W0@;&]A9"!D>6YA;6EC(&QI;FME<B`G+VQI8B]L9"YS;R<*````````````
>M`(/L.%=64XMT)$B+7"1,@ST$!`````^$LP```,=$)$`@`/!B:$8"``#H(___
>M_X/$!(7`=%R+`XU\)!2^40(``/RY"@```/.E9J6%P'0=@#@`=`B0D$"`.`!U
>M^BL#4(L;4VH"Z`G___^#Q`QJ*HU$)!A0:@+H^/[__X/$#)!H@````.BJ_O__
>M@\0$Z_&0D)"0D&@8!```:/P#``"+3"1848L;4XU$)!Q0N`(```"%]G\%N`$`
>M``!0BT0D6/_0BTPD*%&+3"0H4>C5_O__@\0@A?9_#I"0:@#H5?[__X/$!.OT
>M6UY?@\0XPP"#[`1FBU0D"&:%TG4%NG(3``#9?"0"9HM$)`)F)<#P9HE$)`*)
>MT&8E/P]FBU0D`F8)T&:)1"0"V6PD`H/$!,,`;&EB8RYS;RXT`$1,3"!*=6UP
>M(#0N-'!L-````-,>Z_[4`P``````````````````````````````````K`,`
>M`+8#``````!@E`$$``#P"&`"````Q`,``.@#`````````0```/@_`&``````
>L`P```,@#```T!```^`,```````````````````````````````````0`````
>`
>end
Patrick Reijnen
--
************************* Patrick Reijnen *************************
* Department of Computer Science, Catholic University of Nijmegen *
* Email: patrickr@{sci,cs}.kun.nl *
* WWW: http://{atlas,zeus}.cs.kun.nl:4080/homepage.html *
------------------------------
From: dak@rama.informatik.rwth-aachen.de (David Kastrup)
Subject: Re: Any interest for DCF77 clock code?
Date: 6 Sep 1994 07:57:32 GMT
hm@ix.de (Harald Milz) writes:
>In comp.os.linux.development, Rob Janssen (rob@pe1chl.ampr.org) wrote:
>> When I want to sync only a single machine from my clock (which already
>> is interfaced to the RS232), can I configure xntp to leave out all the
>> network stuff? I don't need another large daemon in my 16M system...
>No, you need IP up and running. xntp handles the receivers as pseudo-
>hosts with addresses in the range 127.*.*.*. The daemon is not _that_
>large. The good news is that you can configure a single xntpd to handle
>both local receivers and remote NTP servers which is good to have
>backups in vital environments.
>> How difficult is it to configure this? (I have been on the newsgroup
>> for a while and I see a lot of problem discussion that extends way beyond
>> what I want to do...)
>Quite easy if you can read ;^)
So I can't. Sue me.
I am still trying to get the xntp3p3 source distribution to run. Main
problem currently: Linux kernel includes a kernel PLL which can be
properly adjusted (much superior to usual adjtime behaviour). The
kernel PLL code in the distrib (I think MCC 1.0+), however, calls
*system* calls of the SUN, only. So I will have to tweak sources
quite a bit to get optimal behaviour.
--
David Kastrup dak@pool.informatik.rwth-aachen.de
Tel: +49-241-72419 Fax: +49-241-79502
Goethestr. 20, D-52064 Aachen
------------------------------
From: shendrix@escape.widomaker.com (Shannon Hendrix)
Subject: Re: Future of linux -- the sequel
Date: Mon, 5 Sep 1994 17:55:21 GMT
pyeatt@cervesa.cs.colostate.edu (Larry Pyeatt) writes:
>In article <348vsp$68c@cesdis1.gsfc.nasa.gov>, becker@cesdis.gsfc.nasa.gov (Donald Becker) writes:
>|>
>|> That's just way more than a reasonable Linux box will cost.
>Define "reasonable." I defined reasonable to be "something similar to
>SGI Indy. You can't get that sort of performance with cheap parts.
Yes you can. The point was that the prices for the individual parts
listed in the Pentium system were far more than what they actually cost.
The $6400 Pentium listed would be more like $2700 to anyone that knows
where to look and I don't mean getting low-quality either.
>If I wanted to do any floating point, I would also want the SGI, since
>it puts Pentium to shame. Which brings us back to my main point, which
>is that a Linux system with a non-Intel processor would be a "good thing."
Sure, that would be great. But it will still be awhile before you will
get more bang for the buck from a non-Intel system.
--
csh
===========================================================================
shendrix@escape.widomaker.com | Linux and BSD
------------------------------
From: visigoth@olivier.dementia.org (John McClary Prevost)
Subject: Re: Kernel change summary 1.1.45 -> 1.1.46
Date: 06 Sep 1994 08:16:20 GMT
In article <344hma$4de@vishnu.jussieu.fr> card@masi.ibp.fr (Remy CARD) writes:
{...}
] I seem to remember reading that under BSD the immutable
] files can only be modified in single-user mode. Is it necessary to be in
] single-user to remove the immutable attribute as mentioned above? I think
] this would probably be a good idea. Thoughts?
In 4.4BSD, immutable and append-only flags can only be set and cleared
in single-user mode. It should be easy to make it work the same way in
Linux: add a system call which specifies the run-level and modify init to
call it when going into single user mode or multi user mode. The problem is
that Linux has many versions of init floatting around and such a solution
would require that everybody upgrades his init program.
In the current Linux implementation, only root can change the immutable
and append-only attribute on a file, in single user mode and in
multi user mode.
Hmm. Doesn't this decrease the usefulness of the append-only and
immutable bits? As I understood it, the rational for adding these
attributes was to make it harder for would-be system crackers to do
serious damage or remove traces of their work. (i.e., they break in,
hack root, try to remove entries from /var/adm/syslog, and discover
that they have to be in single user mode to do anything except append
to it.)
In any case, bravo on the new addition. :)
@-`-,-- John McClary Prevost
Systems Programmer, CS Facilities, Carnegie Mellon University
--
@-`-,-- John McClary Prevost
Systems Programmer, CS Facilities, Carnegie Mellon University
------------------------------
From: smattila@metz.une.edu.au (Sakari Mattila)
Crossposted-To: alt.os.linux,comp.os.linux.help,comp.os.linux.misc
Subject: Re: Fortran Compiler for Linux??
Date: 6 Sep 94 07:32:59 GMT
Is there any full Ada(tm) compilers for Linux ? Some Ada subset compiler
is on PrimeTime CDROM.
Sakari Mattila smattila@metz.une.edu.au VK2XIN, OH2AZG (Cis: 71307,1525)
P.O.Box u13 tel. +61 67 733752 --------------------------------
Armidale NSW 2351 ---------------------------
===================
------------------------------
From: davison@bruce.cs.monash.edu.au (Andrew Davison)
Crossposted-To: comp.os.linux.misc
Subject: Looking for term2.x applications
Date: 6 Sep 1994 08:01:34 GMT
Perhaps I'm missing something important, but has anyone compiled any of
the major applications (Mosaic, ncftp...) for term 2.x (specifically
2.0.4). If I try to run an app compiled for earlier term versions I get
the error "Connect: Invalid Argument".
If nobody's done it yet, I might set aside some time to do it.
Regards,
Andy
------------------------------
From: lendecke@namu09.gwdg.de (Volker Lendecke 29121346)
Subject: Re: Netware Client
Date: 06 Sep 1994 08:45:13 GMT
Hi!
In article <Cvno0E.IEC@aston.ac.uk> evansmp@mb5194.aston.ac.uk (Mark Evans) writes:
One problem with the Filesystem side of netware is that there dosn't appear
to be anything attached to a file which can be used to "fake" an inode number.
I do not think that this is really a problem. You might take a
look at my smbfs (sunsite.unc.edu:/pub/Linux/ALPHA/smbfs). smbfs
implements a client for WfW. The protocol used does not give you
a number to identify the file. You only have the path.
I studied the 'dynamics' of inodes quite a lot, and noticed the
following: You do not really need unique inode numbers for each
file on the complete filesystem. The only inode numbers which
must be unique are those currently in use. All others can be
allocated freely. A little exception to this scheme is a problem
which Philipp Auersperg detected. The getwd() function relies on
the inode numbers given back by readdir(). So you have to keep
the inode numbers of the complete path leading to each inode in
use unique and reproducable. (This is not implemented in
smbfs-0.2, but 0.3 will come soon.)
If I'm completely wrong, please tell me.
I think the main problem with a Novell client is the protocol
itself. All other things should be solvable.
Volker
+=================================================================+
! Volker Lendecke Internet: lendecke@namu01.gwdg.de !
! D-37081 Goettingen, Germany !
+=================================================================+
------------------------------
From: bartddgd@w202zrz (Bernd Bartmann)
Subject: Adaptec 2742AT
Date: 6 Sep 1994 10:07:16 GMT
Has anybody heard something about the new ADAPTEC 2742AT. Somebody told me
that is has a new controller chip (AIC7870). I would like to know if it works
with the LINUX 2742T driver from ftp.cpsc.ucalgary.ca and which new features
it has.
Bernd
<bartddgd@w250zrz.zrz.tu-berlin.de>
------------------------------
** 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: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU
You can send mail to the entire list (and comp.os.linux.development) via:
Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU
Linux may be obtained via one of these FTP sites:
nic.funet.fi pub/OS/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development Digest
******************************