Re: Call for bge(4) testers
On Tue, Oct 02, 2012 at 11:10:23AM -0700, Sean Bruno wrote: > On Tue, 2012-10-02 at 15:59 -0700, YongHyeon PYUN wrote: > > Sean, do you have a box with BCM5703/5704/5714/5715 controller? > > I have a 5704C in an HP DL380G4 here that seems to be working. I'll > have to poke around further to see what else I have lying around. > > bge0: mem > 0xfdef-0xfdef irq 25 at device 1.0 on pci3 > bge0: CHIP ID 0x2100; ASIC REV 0x02; CHIP REV 0x21; PCI-X 133 MHz > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow > bge0: Ethernet address: 00:0f:20:f6:e6:23 > bge1: mem > 0xfdee-0xfdee irq 26 at device 1.1 on pci3 > bge1: CHIP ID 0x2100; ASIC REV 0x02; CHIP REV 0x21; PCI-X 133 MHz > miibus1: on bge1 > brgphy1: PHY 1 on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow > bge1: Ethernet address: 00:0f:20:f6:e6:22 > Sean, I have checked in all changes except one in the WIP version to HEAD. If you happen to see any abnormal bge(4) behavior on CURRENT let me know. 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: [HEADSUP] current switched by default to pkgng
On 10/10/2012 23:20, Vincent Hoffman wrote:
>> That's if you were to patch an already installed copy of portmaster.
>> > The patch is designed to be placed in
>> >
>> > ${PORTSDIR}/ports-mgmt/portmaster/files/
>> >
>> > so it would be applied as part of the normal process of building the
>> > portmaster port. In which case portmaster.sh.in is definitely the
>> > correct target.
> Actually not so, maybe something has changed recently?
I stand corrected. Looks like Bryan switched things around a bit when
he imported everything to GitHub.
I'll fix the patch pro-tem although it should become redundant Real Soon
Now.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 20:50, Matthew Seaman wrote:
> On 10/10/2012 19:35, Stefan Esser wrote:
>> Am 10.10.2012 19:14, schrieb Matthew Seaman:
>>> On 10/10/2012 15:07, O. Hartmann wrote:
Is ports-mgmt/portmaster now dealing with pkgng?
>>>
>>> Not yet. bdrewery has taken over the portmaster port and pkgng
>>> related updates are expected in the near future.
>>>
>>> Until then, you still need to follow the instructions here:
>>>
>>> https://github.com/pkgng/pkgng/blob/master/FAQ.md#15
>>
>> In order to get the portmaster-pkgng patch to apply,
>> the filename in the second line must be changed:
>>
>> from ./portmaster.sh.in
>> to ./portmaster
>
> That's if you were to patch an already installed copy of portmaster.
> The patch is designed to be placed in
>
> ${PORTSDIR}/ports-mgmt/portmaster/files/
>
> so it would be applied as part of the normal process of building the
> portmaster port. In which case portmaster.sh.in is definitely the
> correct target.
Actually not so, maybe something has changed recently?
[root@ostracod /usr/ports/ports-mgmt/portmaster]# head -4
files/patch-portmaster-pkgng
--- ./portmaster.sh.in.orig 2012-10-01 09:34:15.0 +0100
+++ ./portmaster.sh.in 2012-10-02 18:14:34.319249588 +0100
@@ -47,7 +47,7 @@
#=== Begin functions we always want to have ===
[root@ostracod /usr/ports/ports-mgmt/portmaster]# make patch
===> License BSD accepted by the user
===> Found saved configuration for portmaster-3.11
===> portmaster-3.14 depends on file: /usr/local/sbin/pkg - found
===> Extracting for portmaster-3.14
=> SHA256 Checksum OK for portmaster-portmaster-3.14-31009f6.tar.gz.
===> Patching for portmaster-3.14
===> Applying FreeBSD patches for portmaster-3.14
File to patch: ^C=> Patch patch-portmaster-pkgng failed to apply cleanly.
While if edited as suggested
[root@ostracod /usr/ports/ports-mgmt/portmaster]# !head
head -4 files/patch-portmaster-pkgng
--- ./portmaster.sh.in.orig 2012-10-01 09:34:15.0 +0100
+++ ./portmaster2012-10-02 18:14:34.319249588 +0100
@@ -47,7 +47,7 @@
#=== Begin functions we always want to have ===
[root@ostracod /usr/ports/ports-mgmt/portmaster]# make patch
===> License BSD accepted by the user
===> Found saved configuration for portmaster-3.11
===> portmaster-3.14 depends on file: /usr/local/sbin/pkg - found
===> Extracting for portmaster-3.14
=> SHA256 Checksum OK for portmaster-portmaster-3.14-31009f6.tar.gz.
===> Patching for portmaster-3.14
===> Applying FreeBSD patches for portmaster-3.14
[root@ostracod /usr/ports/ports-mgmt/portmaster]#
Vince
___
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] current switched by default to pkgng
On 10/10/2012 19:35, Stefan Esser wrote:
> Am 10.10.2012 19:14, schrieb Matthew Seaman:
>> On 10/10/2012 15:07, O. Hartmann wrote:
>>> Is ports-mgmt/portmaster now dealing with pkgng?
>>
>> Not yet. bdrewery has taken over the portmaster port and pkgng
>> related updates are expected in the near future.
>>
>> Until then, you still need to follow the instructions here:
>>
>> https://github.com/pkgng/pkgng/blob/master/FAQ.md#15
>
> In order to get the portmaster-pkgng patch to apply,
> the filename in the second line must be changed:
>
> from ./portmaster.sh.in
> to./portmaster
That's if you were to patch an already installed copy of portmaster.
The patch is designed to be placed in
${PORTSDIR}/ports-mgmt/portmaster/files/
so it would be applied as part of the normal process of building the
portmaster port. In which case portmaster.sh.in is definitely the
correct target.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
Am 10.10.2012 19:14, schrieb Matthew Seaman: > On 10/10/2012 15:07, O. Hartmann wrote: >> Is ports-mgmt/portmaster now dealing with pkgng? > > Not yet. bdrewery has taken over the portmaster port and pkgng > related updates are expected in the near future. > > Until then, you still need to follow the instructions here: > > https://github.com/pkgng/pkgng/blob/master/FAQ.md#15 In order to get the portmaster-pkgng patch to apply, the filename in the second line must be changed: from./portmaster.sh.in to ./portmaster Regards, STefan ___ 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] FYI: patch to ports that do not build with clang has been committed
On Wed, Oct 10, 2012 at 05:11:07PM +0200, Roman Divacky wrote: > Can we arrange exp builds with FORCE_BASE_CC_FOR_TESTING=clang that > will report all ports with USE_GCC=* but build with clang? Sure. That was kind of the intention. mcl ___ 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] current switched by default to pkgng
On Wed, Oct 10, 2012 at 07:11:22PM +0200, Victor Balada Diaz wrote: > On Wed, Oct 10, 2012 at 06:31:49PM +0200, Baptiste Daroussin wrote: > > Yes there is http://pkg.FreeBSD.org (no website in there no need to try to > > there) which will point you to pkgbeta.freebsd.org where some packages > > resides. > > > > Unfortunatly the package building cluster needs some time to get more > > reliable > > and thus the packages out there are not updated very often. > > > > regards, > > Bapt > > Is there anything we can do to help with build cluster reliability? > > Regards. > Victor. > -- > La prueba más fehaciente de que existe vida inteligente en otros > planetas, es que no han intentado contactar con nosotros. 1/ send me motivation :) 2/ if you are willing to code the new version, please contact me in private I'll share the designs, code repository and how it works. beware the architecture needed to test is not trivial at all :D regards, Bapt pgpwg342kKvKE.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 10:14 AM, Matthew Seaman wrote: > On 10/10/2012 15:07, O. Hartmann wrote: >> Is ports-mgmt/portmaster now dealing with pkgng? > > Not yet. bdrewery has taken over the portmaster port and pkgng related > updates are expected in the near future. > > Until then, you still need to follow the instructions here: > > https://github.com/pkgng/pkgng/blob/master/FAQ.md#15 Ok, nevermind. That's what I get for running make patch but not actually following through figuring out why the make patch didn't stick :). -Garrett ___ 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] current switched by default to pkgng
On Wed, Oct 10, 2012 at 7:07 AM, O. Hartmann wrote: > On 10/10/12 15:44, Baptiste Daroussin wrote: >> Hi all, >> >> If you are using the ports tree on a FreeBSD current setup, then you are >> concerned by the announce. >> >> As nvidia-drivers has been fixed and is now properly working with pkgng, the >> ports tree as been switch by default to use pkgng on FreeBSD Current based on >> version >= 117 which was the version when we tested the switch code. >> >> Make sure to read UPDATING (from ports) to correctly migrate your system or >> find >> instruction to make your system still running with legacy pkg_install tools. >> >> regards, >> Bapt >> > > Thank you very much. > > Is ports-mgmt/portmaster now dealing with pkgng? Hmm.. looks like it is now. Thanks, -Garrett ___ 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] current switched by default to pkgng
On 10/10/2012 15:07, O. Hartmann wrote: > Is ports-mgmt/portmaster now dealing with pkgng? Not yet. bdrewery has taken over the portmaster port and pkgng related updates are expected in the near future. Until then, you still need to follow the instructions here: https://github.com/pkgng/pkgng/blob/master/FAQ.md#15 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 06:31:49PM +0200, Baptiste Daroussin wrote: > Yes there is http://pkg.FreeBSD.org (no website in there no need to try to > there) which will point you to pkgbeta.freebsd.org where some packages > resides. > > Unfortunatly the package building cluster needs some time to get more reliable > and thus the packages out there are not updated very often. > > regards, > Bapt Is there anything we can do to help with build cluster reliability? Regards. Victor. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ 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] current switched by default to pkgng
On Wed, Oct 10, 2012 at 2:44 PM, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. I read UPDATING, but I'm still not sure what this means when I use ports and not packages. Does it mean that I should install pkg to have /var/db/pkg managed, but otherwise ports keeps working the same way, or? -- Simon L. B. Nielsen ___ 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] current switched by default to pkgng
--- On Wed, 10/10/12, Glen Barber wrote: > From: Glen Barber > Subject: Re: [HEADSUP] current switched by default to pkgng > To: "Baptiste Daroussin" > Cc: po...@freebsd.org, ports-annou...@freebsd.org, curr...@freebsd.org > Date: Wednesday, October 10, 2012, 6:51 AM > On Wed, Oct 10, 2012 at 03:44:21PM > +0200, Baptiste Daroussin wrote: > > Hi all, > > > > If you are using the ports tree on a FreeBSD current > setup, then you are > > concerned by the announce. > > > > As nvidia-drivers has been fixed and is now properly > working with pkgng, the > > ports tree as been switch by default to use pkgng on > FreeBSD Current based on > > version >= 117 which was the version when we > tested the switch code. > > > > Make sure to read UPDATING (from ports) to correctly > migrate your system or find > > instruction to make your system still running with > legacy pkg_install tools. > > > > Congratulations, and thank you for all of your hard work on > this! > > Glen > > I was/am confused by the UPDATING instructions. To make the switch: (which switch, and only for V10, from which to which?) ... Before and after step 3, how specifically is the system set up? ... Should any of this be done by persons using V9 immediately before a v9 v10 upgrade? And can another synopsis be written for those before the upgrade, specifically to prepare for either case after the upgrade? IOW more subsections and a longer explanation. (I think maybe more context before/after some of the steps in the procedure...) Just a suggestion. I could probably figure it all out later... J. Bouquet ___ 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] current switched by default to pkgng
On 10/10/12 15:44, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > > regards, > Bapt > Thank you very much. Is ports-mgmt/portmaster now dealing with pkgng? Regards, Oliver ___ 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] current switched by default to pkgng
On 10/10/2012 17:43, Bruce Cran wrote: > On 10/10/2012 17:31, Baptiste Daroussin wrote: >> Yes there is http://pkg.FreeBSD.org (no website in there no need to >> try to there) which will point you to pkgbeta.freebsd.org where some >> packages resides. > > On my systems pkg.freebsd.org doesn't seem to exist: > >> ping pkg.freebsd.org > ping: cannot resolve pkg.freebsd.org: No address associated with name > % dig IN SRV _http._tcp.pkg.freebsd.org ; <<>> DiG 9.8.3-P1 <<>> IN SRV _http._tcp.pkg.freebsd.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34727 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_http._tcp.pkg.freebsd.org.IN SRV ;; ANSWER SECTION: _http._tcp.pkg.freebsd.org. 3600 IN SRV 10 10 80 pkgbeta.FreeBSD.org. ;; Query time: 71 msec ;; SERVER: ::1#53(::1) ;; WHEN: Wed Oct 10 17:50:20 2012 ;; MSG SIZE rcvd: 83 -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 17:31, Baptiste Daroussin wrote: Yes there is http://pkg.FreeBSD.org (no website in there no need to try to there) which will point you to pkgbeta.freebsd.org where some packages resides. On my systems pkg.freebsd.org doesn't seem to exist: > ping pkg.freebsd.org ping: cannot resolve pkg.freebsd.org: No address associated with name -- Bruce Cran ___ 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] current switched by default to pkgng
On 10/10/2012 16:52, Simon L. B. Nielsen wrote: > I read UPDATING, but I'm still not sure what this means when I use > ports and not packages. It means that if you're a user of HEAD, and you don't opt out by setting WITHOUT_PKGNG=yes in make.conf, then: * the next time you use the ports, ports-mgmt/pkg will be installed as a dependency * pkgng will be used to register all the ports you subsequently install into /var/db/pkg/local.sqlite However, unless you take some preventive action, any ports that were installed before this update won't be added to the registry in local.sqlite. You'll end up with a mix of stuff using the old subdirs of /var/db/pkg from pkg_tools and the new local.sqlite from pkgng. Sorting that out is a one-time job to import the pkg_tools data into pkgng's database using pkg2ng, which is what the instructions in UPDATING describe. > Does it mean that I should install pkg to have /var/db/pkg managed, > but otherwise ports keeps working the same way, or? pkgng will need to be installed, yes. You'll need to switch to using pkgng commands rather than pkg_tools -- eg: pkg info -a to get a list of all installed ports. You need to patch portmaster(8) if you use that -- although a patched version will soon be available in ports. Apart from that, the ports will work pretty much exactly as they used to do. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 06:25:08PM +0200, Victor Balada Diaz wrote: > On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > > Hi all, > > > > If you are using the ports tree on a FreeBSD current setup, then you are > > concerned by the announce. > > > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > > ports tree as been switch by default to use pkgng on FreeBSD Current based > > on > > version >= 117 which was the version when we tested the switch code. > > > > Make sure to read UPDATING (from ports) to correctly migrate your system or > > find > > instruction to make your system still running with legacy pkg_install tools. > > > > regards, > > Bapt > > Hello Baptiste, > > Thanks a lot for your hard work. > > I've been using pkgng for a while on 9.0 and it's been a great experience. > > Right now you can use pointyhat packages[1] if you use old pkg tools. Is > there any plan to create binary packages more often than once per release? > > Regards. > Victor. > > [1]: http://pointyhat.freebsd.org/errorlogs/amd64-10-packages-latest/ > -- > La prueba más fehaciente de que existe vida inteligente en otros > planetas, es que no han intentado contactar con nosotros. Yes there is http://pkg.FreeBSD.org (no website in there no need to try to there) which will point you to pkgbeta.freebsd.org where some packages resides. Unfortunatly the package building cluster needs some time to get more reliable and thus the packages out there are not updated very often. regards, Bapt pgpOuMExyOSpU.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 04:52:45PM +0100, Simon L. B. Nielsen wrote: > On Wed, Oct 10, 2012 at 2:44 PM, Baptiste Daroussin wrote: > > Hi all, > > > > If you are using the ports tree on a FreeBSD current setup, then you are > > concerned by the announce. > > > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > > ports tree as been switch by default to use pkgng on FreeBSD Current based > > on > > version >= 117 which was the version when we tested the switch code. > > > > Make sure to read UPDATING (from ports) to correctly migrate your system or > > find > > instruction to make your system still running with legacy pkg_install tools. > > I read UPDATING, but I'm still not sure what this means when I use > ports and not packages. > > Does it mean that I should install pkg to have /var/db/pkg managed, > but otherwise ports keeps working the same way, or? > > -- > Simon L. B. Nielsen That means you either have to add WITHOUT_PKGNG to you make.conf so that nothing changes for you or follow the procedure (which is for ports only) and your local ports will be managed by pkgng, and you can forget about all the pkg_* tools :) regards, Bapt pgpCE4csaTwqK.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > > regards, > Bapt Hello Baptiste, Thanks a lot for your hard work. I've been using pkgng for a while on 9.0 and it's been a great experience. Right now you can use pointyhat packages[1] if you use old pkg tools. Is there any plan to create binary packages more often than once per release? Regards. Victor. [1]: http://pointyhat.freebsd.org/errorlogs/amd64-10-packages-latest/ -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ 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] current switched by default to pkgng
On Wed, Oct 10, 2012 at 08:42:39AM -0700, Jeffrey Bouquet wrote: > > > --- On Wed, 10/10/12, Glen Barber wrote: > > > From: Glen Barber > > Subject: Re: [HEADSUP] current switched by default to pkgng > > To: "Baptiste Daroussin" > > Cc: po...@freebsd.org, ports-annou...@freebsd.org, curr...@freebsd.org > > Date: Wednesday, October 10, 2012, 6:51 AM > > On Wed, Oct 10, 2012 at 03:44:21PM > > +0200, Baptiste Daroussin wrote: > > > Hi all, > > > > > > If you are using the ports tree on a FreeBSD current > > setup, then you are > > > concerned by the announce. > > > > > > As nvidia-drivers has been fixed and is now properly > > working with pkgng, the > > > ports tree as been switch by default to use pkgng on > > FreeBSD Current based on > > > version >= 117 which was the version when we > > tested the switch code. > > > > > > Make sure to read UPDATING (from ports) to correctly > > migrate your system or find > > > instruction to make your system still running with > > legacy pkg_install tools. > > > > > > > Congratulations, and thank you for all of your hard work on > > this! > > > > Glen > > > > > I was/am confused by the UPDATING instructions. > To make the switch: (which switch, and only for V10, from which > to which?) > ... > Before and after step 3, how specifically is the system set up? > ... > Should any of this be done by persons using V9 immediately before > a v9 v10 upgrade? And can another synopsis be written for those > before the upgrade, specifically to prepare for either case > after the upgrade? > IOW more subsections and a longer explanation. (I think maybe more > context before/after some of the steps in the procedure...) > > > Just a suggestion. I could probably figure it all out later... the AFFECT line was updated to specify which version of FreeBSD are concerned. This also concern people doing an upgrade from v9 to v10, but after the upgrade to v10. regards, Bapt pgpPqxtHpeEkW.pgp Description: PGP signature
Re: [HEADSUP] FYI: patch to ports that do not build with clang has been committed
Can we arrange exp builds with FORCE_BASE_CC_FOR_TESTING=clang that will report all ports with USE_GCC=* but build with clang? Lets say every three months or so? On Tue, Oct 09, 2012 at 07:45:23PM -0500, Mark Linimon wrote: > The commit mail hasn't gone through yet, so I guess I need to post this > first and reference the commit mail later. > > Sometime in the near future, the default CC on -current will be switched > to clang. The patch I have committed is a workaround -- an interim measure -- > to get ready for this transition. > > I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of > "USE_GCC=any" to a port's Makefile, and then committed that change to > various ports. In most (but not all!) cases this will tell the port > "build with gcc instead of clang" (*) . > > For those users with CC installed as gcc (including -stable), this > patch should have no effect. Variations of combinations have been > heavily tested on pointyhat-west. If there are any regressions, please > contact me. > > You can see the difference in the errorlogs here: > > With USE_GCC=any: > > > http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp-clang.20121007231359.pointyhat-west/index-category.html > > Without USE_GCC=any: > > > http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp-clang.20121005165436.pointyhat-west/index-category.html > > While the absolute number of errors is not that much different, that > is a false indication: over 2500 more packages are built "with" than > "without". > > For those who wish to build *only* with clang, and thus defeat the > workaround, simply set FORCE_BASE_CC_FOR_TESTING=anything, either > in the Makefile line, or, if you are adventurous, in your /etc/make.conf. > We appreciate all the testing that we can get (it is too much for any > small group of people, much less one person.) > > In the long run, I would like to see as many ports built natively with > clang as possible, and I appreciate the work that people have been doing > to move us towards that goal. However, once the switch is made, it > would have been a burden to everyone tracking -current to have suddenly > found themselves "enlisted" in that effort :-) So, for the medium-term, > this workaround should reduce the POLA violation. > > *Note* that due to the high number (over a thousand!) ports that do not > build with clang, I arbitrarily decided to apply the workaround only to > "ports that block 2 or more other ports from building" union "important > ports". This does not mean that the workaround shouldn't be applied to > other ports that are too hard to fix. > > This is part 1 of a set of patches that are being proposed to deal with > the switchover. As I merge and test them some more, I will put them out > for further review. > > Thanks. > > mcl > > * several ports are very, very, clever, and detect clang anyways; others > build with gcc if CC is unset, but don't with CC=gcc. These ports are > broken, and need to be fixed as we continue the process of switching over. > ___ > 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" ___ 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: MPSAFE VFS -- List of upcoming actions
On Wed, Oct 10, 2012 at 6:15 AM, Kevin Oberman wrote: > On Mon, Oct 8, 2012 at 7:57 AM, Attilio Rao wrote: >> On Fri, Sep 28, 2012 at 4:47 PM, Harald Schmalzbauer >> wrote: >>> schrieb Attilio Rao am 28.09.2012 16:18 (localtime): On Wed, Sep 26, 2012 at 12:02 PM, Harald Schmalzbauer wrote: > ... After many people willing to test fuse on STABLE_9, I made this patch that at least compiles there: http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch >>> >>> Thanks a lot! In the meantime I made the original patch compiling. I >>> simply looked at the changes which were made around july in the fuse >>> project to follow changes in head (checkpath(), vrecycle() and >>> vtruncbuf()) and "reverted" them. >>> Since I have no idea about the code I modified, I'm happy that you did a >>> more qualified patch set :-) >>> Of course, I didn't have a chance to test it because I'm also out for vacation right now but please do and report. >>> >>> Happy holiday!!! If you're by chance arround the Oktoberfest, drop me a >>> note, I'll pay you a Maß (or any other drink if you don't like >>> „Wiesnbier“) :-) >> >> I really hoped to make this year, but no luck :/ >> > ... > Some questions: Is this planned to be mfc'd and if so, how can one know? In which sense "how can one know?". We usually specify MFC timeouts in the commit message (not sure if this answers your concerns). >>> >>> Yep, that's what I wanted to know. So if there's no MFC timeout in the >>> log, it's not intended to be MFCd ever I guess. >>> >>> Thanks a lot! >>> World/Kernel compiled fine in the meantime, I'll do some sshfs tests. >> >> Did you do any test in the end? >> >> Thanks, >> Attilio > > i have done same testing and it clearly is more stable than the old > kmod. At least operations that crashed my system now work. > > I did see one weird anomaly, though. I had several NTFS file system > mounted, one a Windows OS. I also had a GELI encrypted UFS file system > mounted. They were both mounted and working. I finished with the data > disk and tried to unmount it. I got no error, but it remained mounted. > I did not actually try to access it. Figured it would umount when I > shut down or end up dirty and I'd have to fsck it. The unmount attempt > was using nautilus/gnome-mount. This is not the odd part, though. > > After the attempt to unmount the UFS device, I could no longer access > the Window_OS file system. an ls showed the mount point to be > d- and an attempt to list files in the directory reported that > the socket was not found. So it looks like the attempt to unmount one > NTFS FS deleted the socket for the other. > > This make absolutely no sense to me, but you understand the underlying > opertations better than I do. Repeated efforts have failed to > re-create the problem. I'm baffled. It is possible that there is no > relationship between the two odd things happening at about the same > time (NTFS volume lost socket and UFS disk won;t unmount, but reports > no errors), but neither has happened since. > > FWIW, I also see that no device numbers are listed for the fuse devices: > /dev/fuse 184319948 165594236 1872571290%/media/Media > /dev/fuse 110636028 82934424 2770160475%/media/Windows7_OS > > How does the system distinguish between them? Sorry, forgot to reply about this and it is due: differently from fuse4bsd version, this one doesn't do device cloning but uses devfs*cdevpriv() infrastructure. So effectively different filedescriptors are handled internally. This is why it requires further changes to the mount_fusefs(8) (because the vfs_mount operation also need further knowledge on the per-filedescriptor handle and it cannot acquire it easilly because it is not a devfs operation). Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein ___ 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: MPSAFE VFS -- List of upcoming actions
On Wed, Oct 10, 2012 at 6:15 AM, Kevin Oberman wrote: > On Mon, Oct 8, 2012 at 7:57 AM, Attilio Rao wrote: >> On Fri, Sep 28, 2012 at 4:47 PM, Harald Schmalzbauer >> wrote: >>> schrieb Attilio Rao am 28.09.2012 16:18 (localtime): On Wed, Sep 26, 2012 at 12:02 PM, Harald Schmalzbauer wrote: > ... After many people willing to test fuse on STABLE_9, I made this patch that at least compiles there: http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch >>> >>> Thanks a lot! In the meantime I made the original patch compiling. I >>> simply looked at the changes which were made around july in the fuse >>> project to follow changes in head (checkpath(), vrecycle() and >>> vtruncbuf()) and "reverted" them. >>> Since I have no idea about the code I modified, I'm happy that you did a >>> more qualified patch set :-) >>> Of course, I didn't have a chance to test it because I'm also out for vacation right now but please do and report. >>> >>> Happy holiday!!! If you're by chance arround the Oktoberfest, drop me a >>> note, I'll pay you a Maß (or any other drink if you don't like >>> „Wiesnbier“) :-) >> >> I really hoped to make this year, but no luck :/ >> > ... > Some questions: Is this planned to be mfc'd and if so, how can one know? In which sense "how can one know?". We usually specify MFC timeouts in the commit message (not sure if this answers your concerns). >>> >>> Yep, that's what I wanted to know. So if there's no MFC timeout in the >>> log, it's not intended to be MFCd ever I guess. >>> >>> Thanks a lot! >>> World/Kernel compiled fine in the meantime, I'll do some sshfs tests. >> >> Did you do any test in the end? >> >> Thanks, >> Attilio > > i have done same testing and it clearly is more stable than the old > kmod. At least operations that crashed my system now work. > > I did see one weird anomaly, though. I had several NTFS file system > mounted, one a Windows OS. I also had a GELI encrypted UFS file system > mounted. They were both mounted and working. I finished with the data > disk and tried to unmount it. I got no error, but it remained mounted. > I did not actually try to access it. Figured it would umount when I > shut down or end up dirty and I'd have to fsck it. The unmount attempt > was using nautilus/gnome-mount. This is not the odd part, though. Kevin, can you please report steps required to reproduce it in high detail (rather than a description), please? This will help in reproducing it and eventually fixing it. Attilio -- Peace can only be achieved by understanding - A. Einstein ___ 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] current switched by default to pkgng
On 10/10/2012 15:44, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. Thank you! signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > Congratulations, and thank you for all of your hard work on this! Glen pgpwaQS43VTNl.pgp Description: PGP signature
[HEADSUP] current switched by default to pkgng
Hi all, If you are using the ports tree on a FreeBSD current setup, then you are concerned by the announce. As nvidia-drivers has been fixed and is now properly working with pkgng, the ports tree as been switch by default to use pkgng on FreeBSD Current based on version >= 117 which was the version when we tested the switch code. Make sure to read UPDATING (from ports) to correctly migrate your system or find instruction to make your system still running with legacy pkg_install tools. regards, Bapt pgpz7S7kRpT25.pgp Description: PGP signature
Re: [HEADSUP] FYI: patch to ports that do not build with clang has been committed
On 10/10/2012 02:45, Mark Linimon wrote: The commit mail hasn't gone through yet, so I guess I need to post this first and reference the commit mail later. Sometime in the near future, the default CC on -current will be switched to clang. The patch I have committed is a workaround -- an interim measure -- to get ready for this transition. I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of "USE_GCC=any" to a port's Makefile, and then committed that change to various ports. In most (but not all!) cases this will tell the port "build with gcc instead of clang" (*) . Why not USE_GCC ?= any for the poor guys like me who build (some) ports with USE_GCC=4.6 ? For those users with CC installed as gcc (including -stable), this patch should have no effect. Variations of combinations have been heavily tested on pointyhat-west. If there are any regressions, please contact me. .. mcl Thanks, Claude Buisson ___ 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"
