On 2023-10-17 09:40:37, Kevin Bowling wrote:
The flash SLOG system took around 12 hours to complete freebsd-update
from 13.2 to 14.0-RC1. The system without the SLOG took nearly 24
hours. This was the result of ~50k patches, and ~10k files from
freebsd-update and a very pathological 'install
Kevin Bowling wrote on
Date: Tue, 17 Oct 2023 16:40:37 UTC :
> I have two systems with a zpool 2x2 mirror on 7.2k RPM disks. One
> system also has a flash SLOG.
>
> The flash SLOG system took around 12 hours to complete freebsd-update
> from 13.2 to 14.0-RC1. The system withou
Hi,
I have two systems with a zpool 2x2 mirror on 7.2k RPM disks. One
system also has a flash SLOG.
The flash SLOG system took around 12 hours to complete freebsd-update
from 13.2 to 14.0-RC1. The system without the SLOG took nearly 24
hours. This was the result of ~50k patches, and ~10k
Am 2023-10-12 07:08, schrieb Mark Millard:
I use the likes of:
BE Active Mountpoint Space Created
build_area_for-main-CA72 - - 1.99G 2023-09-20 10:19
main-CA72NR / 4.50G 2023-09-21 10:10
NAME
Evans
AuthorDate: 2023-10-12 02:51:07 +
Commit: Kyle Evans
CommitDate: 2023-10-12 02:54:03 +
freebsd-update: create deep BEs by default
The -r flag to bectl needs to go away, and we need to just do the right
thing. In the meantime, we can apply an -r in freebsd-update as a
minimal fix
> AuthorDate: 2023-10-12 02:51:07 +
> Commit: Kyle Evans
> CommitDate: 2023-10-12 02:54:03 +
>
> freebsd-update: create deep BEs by default
>
> The -r flag to bectl needs to go away, and we need to just do the right
> thing. In the meantime, we can apply an -r
On Mon, 2 May 2022 at 20:17, Graham Perrin wrote:
>
> <https://github.com/freebsd/freebsd-src/commit/6cd1bc53160973fc421c59f66aaa7e4b37a8cebe#diff-ed3905e89b1b292bd271b3defd3ae0442a250eeed5623f5dc31aeba248b353a8R3028>
> (line 3028)
>
> How will freebsd-update behave in th
On 03/05/2022 02:15, Graham Perrin wrote:
<https://github.com/freebsd/freebsd-src/commit/6cd1bc53160973fc421c59f66aaa7e4b37a8cebe#diff-ed3905e89b1b292bd271b3defd3ae0442a250eeed5623f5dc31aeba248b353a8R3028>
(line 3028)
How will freebsd-update behave in this case?
Cannot 'status' ssh
<https://github.com/freebsd/freebsd-src/commit/6cd1bc53160973fc421c59f66aaa7e4b37a8cebe#diff-ed3905e89b1b292bd271b3defd3ae0442a250eeed5623f5dc31aeba248b353a8R3028>
(line 3028)
How will freebsd-update behave in this case?
Cannot 'status' sshd. Set sshd_enable to YES in /etc/rc.conf
On 19/02/2021 21:59, Chris Rees wrote:
Hey,
On 16 February 2021 08:53:29 GMT, Graham Perrin wrote:
<https://cgit.freebsd.org/src/tree/usr.sbin/freebsd-update/freebsd-update.sh?id=48ffe56ac5b7adb5b851d32be12b2ec0f13705a4#n555>
echo "You must be root to run this."
B
Hey,
On 16 February 2021 08:53:29 GMT, Graham Perrin wrote:
><https://cgit.freebsd.org/src/tree/usr.sbin/freebsd-update/freebsd-update.sh?id=48ffe56ac5b7adb5b851d32be12b2ec0f13705a4#n555>
>
> echo "You must be root to run this."
>
>Below: is th
<https://cgit.freebsd.org/src/tree/usr.sbin/freebsd-update/freebsd-update.sh?id=48ffe56ac5b7adb5b851d32be12b2ec0f13705a4#n555>
echo "You must be root to run this."
Below: is this my PEBKAM, or (with a system that is preconfigured to
deny login as root) _should_
On Mon, 27 Jul 2020 15:49:46 -0700 bsd-li...@bsdforge.com said
On Mon, 27 Jul 2020 15:14:49 -0700 Michael Dexter edi...@callfortesting.org
said
> On 7/17/20 4:37 AM, Cristian Cardoso wrote:
> > I would like to know if by chance in freeBSD there is some kind of log
> > when the
On Mon, 27 Jul 2020 15:14:49 -0700 Michael Dexter edi...@callfortesting.org said
On 7/17/20 4:37 AM, Cristian Cardoso wrote:
> I would like to know if by chance in freeBSD there is some kind of log
> when the command freebsd-update fetch / install is executed?
> I looked in the docu
On 7/17/20 4:37 AM, Cristian Cardoso wrote:
I would like to know if by chance in freeBSD there is some kind of log
when the command freebsd-update fetch / install is executed?
I looked in the documentation and found nothing about it.
There does not appear to be a log but running
Hello
I would like to know if by chance in freeBSD there is some kind of log
when the command freebsd-update fetch / install is executed?
I looked in the documentation and found nothing about it.
Does anyone know if this exists?
___
freebsd-current
On 18-03-24 10:26 AM, Derek wrote:
On 18-03-23 06:44 AM, Kurt Jaeger wrote:
To be clear, *I've included a link to a patch to freebsd-update
in my initial post, and the help I'm looking for: is to get this
functionality added as a feature so others can benefit.* It
works for me already
On 18-03-23 06:44 AM, Kurt Jaeger wrote:
Hi!
To be clear, *I've included a link to a patch to freebsd-update
in my initial post, and the help I'm looking for: is to get this
functionality added as a feature so others can benefit.* It
works for me already, and I've already benefited.
(I'm
Hi!
> To be clear, *I've included a link to a patch to freebsd-update
> in my initial post, and the help I'm looking for: is to get this
> functionality added as a feature so others can benefit.* It
> works for me already, and I've already benefited.
>
> (I'm hap
On 18-03-21 05:24 PM, Rainer Duffner wrote:
Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists) <48225...@razorfever.net>:
Hi!
I was surprised when using freebsd-update, that there was no way to specify a
patch level.
AFAIK, the usual answer to these kinds of requests is: „Run yo
> Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists)
> <48225...@razorfever.net>:
>
> Hi!
>
> I was surprised when using freebsd-update, that there was no way to specify a
> patch level.
AFAIK, the usual answer to these kinds of requests is: „Run your
Hi!
I was surprised when using freebsd-update, that there was no way
to specify a patch level.
In my day to day, I need to ensure security patches are applied.
I also need to assess the impact of patches, and ensure
consistency (ie. versions) in my environments. This can take time
submitted as suspect:
https://gist.github.com/anonymous/e48209b03f1dd9625a992717e7b89c4f
The document is from an unknown author and describes "non-cryptanalytic
attacks against FreeBSD update components." The affected components are
the portsnap and freebsd-update tools, both directly and indir
Hello.
Please consider a new clean command in the freebsd-update script. The modified
manual and script are located at https://github.com/textbrowser/freebsd-update.
Included are two diffs. Sorry for the long e-mail.
--- /usr/src/usr.sbin/freebsd-update/freebsd-update.8 2015-08-12
10:21
FreeBSD releases and use freebsd-update
to install official updates.
We found that when the invocation of freebsd-update was scripted
and not run via a real tty, we can into this error:
freebsd-update fetch should not be run non-interactively.
There are various workarounds mentioned
Hi,
Ahmed Kamal, a devops expert, is helping me to script the steps to
upgrade a cluster of FreeBSD machines. For certain machines,
we want to track the official FreeBSD releases and use freebsd-update
to install official updates.
We found that when the invocation of freebsd-update was scripted
On 1/13/2015 5:11 PM, Craig Rodrigues wrote:
Hi,
Ahmed Kamal, a devops expert, is helping me to script the steps to
upgrade a cluster of FreeBSD machines. For certain machines,
we want to track the official FreeBSD releases and use freebsd-update
to install official updates.
We found
releases and use freebsd-update
to install official updates.
We found that when the invocation of freebsd-update was scripted
and not run via a real tty, we can into this error:
freebsd-update fetch should not be run non-interactively.
There are various workarounds mentioned on various
releases and use freebsd-update
to install official updates.
We found that when the invocation of freebsd-update was scripted
and not run via a real tty, we can into this error:
freebsd-update fetch should not be run non-interactively.
There are various workarounds mentioned on various web
of FreeBSD machines. For certain machines,
we want to track the official FreeBSD releases and use freebsd-update
to install official updates.
We found that when the invocation of freebsd-update was scripted
and not run via a real tty, we can into this error:
freebsd-update fetch should not be run non
On 2015-01-13 18:11, Craig Rodrigues wrote:
Hi,
Ahmed Kamal, a devops expert, is helping me to script the steps to
upgrade a cluster of FreeBSD machines. For certain machines,
we want to track the official FreeBSD releases and use freebsd-update
to install official updates.
We found
d...@gmx.com wrote on 10/24/2014 04:09:
# freebsd-update install
Installing updates...install: ///usr/src/contrib/tzdata/zone1970.tab: No such
file or directory
done.
#
OK, maybe the install didn't fail, and the quirk is ignorable.
However, in any case, freebsd-update shouldn't try
On 2014-10-24 12:23, d...@gmx.com wrote:
d...@gmx.com wrote on 10/24/2014 04:09:
# freebsd-update install
Installing updates...install: ///usr/src/contrib/tzdata/zone1970.tab:
No such file or directory
done.
#
OK, maybe the install didn't fail, and the quirk is ignorable.
However
with freebsd-update where it gets confused the odd
time a new file has to be added in a security update.
It is a problem with the update package, actually. To update /usr/src, one
should use Subversion. Not? If it is the job of freebsd-update to update /usr/src (when
it exists), then freebsd
not
exist.
It is a minor problem with freebsd-update where it gets confused
the odd time a new file has to be added in a security update.
It is a problem with the update package, actually. To
update /usr/src, one should use Subversion. Not? If it is the job of
freebsd-update to update /usr/src
Do what (is it safe to retry the install?)?
log:
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching public key from update5.freebsd.org... done.
Fetching metadata signature for 10.0-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done
Hi.
i`m trying to update my FreeBSD 10 Release to Stable, but i`m not getting
to fetch on portsnap and freebsd-update
look:
# portsnap --debug fetch
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org...
snapshot.ssl
Am 2014-01-29 22:51, schrieb Colin Percival:
On 01/29/14 12:51, Lars Engels wrote:
On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast internet connection
that it has full end-to-end
pipelining. I'm not sure what the current state of squid is, but for
years it translated client side HTTP 1.1 pipelining into individual
HTTP 1.0 requests on the server side.
I don't use freebsd-update myself, but from a quick look at the manpage
I think it could
On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast internet connection (normally download rates ca. 3 MBytes / s)
downloading all the tiny
On 01/29/14 12:51, Lars Engels wrote:
On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast internet connection (normally download rates ca. 3 MBytes /
s
On 29 January 2014 13:51, Colin Percival cperc...@freebsd.org wrote:
On 01/29/14 12:51, Lars Engels wrote:
On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very
On 01/29/14 14:26, Adrian Chadd wrote:
On 29 January 2014 13:51, Colin Percival cperc...@freebsd.org wrote:
FWIW, the performance problems with proxies are limited to HTTP proxies
which don't speak HTTP/1.1.
Did you / others ever actually benchmark this?
The fact that performance sucks when
Am 25.01.2014 um 16:11 schrieb Mark Felder f...@freebsd.org:
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast internet connection (normally download rates ca. 3 MBytes / s)
downloading all the tiny binary
On Jan 29, 2014, at 12:51 PM, Lars Engels lars.eng...@0x20.net wrote:
On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast internet connection
...@gmail.com
wrote:
On Tue, Jan 21, 2014 at 7:49 AM, Ivan Voras ivo...@freebsd.org
wrote:
Hi,
Is there any way I can avoid manually resolving hundreds of merge
conflicts of the following type while using freebsd-update ?
1 current version
2 # $FreeBSD: release/9.0.0/etc
On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast internet connection (normally download rates ca. 3 MBytes / s)
downloading all the tiny binary diff files took more than 8 hours.
Maybe freebsd-update's
I agree with the rest of this thread. This is just awful. I'm basically
forced to do source based updates when jumping major versions because
freebsd-update is a nightmare to use.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
ivo...@freebsd.org
wrote:
Hi,
Is there any way I can avoid manually resolving hundreds of merge
conflicts of the following type while using freebsd-update ?
1 current version
2 # $FreeBSD: release/9.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z
peter $
3 ===
4 # $FreeBSD
On 2014-01-24 20:31, Mark Felder wrote:
I agree with the rest of this thread. This is just awful. I'm basically
forced to do source based updates when jumping major versions because
freebsd-update is a nightmare to use.
Not tested, but maybe this works.
a) use etcmerge before freebsd-upgrade
On 1/24/2014 11:31 AM, Mark Felder wrote:
I agree with the rest of this thread. This is just awful. I'm basically
forced to do source based updates when jumping major versions because
freebsd-update is a nightmare to use.
I've yet to go through a freebsd-update process that didn't require
Hi,
Is there any way I can avoid manually resolving hundreds of merge
conflicts of the following type while using freebsd-update ?
1 current version
2 # $FreeBSD: release/9.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z
peter $
3 ===
4 # $FreeBSD: release/10.0.0/etc/csh.cshrc
On Tue, Jan 21, 2014 at 7:49 AM, Ivan Voras ivo...@freebsd.org wrote:
Hi,
Is there any way I can avoid manually resolving hundreds of merge
conflicts of the following type while using freebsd-update ?
1 current version
2 # $FreeBSD: release/9.0.0/etc/csh.cshrc 50472 1999-08-27 23:37
On 21 Jan 2014, at 07:13, Antonio Olivares olivares14...@gmail.com wrote:
On Tue, Jan 21, 2014 at 7:49 AM, Ivan Voras ivo...@freebsd.org wrote:
Hi,
Is there any way I can avoid manually resolving hundreds of merge
conflicts of the following type while using freebsd-update ?
1 current
conflicts of the following type while using freebsd-update ?
1 current version
2 # $FreeBSD: release/9.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z
peter $
3 ===
4 # $FreeBSD: release/10.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z
peter $
5 10.0-RELEASE
,
Is there any way I can avoid manually resolving hundreds of merge
conflicts of the following type while using freebsd-update ?
1 current version
2 # $FreeBSD: release/9.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z
peter $
3 ===
4 # $FreeBSD: release
Hi,
I tried to upgrade a server at work from 8.2-RELEASE-i386 to 9.0-RC1-i386
using freebsd-update.When running 'freebsd-update install' to install the new
kernel, but that failed because there was insufficient disk space. This resulted
in freebsd-update thinking everything is ok but left
On 10/25/11 00:52, René Ladan wrote:
I tried to upgrade a server at work from 8.2-RELEASE-i386 to 9.0-RC1-i386
using freebsd-update.When running 'freebsd-update install' to install the new
kernel, but that failed because there was insufficient disk space. This
resulted
in freebsd-update
58 matches
Mail list logo
