On Jan 17, 2025, at 1:30 pm, Dennis Clarke wrote:
>I have plenty of logs. Piles of them. Perhaps the problem is that I
> am building on a 15-CURRENT machine which has poudriere jails like so :
>
> titan# poudriere jails -l
> JAILNAME VERSION ARCH METHOD TIMESTA
On Oct 31, 2024, at 3:50 pm, Alexander Leidinger
wrote:
> Am 2024-10-31 20:43, schrieb Mark Millard:
>> lexander Leidinger wrote on
>> Date: Wed, 30 Oct 2024 21:11:52 UTC :
>>> I've updated an oracle ampere instance running -current from
>>> 2024-09-12-140543 to 2024-10-30-121420 and now I get:
On Apr 22, 2024, at 3:26 AM, Alexander Leidinger
wrote:
> Hi,
>
> I see a higher failure rate of socket/network related stuff since a while.
> Those failures are transient. Directly executing the same thing again may or
> may not result in success/failure. I'm not able to reproduce this at w
On Feb 27, 2023, at 2:57 PM, Dimitry Andric wrote:
> On 27 Feb 2023, at 19:19, FreeBSD User wrote:
>>
>> Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23
>> main-n261147-b8bb73ab724b: Sun Feb 26
>> 17:39:38 CET 2023 amd64), and nanoBSD (recent 13-STABLE, git stable/13).
>>
>> Building
On Nov 6, 2022, at 9:20 AM,
wrote:
> I try to get FreeBSD14 current running with both
> - GNOME
> - SAMBA
> That seems to be impossible ☹ GNOME and SAMBA416 seems to be conflicting !
> I need SAMBA416 since SAMBA413 is simply not working :(
>
> Installing SAMBA does remove GNOME components
On Sep 20, 2022, at 6:19 PM, Alan Somers wrote:
> On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira wrote:
>>
>> Hello to all,
>>
>> I will use becl for the first time for current upgrades.
>> Just to check that I'm thinking correctly:
>>
>> Create a test environment for upgrade:
>>> bectl create
On Apr 25, 2022, at 3:26 PM, Patrick M. Hausen wrote:
> Hi,
>
>> Am 25.04.2022 um 21:18 schrieb Brooks Davis :
>> Cross install is not supported. As you have seen, certain tools are
>> bootstrapped on the build host and used during the install process. You
>> might be able to get away with nuk
On Apr 19, 2022, at 4:49 AM, Michael Schuster wrote:
> Hi,
>
> I'm highjacking and re-purposing the previous thread, I hope that's OK
> (I did change the subject ;-)) - I'm keeping some of the previous
> contents for reference.
>
> I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and
On Feb 24, 2021, at 11:18 AM, Jung-uk Kim wrote:
> On 21. 2. 24., Paul Mather wrote:
>> I have two systems on which I run -CURRENT. I updated them yesterday to the
>> following: FreeBSD 14.0-CURRENT #1 main-n245033-6ab923cbca87: Tue Feb 23
>> 21:29:31 EST 2021. Both
I have two systems on which I run -CURRENT. I updated them yesterday to the
following: FreeBSD 14.0-CURRENT #1 main-n245033-6ab923cbca87: Tue Feb 23
21:29:31 EST 2021. Both use the stock GENERIC-NODEBUG kernel.
Since the update, the systems do not boot up correctly. I get this late in the
bo
On Dec 22, 2020, at 1:39 PM, bob prohaska wrote:
> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>>
>> The FreeBSD project will be moving it's source repo from subversion to git
>> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
>> repo will move at the
On Jun 20, 2016, at 6:33 PM, Keith White wrote:
> On Mon, 20 Jun 2016, Luiz Otavio O Souza wrote:
>
>> On Sun, Jun 19, 2016 at 1:11 AM, Maxim Sobolev wrote:
>>> Jim, some update from here. Running r283287 of the driver, I still see the
>>> same "watchdog timeout" messages, but they do not lead t
On Jun 18, 2016, at 2:50 AM, Maxim Sobolev wrote:
> Updated my BBB to the latest -current, immediately got this while trying to
> make world over ssh console:
>
> 06:02:17 CPSW watchdog cpswss0: watchdog timeout
> cpswss0: Unable to cleanly shutdown transmitter
>
> Interface seems to be locked
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Apr 20, 2016, at 10:54 AM, Slawa Olhovchenkov wrote:
>> A packaged base is just another way of describing the state of the
>> system. People on mailing lists will still be able to help people
>> fix their problems, but they'll just use different information to
>> pinpoint the precise componen
> Message: 20
> Date: Wed, 20 Apr 2016 12:48:06 +0300
> From: Slawa Olhovchenkov
> To: Dan Partelly
> Cc: David Chisnall , Julian Elischer
> , Nathan Whitehorn ,
> freebsd-current@freebsd.org
> Subject: Re: [CFT] packaging the base system with pkg(8)
> Message-ID: <20160420094806.gj6
On Oct 4, 2011, at 12:09 PM, Olivier Smedts wrote:
> 2011/10/3 Paul Mather :
>> I know ZFS does not have a fsck utility ("because it doesn't need one":),
>> but does anyone know of any way of fixing this corruption short of
>> destroying the pool, creating
On Oct 5, 2011, at 9:03 AM, krad wrote:
> Have you dont the simple thing and checked to see if you have any weird
> whitespace in the dir names. Try using bash tab completion for the dir name.
> Also drop all non bash completion rules as these might be messing things up.
>
> I have seen odd cha
On Oct 3, 2011, at 6:19 PM, Artem Belevich wrote:
> On Mon, Oct 3, 2011 at 11:21 AM, Paul Mather wrote:
>> =
>>
>> The pool itself reports no errors. I performed a scrub on the pool yet this
>> bizarre filesystem corruption persists:
>>
>> =
I wasn't sure whether to post this here or on sta...@freebsd.org. The system
now runs RELENG_9, but the ZFS pool exhibiting problems was created, IIRC,
under 9-CURRENT. I believe RELENG_9 is sufficiently close to HEAD at this
stage that this list is probably the correct place for this message.
20 matches
Mail list logo
