Date: Mon, 28 Jan 2013 03:04:27 +0100 From: Ralf Mardorf <ralf.mardorf@rocketmail.com> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Sharing a mail folder between Linux and FreeBSD Message-ID: <1359338667.2513.48.camel@q> In-Reply-To: <20130128014631.4a31dade.freebsd@edvax.de> References: <op.wrguj103uwjkcr@freebsd> <20130125133346.f1484ed8.freebsd@edvax.de> <op.wrgzatq7uwjkcr@freebsd> <20130125150414.f262d162.freebsd@edvax.de> <op.wrg019couwjkcr@freebsd> <20130125161215.f498f4e4.freebsd@edvax.de> <5102FE7B.4070808@gmail.com> <op.wrj87jhnuwjkcr@freebsd> <20130127153838.15b97613@X220.ovitrap.com> <20130127135806.4d19e997.freebsd@edvax.de> <1359333396.2513.10.camel@q> <20130128014631.4a31dade.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2013-01-28 at 01:46 +0100, Polytropon wrote: > On Mon, 28 Jan 2013 01:36:36 +0100, Ralf Mardorf wrote: > > On Sun, 2013-01-27 at 13:58 +0100, Polytropon wrote: > > > # 1. `cd /usr/src' (or to the directory containing your source tree). > > > # 2. `make buildworld' > > > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > > > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > > > # [steps 3. & 4. can be combined by using the "kernel" target] > > > # 5. `reboot' (in single user mode: boot -s from the loader prompt). > > > # 6. `mergemaster -p' > > > # 7. `make installworld' > > > # 8. `make delete-old' > > > # 9. `mergemaster' (you may wish to use -i, along with -U or -F). > > > # 10. `reboot' > > > # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) > > > > > > What source tree? I only checked out the kernel source using svn and > > IIRC it's using the /usr/src directory (I'm booted into Linux at the > > moment), without a subdirectory /kernel. I can delete the kernel source, > > since it's IMO fishy to have headers of another revision, than the > > kernel is, but when I asked, I got a reply, that it should be ok for > > FreeBSD. However, I never used the kernel source. > > The content of /usr/src does not only contain the kernel. It's > the whole OS, except of course you have only installed selected > parts of this tree. The file I've mentioned is at the top of > this structure: /usr/src/Makefile contains a short instruction > of how to install kernel and world (and explains other possible > targets). Before I checked out the kernel source it was empty. > > When I updated I did it like that (without subversion or cvs): > > > > # cd /usr/ports/misc/mc && make install clean > > # uname -r > > 8.3-RELEASE > > # freebsd-update -r 9.1-RELEASE upgrade > > # freebsd-update install > > # shutdown -r now > > > > # freebsd-update install > > # cd /usr/ports/ports-mgmt/portupgrade && make install clean > > # /usr/local/sbin/portupgrade -f ruby > > # rm /var/db/pkg/pkgdb.db > > # /usr/local/sbin/portupgrade -f ruby18-bdb > > # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db > > # /usr/local/sbin/portupgrade -af > > # freebsd-update install > > # shutdown -r now > > > > # freebsd-update IDS >> outfile.ids > > > > I wanted to run it tonight, but since I don't know where my source tree > > is, I can't continue. > > That's the binary way of updating. The kernel definitively was compiled. > If you'd update from source, > the steps would usually involve first updating /usr/src (by > whatever means, CVS no more, SVN or as part of a binary update > that also keeps the OS sources current). To take this approach, > the sources have to be complete. You can follow a -STABLE and > even -CURRENT (-HEAD) branch if you like. > > My suggestion would have been: If you have already used this > method before, and maybe if your current system has been installed > that way, you can "do it again"; if /usr/obj (the "result tree" > for building world and kernel) is still present, only the > "make installworld" steps would have been involved; even better, > if you only have to deal with a few system components, a selective > "make install" would have been sufficient. > > However, it has already been suggested to utilize mtree, because > a real re-installation isn't actually needed (as no files have > been changed, only their permissions, and that can be checked > and corrected using the /etc/mtree reference files). # umount <Linux> # mtree -U -f /etc/mtree ? Regards, Ralf
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1359338667.2513.48.camel>