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. Nils On Wed 12/05/07 at 14:04 PM, beardal at unixservice.com.au wrote: > Hardware: AMD64 Dual Core 4600, 4G ram, 300G disk > AMD64 Single core 3000, 1.5Gb ram, 160Gb disk > > So far, Build 76, Centos 5 (downloaded a week ago) > "bash" crashes. Replace with "ksh": > cd </zones/c5/root/>/bin; mv bash bash-; ln -s ksh bash > > Yes, it's HEAPS cludgy, but, it comes up. > Networking broken, "ping" works, "netstat -rn" fails, bad system call. > > Centos 5 was loaded on a Sempron 32bit, 256Mb ram, from DVD. > Default install > > > This message posted from opensolaris.org > _______________________________________________ > brandz-discuss mailing list > brandz-discuss at opensolaris.org
