Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 03:31:16PM +0200, Matthias Apitz escribió: > Meanwhile I did: > > # cp -Rp ~guru/PKGDIR/mnt > > # PKG_PATH=/PKGDIR > # export PKG_PATH > # chroot /mnt pkg_add xorg-7.7 > # chroot /mnt pkg_add kde-4.10.5 > # chroot /mnt pkg_add vim-7.3.1314 > ... > > # chroot /mnt pkg_info | wc -l > 654 > > which went fine without any errors (only the normal messages about > creation of users, etc.); I will test the resulting image and report > back. I have transferred the image with dd(1) to a 16 "marketing-GByte" USB key; it boots fine in my little EeePC 900, takes around 90 secs until login: and KDE4 starts fine too, takes around 240 secs from "startx" to be able to start an xterm application in KDE4 desktop; i.e. it works, even from such a slow USB key which has a read performance of 1 to 17 MByte per sec, depending of the blocksize 512 or 8m; All this is only a proof of concept to prepare such USB key to boot from and reinstall from it the system on my EeePC netbook whic runs at themoment r235646 with KDE3 (which is now dropped from our ports tree). It seems that KDE4 launches a lot of application or services which I will not need, for example all these akonadi_maildir processes (see attached "ps -ax" output; for what they are good for? Ok, this question goes more to the kde@ mailing list. Thx matthias PID TT STATTIME COMMAND 0 - DLs 0:00.05 [kernel] 1 - ILs 0:00.02 /sbin/init -- 2 - DL 0:00.00 [sctp_iterator] 3 - DL 0:00.00 [xpt_thrd] 4 - DL 0:00.11 [pagedaemon] 5 - DL 0:00.00 [vmdaemon] 6 - DL 0:00.00 [pagezero] 7 - DL 0:00.00 [bufdaemon] 8 - DL 0:00.09 [syncer] 9 - DL 0:00.00 [vnlru] 10 - DL 0:00.00 [audit] 11 - RL 2:53.86 [idle] 12 - WL 0:02.35 [intr] 13 - DL 0:00.84 [geom] 14 - DL 0:00.05 [rand_harvestq] 15 - DL 0:00.90 [usb] 16 - DL 0:00.03 [acpi_thermal] 17 - DL 0:00.00 [softdepflush] 1391 - Ss 0:00.03 /sbin/devd 1536 - Ss 0:00.04 /usr/sbin/syslogd -s 1560 - DL 0:00.04 [md0] 1641 - Is 0:00.60 /usr/sbin/moused -p /dev/psm0 -t auto 1686 - Is 0:00.00 /usr/sbin/sshd 1689 - Ss 0:00.02 sendmail: accepting connections (sendmail) 1692 - Is 0:00.00 sendmail: Queue runner@00:30:00 for /var/spool/clientmque 1696 - Ss 0:00.05 /usr/sbin/cron -s 1796 - Is 0:19.46 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-a 1802 - Is 0:00.91 kdeinit4: kdeinit4 Running... (kdeinit4) 1803 - I0:00.60 kdeinit4: kdeinit4: klauncher --fd=8 (kdeinit4) 1805 - I0:05.90 kdeinit4: kdeinit4: kded4 (kdeinit4) 1807 - I0:00.07 /usr/local/libexec/gam_server 1811 - I0:02.99 kdeinit4: kdeinit4: kglobalaccel (kdeinit4) 1817 - I0:06.23 /usr/local/kde4/bin/knotify4 1819 - I0:02.45 kdeinit4: kdeinit4: ksmserver (kdeinit4) 1820 - I0:11.72 kwin -session 10d6114d4e60001381347192001812_1381 1824 - I0:14.72 kdeinit4: kdeinit4: plasma-desktop (kdeinit4) 1827 - I0:20.26 /usr/local/kde4/bin/akonadi_control 1828 - I0:02.79 akonadiserver 1830 - I0:03.56 /usr/local/libexec/mysqld --defaults-file=/home/guru/.loc 1838 - I0:02.07 /usr/local/kde4/bin/kuiserver 1840 - I0:00.08 kdeinit4: kdeinit4: nepomukserver (kdeinit4) 1843 - I0:04.73 kdeinit4: kdeinit4: krunner (kdeinit4) 1845 - I0:02.35 kdeinit4: kdeinit4: kmix -session 10d6114d4e6000138134736 1846 - IN 0:00.93 /usr/local/kde4/bin/nepomukservicestub nepomukstorage 1849 - I0:00.60 /usr/local/kde4/bin/nepomukcontroller -session 10d6114d4e 1852 - I0:01.04 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1853 - I0:01.07 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1854 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1855 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1856 - I0:03.81 /usr/local/kde4/bin/akonadi_archivemail_agent --identifie 1857 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_ical_r 1858 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1859 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1860 - I0:01.12 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1861 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1862 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1863 - I0:01.10 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1864 - I0:01.06 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1865 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1866 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1867 - I0:01.03 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1868 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1869 -
Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 08:12:31AM -0500, Mark Felder escribió: > > No. The r255948 was built on a clean, empty environment but with > > > > $ cat /etc/src.conf > > WITH_PKGTOOLS=yes > > > > Ok, I won't question your needs for pkg_* as you seem to be aware of > what you're doing :-) > > When you use pkg_* or pkg with their built-in chroot options it seems > that it executes those tools within those chroots instead of setting the > chroot as a destination for the installation. So if you wanted to use > --chroot I think you have to make sure the packages are available inside > the chroot. Perhaps there's some sort of DESTDIR option for the package > installation? I've been searching but have had no luck yet. I'll ask > around. It might be more reliable to do something like nullfs mount the > packages into the chroot and do the installation completely within the > chroot. Meanwhile I did: # cp -Rp ~guru/PKGDIR/mnt # PKG_PATH=/PKGDIR # export PKG_PATH # chroot /mnt pkg_add xorg-7.7 # chroot /mnt pkg_add kde-4.10.5 # chroot /mnt pkg_add vim-7.3.1314 ... # chroot /mnt pkg_info | wc -l 654 which went fine without any errors (only the normal messages about creation of users, etc.); I will test the resulting image and report back. matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: install packages with pkg_add(1) into another file system
On Tue, Oct 8, 2013, at 8:07, Matthias Apitz wrote: > El día Tuesday, October 08, 2013 a las 07:58:06AM -0500, Mark Felder > escribió: > > > On Tue, Oct 8, 2013, at 6:16, Matthias Apitz wrote: > > > > > > So far so good. Now I want install the packages as well into the image > > > in /mnt. What would be the best method for this? Run pkg_add with the > > > flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? > > > > > > Thanks in advance > > > > > > All this is with 10-CURRENT (base and ports). > > > > > > > pkg_add and all of the old "pkgtools" do not exist in 10-CURRENT > > anymore. Are you running a build of 10-CURRENT before they were removed? > > No. The r255948 was built on a clean, empty environment but with > > $ cat /etc/src.conf > WITH_PKGTOOLS=yes > Ok, I won't question your needs for pkg_* as you seem to be aware of what you're doing :-) When you use pkg_* or pkg with their built-in chroot options it seems that it executes those tools within those chroots instead of setting the chroot as a destination for the installation. So if you wanted to use --chroot I think you have to make sure the packages are available inside the chroot. Perhaps there's some sort of DESTDIR option for the package installation? I've been searching but have had no luck yet. I'll ask around. It might be more reliable to do something like nullfs mount the packages into the chroot and do the installation completely within the chroot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 07:58:06AM -0500, Mark Felder escribió: > On Tue, Oct 8, 2013, at 6:16, Matthias Apitz wrote: > > > > So far so good. Now I want install the packages as well into the image > > in /mnt. What would be the best method for this? Run pkg_add with the > > flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? > > > > Thanks in advance > > > > All this is with 10-CURRENT (base and ports). > > > > pkg_add and all of the old "pkgtools" do not exist in 10-CURRENT > anymore. Are you running a build of 10-CURRENT before they were removed? No. The r255948 was built on a clean, empty environment but with $ cat /etc/src.conf WITH_PKGTOOLS=yes matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: install packages with pkg_add(1) into another file system
On Tue, Oct 8, 2013, at 6:16, Matthias Apitz wrote: > > So far so good. Now I want install the packages as well into the image > in /mnt. What would be the best method for this? Run pkg_add with the > flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? > > Thanks in advance > > All this is with 10-CURRENT (base and ports). > pkg_add and all of the old "pkgtools" do not exist in 10-CURRENT anymore. Are you running a build of 10-CURRENT before they were removed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
