Re: PACKAGESITE spam
On 12/21/2013 9:14 PM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 03:10:26PM -0500, Glen Barber wrote: On Sat, Dec 21, 2013 at 12:05:38PM -0800, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? echo 'SYSLOG: no' /usr/local/etc/pkg.conf It did not ask how to stop this stupidity. I asked to have this stupidity stopped by default. The spewing of this information in /var/log/messages provides NOTHING. Please turn it off by default. Obviously, if it is on by default, others have different opinions on this subject... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On 12/22/2013 12:04 AM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: this has been done and activated for reason, first for lot of companies, companies can turn it on it they want it. And if you want to save the few extra kB, you can turn it off... secondly I receive tons of request to actiavte on by default while you are the first to request it off by default I certainly can't refute 'tons of [private] requests'. There is no discussing of such logging in freebsd-current, freebsd-hackers, or freebsd-ports lists. Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! Please turn of this feature by default. Actually, you are the one making noise... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On 12/22/2013 12:25 AM, Steve Kargl wrote: On Sun, Dec 22, 2013 at 12:16:00AM +0100, Julien Laffaye wrote: On 12/22/2013 12:04 AM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: this has been done and activated for reason, first for lot of companies, companies can turn it on it they want it. And if you want to save the few extra kB, you can turn it off... I have turned it off. secondly I receive tons of request to actiavte on by default while you are the first to request it off by default I certainly can't refute 'tons of [private] requests'. There is no discussing of such logging in freebsd-current, freebsd-hackers, or freebsd-ports lists. Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! Please turn of this feature by default. Actually, you are the one making noise... What does this logging in /var/log/message provide that is not provided by 'pkg info'? It is useless noise. Forensics ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg - Shared object libarchive.so.5 not found, required by pkg
On 11/24/2012 7:38 PM, Christer Solskogen wrote: On Sat, Nov 24, 2012 at 3:45 PM, Victor Balada Diaz vic...@bsdes.net wrote: You have pkg-static for that kind of problems. You should rebuild pkg port to get pkg working again. So I still need /usr/ports when I use pkg? No. CURRENT is a special case because there is no ABI guarantee throughout its lifetime. (A package built for -CURRENT has a very little meaning, and we cant build them for every svn revision). So, yes, on CURRENT you'd better build your packages. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 9/1/2012 7:43 PM, Tijl Coosemans wrote: On 31-08-2012 14:22, Baptiste Daroussin wrote: On Fri, Aug 31, 2012 at 08:10:50AM -0400, John Baldwin wrote: On Friday, August 31, 2012 5:59:10 am Baptiste Daroussin wrote: On Thu, Aug 30, 2012 at 01:02:06PM -1000, Doug Barton wrote: I agree with John on all counts here. Further, the idea of a self-installing package, at least for the pkg stuff itself, addresses the issue that someone else brought up about how to handle installation of pkg by the installer for a new system. I like the idea of also providing a self-installing package, and it seems really easy to do, so I'll try to see what I can do in this area I'll wrote a PoC in 5 minutes which looks pretty good, this could also be a very simple and easy way to integrate into bsdinstaller. I'll do work in that direction. Still it doesn't solve the problem of boostrapping pkgng in a fresh new box, because the user may not know where to download the pkg-setup.sh. I do think that is something bsdinstall should be able to handle, and I would certainly want bsdinstall to include a dialog that says do you want to install the package manager? Of course this is being worked on by dteske@ on his bsdconfig scripts, so yes in anycase the bsdinstaller will end up with a boostrap dialog to install pkgng. Something else I thought of, you can't assume there's a working internet connection during installation. And also, even if there is a connection, can you guarantee that the downloaded pkg supports the packages on the dvd for the lifetime of the release? The packages set included on the dvd will probably be EOLed before the lifetime of the release. I really think you should just do vendor imports of pkg in base and include pkg on the dvd. There's no bootstrap problem then and the dvd is nicely self-contained. It also shouldn't be a problem to keep the official pkg repo for that release compatible with it. Just keep using the same version of pkg to create the repo. You've been able to develop and introduce pkgng without breaking older releases which shows having pkg tools tied to releases was never a problem. All that was needed was to move pkg development outside base. You should be able to do pkg 2.0 development in the same way. And when that new version is ready you import betas and release candidates in head and use current users as testers, just like is done with clang. In this scenario the ports tree needs to keep support for older releases, but that's a consequence of the fact that there's only one ports tree for all releases. Somewhere in between the ports and the various releases there has to be some form encapsulation, not just for pkg, but for all the tools used by the ports tree. Given how the ports tree currently encapsulates both the old and new pkg tools I don't see how supporting multiple versions of pkgng would be a problem because presumably the difference between pkgng versions is going to be much smaller than the difference between the old and new tools. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Script to set/unset automatic status in PKGNG database
On 8/30/2012 11:19 PM, John Nielsen wrote: I today noticed the pkg autoremove command for the first time, which does much the same thing as pkg_cutleaves but relies on the automatic flag in the pkgng database rather than user input to determine which leaf ports can be removed. Unfortunately, the pkg2ng utility has no way of knowing which old-style packages it converts were installed automatically as dependencies, so they are all marked as non-automatic (i.e. user-requested). In my case, this was not true for the majority of installed ports. Since I really like this functionality, I decided to update my local package database to match my preferences. Having succeeded, I decided a tool to make doing so easy could well benefit others (as well as my future self). (Plus I wanted an excuse to play with dialog(1) and pkg query a bit.) So here's the result. I'm not too attached to the name. It shouldn't eat your package database or steal your lunch money, but I'm not responsible if it does. Other than that, feedback is welcome. JN You want to use `pkg set -A` :) We make zero promises concerning the SQL schema in pkgng so it can change at every time and break your script. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 8/24/2012 11:57 PM, Doug Barton wrote: On 8/23/2012 8:03 PM, Eitan Adler wrote: On 23 August 2012 22:59, Doug Barton do...@freebsd.org wrote: I tend to agree with Steve here ... we can't be responsible for other people's poorly written docs. This isn't about poorly written docs. This is the user expecting a tool to exist, which doesn't. Take another example of a sysadmin which rarely installs new systems, installs FreeBSD for the third time, and then gets confused when pkg install vim fails. Aren't we going to install the pkg package on new systems when they are installed? Isn't that (shouldn't that be?) part of the project plan? It would be insane for us not to do that, at least for the releases where pkg is the default. True. But when you create jails without the installer, you have to install pkgng by hand. Hence the /usr/sbin/pkg bootstrap. You bring up a valid point that we should keep in mind for our own however. The bootstrapping issue will be the smallest possible annoyance on a long road of the migration process. The bootstrapping issue is a factor even after the migration :) I think that the point I'm trying to make is that it shouldn't be. note that I'm not talking about the mechanism here, I'm trying to avoid pkg doesn't seem to be installed on my fresh system becoming a FAQ. The way that we avoid that problem is not to create it for ourselves in the first place. :) The role of pkg-bootstrap is for those users who have already-installed systems that need to do the conversion, or if somehow pkg becomes corrupted on the user's system and needs to be reinstalled. That's it. I like that you're thinking through the related issues, but in this particular case I think you're overthinking it. Doug ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 8/24/2012 3:57 AM, Eitan Adler wrote: On 23 August 2012 18:19, Steve Wills swi...@freebsd.org wrote: Hi, It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to. Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. no opinion on the name, but imho there should be *something* called pkg on a fresh system. Users will install a new system, follow some random how-to, and not realize they missed a step. If the default package errors with exit code 1 and says run pkgbootstrap first that is okay too. Ideally, pkgng bootstrap process will be part of the bsdinstall steps (using the pkg package tarball on the installation media). The bootstrap tool is in base (instead of only on the install media) essentially for installations without the installer (like creating jails). So its true that in these case you have to think to run the bootstrap command. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng default schedule... registering a few reasons for rethinking the final implementation...
On 8/23/2012 6:26 PM, Jeffrey Bouquet wrote: I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 py27. cd /var/db/pkg ls -lac | grep py26 ls -lac | grep python as the more simple example. With due respect to its developers and the persons who agree that the package tools could be upgraded, the mandatory usage of a front-end database to a file directory one is here viewd as mutt-only-mbox, registry-and-bsod rather than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; ... I see concurrently too few tests on lower-end p2, p3 as to whether pkg can run with lesser memory machines (routers...) (pfsense) Everyone's is welcome to help us with that! The memory usage can be decreased by using gzip over xz for (un)compression. ... I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, pfsense..) due to less-reliability, more-possibility of bugs.. If we get useful detailed bug reports, we will fix 'em! ... Not to mention native tab-completion not dependent upon further customizations, ... Introduces complexity to running earlier versions of BSD virtualized in later versions and vice versa... ... I've innumerable times made quick work (2 hours or so) of cross-disk backup/fix/upgrade using /var/db/pkg where doing so with just the pkg tools or my own scripts would take immeasurably longer... Why ? ... It would deprecate searching +CONTENTS, for example, or quickly checking the text file +REQUIRED_BY without a database frontend. ... Almost every reply and post have glossed over those points, referring to the benefits of a newer package management system, again glossing over the added memory requirements, number of .so. required, lack of extensive testing across all hardware cpu/memory scenarios... ... it will be a single tool that will do the job of all the many port/package management scripts currently only available in the ports system (bsdadminscripts) for example. A single tool, yes. But it won't do all of the edge-case jobs *not* covered by the present pkg_ tools that can be crafted hooking into the /var/db/pkg/ directory structure, with find for example. pkgng is not a replacement for portmaster or portupgrade... That was not my question. My concern was with the deprecation of the latter and /var/db/pkg along with the introduction of pkgng. ... Each pkg_ legacy uses about 3-6 .so. afaik. pkg uses 19. 18 :) ... A review of pkgng on mebsd.com, suggests replacment CLI for tasks one might do with portmaster now. However, they are much more arcane (%H-%M vs -g...) and thus unwelcoming... ... patches for portmaster and portupgrade to use pkgng tools Memory requirements with both working together? The ABI between them breaks? ... My concerns are more or less, why should the following *ever* be mandatory... On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via pkgng only depends on lib in the base system. Why was libarchive.so missing? portmaster or via core dumping install. By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install and mtree didn't coredump and it worked - and this procedure rescued me. But on my lab's development box, it didn't work! (Continues with more equally terrible detail...) (Freebsd-questions, august) ... Or my own experience, today, testing on a p4 pre-p2 memory req. investigations. # pkg stats Unable to open remote database repo. Try running 'pkg update' first. # pkg update Updating repository catalogue zsh: segmentation fault pkg update Do you have useful details about this segv, like a backtrace ? . So, a kernel option (non default) to deprecate /var/db/pkg? A further development of pkg to concurrently maintain a /var/db/pkg? ...not implying the concurrent deprecation of the latter! Brighter ideas? Thanks for reading these concerns. I am quite perturbed by the announcement of v11 erasing the /var/db/pkg upon which I presently use daily numerous times... And I apologize, in advance, for typos etc. herein... J. Bouquet 2004 v5... Regards, Julien ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] pkgng 1.0-beta9 please test
On 03/30/2012 01:10 PM, Lars Engels wrote: On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote: Hi, On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 [...] Please note that normally this will be the last beta version, So we can expect an official package repository with the first RC? A public repo, maybe. An official repo endorsed by portmgr that's another story... :) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Beta 3 still not OK
On 2/11/2012 2:13 AM, Sergio de Almeida Lenzi wrote: Seems that the sqlite database has changed from beta1 to beta3??? I have all the system running exclusive on pkg there is no more old pkg How can I upgrade the sqlite database from beta1 to beta3??? There is nothing to upgrade. The on-disk format of the sqlite database is frozen by the sqlite guys and they are very conservative about that. We just upgraded the code to have latest bugfixes and improvements. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] pkgng alpha2
On 12/13/2011 06:16 PM, Andriy Gapon wrote: on 30/11/2011 22:32 Julien Laffaye said the following: [1] : https://github.com/pkgng/pkgng/issues [2] : https://github.com/pkgng/pkgng [3] : http://wiki.freebsd.org/pkgng [4] : http://people.freebsd.org/~bapt/pkgng-bsdcan2011.pdf [5] : http://wiki.freebsd.org/201110DevSummit/Ports?action=AttachFiledo=gettarget=pkgng-devsummit.pdf [6] : http://wiki.freebsd.org/201110DevSummit?action=AttachFiledo=gettarget=pkgng-devsummit-track.pdf Couple of questions/suggestions: 1. Do you plan to have a pkgng port to issue the preview releases pkgng? Current pkgng installation/bootstrap procedure is really easy, but the port would be even more convenient for prospective testers. Yes, this is planned. The ports will bootstrap pkgng. 2. Is there a public pre-built package repository with pkgng-format packages that could be used for testing and getting a taste of a packages-only pkgng-managed system? Unfortunately, no. I think I now have the resources to do that for the next CFT. But it will only be 9.0 amd64 I am afraid. We cant build packages for the entire matrix. Thank you. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[CFT] pkgng alpha2
Hi all, We are releasing pkgng (the next pkg_install) alpha2 to the world and we want you to test it! There is no good method to test it: use it as you would in the real world. Of course, you are encouraged to backup your data or test it in some kind of virtualized environment. After using it for some time, you will certainly find bugs. You can report them on the issues tracker [1]. If you find missing features, that is things you can't do with pkgng but can with pkg_install, you can also report them. New features are not the expected outcome of this call, as we want to release a final version ASAP. FYI, an alpha3 should follow shortly to fix issues in alpha3 and test additional features. After that, there will be a feature freeze with beta1. Getting started: You can download or git clone the source code of pkgng on the github page [2]. Then, a boring `make' followed by `make install' will do it. If you have some packages installed by pkg_add, you can convert the old database to the pkgng database with the 'pkg2ng' shell script in the ports/ folder. You can also add packages from the ports tree (with bsd.pkgng.mk) or with a pkgng repository. All is documented in the README and manpages. If you are a newcomer to pkgng, this doc reading step is also valuable to us. Indeed, if you fight to get the right infos, or if some things feel counter intuitive, we should improve it! Which brings me to the topic of contributing to pkgng. The best thing you can do is to write down the documentation you would have loved to read while testing pkgng! And of course, if you have a patch with your bug report, it is much appreciated. If you read this entire mail and wonder what is this pkgng thing, you can read the wiki page [3], bapt's presentation from BSDCan [4], EuroBSDCon [5] [6] and browse the source code. Regards, Julien, on behalf of the pkgng team. And remember, we _do_ want to hear back from you! Please also note that it is still alpha code and it can kill kitten and puppies. You are warned ;-) [1] : https://github.com/pkgng/pkgng/issues [2] : https://github.com/pkgng/pkgng [3] : http://wiki.freebsd.org/pkgng [4] : http://people.freebsd.org/~bapt/pkgng-bsdcan2011.pdf [5] : http://wiki.freebsd.org/201110DevSummit/Ports?action=AttachFiledo=gettarget=pkgng-devsummit.pdf [6] : http://wiki.freebsd.org/201110DevSummit?action=AttachFiledo=gettarget=pkgng-devsummit-track.pdf ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD ftp mirror sites and pkg_add
On 11/14/2011 12:45 PM, Mehmet Erol Sanliturk wrote: In Arch Linux , package manager Pacman is using a configuration file /etc/pacman.conf with its included files . It is using a file such as the following ( some parts are deleted for message ) : ( obtained from http://www.archlinux.org/mirrorlist/all/ftp/ ) : - ## ## Arch Linux repository mirrorlist ## Generated on 2011-11-13 ## ## Any #Server = ftp://mirrors.kernel.org/archlinux/$repo/os/$arch ## Australia #Server = ftp://mirror.aarnet.edu.au/pub/archlinux/$repo/os/$arch #Server = ftp://ftp.iinet.net.au/pub/archlinux/$repo/os/$arch #Server = ftp://mirror.internode.on.net/pub/archlinux/$repo/os/$arch #Server = ftp://mirror.optus.net/archlinux/$repo/os/$arch ... ## Canada #Server = ftp://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/$arch #Server = ftp://mirror.its.dal.ca/archlinux/$repo/os/$arch #Server = ftp://less.cogeco.net/pub/archlinux/$repo/os/$arch ... ## Great Britain #Server = ftp://mirror.lividpenguin.com/pub/archlinux/$repo/os/$arch #Server = ftp://mirror.cinosure.com/archlinux/$repo/os/$arch #Server = ftp://mirrors.uk2.net/pub/archlinux/$repo/os/$arch ... ## Turkey #Server = ftp://ftp.linux.org.tr/archlinux/$repo/os/$arch ... ## United States #Server = ftp://archlinux.supsec.org/pub/linux/arch/$repo/os/$arch #Server = ftp://cake.lib.fit.edu/archlinux/$repo/os/$arch #Server = ftp://cosmos.cites.illinois.edu/pub/archlinux/$repo/os/$arch #Server = ftp://ftp.archlinux.org/$repo/os/$arch #Server = ftp://ftp.gtlib.gatech.edu/pub/archlinux/$repo/os/$arch #Server = ftp://mirror.ancl.hawaii.edu/linux/archlinux/$repo/os/$arch #Server = ftp://mirror.us.leaseweb.net/archlinux/$repo/os/$arch #Server = ftp://locke.suu.edu/linux/dist/archlinux/$repo/os/$arch #Server = ftp://ftp.osuosl.org/pub/archlinux/$repo/os/$arch #Server = ftp://mirror.rit.edu/archlinux/$repo/os/$arch - The advised action is to edit this file and activate nearest or suitable mirrors by removing comment sign ( # ) in front of the relevant mirror . During package install , this file is used and traversed up to an available mirror , when a mirror fails from beginning . . In FreeBSD , pkg_add http://svnweb.freebsd.org/base/head/usr.sbin/pkg_install/add/main.c?view=markup the ONLY package site is taken by getpackagesite(void) from if (getenv(PACKAGESITE)) which it is ONLY ftp.FreeBSD.org . When the statement if ((packagesite = getpackagesite()) == NULL) fails , it is necessary either to wait up to a working state of the ftp.FreeBSD.org or edit the PACKAGESITE environment variable up to a success which is NOT an expected action from the beginners . Instead of this , it is possible to use a pkg_add.conf and insert into a list of ALL available ftp.*.FreeBSD.org sites http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html AND OTHER mirror ftp sites synchronized by central FreeBSD ftp sites . Every site will be commented out , but ftp://ftp.FreeBSD.org... will be available . For example : - # From # http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html : # The official sources for FreeBSD are available via anonymous FTP # from a worldwide set of mirror sites. # The site ftp://ftp.FreeBSD.org/pub/FreeBSD/ is well connected and # allows a large number of connections to it, # but you are probably better off finding a closer mirror site # (especially if you decide to set up some sort of mirror site). # The adviced action is the following : # Move the nearest mirror site link to top , # and second nearest mirror to second line , # up to mirrors suitable to use , # AND remove comment signs in front of them . ## Australia #ftp://ftp.au.freebsd.org/pub/FreeBSD/ #ftp://ftp2.au.freebsd.org/pub/FreeBSD/ ... ## Canada #ftp://ftp.ca.freebsd.org/pub/FreeBSD/ #ftp://ftp2.ca.freebsd.org/ #ftp://ftp3.ca.freebsd.org/pub/FreeBSD/ ... ## Turkey #ftp://ftp.tr.freebsd.org/pub/FreeBSD/ #ftp://ftp2.tr.freebsd.org/pub/FreeBSD/ ... ## United Kingdom #ftp://ftp.uk.freebsd.org/pub/FreeBSD/ #ftp://ftp2.uk.freebsd.org/pub/FreeBSD/ ... ## United States #ftp://ftp1.us.freebsd.org/pub/FreeBSD/ #ftp://ftp2.us.freebsd.org/pub/FreeBSD/ ... ftp://ftp.freebsd.org/pub/FreeBSD/ - This feature and what to do advise will be stated in the release notes . When pkg_add is started , it will load pkg_add.conf list into an array , AND traverse this array from element one to end , last being the ftp://ftp.freebsd.org/pub/FreeBSD/ . If a mirror site is successful , the package will be installed from this one , and the loop will be discontinued . The suggested structure does NOT change anything from the new user point of view . It is very likely that , experienced users will adhere to use nearest mirror usage advise to reduce load currently carried by the default FreeBSD ftp site . I think ,
Re: FreeBSD 9.0
On 09/15/2011 16:42, Alisson wrote: Somebody know when FreeBSD 9.0 Releng will be available? When it is ready? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0-BETA1 installer issues
On 08/03/2011 21:42, Garrett Cooper wrote: also the extension for the file is wrong (it should be txz, right?) pkg_add still use the bzip2 format iirc. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] rcexecr: rcorder in parallel
On Sat, Jun 4, 2011 at 10:10 AM, Buganini bugan...@gmail.com wrote: https://github.com/buganini/rcexecr Currently it is able to determine the exec/wait order There are something I haven't digged in deeply in the self modification part. patches/ideas are welcome. Hello, Thanks for doing that! You should use kqueue(2) instead of waitpid(2) so that you can efficiently monitor a pool of processes. See pwait(1) for an example. Regards, Julien ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 12:33 PM, Julien Laffaye jlaff...@freebsd.org wrote: On Fri, Mar 25, 2011 at 11:52 AM, Ivan Voras ivo...@freebsd.org wrote: At this time I'd just like to suggest you add the use of WAL journal (http://www.sqlite.org/pragma.html#pragma_journal_mode) on database creation so you get the benefits of multiple-readers-single-writer concurrency model. It sounds like a good idea. I'll add WAL support and if no problem arise from that we should keep it. Despite the fact that WAL allows cool things, one disadvantage is that the process require write privileges on the database file even if it is only reading. Thus, pkg info and things like that would need to be run as root... Regards, Julien ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 10:11 AM, Baptiste Daroussin b...@freebsd.org wrote: Developpement site: http://git.etoilebsd.net/pkgng/ FYI, we moved to github[1] in order to have a bug tracker, pull request and code review. Also, I recommend to build from the HEAD of the git repository, to not report fixed compilation warnings/bugs. [1]: https://github.com/pkgng/pkgng ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 11:52 AM, Ivan Voras ivo...@freebsd.org wrote: On 25/03/2011 11:11, Baptiste Daroussin wrote: In term of technology we decided to use a sqlite3 database, and to prevent potential trolling, sqlite3 is used in it's amalgamation form which means it is incorporated in the code sources (as recommanded by sqlite developpers like a statically linked library) on build we only activate the features we need in sqlite. I'm very glad you went with sqlite3! I've looked at pkgng source a bit and it looks like you use transactions and foreign keys which is a huge benefit for the whole effort. At this time I'd just like to suggest you add the use of WAL journal (http://www.sqlite.org/pragma.html#pragma_journal_mode) on database creation so you get the benefits of multiple-readers-single-writer concurrency model. It sounds like a good idea. I'll add WAL support and if no problem arise from that we should keep it. The alpha release come with an experimental tool pkg2ng to convert an existing package database to the new pkgng database format. So one can test pkgng without rebuild all its packages. Could you change the filename of the database to have the .sqlite extension? It's not important but it indicates what it is used by and newer software is moving to .sqlite. Sure. Maybe rename pkg.db to local.sqlite so it will consistent with the repo.sqlite (both in /var/db/pkg) One of the thing we are thinking about pkgng is to perhaps be able to provide it only as a ports (with simple script in base to boostrap/install it). That would allow pkgng to live with the ports to be able to easily integrate new features without having to support very old version of pkgng. Maybe I'm misunderstanding but won't that mean that the ports system without pkgng will continue to maintain their data in the current format? If pkgng is not installed, the first thing the port system will do is to install it. more informations can be found here: http://git.etoilebsd.net/pkgng/tree/docs/GOALS, the database will be a sqlite file compressed with the xz format. the database will be signed so we can trust the sha256 of the packages, so if a package has the expected hash, it is considered trusted. I'm not sure on what the database refers at this point, but is it really necessary to compress it? I don't mean it's hard to do, just that maybe it would be simpler without it. It is the database describing the remote repository. It is interesting to compress it because it will be downloaded. About this signature: hashing like this is very rudimentary. Could you design this to extensible, expecting real PGP-based signatures in the future? We thought that signing the repo.sqlite file would be simpler. If we want to sign each package individually, we must have a tarball which contains the real tarball plus the signature. Regards, Julien ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 2:38 PM, Alexander Leidinger alexan...@leidinger.net wrote: Quoting Baptiste Daroussin b...@freebsd.org (from Fri, 25 Mar 2011 15:14:52 +0100): 2011/3/25 Alexander Leidinger alexan...@leidinger.net: Quoting Baptiste Daroussin b...@freebsd.org (from Fri, 25 Mar 2011 11:11:11 +0100): pkgng is a binary package manager written from scratch for FreeBSD. I didn't had a look at it, just some comments about some parts you explained. features supported are or will be : - a special architecture all allows to specify when a package can be used on every architecture. (not done yet) What if a package is able to install on a subset, e.g. the linuxulator ports are for amd64 and i386? No clue for that at the moment but we are open to suggestions. The suggestion is easy, allow a way to specify a set of valid architectures. That looks reasonable and easy to implement. What about DB corruption/loss? Do you keep the /var/db/pkg/package/xxx files even with pkgng and only use the DB as a way to speed up some work (so the DB corruption just requires to run pkg2ng), or are you lost of the DB is lost? Nothing is done about DB corruption/loss, I am not sure we need to do something. Maybe. I would say for sure. Info: In Solaris 10 sqlite is used for the service managenemt framework (SMF). It is possible that the DB is corrupt in some bad situations. In this case you have to rebuild the DB (script provided, been there, had to use it). If sqlite is properly used with transactions, it is very hard to corrupt the database. But if hardware lies to us and say that the data is on disk whereas it isnt... what can we do? Another potential problem is fsync(), but if it is broken on FreeBSD we want to fix it! BTW, the goal is to only have the database and not the flat files. If you are paranoid about power outage, use something like zfs snapshots... Currently a filesystem corruption/loss on /var/db/pkg would do the same. Put a corruption of /var/db/pkg/xyz-1/+REQUIRED_BY would only affect a small part, and this part could be even recovered from (pkgdb from portupgrade is able to do it). With sqlite we have atomicity! And locks! but it is sqlite so we can perhaps provide a way to get compressed dump so user can periodically backup their database. It needs to be automated. Maybe periodic daily... but maybe this is not often enough after a day of a lot of changes (think about it this way: do you want to lose a day of changes?). The current FS based DB is very robust, partly because there is redundant data, pertly because losing a file just means that the very limited subset of information is lost (and a reinstall of one port will fix it). Bye, Alexander. Regards, Julien ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 4:14 PM, Pietro Cerutti g...@freebsd.org wrote: On 2011-Mar-25, 17:04, Baptiste Daroussin wrote: if you are going to test on current please notice that make install will overwrite /usr/lib/libpkg so pkg_* tools won't work anymore. We will workaround that later by renaming our lib libpkgng for the test phase. But I won't be able to do that before monday. I was: http://people.freebsd.org/~gahr/pkgng-0.1-alpha1.diff Commited! Thanks! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: DHCP server in base
On Fri, Sep 10, 2010 at 8:36 PM, Doug Barton do...@freebsd.org wrote: As I've said many times, I'm ready to have it out when there is consensus to do so. The usual discussion goes like this: 1. Get BIND out of the base! 2. If we remove it, the command line tools (dig, host, nslookup) go with it. DragonflyBSD chose to remove BIND and to use drill as a replacement [1]. Don't know if it meet our requirements, though. [1]: http://leaf.dragonflybsd.org/mailarchive/submit/2010-03/msg3.html ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
