[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

lchown and the 2.1 kernel (was: what do you think?)



I'm a little late stepping in to this, I know (I only get to read the archive)
but about this whole chown/lchown thing...

In the 2.1.81 kernel, chown was changed to follow symlinks, lchown was introduced.
At 2.1.86, the syscall number of chown and lchown was reversed, so that
old binaries and libs got the old behaiviour, BUT THIS CHANGE WAS MADE IN
THE X86 ARCH ONLY! Our beloved Alpha arch is still the reverse of the
x86 world, which breaks dpkg etc.

I reversed the two on my kernel, and dpkg works fine. Patch is below.

So, what, are we gonna keep the "new" way, or are we gonna do like the X86
guys?


diff -u --recursive --new-file linux.old/arch/alpha/kernel/entry.S linux/arch/alpha/kernel/entry.S
--- linux.old/arch/alpha/kernel/entry.S	Tue Sep  8 23:20:41 1998
+++ linux/arch/alpha/kernel/entry.S	Wed Sep 30 21:03:50 1998
@@ -772,7 +772,7 @@
 	.quad sys_fchdir
 	.quad sys_mknod
 	.quad sys_chmod				/* 15 */
-	.quad sys_chown
+	.quad sys_lchown
 	.quad osf_brk
 	.quad alpha_ni_syscall
 	.quad sys_lseek
@@ -965,7 +965,7 @@
 	.quad sys_semget			/* 205 */
 	.quad sys_semop
 	.quad osf_utsname
-	.quad sys_lchown
+	.quad sys_chown
 	.quad osf_shmat
 	.quad sys_shmctl			/* 210 */
 	.quad sys_shmdt
diff -u --recursive --new-file linux.old/include/asm-alpha/unistd.h linux/include/asm-alpha/unistd.h
--- linux.old/include/asm-alpha/unistd.h	Sun Sep  6 13:06:04 1998
+++ linux/include/asm-alpha/unistd.h	Thu Oct  1 00:55:23 1998
@@ -17,7 +17,7 @@
 #define __NR_fchdir		 13
 #define __NR_mknod		 14
 #define __NR_chmod		 15
-#define __NR_chown		 16
+#define __NR_lchown		 16
 #define __NR_brk		 17
 #define __NR_osf_getfsstat	 18	/* not implemented */
 #define __NR_lseek		 19
@@ -186,7 +186,7 @@
 #define __NR_semget		205
 #define __NR_semop		206
 #define __NR_osf_utsname	207
-#define __NR_lchown		208
+#define __NR_chown		208
 #define __NR_osf_shmat		209
 #define __NR_shmctl		210
 #define __NR_shmdt		211


Reply to: