Linux 2.2.18 almost...

Linux 2.2.18 almost...

[Alan Cox]

The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
I'll move it over tomorrow if nobody reports any horrors, missing files etc

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Tom Rini]

On Sat, Dec 09, 2000 at 11:00:41PM +0000, Alan Cox wrote:

> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> I'll move it over tomorrow if nobody reports any horrors, missing files etc

I haven't checked anywhere yet, but is there a changelog someplace?

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Michael Rothwell]

Alan Cox wrote:
> 
> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> I'll move it over tomorrow if nobody reports any horrors, missing files etc


Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"

can't find file to patch at input line 38909
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -u --new-file --recursive --exclude-from /usr/src/exclude
v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
|--- v2.2.17/arch/i386/vmlinux.lds	Wed May  3 21:22:13 2000
|+++ linux/arch/i386/vmlinux.lds	Sat Dec  9 21:23:21 2000
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Eyal Lebedinsky]

On Sat, Dec 09, 2000 at 11:00:41PM +0000, Alan Cox wrote:

> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> I'll move it over tomorrow if nobody reports any horrors, missing files etc

The text leading up to this was:
--------------------------
|diff -u --new-file --recursive --exclude-from /usr/src/exclude
v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
|--- v2.2.17/arch/i386/vmlinux.lds      Wed May  3 21:22:13 2000
|+++ linux/arch/i386/vmlinux.lds        Sat Dec  9 21:23:21 2000
--------------------------
File to patch: 
Skip this patch? [y] y
1 out of 1 hunk ignored

--
Eyal Lebedinsky		(eyal@eyal.emu.id.au)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Keith Owens]

On Sat, 09 Dec 2000 18:32:56 -0500, 
Michael Rothwell <rothwell@holly-springs.nc.us> wrote:
>Alan Cox wrote:
>> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
>> I'll move it over tomorrow if nobody reports any horrors, missing files etc
>
>Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
>
>can't find file to patch at input line 38909
>Perhaps you used the wrong -p or --strip option?
>The text leading up to this was:
>--------------------------
>|diff -u --new-file --recursive --exclude-from /usr/src/exclude
>v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
>|--- v2.2.17/arch/i386/vmlinux.lds	Wed May  3 21:22:13 2000
>|+++ linux/arch/i386/vmlinux.lds	Sat Dec  9 21:23:21 2000

Ignore that bit of the patch.  arch/i386/vmlinux.lds is generated from
arch/i386/vmlinux.lds.S and the latter is correctly patched.  The patch
for arch/i386/vmlinux.lds should not have been generated.

<rant size="small">
There are a lot of unnecessary inconsistencies between architectures.
Some archs generate vmlinux.lds from vmlinux.lds.S, some from
vmlinux.lds.in, some do not generate vmlinux.lds, it is shipped in the
tarball.  The inconsistencies make it difficult to distinguish between
files that are generated (not shipped, ignore for patching) and master
files (shipped in tar ball, check for patches).

There is a similar problem with oops text.  Each architecture needs an
oops report but each one prints it differently.

I implore architecture maintainers to adopt a common approach to
generated files, oops reports etc.  Remember that each arch needs to be
part of the common tar ball and has to operate with a single set of
make and other user space tools.
</rant>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Andre Hedrick]

On Sat, 9 Dec 2000, Michael Rothwell wrote:

> Alan Cox wrote:
> > 
> > The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> > I'll move it over tomorrow if nobody reports any horrors, missing files etc
> 
> 
> Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
> 
> can't find file to patch at input line 38909
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |diff -u --new-file --recursive --exclude-from /usr/src/exclude
> v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
> |--- v2.2.17/arch/i386/vmlinux.lds	Wed May  3 21:22:13 2000
> |+++ linux/arch/i386/vmlinux.lds	Sat Dec  9 21:23:21 2000

So do something silly like

cp linux/arch/i386/vmlinux.lds.S linux/arch/i386/vmlinux.lds

and you will see that the patch against the files are identical.

/linux/arch/i386/Makefile

arch/i386/vmlinux.lds: arch/i386/vmlinux.lds.S FORCE
        $(CPP) -C -P -I$(HPATH) -imacros $(HPATH)/asm-i386/page_offset.h -Ui386
arch/i386/vmlinux.lds.S >arch/i386/vmlinux.lds

All it is is a leftover file........

Cheers,

Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Alan Cox]

> > The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> > I'll move it over tomorrow if nobody reports any horrors, missing files etc
> 
> Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
> 
> can't find file to patch at input line 38909
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |diff -u --new-file --recursive --exclude-from /usr/src/exclude
> v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
> |--- v2.2.17/arch/i386/vmlinux.lds	Wed May  3 21:22:13 2000
> |+++ linux/arch/i386/vmlinux.lds	Sat Dec  9 21:23:21 2000

