Re: [HEADSUP] making /bin/sh the default shell for root

2021-10-12 Thread Guido Falsi via freebsd-current
On 12/10/21 14:21, Gary Jennejohn wrote: On Tue, 12 Oct 2021 06:59:00 -0400 grarpamp wrote: No. The system shell is supposed to make the system usable by the users. Actually, the real problem is that the easiest way to shoot one's own foot is by changing the language (say, the shell) spoken

Re: recent head having significantly less "avail memory"

2021-09-13 Thread Guido Falsi via freebsd-current
On 14/09/21 00:12, Konstantin Belousov wrote: On Mon, Sep 13, 2021 at 10:07:46PM +0200, Guido Falsi wrote: On 13/09/21 19:08, Konstantin Belousov wrote: On Mon, Sep 13, 2021 at 02:59:25PM +0200, Guido Falsi via freebsd-current wrote: Hi, I updated head recently and today I noticed

Re: recent head having significantly less "avail memory"

2021-09-13 Thread Guido Falsi via freebsd-current
On 13/09/21 19:08, Konstantin Belousov wrote: On Mon, Sep 13, 2021 at 02:59:25PM +0200, Guido Falsi via freebsd-current wrote: Hi, I updated head recently and today I noticed a difference which looks wrong. At boodt the new head shows signifcantly less avail memory than before, around 3 GiB

Re: recent head having significantly less "avail memory"

2021-09-13 Thread Guido Falsi via freebsd-current
On 13/09/21 20:17, Ryan Stone wrote: On Mon, Sep 13, 2021 at 2:13 PM Guido Falsi via freebsd-current wrote: I'm not sure how to get the verbose data for the old boot, since I've been unable to revert the machine to the old state. I'll try anyway though. Do you have physical access

Re: recent head having significantly less "avail memory"

2021-09-13 Thread Guido Falsi via freebsd-current
On 13/09/21 19:08, Konstantin Belousov wrote: On Mon, Sep 13, 2021 at 02:59:25PM +0200, Guido Falsi via freebsd-current wrote: Hi, I updated head recently and today I noticed a difference which looks wrong. At boodt the new head shows signifcantly less avail memory than before, around 3 GiB

recent head having significantly less "avail memory"

2021-09-13 Thread Guido Falsi via freebsd-current
Hi, I updated head recently and today I noticed a difference which looks wrong. At boodt the new head shows signifcantly less avail memory than before, around 3 GiB less. I moved from commit 71fbc6faed6 [1] where I got: Aug 28 22:03:03 marvin kernel: real memory = 17179869184 (16384 MB)

Re: -CURRENT compilation time

2021-09-06 Thread Guido Falsi via freebsd-current
On 06/09/21 10:08, Jeremie Le Hen wrote: Hey, I want to build -CURRENT again from sources. It's been a long time since I hadn't done that. I'm shocked by the compilation time. I started the whole thing on Friday night and Monday morning it's still in stage 4.2 (building libraries). Through

Re: poudriere: net/openldap24-server: stage/runaway , building forever

2021-04-09 Thread Guido Falsi via freebsd-current
On 09/04/21 11:56, O. Hartmann wrote: On Fri, 9 Apr 2021 10:16:27 +0200 (CEST) Ronald Klop wrote: Hi, The official pkg builders are also stuck for 14-CURRENT. Although at a different port sysutils/msktutil. See main-amd64 at https://pkg-status.freebsd.org/builds?type=package It is stuck in

Re: Problem compiling libgit2

2021-04-06 Thread Guido Falsi via freebsd-current
On 06/04/21 18:59, Filippo Moretti via freebsd-current wrote: After moving ports to git I had the following error while updating libgit2:===>  Extracting for libgit2-1.1.0 => ===>  Extracting for libgit2-1.1.0 => SHA256 Checksum OK for libgit2-1.1.0.tar.gz. ===>  Patching for libgit2-1.1.0 sed:

Re: 13.0 RC4 might be delayed

2021-03-30 Thread Guido Falsi via freebsd-current
On 29/03/21 16:28, Mario Lobo wrote: [snip] Good point. Now the question is, what the default should be. Since the correct aio configuration is in the pkg-message and easy to setup I'd go for default to AIO turned on. -- Guido Falsi +1 The way it is, is running smooth here on STABLE/13

Re: 13.0 RC4 might be delayed

2021-03-29 Thread Guido Falsi via freebsd-current
On 29/03/21 06:26, Greg Rivers wrote: On Sunday, 28 March 2021 20:37:13 CDT David G Lawrence via freebsd-current wrote: On 27/03/21 06:04, David G Lawrence via freebsd-current wrote: On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin wrote: On 26/03/2021 03:40, The Doctor via freebsd-current

Re: 13.0 RC4 might be delayed

2021-03-28 Thread Guido Falsi via freebsd-current
On 28/03/21 22:34, Guido Falsi via freebsd-current wrote: On 27/03/21 06:04, David G Lawrence via freebsd-current wrote: On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin wrote: On 26/03/2021 03:40, The Doctor via freebsd-current wrote: ??? if people are having issues with ports like

