Re: staying in stable but compiling for sid
Am 2007-04-13 22:50:23, schrieb Steve Kemp: These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. This is definitivly wrong because thr output of mount of my Devel- Station: --- /dev/sda1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda3 on /tmp type ext3 (rw) /dev/sda4 on /Chroot-Backups type ext3 (rw) /dev/sdb1 on /PostgreSQL type ext3 (rw) /dev/sdb2 on /Chroot-Archive type ext3 (rw) /dev/sdg1 on /usr/src type ext3 (rw) usbfs on /proc/bus/usb type usbfs (rw) samba3.private.tamay-dogan.net:/home on /home type nfs (rw,bg,hard,intr,tcp,vers=3,rsize=8192,wsize=8192,addr=192.168.0.69) /dev/sdc1 on /Chroot-999-sid type ext3 (rw) /dev/sdc3 on /Chroot-999-sid/var type ext3 (rw) /dev/sdc4 on /Chroot-999-sid/var/log type ext3 (rw) /dev on /Chroot-999-sid/dev type none (rw,bind) /proc on /Chroot-999-sid/proc type none (rw,bind) /sys on /Chroot-999-sid/sys type none (rw,bind) /usr/src on /Chroot-999-sid/usr/src type none (rw,bind) /PostgreSQL on /Chroot-999-sid/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-999-sid/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-999-sid/Chroot-Archive type none (rw,bind) /home on /Chroot-999-sid/home type none (rw,bind) /dev/sdd1 on /Chroot-4.0-etch type ext3 (rw) /dev/sdd3 on /Chroot-4.0-etch/var type ext3 (rw) /dev/sdd4 on /Chroot-4.0-etch/var/log type ext3 (rw) /dev on /Chroot-4.0-etch/dev type none (rw,bind) /proc on /Chroot-4.0-etch/proc type none (rw,bind) /sys on /Chroot-4.0-etch/sys type none (rw,bind) /usr/src on /Chroot-4.0-etch/usr/src type none (rw,bind) /PostgreSQL on /Chroot-4.0-etch/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-4.0-etch/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-4.0-etch/Chroot-Archive type none (rw,bind) /home on /Chroot-4.0-etch/home type none (rw,bind) /dev/sde1 on /Chroot-3.1-sarge type ext3 (rw) /dev/sde3 on /Chroot-3.1-sarge/var type ext3 (rw) /dev/sde4 on /Chroot-3.1-sarge/var/log type ext3 (rw) /dev on /Chroot-3.1-sarge/dev type none (rw,bind) /proc on /Chroot-3.1-sarge/proc type none (rw,bind) /sys on /Chroot-3.1-sarge/sys type none (rw,bind) /usr/src on /Chroot-3.1-sarge/usr/src type none (rw,bind) /PostgreSQL on /Chroot-3.1-sarge/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-3.1-sarge/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-3.1-sarge/Chroot-Archive type none (rw,bind) /home on /Chroot-3.1-sarge/home type none (rw,bind) /dev/sdf1 on /Chroot-3.0-woody type ext3 (rw) /dev/sdf3 on /Chroot-3.0-woody/var type ext3 (rw) /dev/sdf4 on /Chroot-3.0-woody/var/log type ext3 (rw) /dev on /Chroot-3.0-woody/dev type none (rw,bind) /proc on /Chroot-3.0-woody/proc type none (rw,bind) /sys on /Chroot-3.0-woody/sys type none (rw,bind) /usr/src on /Chroot-3.0-woody/usr/src type none (rw,bind) /PostgreSQL on /Chroot-3.0-woody/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-3.0-woody/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-3.0-woody/Chroot-Archive type none (rw,bind) /home on /Chroot-3.0-woody/home type none (rw,bind) --- and now the pstree -pan --- init,1 ??(keventd,2) ??(ksoftirqd_CPU0,3) ??(kswapd,4) ??(bdflush,5) ??(kupdated,6) ??(ahc_dv_0,18) ??(scsi_eh_0,19) ??(kjournald,49) ??(khubd,214) ??(kcopyd,234) ??(kjournald,261) ??(kjournald,262) ??(kjournald,263) ??(kjournald,264) ??(kjournald,265) ??portmap,325 ??syslogd,633 ??klogd,636 ??inetd,648 ??postmaster,707 -D /PostgreSQL/data_7.4 ??? ??postmaster,712 ??? ??postmaster,713 ??pg_autovacuum,718 -D -p 5432 -L /var/log/postgresql/autovacuum_log ??sshd,725 ??? ??sshd,2759 ??? ??sshd,2761 ??? ??bash,2784 ??? ??pstree,3030 -pan ??rpc.statd,730 ??atd,733 ??cron,736 ??rplayd,744 --forward=michelle1.private.tamay-dogan.net ??(rpciod,747) ??(lockd,748) ??(kjournald,756) ??(kjournald,760) ??(kjournald,764) ??(kjournald,778) ??(kjournald,782) ??(kjournald,786) ??(kjournald,800) ??(kjournald,804) ??(kjournald,808) ??(kjournald,821) ??(kjournald,825) ??(kjournald,829) ??wdm,881 ??? ??XFree86,31725 :4 vt12 -nolisten TCP -auth /var/lib/wdm/authdir/authfiles/A:4-VM8TKT ??? ??wdm,31726 ??? ??wdmLogin,31819 -d:4 -wdefault:fvwm2 -l/usr/share/pixmaps/200x130.wdm.woody.oldstable.xpm -bsolid:Gray85 -a ??wdm,1032 ??? ??wdm,1033 ??? ??XFree86,1035 :3 vt11
Re: staying in stable but compiling for sid
Kamaraju S Kusumanchi wrote: Hi all I want to run software only from Stable (ie Etch) when I am doing non-debian related work. However, when I am doing debian related work (ex :- fixing some bugs in the BTS) I want to work in unstable (ex :- compile packages for sid). Is this kind of think possible? [msg snipped] Is there any other elegant solution? I have heard about chroot, pbuilder etc., Will they be of any help in this scenario? I am happy to report that I have had successful results both with pbuilder and pdebuild. It took some time for me to figure out the right sequence of commands for each of them. So I wrote up a short HOWTO giving the exact commands used from start to finish. They can be found at http://malayamaarutham.blogspot.com/2007/04/recipe-for-building-texmacs-packages.html http://malayamaarutham.blogspot.com/2007/04/recipe-for-building-texmacs-package.html They might not be useful if you are already familiar with pbuilder, pdebuild. But I am thinking they might be useful for someone browsing the archives. hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
Hi, Romain Beauxis [EMAIL PROTECTED] wrote: Well, if it's only meant for using the application in your current X server, you simply have to bind mount the /tmp directory in the chroot: mount -t none -o bind /tmp /path/to/chroot/tmp I think it's enough to get the chroot to use the X server with UNIX sockets.. Of course if you don't have the same users in the chroot, you may also xhost + to allow other users.. Et voila ! Even with the same user, it's not enough. You need to import the MIT-MAGIC-COOKIES in the chroot if you want to avoid the 'xhost +' security hole. The advantage of this solution is that it's probably faster than TCP connections to localhost. The main disadvantage is that /tmp isn't anymore isolated in the chroot. Programs in the chroot are fiddling with your normal /tmp. To avoid that, it's problably enough to mount --bind only /tmp/.X11-unix, instead of the whole /tmp. I didn't try it, though. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
[Running X apps in a chroot] Székelyi Szabolcs [EMAIL PROTECTED] wrote: You can. Just run an sshd inside the chroot and enable X forwarding on the ssh server sitting inside and the ssh client connecting from outside (from an xterm, of course). There is another way, which I've been using for years: - in the chroot, arrange to have 'DISPLAY=localhost:0.0'; - out of the chroot, run your X server in a way that it does listen to TCP connections (for me, this means ommitting the '-nolisten tcp' arguments that are by default appended to the /usr/bin/X call in /etc/X11/xdm/Xservers). Of course, if you do this, I strongly suggest to configure your firewall so that the TCP ports X is listening on are only accessible from 127.0.0.1, not from your network interfaces connected to the wild world (the ports used for this start at 6000; every display takes up one port). - arrange to have a script transfer the MIT-MAGIC-COOKIES (with xauth) from the user running the X session out of the chroot to the user running the X apps in the chroot, so that X connections to your normal X server are authorized for the apps you run in the chroot. This is a bit of a hack, but it does work. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
Le samedi 14 avril 2007 10:43, Florent Rougon a écrit : [Running X apps in a chroot] (...) This is a bit of a hack, but it does work. Well, if it's only meant for using the application in your current X server, you simply have to bind mount the /tmp directory in the chroot: mount -t none -o bind /tmp /path/to/chroot/tmp I think it's enough to get the chroot to use the X server with UNIX sockets.. Of course if you don't have the same users in the chroot, you may also xhost + to allow other users.. Et voila ! Romain -- The lips of the righteous feed many: but fools die for want of wisdom. - Proverbs 10:21 The lips of the righteous teaches many But fools die for want of wisdom - Peter Tosh, Fools Die
Re: staying in stable but compiling for sid
Kamaraju S Kusumanchi escribe: Is there any other elegant solution? I have heard about chroot, pbuilder etc., Will they be of any help in this scenario? Go for pbuilder. For me the most elegant solution by far is running sid in a chroot environment. Install it using debootstrap. You can even set up a user that once logged in will be in the chroot env. If you're a developer you will find the procedure almost obvious. Google for debian sid chroot. Cordially, Ismael -- Ismael Valladolid Torres m. +34679156321 La media hostia j. [EMAIL PROTECTED] http://lamediahostia.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
Hi Kamaraju! On 4/13/07, Kamaraju S Kusumanchi [EMAIL PROTECTED] wrote: Is there any other elegant solution? I have heard about chroot, pbuilder etc., Will they be of any help in this scenario? Yep. I would go with pbuilder. ;-) Best regards, Nelson -- bash: ~/bin/program-to-generate-a-random-signature: No such file or directory -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
On Fri, 2007-04-13 at 17:33 -0400, Kamaraju S Kusumanchi wrote: Hi all I want to run software only from Stable (ie Etch) when I am doing non-debian related work. However, when I am doing debian related work (ex :- fixing some bugs in the BTS) I want to work in unstable (ex :- compile packages for sid). Is this kind of think possible? The easiest idea is to run two machines one with unstable and one with stable. But I dont have the luxury of running two machines. I also thought of installing 2 Debian versions on the same machine and sharing the /home directory. But I am skeptical about compatibility of rc files across different versions. (Ex:- vim 7's rc files may not work with vim 6's rc files etc.,) Is there any other elegant solution? I have heard about chroot, pbuilder etc., Will they be of any help in this scenario? Yes, this is what you are looking for. http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s-chroot http://www.debian.org/doc/manuals/maint-guide/ch-checkit.en.html#s-pbuilder -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
On Fri, Apr 13, 2007 at 05:33:29PM -0400, Kamaraju S Kusumanchi wrote: I want to run software only from Stable (ie Etch) when I am doing non-debian related work. However, when I am doing debian related work (ex :- fixing some bugs in the BTS) I want to work in unstable (ex :- compile packages for sid). Is this kind of think possible? You have several choices here: * Use pbuilder to setup a build environment. heavyweight but simple. * Use chroots for building. simple and well understood. These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. To solve that problem you could look at using something else: * Xen Complex to setup perhaps, but flexible. * Qemu Simple to setup, but may be too slow. Steve -- # Commercial Debian GNU/Linux Support http://www.linux-administration.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
2007/4/13, Steve Kemp [EMAIL PROTECTED]: You have several choices here: * Use pbuilder to setup a build environment. heavyweight but simple. * Use chroots for building. simple and well understood. These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. That's not exactly sure. You'll have a bit overhead but you can start X from a chroot. If you want, you can have a look at this: http://www.miriamruiz.es/code/create_chroot_system.sh Sorry, the explanation I did it in Spanish ( http://www.miriamruiz.es/weblog/?p=23 ) , but it's quite easy looking at the script. Greetings, Miry
Re: staying in stable but compiling for sid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Kemp wrote: On Fri, Apr 13, 2007 at 05:33:29PM -0400, Kamaraju S Kusumanchi wrote: I want to run software only from Stable (ie Etch) when I am doing non-debian related work. However, when I am doing debian related work (ex :- fixing some bugs in the BTS) I want to work in unstable (ex :- compile packages for sid). Is this kind of think possible? You have several choices here: * Use pbuilder to setup a build environment. heavyweight but simple. * Use chroots for building. simple and well understood. These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. You can. Just run an sshd inside the chroot and enable X forwarding on the ssh server sitting inside and the ssh client connecting from outside (from an xterm, of course). Reards, - -- cc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGIALAGJRwVVqzMkMRAmGRAJ4kFtj6jtRmMjAgPo2QpTAP00WG8ACfdUlx ZrXcDGqPwDg43cPl2hJJHrQ= =b7MW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
On Sat, Apr 14, 2007 at 12:15:48AM +0200, Miriam Ruiz wrote: These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. That's not exactly sure. You'll have a bit overhead but you can start X from a chroot. If you want, you can have a look at this: Sure, I primarily thinking of pbuilder when I wrote that. Sorry! Steve -- Debian GNU/Linux System Administration http://www.debian-administration.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
On Fri, Apr 13, 2007 at 11:26:24PM +0100, Steve Kemp wrote: On Sat, Apr 14, 2007 at 12:15:48AM +0200, Miriam Ruiz wrote: These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. That's not exactly sure. You'll have a bit overhead but you can start X from a chroot. If you want, you can have a look at this: Sure, I primarily thinking of pbuilder when I wrote that. Sorry! Wait a minute. You mean that the package has to do more than compile successfully? :-) Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: staying in stable but compiling for sid
Le Fri, Apr 13, 2007 at 06:37:41PM -0300, Nelson A. de Oliveira a écrit : On 4/13/07, Kamaraju S Kusumanchi [EMAIL PROTECTED] wrote: Is there any other elegant solution? I have heard about chroot, pbuilder etc., Will they be of any help in this scenario? Yep. I would go with pbuilder. ;-) Hi all, there is also cowbuilder (in the cowdancer package) which does the same but faster. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
Hello, On Fri, 13 Apr 2007, Steve Kemp wrote: Sure, I primarily thinking of pbuilder when I wrote that. Sorry! You can use unionfs wth a (pbuilder) chroot to test most things without damaging the pristine nature of the build environment. Secondly you need not run a full-fledged X server unless you are testing some accelerated X features. vncserver for example would be able to test most X-related packages. Regards, Kapil. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: staying in stable but compiling for sid
Kamaraju S Kusumanchi wrote: The easiest idea is to run two machines one with unstable and one with stable. But I dont have the luxury of running two machines. Use vmware/kvm/xen/uml/qemu/whatever... so you can run virtual machines (very small ones should be ok for doing small developments and testings) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
