on 06 Nov 99, Matthew Gregan wrote...inter alia
>
>On Fri, Nov 05, 1999 at 05:57:58PM +, John wrote:
>> I couldn't get this to work. My patches were in /usr/src and I got 'no
>> such file or directory', so I moved them into the kernel source dir.
>> and did -p0 thinking that should be right. N
On Fri, 5 Nov 1999, John wrote:
This may be a dumb question but are you linking your "kernel-sources-2.2.xx"
directory to "linux"? The kernel patch system expects a directory of "./linux".
> on 05 Nov 99, Matthew Gregan wrote...
>
> >
> >On Thu, Nov 04, 1999 at 06:07:31PM +, John wrote:
>
On Fri, Nov 05, 1999 at 05:57:58PM +, John wrote:
> I couldn't get this to work. My patches were in /usr/src and I got 'no
> such file or directory', so I moved them into the kernel source dir.
> and did -p0 thinking that should be right. No luck, so I did -p1 -
> there was action, but only 33
on 05 Nov 99, Matthew Gregan wrote...
>
>On Thu, Nov 04, 1999 at 06:07:31PM +, John wrote:
>
>> I've obtained patches 2 to 5 but now have a problem in applying them.
>> My /usr/src had only 'kernel-sources-2.2.1' (and the .tar.gz source which
>> I'm leaving there for the time being) until I mo
On Thu, Nov 04, 1999 at 06:07:31PM +, John wrote:
> I've obtained patches 2 to 5 but now have a problem in applying them.
> My /usr/src had only 'kernel-sources-2.2.1' (and the .tar.gz source which
> I'm leaving there for the time being) until I moved 'patch-2.2.xx' from the
> download site.
on 03 Nov 99, Matthew Gregan wrote...
>
>On Tue, Nov 02, 1999 at 05:18:00PM +, John wrote:
>
>> Kern.log says the kernel is not compiled for ppp (I've not used any
>> modules).
>>=20
>> My limited experience indicates, therefore, it must have to do with
>> the kernel - but what? I enabled 'netw
On Tue, Nov 02, 1999 at 05:18:00PM +, John wrote:
> Kern.log says the kernel is not compiled for ppp (I've not used any
> modules).
>
> My limited experience indicates, therefore, it must have to do with
> the kernel - but what? I enabled 'networking support' which seems the
> only relevant o
on 27 Oct 99, Brad wrote...inter alia,
>
>> If there is nothing sinister arising out of the above, I propose to apply
>> patches 2 to 7 and then on to 12.
>
>Go to 13, it fixes some problems with 12. In particular, i wouldn't bother
>to compile 8, 9, 10, 11, or 12, just do the patching.
>
I haven
on 27 Oct 99, Brad wrote...
>
I forget to mention in my earlier message that I had read
'Linux kernel release 2.2' and 'changes 2.2 kernels' notes.
Not sure I understood everything, but I ensured I had
the minimum requirements including ppp v2.3.5
(confirmed by 'pppd -v').
John.
on 28 Oct 99, Bryan K. Walton wrote...
>On Wed, 27 Oct 1999, Salman Ahmed wrote:
>
>> > "J" == John <[EMAIL PROTECTED]> writes:
>> J> Firstly, when I boot, I do not get an opportunity apply any
>> J> parameters - the reference to (I think) Peter Anwin and the boot
>> J> prompt do
-BEGIN PGP SIGNED MESSAGE-
On Thu, 28 Oct 1999, Bryan K. Walton wrote:
> On Wed, 27 Oct 1999, Salman Ahmed wrote:
>
> > > "J" == John <[EMAIL PROTECTED]> writes:
> > J> Firstly, when I boot, I do not get an opportunity apply any
> > J> parameters - the reference to (I think)
On Wed, 27 Oct 1999, Salman Ahmed wrote:
> > "J" == John <[EMAIL PROTECTED]> writes:
> J> Firstly, when I boot, I do not get an opportunity apply any
> J> parameters - the reference to (I think) Peter Anwin and the boot
> J> prompt do not appear - the word 'loading' and a fast mov
-BEGIN PGP SIGNED MESSAGE-
On Wed, 27 Oct 1999, John wrote:
> I have upgraded from 2.0.36 to 2.2.1 without appearing to cause
> any great disasters, and with surprising results. At present, I boot
> from a floppy and it now takes 36 secs to reach the log-in screen
> instead of 3mins 50 se
You can hold down the shift or alt keys as lilo loads to be at the boot:
prompt. However, to get the boot prompt back do the following:
edit your /etc/lilo.conf
right before the image=/vmlinuz line add the following line:
prompt
Save the file and exit the editor. Run liloconfig and answer yes a
-BEGIN PGP SIGNED MESSAGE-
On Mon, 18 Oct 1999, John wrote:
> >Are you sure you're not confusing the kernel headers in /usr/include/linux
> >with the actual kernel source tree that is usually placed in
> >/usr/src/linux?
> >
> I may well be, but what is certain is that /usr/src contains o
on 17 Oct 99, Brad wrote...(inter alia)...
>
>Please put plank lines between the quoted text and replies, it makes things
>easier to find
>
>On Sun, 17 Oct 1999, John wrote:
>
>> >> According to the Howto the kernel should be in /usr/src/linux - it
>> >> seems to be in /usr/include/linux/2.0.36
-BEGIN PGP SIGNED MESSAGE-
Please put plank lines between the quoted text and repies, it makes things
easier to find
On Sun, 17 Oct 1999, John wrote:
> I've now discovered that my Debian CD-ROM contains kernel-source-
> 2.2.1 under the devel directory. Can I not use this? I'd like to avo
on 16 Oct 99, Brad wrote...
>
>On Sat, 16 Oct 1999, John wrote:
>
>> It seems an opportunity to upgrade to 2.2.7, and etc, etc
>
>i'd recommend 2.2.12 (the latest), although 2.2.7 might be my second
>choice.
>
I've now discovered that my Debian CD-ROM contains kernel-source-
2.2.1 under the devel
Try using dselect to select the kernel-source you want as well as "kernel
package" which has the scripts for a Debian-style kernel install. Read the
docs with "kernel package".
I've tried both SuSe and RedHat and find Debian easier to get around in--most
of the time.
Eric Wolven
-BEGIN PGP SIGNED MESSAGE-
On Sat, 16 Oct 1999, John wrote:
> It seems an opportunity to upgrade to 2.2.7, and gain experience
> - I think I understand the Howto and other literature - but now I
> come to plan the work, things are not straightforward.
i'd recommend 2.2.12 (the latest),
20 matches
Mail list logo