Re: 13.0 RC4 might be delayed

2021-03-28 Thread Guido Falsi via freebsd-current
On 27/03/21 06:04, David G Lawrence via freebsd-current wrote: On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin wrote: On 26/03/2021 03:40, The Doctor via freebsd-current wrote: ??? if people are having issues with ports like ??? If I'm not mistaken: * 13.0-RC3 seems to be troublesome, as a

Re: Is there any OS builtin git command like svnlite ?

2021-03-14 Thread Guido Falsi via freebsd-current
On 14/03/21 21:09, Kurt Jaeger wrote: Hi! I'm working on clean installed VM -current from NFS mounted src like : admin@tbedfc:~ % df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/vtbd0p2 11G

Re: On 14-CURRENT: no ports options anymore?

2021-03-13 Thread Guido Falsi via freebsd-current
On 13/03/21 20:17, Hartmann, O. wrote: Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set options via "make config" or via poudriere accordingly. I always get "===> Options unchanged" (when options has been already set and I'd expect a dialog menu). This

Re: xfig menu on xfce

2021-03-05 Thread Guido Falsi via freebsd-current
On 04/03/21 21:16, Guido Falsi via freebsd-current wrote: On 04/03/21 20:56, Antonio Olivares wrote: On Thu, Mar 4, 2021 at 1:55 PM Antonio Olivares wrote: On Thu, Mar 4, 2021 at 1:51 PM David Wolfskill wrote: On Thu, Mar 04, 2021 at 01:47:03PM -0600, Antonio Olivares wrote: xfig

Re: xfig menu on xfce

2021-03-04 Thread Guido Falsi via freebsd-current
On 04/03/21 20:56, Antonio Olivares wrote: On Thu, Mar 4, 2021 at 1:55 PM Antonio Olivares wrote: On Thu, Mar 4, 2021 at 1:51 PM David Wolfskill wrote: On Thu, Mar 04, 2021 at 01:47:03PM -0600, Antonio Olivares wrote: xfig installed from pkg on the menu click on xfce we get error message

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-02-03 Thread Guido Falsi via freebsd-current
On 03/02/21 17:02, John Baldwin wrote: On 2/2/21 10:16 PM, Hartmann, O. wrote: On Mon, 1 Feb 2021 03:24:45 + Rick Macklem wrote: Rick Macklem wrote: Guido Falsi wrote: [good stuff snipped] Performed a full bisect. Tracked it down to commit aa906e2a4957, adding KTLS support to embedded

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-02-03 Thread Guido Falsi via freebsd-current
On 03/02/21 07:16, Hartmann, O. wrote: On Mon, 1 Feb 2021 03:24:45 + Rick Macklem wrote: Rick Macklem wrote: Guido Falsi wrote: [good stuff snipped] Performed a full bisect. Tracked it down to commit aa906e2a4957, adding KTLS support to embedded OpenSSL. I filed a bug report about

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-02-01 Thread Guido Falsi via freebsd-current
On 01/02/21 04:24, Rick Macklem wrote: Rick Macklem wrote: Guido Falsi wrote: [good stuff snipped] Performed a full bisect. Tracked it down to commit aa906e2a4957, adding KTLS support to embedded OpenSSL. I filed a bug report about this:

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-31 Thread Guido Falsi via freebsd-current
On 31/01/21 10:35, Hartmann, O. wrote: On Sat, 30 Jan 2021 16:22:50 +0100 Guido Falsi via freebsd-current wrote: On 30/01/21 12:34, Guido Falsi via freebsd-current wrote: On 30/01/21 11:25, Tomoaki AOKI wrote: On Sat, 30 Jan 2021 07:39:23 +0100 "Hartmann, O." wrote: We recent

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-30 Thread Guido Falsi via freebsd-current
On 30/01/21 12:34, Guido Falsi via freebsd-current wrote: On 30/01/21 11:25, Tomoaki AOKI wrote: On Sat, 30 Jan 2021 07:39:23 +0100 "Hartmann, O." wrote: We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021  amd64. After make delet

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-30 Thread Guido Falsi via freebsd-current
On 30/01/21 11:25, Tomoaki AOKI wrote: On Sat, 30 Jan 2021 07:39:23 +0100 "Hartmann, O." wrote: We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021 amd64. After make delete-oldfiles/delete-old-libs, the command make update issued in

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-30 Thread Guido Falsi via freebsd-current
On 30/01/21 07:39, Hartmann, O. wrote: We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021 amd64. After make delete-oldfiles/delete-old-libs, the command make update issued in /usr/ports on those 14-CURRENT boxes remains stuck forever or it

Re: problem building virtualbox-ose-kmod

2021-01-26 Thread Guido Falsi via freebsd-current
On 26/01/21 13:29, Dima Panov wrote: Moin! Stefan, please add check for __FreeBSD_version and fill PR or commit it directly with ports-secteam approval. There's a bug report for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252675 And another one which is marked as a duplicate