Re: Plugins support in pkgng
Glen Barber wrote: >> How about the ability to add new commands to "pkg"? >> For example something like "pkg cutleaves" via plugins would be cool. > > I think 'pkg autoremove' already does this. Does autoremove show you all the leaves and ask which ones you want removed? I honestly don't know (and can't test at the moment); I assumed it only removed the ones with "auto" flag on. In any case, what I actually want is a pkg_cleanup alternative (i.e. cutleaves with a dialog(1)-like interface). There are other utilities that could benefit from being a plugin too. For example "suggest" plugin could use hooks on the build server to construct a database of "binary name->package" mapping, and add "pkg suggest" command on the client to query that database (e.g. "pkg suggest ogg123" would suggest you to install "audio/vorbis-tools", which is an idea that has been floating around). ___ 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: Plugins support in pkgng
Marin Atanasov Nikolov wrote: > This is just to share with you that soon after the official 1.0 > release of pkgng we now have basic plugins support in pkgng's > development branch. > [...] > It's not perfect or covering everything, but it will give you a quick > start though :) How about the ability to add new commands to "pkg"? For example something like "pkg cutleaves" via plugins would be cool. ___ 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] sysutils/bsdconfig: Replacement for sysinstall(8) post-install configuration abilities
Devin Teske wrote: >> "Toggle Startup Services" dialog shows sendmail_enable and >> sendmail_msp_queue_enable variables, but doesn't seem to show >> sendmail_submit_enable and sendmail_outbound_enable. Is this >> by design? > > What does the following produce: > > service sendmail rcvar > > Now what does this say: > > grep sendmail /var/run/bsdconfig/startup_rcvar_map.cache > > Do they agree? OK, both list sendmail_enable and sendmail_msp_queue_enable only. It appears that /etc/rc.d/sendmail only registers sendmail_submit_enable and sendmail_outbound_enable if they are enabled (and enabling or disabling one of the four affects the status of others). That behavior combined with the fact that bsdconfig does not recompute rcvars each time you make modifications means that you can't manipulate (i.e. disable) sendmail from bsdconfig. I think the right thing to do is to fix /etc/rc.d/sendmail, but I don't know how: removing the conditions around sendmail_submit_enable and sendmail_outbound_enable parts fixes rcvar, but probably breaks other commands. Any ideas how to fix this? > The nature of this bug is that if the item that you select in the > menu is evenly divisible by both 2 and 3 landing on a boundary, > the item works as expected, otherwise you can only toggle the item > ON (not off). Sounds interesting; there must be some really hairy stuff inside bsdconfig if this is the kind of edge cases it has. ___ 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] sysutils/bsdconfig: Replacement for sysinstall(8) post-install configuration abilities
Devin Teske wrote: > If you have the time and/or energy, please test and report any issues that > you experience. "Toggle Startup Services" dialog shows sendmail_enable and sendmail_msp_queue_enable variables, but doesn't seem to show sendmail_submit_enable and sendmail_outbound_enable. Is this by design? It also hangs if I try to toggle sendmail_msp_queue_enable. (Tell me if you can't reproduce this easily, I'll provide more details). ___ 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] Xorg 7.7 ready for testing!
Martin Wilke wrote: > With the new mesa 8.0 release, accelerated support for a number of > older graphic cards was dropped. At the moment we are not sure how to > deal with that.We are thinking of just replacing mesa 7.11 with 8.0 or > making a new flag like WITH_MESA= 7.11.2 / 8.0 in combination with > WITH_NEW_XORG, and let the mesa 7.6.1 set as default together with the > old xorg version. Obviosly the latter option make the already complex > situation more complex. The problem is, users, especially the new ones > can easily get confused with it. Another issue is, the packages.We > can't deliver a package set with the new Xorg releases. Will it be possible to provide, say pkgng repo with packages compiled with new xorg and new mesa? That would simplify testing (and using) by a very large factor. We'd just change PACKAGESITE and run pkg upgrade. ___ 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
Baptiste Daroussin wrote: > * pkg set -o oldorigin:neworigin allow the user to modify the origin of a > packages (useful for MOVED) Can such things be tracked automatically? I.e. will "pkg upgrade" upgrade moved 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: Using TMPFS for /tmp and /var/run?
Chris Rees wrote:
> Any rc script that complains about an empty /var/run is buggy- it should be
> assumed that it will be emptied on boot.
Then why are there entries for /var/run/{named,ppp,wpa_supplicant}
in /etc/mtree/BSD.var.dist? Should they be removed?
___
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: ABI/architecture identification for packages
Baptiste Daroussin wrote: > when a package can be installed in both i386 and amd64 > > and maybe in the Makefile: > > PKGARCH= i386 amd64 > > or > > PKGARCH= x86:32 x86:64 Baptiste, if ABI/arch ids will leak out to port Makefiles (i.e. I will need to care about them), then please leave them matching to the usual FreeBSD arch names, i.e. i386 and amd64, not the new ones. For reasons of consistency. ___ 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: KMS testing, intel only
> Along with plain standard ones (plain world+kernel install of bare system) > I'm working on creating specific images. > Like with preset installed packages (kde-set, gnome-set, etc.), like with > some patches (area51/kde-wip/kms) etc. > So, I did not fully automated (yet) creating of this one image, but you > already can grab it to test: > > http://gits.kiev.ua/FreeBSD/FreeBSD-9-kms-i386-r227337-2011-11-10.img.xz This is very cool, Alexander, thanks a lot. May I suggest creating a bootable image to become the standard way of doing big calls for tests? Xorg team could get a lot more testers this way. For the record, my GMA 3150 card works flawlessly now (it only worked with VESA previously, but it was still unusable due to disproportional screen resolution). A big thank you goes to kib@ for the KMS work. Can't wait until this stuff is committed. ___ 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: kern/143370: splash_txt ASCII splash screen module
Antony Mawer wrote: > Not sure if this is the right place to post it -- about 6 years ago I > put together a module which displays an ASCII splash screen on boot > (rather than the graphical splash_pcx and splash_bmp modules). As a user, I think this is rather cool; at least it is more useful for me than bmp/pcx splash modules, as I don't want to load vesa. Hm... Can you center the image if the display size is other than 80x25? Or try to temporarily change the video mode? It looks a bit misplaced in 80x50. Also, this would be 2x as cool if you could animate the splash. For example, if the supplied bitmap is 80x50, you could treat that as 2 frames, and cycle through them periodically (I assume that splash modules work the same way as saved modules do: the main function is called a few times per second, so you can update the screen there). BTW, in txt_init you currently check for data_size <= 0; you should also check for data_size < BIN_IMAGE_WIDTH * BIN_IMAGE_HEIGHT * 2, since if the bitmap is smaller, you'll draw garbage on the screen. > I have uploaded two sample boot splash screens at > http://www.mawer.org/freebsd/freebsd1.bin and > http://www.mawer.org/freebsd/freebsd2.bin . The files can be produced > using TheDraw and saving in its Binary file format, which consists of > a sequence of 2 byte pairs. The first byte in a pair is the character > to draw on the screen, and the second is the colour/display attributes > to draw the character with. As a side note, these images can also be made from video buffer dumps that vidcontrol produces like this: vidcontrol -p < /dev/ttyv0 | tail -c +13 > screenshot.bin (Substitute ttyv0 for the tty you want to take a picture of; the tty should be in 80x25 mode). ___ 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"
