Re: 32-bit jails on a 64-bit system?

2010-03-05 Thread Kostik Belousov
On Fri, Mar 05, 2010 at 01:06:10PM +0100, Mark Huizer wrote:
 On 1/21/2010 10:12, Miroslav Lachman wrote:
 
 I think it is nothing new to 8.0, it is the same as release note for 7.2.
 
 I didn't test it, but I think you can install (copy) i386 jail (or 
 whole system) in to amd64 host and just run it as any other jail.
 
 
 Actually, that's what I tried, since I want to move a server to new 
 hardware, but with serious time constraints on my side :-( So my plan 
 is/was: rsync the entire machine, build a script that fixes IP 
 addresses here and there in the copy, run the jail.
 
 I did have to fix a few little things, stuff like copy a few binaries 
 over (netstat, ps, ifconfig, w, top, ldd, ldd32) and of course the ld* 
 files in /libexec. Furthermore I moved /usr/lib to /usr/lib32 and copied 
 /usr/lib from the amd64 install.
 So far so good, I start jail, I see ssh, apache etc running, I start to 
 get happy.
My own experience is that just moving 32bit i386 image onto amd64 host
is better now then trying to make a hybrid with 32bit binaries and
both 32 and 64 bit libraries.

You have to disable all management operations in the startup, of course.
I do not recommend to touch /libexec. You may put statically linked
64bit ps/top/netstat etc into the jail for convenience.

Having amd64 bit kernel that can be configured and managed by 32bit
binaries is the long road. On the other hand, user 32bit applications
working very good.

 
 But... a few things don't seem to work as intended, although I haven't 
 checked each and every detail:
 
 * cronolog seems to ignore part of the arguments, so if you tell it to 
 log to /data/logs/%Y/%m/%d/access.log it will log to 
 /data/logs/access.log ; didn't investigate yet
 
 * postfix won't start. This I looked at a little more, but without success.
 
 On the count of postfix:
 
 # ldd /usr/local/sbin/postfix
 /usr/local/sbin/postfix:
 libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x2809d000)
 libsasl2.so.2 = /usr/local/lib/libsasl2.so.2 (0x280cf000)
 libpam.so.5 = not found (0x0)
 libcrypt.so.5 = /usr/lib32/libcrypt.so.5 (0x280e6000)
 libssl.so.6 = not found (0x0)
 libcrypto.so.6 = /usr/lib32/libcrypto.so.6 (0x280ff000)
 libc.so.7 = /usr/lib32/libc.so.7 (0x2825a000)
 
 # ls -la /usr/lib*/libpam.so.5
 -r--r--r--  1 root  wheel  35848 Mar  3 23:31 /usr/lib/libpam.so.5
 -r--r--r--  1 root  wheel  28296 Mar  3 23:33 /usr/lib32/libpam.so.5
 
 You'd say it should work, but it doesn't. The best I've got so far is 
 not copy /usr/lib from the amd64 host but make it a symlink to 
 /usr/lib32. Then postfix works, but netstat etc won't, of course.
 While typing this, this brought me to another idea.
 - make /usr/lib symlink to /usr/lib32, mkdir /usr/lib64 filled with the 
 libs from the hostmachine's /usr/lib, and then edit /etc/rc.d/ldconfig, 
 change _LDC's /usr/lib to /usr/lib64, restart, and presto postfix works. 
 It's dirty but it seems to work for now, time for testing.
 
 But I don't really understand why apache etc works, and postfix doesn't. 
 So far I see the issues with libpam and libssl, which both are in 
 /usr/lib, where libc.so.7 is symlinked to /lib. Anyone who can explain 
 the difference to me? And is this intended behaviour?
 
 And now off to cronolog's not working %Y :-)
 
 mark
 
 ___
 freebsd-jail@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-jail
 To unsubscribe, send any mail to freebsd-jail-unsubscr...@freebsd.org


pgpv6spRo5DVq.pgp
Description: PGP signature


Re: starting jails in the background dependencies

2010-03-05 Thread Alexander Leidinger
On Tue, 5 Jan 2010 11:24:47 +0100 Alexander Leidinger
alexan...@leidinger.net wrote:

 On Mon, 07 Dec 2009 08:03:53 +0100 Alexander Leidinger
 alexan...@leidinger.net wrote:
 
  Hi,
  
  now that jails are started in the background (which is good, to
 
 I just realized yesterday that it also stops in parallel (in the
 background). This is bad. It may be the case that a jail is not fully
 stopped via the rc scripts when the OS decides to kill the remaining
 processes during a shutdown.
 
 My first reaction is to only allow to start in the background, but
 everything else needs to be serialized.

I committed now what was discussed in this thread:
 - no start in the background by default
 - only start is allowed to happen in background when
   jail_parallel_start is set to yes in rc.conf
 - stdin is redirected from /dev/null

If someone is not happy about the name of the rc.conf variable: feel
free to change it, I do not care about the name.

Bye,
Alexander.
___
freebsd-jail@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to freebsd-jail-unsubscr...@freebsd.org


Re: [kde-freebsd] okular doesn't open PDFs

2010-03-05 Thread t...@diogunix.com
Raphael,

thanks for replying.

  Okular doesn't open pdf files. It says something about not found plugins
  (from which I guess it means poppler). I already checked whether poppler
  was compiled/installed too. Yes, it was - but nonetheless I cannot find
  any options within the Okular settings to make Okular use poppler. The
  only backend available there is ghostscript. I guess there must be a
  place where I could tie the two ends of the rope together. But cannot
  find that place.

 The only backend listed in the Backends dialog is Ghostscript here too,
 even though poppler support works fine here.

 Did you install poppler-qt4 (or whatever its name was in the ports tree)
 before compiling kdegraphics4? 

Yes, has been available all the time.

 Is poppler correctly detected when CMake is
 called in kdegraphics4?

Did re-compile kdegraphics4 just right now and  also Poppler seemed to get 
recognized while make. Nonetheless, I again get the Can not find a plugin 
which is able ... when trying to open a pdf file with Okular. Also, *.pdf is 
not amongst the supported file types. 

I guess something in the realm of the configuration (done by the make process) 
is broken. But how can I manually fix that ?

Tom


___
freebsd-jail@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to freebsd-jail-unsubscr...@freebsd.org