12-STABLE: poudriere jail installation/updating is failing

2019-05-15 Thread O. Hartmann
Recently an error seem to have spread across our 12-STABLE platforms offering poudriere. Building the binaries for FreeBSD 12-STABLE (recent version r347613) on systems running FreeBSD 12-STABLE (r347613) worked very well before, but now the install process seem to fail on all boxes the very same

Re: error when updating 13.0-CURRENT i386 poudriere jail to r347606

2019-05-15 Thread Don Lewis
On 14 May, Don Lewis wrote: > I just ran into this error when updating my 13.0-CURRENT i386 jail to > r347606. I did not run into this problem when I upgraded by amd64 jail, > or when I updated the i386 jail to r347549. This doesn't seem to be very repeatable. I tried to upgrade the j

error when updating 13.0-CURRENT i386 poudriere jail to r347606

2019-05-14 Thread Don Lewis
I just ran into this error when updating my 13.0-CURRENT i386 jail to r347606. I did not run into this problem when I upgraded by amd64 jail, or when I updated the i386 jail to r347549. --- lib/libgcc_s__L --- sh /var/poudriere/jails/13CURRENTi386/usr/src/tools/install.sh -l rs -o root -g wheel

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 10:13:40AM -0800, Enji Cooper wrote: > > > PS: if anyone cares there are 3 patches sitting in freebsd-numerics@. > > Steve, > As some others noted in the private channel, you’ll need > to reset your Kerberos password via these instructions in the > committer’s

Re: Updating bugzilla password?

2019-02-04 Thread Enji Cooper
> On Feb 4, 2019, at 10:07 AM, Steve Kargl > wrote: > > On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: >> >> >> Let me loop in some other folks. Something might be up with mail forwarding >> for your account. >> > > Just sent an email to ka...@freebsd.org. It was forwarded

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: > > > Let me loop in some other folks. Something might be up with mail forwarding > for your account. > Just sent an email to ka...@freebsd.org. It was forwarded to my local account as expected. Checking /var/log/maillog, I see no

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 09:35:45AM -0800, Enji Cooper wrote: > > > Was this for your old FreeBSD.org address, by chance? > Yes. ka...@freebsd.org .forward is set up to send the email on to my local hacking account. -- Steve

Re: Updating bugzilla password?

2019-02-04 Thread Enji Cooper
gt;>> On Feb 4, 2019, at 08:34, Steve Kargl >>> <mailto:s...@troutmask.apl.washington.edu>> wrote: >>>> >>>> I have forgotten my bugzilla account password. I've >>>> entered the Login: account name, and clicked the >>>> "Forgot Pas

Re: Updating bugzilla password?

2019-02-04 Thread Enji Cooper
I've >>> entered the Login: account name, and clicked the >>> "Forgot Password" button. Expecting to receiving an >>> email that would provide instructions for updating >>> the password. That email never comes. So, is bugzilla >>> broken

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
ot Password" button. Expecting to receiving an > > email that would provide instructions for updating > > the password. That email never comes. So, is bugzilla > > broken? Is it impossible to reset a bugzilla password; > > thereby rendering an account abandoned? > >

Re: Updating bugzilla password?

2019-02-04 Thread Kurt Jaeger
Hi! > > I have forgotten my bugzilla account password. I've > > entered the Login: account name, and clicked the > > "Forgot Password" button. > I'll file a bugzilla bug on your behalf in 10-20 mins. There's > a better mailing list for this kind of query.. it's just evading my mind.

Re: Updating bugzilla password?

2019-02-04 Thread Enji Cooper
> On Feb 4, 2019, at 08:34, Steve Kargl > wrote: > > I have forgotten my bugzilla account password. I've > entered the Login: account name, and clicked the > "Forgot Password" button. Expecting to receiving an > email that would provide instructions for updat

Updating bugzilla password?

2019-02-04 Thread Steve Kargl
I have forgotten my bugzilla account password. I've entered the Login: account name, and clicked the "Forgot Password" button. Expecting to receiving an email that would provide instructions for updating the password. That email never comes. So, is bugzilla broken? Is it impossibl

Re: Suppose a user on a pilgrimage to /usr/src, modified UPDATING

2018-12-10 Thread Jamie Landeg-Jones
miltonott wrote: > O great and powerful FreeBSD biome. May I redirect from here to a paste > site > service, a rearrangement of development directory head file /usr/src/UPDATING. sorry, but left & right justified text is horrible, especially with a mo

