Linux-Development-Sys Digest #73, Volume #7 Thu, 19 Aug 99 20:14:16 EDT
Contents:
Re: Adding a non-standard Parallel Port ("Norm Dresner")
Re: Why so inefficient source RPM's ?? (Peter Mutsaers)
Re: most efficient way to zero out a partition? (Ronald Cole)
Re: most efficient way to zero out a partition? (Ronald Cole)
Re: Importance of TX errors? (pcmcia) (Allin Cottrell)
Re: Troll (was: why not C++?) (Rainer Joswig)
X Windows developement (Tranceport)
IEEE 802 and Ethernet Packet Encapsulations in Linux ("Keith J. Jones")
Re: most efficient way to zero out a partition? (Juergen Heinzl)
Help!! LILO booting stopping on LI (Madhu Bandireddi)
Re: threads (Andi Kleen)
Re: WFQ inside linux (Chris Butler)
Re: Help with Glibc 2.0 Installation! (Raymonds Doetjes)
Re: Help!! LILO booting stopping on LI (Ronald Cole)
----------------------------------------------------------------------------
From: "Norm Dresner" <[EMAIL PROTECTED]>
Subject: Re: Adding a non-standard Parallel Port
Date: 19 Aug 1999 19:21:54 GMT
Alas, I'm using the 2.0.36 kernel. Can I still do this?
Norm
Daniel Robert Franklin <[EMAIL PROTECTED]> wrote in article
<drf03.935016307@wumpus>...
> "Norm Dresner" <[EMAIL PROTECTED]> writes:
>
> >I need to add to a Linux box a parallel port that has been hacked-up to
be
> >at a non-standard address. Where in the kernel source code do I go to
add
> >this address to the list of possible parallel ports?
>
> You shouldn't need to recompile. Assuming you are using 2.2.x with
parport
> compiled into the kernel, then add this to /etc/lilo.conf and re-run
lilo:
>
> append="parport=0xYYY,Z"
>
> where YYY is the I/O address in hex and Z is the IRQ. If you use loadlin
> add the bit between the quotes to your loadlin command line.
>
> Cheers,
>
> - Daniel
> --
>
****************************************************************************
**
> * Daniel Franklin - Postgraduate student in Electrical Engineering
> * [EMAIL PROTECTED]
>
****************************************************************************
**
>
------------------------------
From: Peter Mutsaers <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc,linux.redhat.rpm
Subject: Re: Why so inefficient source RPM's ??
Date: 19 Aug 1999 08:18:34 +0200
>> "JK" == Johan Kullstam <[EMAIL PROTECTED]> writes:
JK> what if the builder doesn't offer a patch. you want to roll up a new
JK> rpm from the newer sources and wish to borrow from past rpm spec
JK> files. you have to download the source twice. it's annoying.
JK> i want a no-source rpm. i want the source-less rpms to be found on
JK> ftp sites. the application maintainer cannot change this situation
JK> one way or another. (unless you are talking about the maintainer of
JK> the rpm application only.)
Indeed, that's just what I meant. I'm just surprised that no-source
rpm's aren't standard.
And the no-source RPM should also (in the spec-file) give a list of
URL's where the original tarball can be found. Then it can be
retrieved automatically if necessary, and stored in a cache
directory. This is more or less how FreeBSD works: the first time you
build a port the tarball is put in /usr/ports/distfiles, subsequent
times (assuming the port is still based on the same original release)
the tarball from /usr/ports/distfiles is automatically reused.
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] | the Netherlands | what I'm doing.
------------------------------
From: Ronald Cole <[EMAIL PROTECTED]>
Subject: Re: most efficient way to zero out a partition?
Date: 19 Aug 1999 12:39:59 -0700
[EMAIL PROTECTED] (Christopher Browne) writes:
> I'd go with
> dd if=/dev/zero of=/dev/sda10 bs=64k
> which will chew up 65536 bytes at a shot.
>
> It's small enough that it's not liable to have any ill effects on
> memory consumption. It's large enough that there shouldn't be nearly
> as much overhead as with the 512 bytes that I suspect it defaults to.
Actually, I just discovered that any bs greater than dd's defaults
will lock up RedHat's linux-2.2.5-22smp.
--
Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
Ronald Cole <[EMAIL PROTECTED]> Phone: (760) 499-9142
President, CEO Fax: (760) 499-9152
My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5
------------------------------
From: Ronald Cole <[EMAIL PROTECTED]>
Subject: Re: most efficient way to zero out a partition?
Date: 19 Aug 1999 12:45:13 -0700
[EMAIL PROTECTED] (H. Peter Anvin) writes:
> Using "cat" is probably somewhat faster than "dd"... however, covering
> the entire disk surface is what takes most of the time.
If the kernel can optimize the buffering for the devices, then cat it
is. I discovered that dd with any blocksize greater than the default
locks up RedHat's linux-2.2.5-22smp.
--
Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
Ronald Cole <[EMAIL PROTECTED]> Phone: (760) 499-9142
President, CEO Fax: (760) 499-9152
My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5
------------------------------
From: Allin Cottrell <[EMAIL PROTECTED]>
Subject: Re: Importance of TX errors? (pcmcia)
Date: Thu, 19 Aug 1999 16:01:18 -0400
Pat Crean wrote:
>
> You need to update net-tools --- your old ifconfig is misinterpreting the
> some newer data structures.... see the Changes file in
> /usr/src/linux/Documentation.....
That is not the problem. I'm using net-tools 1.52.
--
Allin Cottrell
Department of Economics
Wake Forest University, NC
------------------------------
From: [EMAIL PROTECTED] (Rainer Joswig)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.misc
Subject: Re: Troll (was: why not C++?)
Date: Thu, 19 Aug 1999 20:51:07 +0200
In article <[EMAIL PROTECTED]>, Stephan Houben <[EMAIL PROTECTED]>
wrote:
> [EMAIL PROTECTED] (Rainer Joswig) writes:
>
>
> > A Lisp users says: I don't care what language the kernel
> > is written in, as long as it is Lisp.
>
> IMHO, a supposedly "general purpose OS" should do more than
> just please the Lisp users. (Any estimates of the precentage
> of the programming community which consider themselves
> Lisp users?)
Sure, you could use Pascal, C, Prolog, Ada and Fortran
on a Lisp Machine. What was your point?
> > The difference between a Lisp machine and a Linux
> > system is huge. The Lisp Machine has an open, incrementally
> > changeable and dynamic OS. The OS is written in a
> > pure OOP style. That means that things like
> > IP-Packets or Processes are objects. And operations
> > on them are implemented as methods.
>
> But all this could be provided by a Lisp library which interfaces
> with the underlying OS.
Unfortunately the underlying OS then is written in a
low-level langauge. You won't get the dynamic behaviour.
You won't get the expressivity of Lisp. You won't
get the object-oriented structuring, ...
> Have the Linux kernel start up a Lisp
> interpreter
Btw., although the Lisp machine had an interpreter, the
interpreter was only used during development. All
the code was/is compiled to native code. Today's
Lisp systems have optimizing native code compilers
to the usual RISC or CISC chips.
> directly after booting and presto: your Lisp OS is
> ready to run. You can then write a GUI or whatever in Lisp and
> have *that* executed on startup.
Yeah, but the OS is not written in Lisp - this is a big difference.
> Of course, the advantage that this gives you from just running
> a Lisp interpreter from the shell is debatable. At least, you can
> pretend you're not using Linux...
I have that today. But on my Lisp machine I type
Edit Definition process:timer
and I'm editing the source code for timed processes.
I can write subclasses of that with different behaviours,
etc. There is nothing between my classes and the
hardware. The Lisp Machine is basically a huge
object machine.
> Now I think of it, there's also a C++ interpreter floating around
> somewhere. So the same technique could be used to create a "C++ OS",
> thereby answering the question of the original poster.
The point of a Lisp OS is not to have an interpreter. I'm
a Lisp developer and I have never had that much
need to use an interpreter in the last ten years. Instead
all my code is incrementally compiled.
A Lisp system is the ultimate in dynamic changeability
and debuggability. Unless you have **live** debugged stuff
like NFS mounts, you won't hardly understand what
this stuff is about. It is the ultimate hacker's machine.
All code a keypress away, tools tightly integrated,
excellent integrated documentation facilities, not the multitude of
stupid scripting languages, a real graphical and
mousable command interpreter, reusable OS facilities,
on the fly compilation, on the fly updating of change
objects, ...
------------------------------
From: Tranceport <[EMAIL PROTECTED]>
Subject: X Windows developement
Date: Thu, 19 Aug 1999 19:50:53 GMT
I have to develop the X windows system and I would really appreciate
suggestions regarding books or web sites about this.
I said developing X window not developing WITH X window. It's not a
mistake. I do have to develop a part of the X system and I have to find
out how to go about it ASAP.
Anybody knows a good book for developing X?
Thanks in advance..
Trance
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "Keith J. Jones" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,alt.linux,comp.unix.programmer
Subject: IEEE 802 and Ethernet Packet Encapsulations in Linux
Date: Thu, 19 Aug 1999 16:06:07 -0400
Could anyone shed some light on the issue of the IEEE 802 and the
Ethernet encapsulation in linux? I can only find support for the
Ethernet encapsulation in the kernel source. Is 802 still being used?
Does linux support it? Where is 802 being used at?
Thank you for your time and help!
Keith J. Jones
--
Keith J. Jones - Software Development Team Leader
Sytex, INC. - 9891 Broken Land Pkwy, Suite 304, Columbia, MD 21060
Phone: 410-312-9114 Mobile: 410-458-2875 Fax: 410-312-9118
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Subject: Re: most efficient way to zero out a partition?
Date: Thu, 19 Aug 1999 20:08:02 GMT
In article <[EMAIL PROTECTED]>, Eric Hegstrom wrote:
>Speaking of wasting bandwith ....
>
>Ronald Cole wrote:
>
>> If you don't know the answer, then please don't waste everybody's time
>> and bandwidth.
>
>
>Ok, so now I'm guilty to.
We know where the corner is 8)
Juergen
--
\ Real name : J�rgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
------------------------------
From: Madhu Bandireddi <[EMAIL PROTECTED]>
Subject: Help!! LILO booting stopping on LI
Date: Thu, 19 Aug 1999 17:08:40 -0400
This is a multi-part message in MIME format.
==============AE93FAF0434826EE32BBD50E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I have Redhat 6.0 installed on Pentium with Adaptec 2940 SCSI and SCSI
disks. The system was working fine...booting
from hard disk until I messed it up. I tried to upgrade the Kernel to
2.2.11 from 2.2.5-15. I compiled the new kernel
and moved it /boot as vmlinux and then edited /etc/lilo.conf and ran
lilo. Eversince I did whenever I reboot it hangs on the
way up at the lilo prompt with just "LI" printed on the screen. I
reverted back to the original lilo.conf and repointed the links under
/boot to the old 2.2.5-15 files and ran lilo again. But I am still not
able to boot from the hard disk.
Here is the lilo.conf file:
===================================
boot=/dev/sda1
map=/boot/map
install=/boot/boot.b
prompt
timeout=10
image=/boot/vmlinuz-2.2.5-15
label=linux
root=/dev/sda8
initrd=/boot/initrd-2.2.5-15.img
read-only
=======================================
Here are the files under /boot:
lrwxrwxrwx 1 root root 19 Aug 19 16:47 System.map ->
System.map-2.2.5-15
-rw-r--r-- 1 root root 175084 Aug 19 14:54 System.map-2.2.11
-rw-r--r-- 1 root root 186704 Apr 19 23:16
System.map-2.2.5-15
-rw-r--r-- 1 root root 204280 Mar 1 13:46 System.map.old
-rw-r--r-- 1 root root 512 Aug 19 15:38 boot.0801
-rw-r--r-- 1 root root 4544 Apr 13 00:19 boot.b
-rw-r--r-- 1 root root 601021 Mar 19 18:44 bzImage
-rw-r--r-- 1 root root 612 Apr 13 00:19 chain.b
-rw-r--r-- 1 root root 329871 May 23 08:44
initrd-2.2.5-15.img
drwxr-xr-x 2 root root 12288 Feb 18 1999 lost+found/
-rw------- 1 root root 13312 Aug 19 16:48 map
lrwxrwxrwx 1 root root 20 May 23 08:28 module-info ->
module-info-2.2.5-15
-rw-r--r-- 1 root root 11773 Apr 19 23:16
module-info-2.2.5-15
-rw-r--r-- 1 root root 620 Apr 13 00:19 os2_d.b
-rwxr-xr-x 1 root root 1469282 Apr 19 23:16 vmlinux-2.2.5-15*
lrwxrwxrwx 1 root root 16 Aug 19 16:46 vmlinuz ->
vmlinux-2.2.5-15*
-rw-r--r-- 1 root root 672607 Mar 1 13:47 vmlinuz-2.2.1.old
-rw-r--r-- 1 root root 605614 Aug 19 14:54 vmlinuz-2.2.11
-rw-r--r-- 1 root root 617288 Apr 19 23:16 vmlinuz-2.2.5-15
-rw-r--r-- 1 root root 672606 Mar 1 13:46 vmlinuz.old
Can someone help me out of ignorance here?
I greatly appreciate your help.
Thanks
Madhu Bandireddy
==============AE93FAF0434826EE32BBD50E
Content-Type: text/x-vcard; charset=us-ascii;
name="bandired.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Madhu Bandireddi
Content-Disposition: attachment;
filename="bandired.vcf"
begin:vcard
adr;dom:;;5, Wood Hollow Road;Parsippany;NJ;08807;
n:Bandireddy;Madhu
x-mozilla-html:FALSE
org:Philips Consumer Communications
version:2.1
email;internet:[EMAIL PROTECTED]
title:Systems Administrator
tel;fax:973-581-3338
tel;work:973-581-3731
x-mozilla-cpt:;0
fn:Madhu Bandireddy
end:vcard
==============AE93FAF0434826EE32BBD50E==
------------------------------
From: Andi Kleen <[EMAIL PROTECTED]>
Subject: Re: threads
Date: 18 Aug 1999 21:35:08 +0200
[EMAIL PROTECTED] (Kaz Kylheku) writes:
> On Wed, 18 Aug 1999 09:42:08 -0600, Bill Burris <[EMAIL PROTECTED]> wrote:
> >This points out another weakness in Windows. Of the 4G address space for
> >each process the upper 2G is shared by all applications. An easy way to use
> >shared libraries, and inter-process communications, but a way for bugs in
> >one process to affect another.
>
> Some upper memory is also shared in Linux. but it's a protected kernel space.
> It's only accessible to a process that has trapped into the kernel via an
> exception, interrupt or system call.
Actually all physical memory is mapped all the time inside the Linux kernel
ATM. This allows some neat optimizations, for example in Linux a wait queue
is a light weight data structure on the stack, while on most other Unixes
you need slow & clumpsy dynamic allocation. This works because it is always
mapped.
Most of the proposed patches for big memory (4GB on x86) support will
change this of course. The big memory options in newer 2.2 already give
you a trade off between physical memory support and max process space.
-Andi
--
This is like TV. I don't like TV.
------------------------------
From: [EMAIL PROTECTED] (Chris Butler)
Crossposted-To: comp.os.linux.networking
Subject: Re: WFQ inside linux
Date: 19 Aug 1999 22:40:39 +0100
[comp.os.linux.development.system - Thu, 19 Aug 1999 05:00:52 GMT]
* Anshul wrote *
> I am suppose to incorporate WFQ packet scheduling algorithm in the linux
> os. Can any one point me to the documentation of networking
> stuff in linux. I read the lhg & some tutorial but they doesn't
> seems to be of much help as i want to know the implementation of
> the networking protocol and prevailing scheduler.
Have you read the comments at the top of /usr/src/linux/net/sched/sched_api.c?
--
Chris Butler
<[EMAIL PROTECTED]>
------------------------------
From: Raymonds Doetjes <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Help with Glibc 2.0 Installation!
Date: Fri, 20 Aug 1999 00:06:07 +0200
Looks like your libs are still out of date or to new.
But perhaps it is usefull to upgrade your box with a new version of SuSE,
RedHat or Debian wich already use glibc2.1 wich is starting to be standard
by now.
Raymond
Kenny Zhu Qili wrote:
> Hi there. I was installing glibc 2.06 when I had the following error:
>
> spinlock.h: In function `acquire':
> In file included from manager.c:32:
> spinlock.h:20: warning: implicit declaration of function `__sched_yield'
> manager.c: In function `pthread_start_thread':
> manager.c:162: warning: implicit declaration of function
> `__sched_setscheduler'
> manager.c: In function `pthread_handle_create':
> manager.c:229: warning: implicit declaration of function
> `__sched_getscheduler'
> manager.c:230: warning: implicit declaration of function
> `__sched_getparam'
> manager.c:241: warning: implicit declaration of function `__clone'
> manager.c:242: `CLONE_VM' undeclared (first use in this function)
> manager.c:242: (Each undeclared identifier is reported only once
> manager.c:242: for each function it appears in.)
> manager.c:242: `CLONE_FS' undeclared (first use in this function)
> manager.c:242: `CLONE_FILES' undeclared (first use in this function)
> manager.c:242: `CLONE_SIGHAND' undeclared (first use in this function)
> make[2]: *** [/tmp/glibc-2.0.6/compile/linuxthreads/manager.o] Error 1
> make[2]: Leaving directory `/tmp/glibc-2.0.6/linuxthreads'
> make[1]: *** [linuxthreads/others] Error 2
> make[1]: Leaving directory `/tmp/glibc-2.0.6'
> make: *** [all] Error 2
>
> Looks like my pthread lib has some problem. But I have already installed
> linuxpthread 0.3.71 and I have used it without problem. Plus I have
> included linuxthreads add-on with the compilation. Could someone tell me
> what went wrong? Thanks.
>
> Kenny
------------------------------
From: Ronald Cole <[EMAIL PROTECTED]>
Subject: Re: Help!! LILO booting stopping on LI
Date: 19 Aug 1999 16:02:27 -0700
Madhu Bandireddi <[EMAIL PROTECTED]> writes:
> I have Redhat 6.0 installed on Pentium with Adaptec 2940 SCSI and SCSI
> disks. The system was working fine...booting
> from hard disk until I messed it up. I tried to upgrade the Kernel to
> 2.2.11 from 2.2.5-15. I compiled the new kernel
> and moved it /boot as vmlinux and then edited /etc/lilo.conf and ran
> lilo. Eversince I did whenever I reboot it hangs on the
> way up at the lilo prompt with just "LI" printed on the screen. I
> reverted back to the original lilo.conf and repointed the links under
> /boot to the old 2.2.5-15 files and ran lilo again. But I am still not
> able to boot from the hard disk.
> root=/dev/sda8
> Can someone help me out of ignorance here?
I'll bet that you installed the bootstrap loader on /dev/sda8 and that
your /dev/sda8 starts over the 1024 cylinder limit.
--
Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
Ronald Cole <[EMAIL PROTECTED]> Phone: (760) 499-9142
President, CEO Fax: (760) 499-9152
My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5
------------------------------
** 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
******************************
