lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31286.1193785564@redhat.com>
Date:	Tue, 30 Oct 2007 23:06:04 +0000
From:	David Howells <dhowells@...hat.com>
To:	"Suzuki Takashi" <suzuki.takashi@...il.com>
Cc:	dhowells@...hat.com, torvalds@...l.org, akpm@...ux-foundation.org,
	linux-am33-list@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #2]

Suzuki Takashi <suzuki.takashi@...il.com> wrote:

> But is there any utility that depends on that uname says mn10300?

autoconf:-)

> I know existing developers should learn the arch name change.
> But how many developers?

I don't know.  MEI probably does.

> That's the point. They must always be told or consult the documentations.
> Don't you think an arch name should be natural?

Can you guarantee there won't be any non-AM33 variants of mn10300 that need
supporting?  An AM34, perhaps?

So basically, the toolchain name should change from am33 to mn10300 by your
argument.

> People need not to be told on other, at least major, archs.

There are plenty of other complications for other archs, such as 32-bit vs
64-bit, LE vs BE and other more subtle variants, so your argument isn't that
compelling.

> - growing new developers will have difficulties in understanding arch
> name difference,

You tell them, they then know.  It doesn't take long.  Standard practice, I
suspect, will involve giving them the toolchains and basic root filesystems.

The discrepancy has been around for years, and I suspect it's not going to
change now.  If MEI ask, I will change it.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