Re: Suppose a user on a pilgrimage to /usr/src, modified UPDATING

2018-12-10 Thread David Wolfskill
On Mon, Dec 10, 2018 at 09:49:13AM +, miltonott wrote: > O great and powerful FreeBSD biome. May I redirect from here to a paste > site > service, a rearrangement of development directory head file /usr/src/UPDATING. > > UPDATING.ORIG -> http://dpaste.com/1WRWG26.

Suppose a user on a pilgrimage to /usr/src, modified UPDATING

2018-12-10 Thread miltonott
O great and powerful FreeBSD biome. May I redirect from here to a paste site service, a rearrangement of development directory head file /usr/src/UPDATING. UPDATING.ORIG -> http://dpaste.com/1WRWG26.txt - UPDATING -> http://dpaste.com/1Z4E3H1.txt - UPDATING.DIFF -> http://d

Re: drm changes and updating to 12.0

2018-11-06 Thread Carsten Mattner
On Mon, Nov 5, 2018 at 10:18 PM Johannes Lundberg wrote: > > On Mon, Nov 5, 2018 at 10:05 PM Carsten Mattner > wrote: >> >> On Mon, Nov 5, 2018 at 7:00 PM Johannes Lundberg wrote: >> >> > Which Linux version is tracked is listed in the port info. >> > drm-stable-kmod is currently at Linux 4.9

Re: drm changes and updating to 12.0

2018-11-05 Thread Johannes Lundberg
On Mon, Nov 5, 2018 at 10:05 PM Carsten Mattner wrote: > On Mon, Nov 5, 2018 at 7:00 PM Johannes Lundberg > wrote: > > > Which Linux version is tracked is listed in the port info. > > drm-stable-kmod is currently at Linux 4.9 > > drm-devel-kmod is currently at Linux 4.16 > > This is very useful

Re: drm changes and updating to 12.0

2018-11-05 Thread Carsten Mattner
On Mon, Nov 5, 2018 at 7:00 PM Johannes Lundberg wrote: > Which Linux version is tracked is listed in the port info. > drm-stable-kmod is currently at Linux 4.9 > drm-devel-kmod is currently at Linux 4.16 This is very useful to know. I can't find the Linux kernel version in drm-legacy-kmod

Re: drm changes and updating to 12.0

2018-11-05 Thread Konstantin Belousov
On Mon, Nov 05, 2018 at 06:56:57PM +, Johannes Lundberg wrote: > The short version is that drm2 in base (/sys/dev/drm2/) have support for hw > up to 2013 (maybe 2014), that's why drm-legacy-kmod is said to support hw > up to that year. drm2 in base supports everything from gen3 to gen6 and did

Re: drm changes and updating to 12.0

2018-11-05 Thread Johannes Lundberg
ere's a better way to message what's supported, I'm all ears. > > Lacking a better plan: is there a list of which card/gpu is > currently known to work with which drm(-kmod) version, perhaps > gathered from those involved with development? (Is this based on work > from Linu

Re: drm changes and updating to 12.0

2018-11-05 Thread Warner Losh
On Mon, Nov 5, 2018 at 10:23 AM Robert Huff wrote: > > Warner Losh writes: > > > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > > on the system I am using to send this

Re: drm changes and updating to 12.0

2018-11-05 Thread Robert Huff
Warner Losh writes: > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > on the system I am using to send this message. I bought it in 2011, the > year Sandy Bridge

Re: drm changes and updating to 12.0

2018-11-05 Thread Warner Losh
hich will be updated from 11. to 12.0 once 12 is out > > > and the initial round of bugs are squashed. > > > One system is being done now, to allow time to catch any major > > > problems and then plan the update process. > > > Looking at src/

Re: drm changes and updating to 12.0

