On Sat, 25 Jan 2014 00:27:10 -0800 Yuri <[email protected]> wrote: > On 01/24/2014 14:16, Alexander Leidinger wrote: > > Some comments regarding the linux packages: > > - the goal with the linux_base ports is to switch from Fedora to > > CentOS > > - the linux_base ports are not designed for the use with chroot > > - the linux_dist port can be used with chroot > > - do you mind to give the linux_base-c6 port a try and maybe even > > use it as a base for your development? > > But linux_base is a repackaging of the various linux shared libraries > into yet another package. Why even bother doing this, if this all is > already pre-packaged by linux folks?
To use one tool to rule them all (= if you want to install software on FreeBSD, use the FreeBSD package management tool). Apart from that, please investigate more deeply what the linux_base ports are doing, one eample: - NOT packaging files which are available in the linux package to fall through to the FreeBSD files in the same location - replacing linux files with symlinks/wrappers to use the corresponding FreeBSD functionality Both of them result in re-using FreeBSD infrastructure to lessen the need to do some config inside the linux area to have it configured the same way as FreeBSD. > CentOS also uses rpm/yum, just like Fedora. The difference is merely > a repository string for yum. I am not sure if this will practically The difference which was important for us is that the Fedora has a faster turn-around time with new versions than CentOS. We don't have the man-power to cope with the fast release cycle of Fedora. > even make any difference at all, stock Fedora vs. stock CentOS. I can > install any rpm package in fewer lines of code than in a Makefile of > linux_base-c6. > > User side done this way works like a charm. Most work is to implement Off-course, but what you are doing is a linux_dist setup (plain vanilla linux, OK to chroot into), not a linux_base setup (a FreeBSD-blended-linux, NOT OK to chroot into because of missing configs as there is no fall-through to FreeBSD config files). > missing kernel features, and some yet unexplained malfunctions. > Missing futex operations being one of them, but there are quite a few > others. One known problem in the futex area is (attention: this is IIRC!) that futexes don't work after a fork(), but we don't know how often this is used or if it is used at all. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
