Hi,

>>>>> On Tue, 12 Feb 2002 13:19:51 -0600 (CST), Frederick Bruckman <fredb@immanent.net> said:

Frederick> On Wed, 13 Feb 2002, Takeshi Shibagaki wrote:
>> But I took a method which is different above one.

Frederick> You built to a destdir, then installed it. How about this:
Frederick> 	./build.sh -D destdir -R releasedir -m platform

Yes, this is almost same thing, but I'm using make command because I'm
experienced in make command more than build.sh command.

Frederick> then boot and install with the install kernel you've created?

No, I don't use install kernel. I use generic kernel with "options
EXEC_ELF32" and "options COMPAT_AOUT_M68K". I booted it and executed
"make install" into source directory.

# I made /emul/aout before above.

I think an install kernel is not necessary in the case of upgading an
installed system, but when ones install new system, it will be needed.

Frederick> There are users (developers, portmasters) with great expertise in
Frederick> particular areas, who have never had to be familiar with the new build
Frederick> system, so yes, I think we should help these people.

Yes, I understand. That's right.

fredb> It would also be weak to tell people to use a binary snapshot, when
fredb> "sysinstall" is known to be buggy (though the bug shouldn't affect
fredb> upgrades). Does mac68k sysinstall have the a.out -> ELF magic, yet?

>> ??? Does it relate between upgrading elf from a.out and sysinst?

Frederick> Yes, it does. Folks who have tracking current on mac68k will not be able
Frederick> to do it as they have been doing it. If you say, "this is how to upgrade
Frederick> from source, but you really should just use a snapshot", then
Frederick> "sysinstall" had better work.

I don't know what do you expect to sysinst. I think it is unnecessary
to upgrade elf from source and binary snapshot...

I expect to sysinst, which has partitioning function and... I don't
have any other idea. Other function is a simplified install solution?

# We should not write NetBSD disklabel because MacOS don't boot up...

Frederick> There were no reproducible procedures in place to convert from a.out to
Frederick> ELF when i386 switched, so I suppose it's not essential. The whole thing
Frederick> seemed rushed to me, though. (I tracked the release branch all the way
Frederick> to 1.5/i386/a.out before switching, myself.)

Maybe, I think back to a.out are not considered in other ports, but do
you need an environment which could always make a.out binary release set?

# I understand you don't also need it from above sentence...

Takeshi Shibagaki
ie9t-sbgk@asahi-net.or.jp