Re: kernel-headers-2.0.32 vs. kernel-headers-2.0.33

To: Manoj Srivastava <srivasta@datasync.com>
Cc: Tamas Papp <tpapp@students.ahuwc.k12.nm.us>, debian-user@lists.debian.org
Subject: Re: kernel-headers-2.0.32 vs. kernel-headers-2.0.33
From: George Bonser <grep@oriole.sbay.org>
Date: Mon, 13 Apr 1998 00:23:41 -0700 (PDT)
Message-id: <Pine.LNX.3.96.980413002142.15209g-100000@calvin.shorelink.com>
In-reply-to: <87g1jifgfg.fsf@tiamat.datasync.com>

On 13 Apr 1998, Manoj Srivastava wrote:

> 
> 	Please do not use force unless you understand what you are
>  doing, and also understand that others may not be able to help
>  recover a hosed system.

Agreed, and thank you for the information. I now understand how the kernel
headers used for glibc have been "decoupled" from the kernel include
headers. 

George Bonser

If I had a catchy quip, it would be here.

http://www.debian.org
Debian/GNU Linux ... the maintainable operating system.

--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

References:
- Re: kernel-headers-2.0.32 vs. kernel-headers-2.0.33
  - From: Manoj Srivastava <srivasta@datasync.com>

Prev by Date: problems with x links in frozen
Next by Date: Re: kernel-headers-2.0.32 vs. kernel-headers-2.0.33
Previous by thread: Re: kernel-headers-2.0.32 vs. kernel-headers-2.0.33
Next by thread: Re: kernel-headers-2.0.32 vs. kernel-headers-2.0.33
Index(es):
- Date
- Thread