I suppose, the crashing only happens in 32bit mode? Because I sure don't seem to have any issues at all in Solaris (running x64).
root at bigmclargehuge:~ > zoneadm -z centos5 boot root at bigmclargehuge:~ > zlogin centos5 [Connected to zone 'centos5' pts/3] Last login: Sun Dec 2 13:11:12 from zone:global [root at centos5 ~]# export PS1="$0-\\V > " -bash-3.1.17 > -mg > I'm not sure why CentOS 5 is listed as 'working' on the Linux 2.6 page. As > far as I can tell, that's simply not possible. Ed, any idea how CentOS 5 > earned a reputation for working here? > > The gory details: Solaris allocates the stack with the top at 0x8048000. > Luckily for us, on CentOS 3, binaries are built to be installed at > 0x8048000 - right after the stack. In CentOS 4 and 5, it looks like most > binaries are built to be loaded at 0x8047000. So, the process's stack is > clobbered by the first page of the binary. > > For whatever reason, the ksh in CentOS 5 was built to be loaded at > 0x8050000 - which is safely above the stack. (use 'elfdump' on the > binary if this is at all interesting to you. :) > > I don't have an Ubuntu zone handy, but since I've heard multiple success > stories, I assume their binaries go someplace less hazardous. > > I'm trying to figure out a clean way to solve this problem now.