2018-11-04 Thread Kevin Oberman
round of bugs are squashed. > > One system is being done now, to allow time to catch any major > > problems and then plan the update process. > > Looking at src/UPDATING, the only thing I don't understand is the > > whole drm-kmod change. Is there an authoritative write

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Rebecca Cran
On Sunday, 4 November 2018 16:07:17 MST Warner Losh wrote: > Finally, I have a /dev/efi/esp pseudo label support coded up for geom > (along with /dev/efi/boot for the putative root device). There's some > issues with it, so I set it aside some time ago to work on other higher > priority things.

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 4:10 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > > > I think that's a really really bad idea. We should *NEVER* create them by > > default. We are only sliding by on the coat-tails of compatibility by > using > >

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Rebecca Cran
On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > I think that's a really really bad idea. We should *NEVER* create them by > default. We are only sliding by on the coat-tails of compatibility by using > efi/boot/boot*.efi. We shouldn't use those at all, unless there's a > compelling

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 2:27 PM Allan Jude wrote: > On 2018-11-04 16:20, Rebecca Cran wrote: > > I'm currently working on creating and updating the ESP (EFI System > Partition) > > for UEFI booting during installation and installworld. > > > > During installation, w

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 2:43 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > > > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi > is > > hard one of course. But then again, it is problem only when we can not > > setup EFI

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Oliver Pinter
On 11/4/18, Rebecca Cran wrote: > On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > >> it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi >> is >> hard one of course. But then again, it is problem only when we can not >> setup EFI bootmanager variables ? the

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Rebecca Cran
On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi is > hard one of course. But then again, it is problem only when we can not > setup EFI bootmanager variables ? the bootx64.efi is default when bootmgr > is not

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Toomas Soome
> On 4 Nov 2018, at 23:25, Allan Jude wrote: > > On 2018-11-04 16:20, Rebecca Cran wrote: >> I'm currently working on creating and updating the ESP (EFI System >> Partition) >> for UEFI booting during installation and installworld. >> >> During instal

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Rebecca Cran
On Sunday, 4 November 2018 14:25:26 MST Allan Jude wrote: > I wouldn't depend on the /etc/fstab entry existing. I am not sure I want > installworld randomly fobbing around in my EFI partition. Especially if, > for example, my EFI/BOOT is not FreeBSD, but rEFInd or something. I tend to agree. I

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Allan Jude
On 2018-11-04 16:20, Rebecca Cran wrote: > I'm currently working on creating and updating the ESP (EFI System Partition) > for UEFI booting during installation and installworld. > > During installation, with my changes it gets mounted on /boot/efi and > loader.efi > copied

UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Rebecca Cran
I'm currently working on creating and updating the ESP (EFI System Partition) for UEFI booting during installation and installworld. During installation, with my changes it gets mounted on /boot/efi and loader.efi copied into /boot/efi/EFI/FreeBSD and /boot/efi/EFI/BOOT. An entry gets added

Re: drm changes and updating to 12.0

2018-11-04 Thread Niclas Zeising
and then plan the update process. Looking at src/UPDATING, the only thing I don't understand is the whole drm-kmod change. Is there an authoritative write-up on what's going on, how to choose the right drivers for my hardware, and how to do this from source without forcing a fresh install

drm changes and updating to 12.0

2018-11-04 Thread Robert Huff
. Looking at src/UPDATING, the only thing I don't understand is the whole drm-kmod change. Is there an authoritative write-up on what's going on, how to choose the right drivers for my hardware, and how to do this from source without forcing a fresh install

updating my pordriere oven to latest CURRENT

2018-09-17 Thread Matthias Apitz
Hello, I'm short before updating my poudriere oven, a Dell PowerEdge r210, from r318593 to r338641. I have there a ZFS in use for poudriere, created with: # zpool create poudriere /dev/da1 and set in /usr/local/etc/poudriere.conf: ZPOOL=poudriere ZROOTFS=/poudriere # zpool

Re: head's /usr/src/UPDATING vs. "LOADER_DEFAULT_INTERP, documented in build(7)": not documented yet

2018-08-26 Thread Mark Millard
de > is in /usr/src/stand. [Looks like userboot is /boot/userboot.so and is associated with bhyvload.] >> (This assumes that all the changes are in the freebsd-ufs partition >> involved and that the freebsd-boot partition involved need not be >> updated.) > > The freebsd-boot

Re: head's /usr/src/UPDATING vs. "LOADER_DEFAULT_INTERP, documented in build(7)": not documented yet

2018-08-26 Thread Dag-Erling Smørgrav
ains the code that loads the loader and should not need updating. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to &

head's /usr/src/UPDATING vs. "LOADER_DEFAULT_INTERP, documented in build(7)": not documented yet

2018-08-26 Thread Mark Millard
Quoting UPDATING for head: 20180818: The default interpreter has been switched from 4th to Lua. LOADER_DEFAULT_INTERP, documented in build(7), will override the default interpreter. If you have custom FORTH code you will need to set LOADER_DEFAULT_INTERP=4th

Re: options COMPAT_AOUT to file UPDATING to know