Now you know why I put it out as a pre26 first 8)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Tigran Aivazian]

my fault, my fault! Sorry, dontdiff updated on 

http://www.moses.uklinux.net/patches/dontdiff

the old one contained vmlinux.lds which would is good for kdb kernels
where vmlinux.lds is automatically generated at runtime.

Regards,
Tigran


On Sat, 9 Dec 2000, Michael Rothwell wrote:

> Alan Cox wrote:
> > 
> > The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> > I'll move it over tomorrow if nobody reports any horrors, missing files etc
> 
> 
> Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
> 
> can't find file to patch at input line 38909
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |diff -u --new-file --recursive --exclude-from /usr/src/exclude
> v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
> |--- v2.2.17/arch/i386/vmlinux.lds	Wed May  3 21:22:13 2000
> |+++ linux/arch/i386/vmlinux.lds	Sat Dec  9 21:23:21 2000
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Tigran Aivazian]

actually, if you do have a mention of vmlinux.lds in the actual patch then
I can't see how vmlinux.lds in dontdiff could have caused it? But it
needed updating (for this very reason) anyway...

On Sun, 10 Dec 2000, Tigran Aivazian wrote:

> my fault, my fault! Sorry, dontdiff updated on 
> 
> http://www.moses.uklinux.net/patches/dontdiff
> 
> the old one contained vmlinux.lds which would is good for kdb kernels
> where vmlinux.lds is automatically generated at runtime.
> 
> Regards,
> Tigran
> 
> 
> On Sat, 9 Dec 2000, Michael Rothwell wrote:
> 
> > Alan Cox wrote:
> > > 
> > > The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> > > I'll move it over tomorrow if nobody reports any horrors, missing files etc
> > 
> > 
> > Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
> > 
> > can't find file to patch at input line 38909
> > Perhaps you used the wrong -p or --strip option?
> > The text leading up to this was:
> > --------------------------
> > |diff -u --new-file --recursive --exclude-from /usr/src/exclude
> > v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
> > |--- v2.2.17/arch/i386/vmlinux.lds	Wed May  3 21:22:13 2000
> > |+++ linux/arch/i386/vmlinux.lds	Sat Dec  9 21:23:21 2000
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
> > 
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Vasil Kolev]

On Sat, 9 Dec 2000, Alan Cox wrote:

> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> I'll move it over tomorrow if nobody reports any horrors, missing files etc
> 
Will
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.18pre25/VM-global-2.2.18pre25-7.bz2
be included in the final 2.2.18 ? I found that it helped us - we had the
problem with 'trying to free pages' even with 2.2.18pre25 , but that
patch helped, now the machine is like ' rock stable' :)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Alan Cox]

> http://www.moses.uklinux.net/patches/dontdiff
> 
> the old one contained vmlinux.lds which would is good for kdb kernels
> where vmlinux.lds is automatically generated at runtime.

vmlinux.lds for 2.2 is dynamically generated. I should probably have used your
dontdiff ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Eddy]

did we lose ip=autoconf. I see dhcp and arp transmitting infinitely. I was
able to boot only after completely entering nfsroot= and ip= boot commands.

2.2.17 worked thusley.

root=/dev/nfs ether=0,0,eth0

2.2.18-pre26 works only

root=/dev/nfs
nfsroot=192.168.50.11:/tftpboot/191.168.50.2,rsize=8192,wsize=8192
ip=192.168.50.2:192.168.50.11:::Eddys486:eth0:off ether=0,0,eth0

for some reason

root=/dev/nfs ether=0,0,eth0   gives this result

Dec 10 22:48:24 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:24 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:26 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:26 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:29 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:29 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:36 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:36 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:47 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:47 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0

and

root=/dev/nfs ip=both ether=0,0,eth0     gives this result

Dec 10 22:50:52 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:50:52 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0
Dec 10 22:50:55 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:50:55 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0
Dec 10 22:51:00 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:51:00 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0
Dec 10 22:51:09 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:51:09 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Luca Montecchiani]

> did we lose ip=autoconf. I see dhcp and arp transmitting infinitely. I was 
> able to boot only after completely entering nfsroot= and ip= boot commands.
>
> 2.2.17 worked thusley. 
:

I didn't try with 2.2.18 yet but looking at the source (ipconfig.c)
seem that my patch wasn't accepted, you can give it a try :

http://boudicca.tux.org/hypermail/linux-kernel/2000week48/0213.html

hope this help,
luca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.2.18 almost...

[Alan Cox]

> root=/dev/nfs ip=both ether=0,0,eth0     gives this result
> 
> Dec 10 22:50:52 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
> Dec 10 22:50:52 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
> via eth0

Those are DHCP. 'both' is the old keywords for rarp and bootp. It now behaves
as it should do for compatibility. Try 'on' or 'all'


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/