Hi,
On Sun, 03.05.2009 at 11:00:02 -0700, J.C. Roberts wrote:
I don't see how 'set image ...' is a hack, nor how it would be specific
to i386 and amd64.
> The new installer (destined for 4.6) in snapshots *already* picks the
This makes it harder to move a set of already-installed disks to a
different machine, a facility which I value for fast recovery.
> On all archs, when you wish to boot to a different on-disk kernel you
I dislike moving kernels around, but editing boot.conf is ok.
> When you treat i386\amd64 differently with the boot.conf kernel
Hmmm... Can you please point me to some reading about the upcoming
"non-flawed system design"?
> Now, let's say you are using the /etc/boot.conf hack to boot to bsd.mp,
This problem imho *only* arises as a consequence due to installing the
new kernel in the wrong place. Would it have been installed in /bsd.mp,
nothing would have gone wrong. You could even opt to overwrite /bsd.mp
in that case, too, to make sure that you are backwards-compatible.
Kind regards,
--Toni++
| monstr | [PATCH 27/56] microblaze_v2: support for a.out |
| Andrew Morton | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| mdew . | Re: [patch] CFS scheduler, v4 |
| Gabriel C | Re: 2.6.21-mm1 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Willy Tarreau | Re: [PATCH] tcp: splice as many packets as possible at once |
| Linus Torvalds | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