2018-07-14 Thread Stefan Esser
Am 13.07.18 um 19:56 schrieb joun...@yahoo.co.uk: > > === Reason: > > In compiling the kernel again after a long time after 'pkg upgrade' the > following errors. The Intel graphics card is in use and something had changed, > the 'startx' did not start the XFCE session. This was the reason to

options COMPAT_AOUT to file UPDATING to know

2018-07-13 Thread joun...@yahoo.co.uk
esolution: Adding options COMPAT_AOUT to the kernel configuration file. This added the necessary 'imgact_aout.o' to the linking and the 'aout_sysvec' was found. __ It would be nice if a message was written in the /usr/src/UPDATING about this to prevent the unnecessary

updating via svn and usb2 thumbdrives

2018-03-07 Thread tech-lists
Hi, When updating, particularly when downloading the src or ports tree for the first time, even though I've taken all approaches possible to speed up access to attached usb2 drives, I'll get these errors which will cause the update to bail: Aports/www/py-django-otp svn: E120106: ra_serf

Re: [Bug 223383] pathconf querying for posix_falloc not supported on freebsd [devel/llvm*'s lld's are also broken by this for zfs and need updating]

2017-11-12 Thread Brooks Davis
choice of errno on the part of POSIX.) > > > > PR: 223383, 223440 > > Reported by: Mark Millard > > Sponsored by: The FreeBSD Foundation > > > > Changes: > > _U stable/11/ > > stable/11/contrib/llvm/lib/Support/Unix/Path.inc > >

updating /usr/ports to HEAD in a jail r318593 (May 2017)

2017-11-11 Thread Matthias Apitz
in the ports tree which need a newer kernel? I glanced through /usr/ports/UPDATING but could no see anything. Any pointers? Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub signature.asc

Re: [Bug 223383] pathconf querying for posix_falloc not supported on freebsd [devel/llvm*'s lld's are also broken by this for zfs and need updating]

2017-11-09 Thread Mark Millard
e/11/contrib/llvm/lib/Support/Unix/Path.inc > > -- > You are receiving this mail because: > You are on the CC list for the bug. [Context a zfs file system.] >From /usr/src/UPDATING: 20171106: The naive and non-compliant support of posix_fallocate(2) in ZFS has bee

Re: questions re updating to -CURRENT

2017-09-12 Thread Jakub Lach
> Maybe ... but this is one of those things that (in my > experience) either Just Work or Go Horribly Wrong. That's why I would go at least (latest) -RELEASE to -STABLE before going -STABLE to -CURRENT, if you must. Why trying your luck with big jumps? -- Sent from:

Re: questions re updating to -CURRENT

2017-09-10 Thread owner-freebsd-current
Jakub Lach writes: > Are you sure you are not using drm2 already? I would check > with kldstat. Ckecked; it's there. > The message in UPDATING is about removing > old code from the tree. Maybe ... but this is one of those things that (in my experience) eith

Re: questions re updating to -CURRENT

2017-09-08 Thread Jakub Lach
ssage in UPDATING is about removing old code from the tree. In any case, RELEASE to STABLE to CURRENT could be a less bumpy ride. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html ___ freebsd-current@freebsd.org mailing

questions re updating to -CURRENT

2017-08-29 Thread owner-freebsd-current
Hello: I finally get to update a system from: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64 to -CURRENT. After reading src/UPDATING, I understand everything (I think) _except_: 20170311: The old drm (sys/dev/drm/) drivers for i915 and radeon

Re: A question about updating src & ports

2016-12-30 Thread Benjamin Kaduk
On Thu, Dec 29, 2016 at 11:44:20AM +0100, O. Hartmann wrote: > > from my own experience I left the path of "portsnap" and stay with svn alone. > portsnap > tends to "flood" the /var filesystem with a tremendous number of files over > time. Each > time you issue "portsnap fetch update", a file

Re: A question about updating src & ports

2016-12-29 Thread RW
On Thu, 29 Dec 2016 18:11:38 +0800 blubee blubeeme wrote: > Can I mix portsnap fetch update or should I just continue to use svn > update /usr/ports As a general rule don't mix methods in the same directory. ___ freebsd-current@freebsd.org mailing

Re: A question about updating src & ports

2016-12-29 Thread Julian H. Stacey
Hi, Reference: > From: blubee blubeeme > Date: Thu, 29 Dec 2016 18:11:38 +0800 blubee blubeeme wrote: > Howdy > > I went through the process of building world for the first time, that was > interesting but I got it. svn clean up prior object files, build

Re: A question about updating src & ports

2016-12-29 Thread O. Hartmann
Am Thu, 29 Dec 2016 18:11:38 +0800 blubee blubeeme schrieb: > Howdy > > I went through the process of building world for the first time, that was > interesting but I got it. svn clean up prior object files, build world, > kernel, etc. > > Okay that part is fine > > I have

Re: A question about updating src & ports

2016-12-29 Thread Renato Botelho
> On 29 Dec 2016, at 08:11, blubee blubeeme wrote: > > Howdy > > I went through the process of building world for the first time, that was > interesting but I got it. svn clean up prior object files, build world, > kernel, etc. > > Okay that part is fine > > I have a

A question about updating src & ports

2016-12-29 Thread blubee blubeeme
Howdy I went through the process of building world for the first time, that was interesting but I got it. svn clean up prior object files, build world, kernel, etc. Okay that part is fine I have a question about keeping ports up to date, in the past I did portsnap fetch update to update the

UPDATING up for an inclusion?

2016-08-27 Thread Jeffrey Bouquet
Possible man 7 development could be included in /usr/src/UPDATING carefully... by someone way more skilled/versed than I. [ Twelve years and the first I've seen of that man page... today. ] Howsoever, I may have read recent forum or freebsd-questions posts that could update the man page

Re: callout_drain either broken or man page needs updating

2016-07-15 Thread Larry Rosenman
On 2016-07-15 13:34, Matthew Macy wrote: On Fri, 15 Jul 2016 01:43:03 -0700 Gleb Smirnoff wrote > On Thu, Jul 14, 2016 at 10:14:46PM -0700, Matthew Macy wrote: > M> > On 07/15/16 05:45, Matthew Macy wrote: > M> > > glebius last commit needs some further

Re: callout_drain either broken or man page needs updating

2016-07-15 Thread Matthew Macy
On Fri, 15 Jul 2016 01:43:03 -0700 Gleb Smirnoff wrote > On Thu, Jul 14, 2016 at 10:14:46PM -0700, Matthew Macy wrote: > M> > On 07/15/16 05:45, Matthew Macy wrote: > M> > > glebius last commit needs some further re-work. > M> > > M> > Glebius

Re: callout_drain either broken or man page needs updating

2016-07-15 Thread Hans Petter Selasky
On 07/15/16 10:43, Gleb Smirnoff wrote: On Thu, Jul 14, 2016 at 10:14:46PM -0700, Matthew Macy wrote: M> > On 07/15/16 05:45, Matthew Macy wrote: M> > > glebius last commit needs some further re-work. M> > M> > Glebius commit needs to be backed out, at least the API change that M> > changes

Re: callout_drain either broken or man page needs updating

2016-07-15 Thread Gleb Smirnoff
On Thu, Jul 14, 2016 at 10:14:46PM -0700, Matthew Macy wrote: M> > On 07/15/16 05:45, Matthew Macy wrote: M> > > glebius last commit needs some further re-work. M> > M> > Glebius commit needs to be backed out, at least the API change that M> > changes the return value when calling

Re: callout_drain either broken or man page needs updating

2016-07-14 Thread Matthew Macy
On Thu, 14 Jul 2016 21:21:57 -0700 Hans Petter Selasky wrote > On 07/15/16 05:45, Matthew Macy wrote: > > glebius last commit needs some further re-work. > > Hi, > > Glebius commit needs to be backed out, at least the API change that > changes the

Re: callout_drain either broken or man page needs updating

2016-07-14 Thread Hans Petter Selasky
On 07/15/16 05:45, Matthew Macy wrote: glebius last commit needs some further re-work. Hi, Glebius commit needs to be backed out, at least the API change that changes the return value when calling callout_stop() when the callout is scheduled and being serviced. Simply because there is code

callout_drain either broken or man page needs updating

2016-07-14 Thread Matthew Macy
Upon updating my drm-next branch to the latest -CURRENT callout_drain returning no longer means that the function was in fact pending when it was called. This little bit of code will panic because dwork->wq is NULL, because the callout was _not_ in fact enqueued. So either it's no lon

Fwd: Re: UPDATING revision and seperate edge-case question(s)

2016-03-12 Thread Jeffrey Bouquet
Sorry, sent it to this same email originally, on to the list... - Start Forwarded Message - Sent: Sat, 12 Mar 2016 17:33:31 -0800 (PST) From: "Jeffrey Bouquet" <jbt...@iherebuywisely.com> To: "jbtakk" <jbt...@iherebuywisely.com> Subject: Re: UPDATING

UPDATING revision and seperate edge-case question(s)

2016-03-12 Thread Jeffrey Bouquet
Having unexpectedly built world and kernel GENERIC on 3-8 Current, that is not the principal system [1] ... browsing its UPDATING at the bottom the method(s) are not so precise and/or informative [follows...] [make world] make kernel installworld where is installkernel make buildworld

Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

2016-01-10 Thread O. Hartmann
Am Sat, 9 Jan 2016 02:18:27 -0800 Xin Li schrieb: > Please subscribe: > > https://bugs.freebsd.org/205882 > > You can locally apply -r292066 or modify the code to skip the check when > pguid is 0 as a stopgap. > > Cheers, > Is there any chance this get sorted out and

Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

2016-01-10 Thread Alan Somers
On Sun, Jan 10, 2016 at 1:32 AM, O. Hartmann wrote: > Am Sat, 9 Jan 2016 02:18:27 -0800 > Xin Li schrieb: > >> Please subscribe: >> >> https://bugs.freebsd.org/205882 >> >> You can locally apply -r292066 or modify the code to skip the check when

Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

2016-01-09 Thread Ranjan1018 .
2016-01-09 11:18 GMT+01:00 Xin Li : > Please subscribe: > > https://bugs.freebsd.org/205882 > > You can locally apply -r292066 or modify the code to skip the check when > pguid is 0 as a stopgap. > > Cheers, > > Thank you Xin it works, I have replace vdev_geom.c r292066 with

Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

2016-01-09 Thread Xin Li
Please subscribe: https://bugs.freebsd.org/205882 You can locally apply -r292066 or modify the code to skip the check when pguid is 0 as a stopgap. Cheers, signature.asc Description: OpenPGP digital signature

[zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

2016-01-09 Thread Ranjan1018 .
ONLINE 0 0 0 cache gpt/cache ONLINE 0 0 0 After updating 11.0-CURRENT from r291458 to r293055 the cache stops working. I am running: # uname -a FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r293055: Sun Jan 3 00:15:33 CET 2016 root@ativ

Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

2016-01-09 Thread O. Hartmann
0 errors on Mon Jan 4 00:02:42 2016 > > config: > >NAME STATE READ WRITE CKSUM > >sys ONLINE 0 0 0 > > gpt/sys0 ONLINE 0 0 0 > > cache > > gpt/cache ONLINE 0

Is updating contrib/gcc desirable?

2015-12-31 Thread Yuri
Currently the only way how fortran is supported is through lang/gccXX ports. They install their own version of libgcc.so, which is incompatible with the base. As a result, mix of fortran ports and regular C++ ports is broken. This breaks most of science/math software on FreeBSD. Would it be

Re: Is updating contrib/gcc desirable?

2015-12-31 Thread David Chisnall
On 31 Dec 2015, at 11:59, Yuri wrote: > > Would it be the right way of solving the problem if I submitted an update of > contrib/gcc and contrib/gcclibs from the gcc-5.3.0 tree? No. > Any pitfalls with this? The newer versions of GCC are GPLv3 and so are unacceptable for the

Re: Is updating contrib/gcc desirable?

2015-12-31 Thread Yuri
On 12/31/2015 04:15, David Chisnall wrote: The newer versions of GCC are GPLv3 and so are unacceptable for the FreeBSD base system. Most of libgcc in base now comes from compiler-rt. The correct solution would be to identify the missing functionality in compiler-rt so that it can be fixed

src/UPDATING to more precisely document usr.bin/make removal

2015-06-21 Thread Julian H. Stacey
Hi Warner cc current@, I discovered make had dissapeared (A local patch script failed), so I had to hunt. Let's make text string hunting easier with this for 11.0-CURRENT/src/UPDATING Sun Jun 21 16:29:53 2015 52,53c52,54 FreeBSD's old make (fmake) has been removed from the system

11.0-CURRENT: SBUF_INCLUDENUL, /head/sys/kern/subr_sbuf.c -r280193 vs. updating to head snaphot -r280598

2015-03-27 Thread Mark Millard
Basic context: # freebsd-version -ku; uname -apKU 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279514M: Sat Mar 21 05:15:23 PDT 2015 root@FBSDG5C0:/usr/obj/usr/srcC/sys/GENERIC64vtsc-NODEBUG powerpc powerpc64 1100062 1100062 The problem: Summary of

11.0-CURRENT: BIO_F_DGRAM_SCTP_WRITE, /head/crypto/openssl/crypto/bio/bio_err.c -r280297 vs. updating to head snaphot -r280598

2015-03-27 Thread Mark Millard
Basic context: # freebsd-version -ku; uname -apKU 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279514M: Sat Mar 21 05:15:23 PDT 2015 root@FBSDG5C0:/usr/obj/usr/srcC/sys/GENERIC64vtsc-NODEBUG powerpc powerpc64 1100062 1100062 The problem: Summary of

11.0-CURRENT: DTLS1_VERSION_MAJOR, /head/crypto/openssl/ssl/ssl_asn1.c -r280297 vs. updating to head snaphot -r280598

2015-03-27 Thread Mark Millard
/head/crypto/openssl/ssl/ssl_asn1.c has a similar issue to /head/crypto/openssl/crypto/bio/bio_err.c but relative to: /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -fpic -DPIC -O2 -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libssl/../../../crypto/openssl

Re: 11.0-CURRENT: SCTP_MAX_CWND, lib/libc/net/sctp_sys_calls.c -r279859 vs. updating to head snaphot -r280598

2015-03-27 Thread Ian Lepore
On Fri, 2015-03-27 at 10:17 -0500, Michael Tuexen wrote: On 26 Mar 2015, at 21:36, Mark Millard mar...@dsl-only.net wrote: Basic context: # freebsd-version -ku; uname -apKU 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279514M: Sat Mar 21

Re: 11.0-CURRENT: SCTP_MAX_CWND, lib/libc/net/sctp_sys_calls.c -r279859 vs. updating to head snaphot -r280598

2015-03-27 Thread Michael Tuexen
On 26 Mar 2015, at 21:36, Mark Millard mar...@dsl-only.net wrote: Basic context: # freebsd-version -ku; uname -apKU 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279514M: Sat Mar 21 05:15:23 PDT 2015

11.0-CURRENT: SCTP_MAX_CWND, lib/libc/net/sctp_sys_calls.c -r279859 vs. updating to head snaphot -r280598

2015-03-26 Thread Mark Millard
Basic context: # freebsd-version -ku; uname -apKU 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279514M: Sat Mar 21 05:15:23 PDT 2015 root@FBSDG5C0:/usr/obj/usr/srcC/sys/GENERIC64vtsc-NODEBUG powerpc powerpc64 1100062 1100062 The problem: Summary of

Re: updating standard headers to meet c++11 standard

2014-05-21 Thread Shane Ambler
are technically correct but it also appears that we are the odd one out. Which would depend on what you consider the default standard. I have just been updating graphics/openimageio to 1.4.7 Larry is adding the following to fix compile on several targets https://github.com/OpenImageIO/oiio/pull/858

updating standard headers to meet c++11 standard

2014-05-20 Thread Shane Ambler
When including stdint.h in c++ we can #define __STDC_LIMIT_MACROS so that we get macros like INT32_MAX defined. Also related is __STDC_CONSTANT_MACROS I have recently found that the need for these has been removed within the c++11 standard. This year old bug report was to update glibc to this

Re: updating standard headers to meet c++11 standard

2014-05-20 Thread David Chisnall
Hi, I thought I'd already fixed this a year or so ago. Looking at my system, I see this in cdefs.h: /* C++11 exposes a load of C99 stuff */ #if defined(__cplusplus) __cplusplus = 201103L #define __LONG_LONG_SUPPORTED #ifndef __STDC_LIMIT_MACROS #define __STDC_LIMIT_MACROS #endif #ifndef

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-26 Thread Scot Hetzel
On Tue, Jan 21, 2014 at 3:11 PM, Thomas Hoffmann trh...@gmail.com wrote: On Tue, Jan 21, 2014 at 10:47 AM, Andriy Gapon a...@freebsd.org wrote: on 21/01/2014 13:18 Andrey V. Elsukov said the following: On 21.01.2014 14:45, Andriy Gapon wrote: What do I need to do to get the boot2 code

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-26 Thread Thomas Hoffmann
On Sun, Jan 26, 2014 at 3:46 AM, Scot Hetzel swhet...@gmail.com wrote: On Tue, Jan 21, 2014 at 3:11 PM, Thomas Hoffmann trh...@gmail.com wrote: On Tue, Jan 21, 2014 at 10:47 AM, Andriy Gapon a...@freebsd.org wrote: on 21/01/2014 13:18 Andrey V. Elsukov said the following: On 21.01.2014

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-21 Thread Andrey V. Elsukov
On 20.01.2014 23:32, Thomas Hoffmann wrote: I am running 11.0-CURRENT (r260850) with zfs on root with MBR. After upgrading my 10.0-RELEASE (r260669) system to 11.0-CURRENT (r260850) my zpools reported that they needed to be upgraded. So, I upgraded my zpools and I am attempting to update the

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-21 Thread Andriy Gapon
on 21/01/2014 11:35 Andrey V. Elsukov said the following: On 20.01.2014 23:32, Thomas Hoffmann wrote: I am running 11.0-CURRENT (r260850) with zfs on root with MBR. After upgrading my 10.0-RELEASE (r260669) system to 11.0-CURRENT (r260850) my zpools reported that they needed to be upgraded.

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-21 Thread Andrey V. Elsukov
On 21.01.2014 14:45, Andriy Gapon wrote: What do I need to do to get the boot2 code written to /dev/ada0s1a? This will work only if ada0s1a isn't in use. The debugflags trick works only for whole disk, i.e. for geoms with rank=1. Another way is calculate needed offset and write bootcode

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-21 Thread Andriy Gapon
on 21/01/2014 13:18 Andrey V. Elsukov said the following: On 21.01.2014 14:45, Andriy Gapon wrote: What do I need to do to get the boot2 code written to /dev/ada0s1a? This will work only if ada0s1a isn't in use. The debugflags trick works only for whole disk, i.e. for geoms with rank=1.

Re: Problem updating bootcode on ZFS on root system with MBR

2014-01-21 Thread Thomas Hoffmann
On Tue, Jan 21, 2014 at 10:47 AM, Andriy Gapon a...@freebsd.org wrote: on 21/01/2014 13:18 Andrey V. Elsukov said the following: On 21.01.2014 14:45, Andriy Gapon wrote: What do I need to do to get the boot2 code written to /dev/ada0s1a? This will work only if ada0s1a isn't in use. The

Problem updating bootcode on ZFS on root system with MBR

2014-01-20 Thread Thomas Hoffmann
I am running 11.0-CURRENT (r260850) with zfs on root with MBR. After upgrading my 10.0-RELEASE (r260669) system to 11.0-CURRENT (r260850) my zpools reported that they needed to be upgraded. So, I upgraded my zpools and I am attempting to update the bootcode (as required). I managed to get the

Re: /usr/ports/UPDATING entry September 04, 2013

2013-10-14 Thread Guido Falsi
On 10/13/13 18:40, Joe Nosay wrote: Will the pkg upgrade work with applications built from ports and not pkg add $APPLICATION? I'm not sure What you mean. the pkg upgrade command works only using binary packages, which can come and official repository or your own one. This is going to

Re: /usr/ports/UPDATING entry September 04, 2013

2013-10-14 Thread Joe Nosay
On Mon, Oct 14, 2013 at 3:43 AM, Guido Falsi madpi...@freebsd.org wrote: On 10/13/13 18:40, Joe Nosay wrote: Will the pkg upgrade work with applications built from ports and not pkg add $APPLICATION? I'm not sure What you mean. the pkg upgrade command works only using binary packages,

/usr/ports/UPDATING entry September 04, 2013

2013-10-13 Thread Joe Nosay
Will the pkg upgrade work with applications built from ports and not pkg add $APPLICATION? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Updating from 9.1-release to svn head: what might be the problem?

2013-06-20 Thread Super Bisquit
I've been using 10.0 current for a few months now with no problem. What I do know about virtual machines is that they don't share kernel resources too well. If both virtual machines are trying to access the kernel, there will be a problem. On Wed, Jun 19, 2013 at 10:51 PM, Alexey Dokuchaev

Re: Updating from 9.1-release to svn head: what might be the problem?

2013-06-19 Thread Alexey Dokuchaev
On Tue, Jun 18, 2013 at 10:21:33PM +0700, Alexey Dokuchaev wrote: I've been trying to install fresh -CURRENT (in VirtualBox/i386), and since recent snapshots did not work for me, had to do this by first installing from 9.1-release .iso. After svn co .../head /usr/src and standard make

  1   2   3   4   5   >