> On 30. Mar 2024, at 07:30, Chris wrote:
>
> On 2024-03-29 23:06, Michael Schuster wrote:
>> Two ideas:
>> - does CTL-ALT-Fn work?
> Thanks. But no, I tried that.
>
>> - perhaps the number of predefined ttys was overwritten/set to 0 somewhere?
> I'm only aware of /etc/ttys, and they're all
> On 23. Dec 2023, at 16:10, Enji Cooper wrote:
>
>
>> On Dec 22, 2023, at 23:18, Xin Li wrote:
>>
>> Hi,
>>
>> Inspired by D42961, I propose that we move forward with disabling the
>> compression by default in newsyslog, as implemented in
>> https://reviews.freebsd.org/D43169
>>
>>
> On 3. Oct 2023, at 18:27, Matthias Apitz wrote:
>
> El día martes, octubre 03, 2023 a las 06:14:23p. m. +0200, Olivier Certner
> escribió:
>
>> Hi Matthias,
>>
>> Some ZFS dataset with zstd compression on jet, and no compression on
>> c720-1400094?
>>
>
> Yes, on jet it is ZFS:
>
>
> On 19. Sep 2023, at 12:30, Ronald Klop wrote:
>
> Hi,
>
> In current the way ps -p works has been changed [1].
> I could use "ps axd -p " to see the process tree of some ongoing task.
> In current this has changed to always need an extra option "ps axd -p
> -D down". Can this become the
using has to understand the ZFS dataset that it's
> booting off of. FreeBSD
> 13's userboot.so doesn't support all the bells and whistles that the
> ZFS folks have added
> to 14.
>
> So, either you have to turn off those features (which I got no clue
> how to do in the
> normal installer), or you have to update userboot.so to the FreeBSD 14
> version (which
> I think had a good chance of actually running on FreeBSD 13 since it
> has no 'system'
> references, which are confined to bhyveload).
>
> Warner
>
>
> > >
> > > # find /boot/efi/EFI/ -print
> > > /boot/efi/EFI/
> > > /boot/efi/EFI/FREEBSD
> > > /boot/efi/EFI/FREEBSD/loader.efi
> > > /boot/efi/EFI/BOOT
> > > /boot/efi/EFI/BOOT/bootaa64.efi
> > >
> > > There may well be only:
> > >
> > > EFI/BOOT/bootaa64.efi
> > >
> > > for all I know.
> > >
> > > From an amd64 context:
> > >
> > > # find /boot/efi/EFI/ -print
> > > /boot/efi/EFI/
> > > /boot/efi/EFI/FREEBSD
> > > /boot/efi/EFI/FREEBSD/loader.efi
> > > /boot/efi/EFI/BOOT
> > > /boot/efi/EFI/BOOT/bootx64.efi
> > >
> > > There may well be only:
> > >
> > > EFI/BOOT/bootx64.efi
> > >
> > > for all I know.
> > >
> > > (I set things up to have the EFI capitalization
> > > so that referencing efi/ vs. EFI/ in my context
> > > is unique for the mount point. vs. the msdosfs
> > > directory.)
> > >
> > > ===
> > > Mark Millard
> > > marklmi at yahoo.com
> > >
> > >
> >
> >
> >
--
Michael Gmelin
> On 4. Sep 2023, at 19:34, Matthias Apitz wrote:
>
> El día lunes, septiembre 04, 2023 a las 07:29:41p. m. +0200, Michael Gmelin
> escribió:
>
>>
>>
>>>> On 4. Sep 2023, at 19:23, Matthias Apitz wrote:
>>>
>>>
, could you please Cc me on it?
Do you know which version of FreeBSD was the last that worked for you?
Cheers
>
>
>> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael Gmelin
>> escribió:
>>
>>
>>
>> On Mon, 4 Sep 2023 18:43:11 +020
board/mouse freezes on some hardware, please set
loader tunable hw.atkbd.hz=1 as workaround and report the issue.
So you could try to set hw.atkbd.hz=1 (or hw.atkbd.hz=10) in
/boot/loader.conf, then reboot and see if it helps.
Best
Michael
--
Michael Gmelin
d.org/ports.git` work for you?
(currently it's not working from where I am). Maybe related.
Best
Michael
--
Michael Gmelin
On 6. Aug 2023, at 18:12, Warner Losh wrote:On Sun, Aug 6, 2023 at 10:05 AM Matthias Apitz wrote:El día domingo, agosto 06, 2023 a las 09:58:32a. m. -0600, Warner Losh escribió:
> On Sun, Aug 6, 2023 at 7:58 AM Matthias Apitz wrote:
>
> >
> > I did, based
On Thu, 8 Jun 2023 11:32:19 -0600
Warner Losh wrote:
> On Thu, Jun 8, 2023, 11:18 AM Michael Gmelin
> wrote:
>
> > >
> > > Tried today's snaphot, same problem.
> > >
> > > # reboot
> > > Waiting (max 60 seconds) for system process
On Thu, 8 Jun 2023 19:06:23 +0200
Michael Gmelin wrote:
> On Thu, 8 Jun 2023 16:20:12 +
> Glen Barber wrote:
>
> > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote:
> > > Hi,
> > >
> > > I didn't dig into this yet.
> > &
On Thu, 8 Jun 2023 16:20:12 +
Glen Barber wrote:
> On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote:
> > Hi,
> >
> > I didn't dig into this yet.
> >
> > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I
> > get th
--
Michael Gmelin
On Thu, 23 Jun 2022 11:15:55 -0600
Warner Losh wrote:
> On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin
> wrote:
>
> >
> >
> > On Fri, 21 May 2021 08:36:49 -0600
> > Warner Losh wrote:
> >
> > > On Fri, May 21, 2021 at 7:38 AM Ceri Davies
&
> On 31. Jan 2023, at 22:44, Kurt Jaeger wrote:
>
> Hi!
>
This can be as easy as moving everything into Phabricator.
>>> There's the issue that Phabricator itself is no longer supported
>>> upstream:
> [...]
>>> https://we.phorge.it/
>
>> Should be no harder than regular update. They
On Sun, 28 Aug 2022 03:21:24 -0700
Cy Schubert wrote:
> In message <16b4-76a1-4e46-b7c3-60492d379...@freebsd.org>,
> Michael Gmelin w
> rites:
> >
> >
> >
> > > On 28. Aug 2022, at 10:42, free...@oldach.net wrote:
> > >=20
> >
> On 28. Aug 2022, at 10:42, free...@oldach.net wrote:
>
> Cy Schubert wrote on Sat, 27 Aug 2022 17:26:38 +0200 (CEST):
>> As stated before in this thread, replacing /var/run with tmpfs is not a
>> supported configuration.
>
> Not supported? What is the purpose of /etc/rc.d/var then? That
> On 27. Aug 2022, at 15:18, free...@oldach.net wrote:
>
> Michael Gmelin wrote on Sat, 27 Aug 2022 15:02:04 +0200 (CEST):
>> (you're removing /var/run, which shouldn't be removed
>
> Not quite. It's actually not uncommon to boot with an empty /var. Please see
> /
> On 27. Aug 2022, at 12:54, FreeBSD User wrote:
>
> Am Sat, 27 Aug 2022 11:21:40 +0200
> Michael Gmelin schrieb:
>
>>>> On 27. Aug 2022, at 08:31, FreeBSD User wrote:
>>>
>>> Hello,
>>>
>>> I'm referencing to Bug 259699 [
> On 27. Aug 2022, at 08:31, FreeBSD User wrote:
>
> Hello,
>
> I'm referencing to Bug 259699 [2] and Bug 259585 [1].
>
> Port security/clamav is without doubt for many of FreeBSD users an important
> piece of security
> software so I assume a widespread usage.
>
> It is also a not
> On 26. Aug 2022, at 18:55, Nuno Teixeira wrote:
>
>
> Hello to all,
>
> Today I updated and uname -a shows main-n257625-587649902329-dirty.
> Why is showing -dirty?
>
This means that the git workdir it was built on was dirty, see
> On 15. Aug 2022, at 18:22, Toomas Soome wrote:
>
>
>
>> On 15. Aug 2022, at 18:01, FreeBSD User wrote:
>>
>> Hello,
>>
>> I'm running a FreeBSD 13.1-RELENG-p1 zroot-based guest in a VirtualBox
>> 4.1.24/26 (do not know
>> exactly). The host is a special system based on Linux und
m.
You can point it to checking another file by setting ABI_FILE[0] in the
environment or ignore the check by setting IGNORE_OSVERSION (like
advised). The "running kernel:" label seems a bit misleading.
Cheers
Michael
--
Michael Gmelin
> On 9. Jul 2022, at 03:22, Klaus Küchemann wrote:
>
>
>> Am 07.07.2022 um 19:32 schrieb Hans Petter Selasky :
>>
>> Hi,
>>
>> The only argument I've heard from some non-sighted friends about not using
>> FreeBSD natively is that ooh, MacOSX is so cool. It starts speaking from the
>>
> On 8. Jul 2022, at 14:48, Hans Petter Selasky wrote:
>
> On 7/8/22 14:34, David Chisnall wrote:
> Snipsnap
> Hi,
>
> I've updated my patch a little bit, so please re-fetch it.
>
> I tried:
>
> action "echo -- $text | rtprio 8
> /usr/local/bin/flite_cmu_us_slt"
>
> And
.usbhid.enable="1"
>
> with the order below , after 5 reboots and lots of kvm switches , it
> always ended up on the right iichid device. Seems to be working now
>
> but like I said, its random, let see after some more reboots if this
> rule is still valid
I don't know if it makes any difference in your case, but I had best
results loading these drivers through rc.conf, e.g.:
sysrc kld_list+="hidraw hkbd"
Cheers
Michael
--
Michael Gmelin
usbhid.enable="1" in /boot/loader.conf, or by using
the sysctl? If you don't do it yet, I'd recommend the former.
Cheers
Michael
>
> Thanks
>
> --tzk
>
--
Michael Gmelin
f course ;)
>
> Walter
>
>> On Sun, Jun 26, 2022 at 2:56 AM Michael Gmelin wrote:
>>
>>
>>>> On 26. Jun 2022, at 09:37, grarpamp wrote:
>>>>
>>>
>>>>
>>>> https://github.com/freebsd/freebsd-doc/blob/main/doc
> On 26. Jun 2022, at 09:37, grarpamp wrote:
>
>
>>
>> https://github.com/freebsd/freebsd-doc/blob/main/documentation/content/en/books/handbook/eresources/_index.adoc
>>
>> FreeBSD Handbook: Appendix C: updates and corrections
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264754
>>
ASE production
system (non-INVARIANT kernel) and it seems like SIGINFO still outputs
kernel stack information.
Cheers
Michael
--
Michael Gmelin
> On 18. Jun 2022, at 15:10, Larry Rosenman wrote:
>
>
> On 06/18/2022 3:54 am, Michael Gmelin wrote:
>
> [SNIP]
>
>
> Subvendor is Fujitsu Siemens - so I guess this is integrated into a system by
> them.
>
> Seems like flashing the 2108 to a
> On 18. Jun 2022, at 01:31, Larry Rosenman wrote:
> On 06/17/2022 6:20 pm, Michael Gmelin wrote:
>>>> On 18. Jun 2022, at 00:57, Larry Rosenman wrote:
>>> On 06/17/2022 5:48 pm, Michael Gmelin wrote:
>>>>> On 18. Jun 2022, at 00:31, Alexander Motin
> On 18. Jun 2022, at 00:57, Larry Rosenman wrote:
> On 06/17/2022 5:48 pm, Michael Gmelin wrote:
>>> On 18. Jun 2022, at 00:31, Alexander Motin wrote:
>>>
>>>> On 17.06.2022 18:24, Alexander Motin wrote:
>>>>> On 17.06.2022 18:16
What is the error message?
Did you try “git push -f”
> On 9. Jun 2022, at 21:33, Rick Macklem wrote:
>
> I just tried to MFC a commit done to fix my commit by imp@
> and it won't let be push the cherry-pick.
>
> What's the trick to doing this?
> Or do I need to get Warner to do it?
> If so,
the same name (on FreeBSD, at
> least), it is safe to assume that the file will not be kept when the
> package is installed.
The opposite case seems more interesting/problematic.
-m
--
Michael Gmelin
> On 17. Apr 2022, at 06:20, Peter Jeremy wrote:
>
> On 2022-Apr-17 01:13:02 +0300, Sami Halabi wrote:
>> I understand its hard to undelete since no one designed UFS/ZFS to do so..
>> that why I asked in later replies to see if someone would step in and
>> implement such a "feature" and I
ually.
Best
Michael
>
>> On Sat, Apr 16, 2022 at 2:59 PM Michael Gmelin wrote:
>> Depends on the kind of file.
>>
>> You can always:
>> 1. reboot the system into single user mode, mount the fs readonly (important
>> to not overwrite data you want to recover
Depends on the kind of file.
You can always:
1. reboot the system into single user mode, mount the fs readonly (important to
not overwrite data you want to recover)
2. dd the partition and into a file
3. find the content of the deleted file in the dump
I was able to recover a complete codebase
> On 20. Mar 2022, at 15:45, David Chisnall wrote:
>
> On 19 Mar 2022, at 21:24, Chris wrote:
>>
>>> On 2022-03-18 09:08, Ed Maste wrote:
>>> ISA sound cards have been obsolete for more than a decade, and it is
>>> (past) time to retire their drivers. This includes the following
>>>
017 and 2014 and I
> guess this is solved right now.
>
> The difference between our manually jail.conf driven setup and the
> XigmaNAS/bastille based one is, bastille uses jib/netgraph based
> seutups of the vnet and the ip4/ip6 is setup from rc.conf, while we
> use epair in the other world and the ip is setup from withing the
> jail definition in jail.conf.
>
> I'm out of ideas here and after two days of trial and error and
> trying to understand what's going on lost ... Any hints or tipps?
>
> Thanks in advance,
>
> O. Hartmann
Hi Oliver,
I don't see `children.max` set in any of the configuration you shared
above.
Cheers
Michael
--
Michael Gmelin
This should have been resolved today in
https://cgit.freebsd.org/src/commit/?id=5e6a2d6eb220d780c9128c81b58f133114061415
-m
> On 30. Dec 2021, at 20:17, tue...@freebsd.org wrote:
> Dear all,
>
> on a system updated yesterday I get
>
> tuexen@head:~/freebsd-src % git branch
> * main
>
> On 10. Dec 2021, at 16:57, Chris wrote:
>
> On 2021-12-09 05:36, Sergey V. Dyatko wrote:
>> Hi,
>> Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh
>> 14-current from git,it looked like this:
>> 1) git pull https://git.freebsd.org/src.git /usr/src
>> 2) cd /usr/src ;
rence).
>
> Thanks for the fix :-)
Before reading your message, I (ironically) wanted to tell you about
your email's date header containing the wrong timezone ^_^
-m
--
Michael Gmelin
there any (security) reasons why this might be a bad idea?
Best,
Michael
--
Michael Gmelin
kg binary isn't installed in $LOCALBASE/sbin/pkg,
(whatever LOCALBASE is at that point)? This would make pkg --version
shows its bootstrap message:
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]:
which could explain the behavior.
Just speculating...
-m
--
Michael Gmelin
+ $17 + $1
Which is:
1 + 0 + 1
Which equals
10001
-m
>
> imb
--
Michael Gmelin
> On 16. Jul 2021, at 19:38, Warner Losh wrote:
>
> On Fri, Jul 16, 2021 at 6:14 AM Thomas Laus wrote:
>
>> Group:
>>
>> This is an issue for more than just CURRENT. The 'usr/src/UPDATING'
>> file has the instructions for updating the ZFS bootblocks but not the
>> EFI partition. I
a lot
of sense to me.
-m
> Is there a
> good reason for this convention, or is it just inertia?
> -Alan
--
Michael Gmelin
On Wed, 30 Jun 2021 20:05:43 +0200
"O. Hartmann" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Mon, 28 Jun 2021 23:34:44 +0200
> Michael Gmelin schrieb:
>
> > > On 28. Jun 2021, at 22:41, O. Hartmann
> > > wrot
> On 28. Jun 2021, at 22:41, O. Hartmann wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> Hello,
>
> we ran into serious trouble here with an www/nextcloud installation on a
> recent 14-CURRENT
> (FreeBSD 14.0-CURRENT #23 main-n247612-e6dd0e2e8d4: Mon Jun 28 18:08:20
> On 13. Jun 2021, at 20:50, Ronald Klop wrote:
>
> What do you have configured as prompt? Or shell startup script?
> Does it contain a call to git?
>
I agree that this smells like a prompt that calls "git status" or something
similar (when on the FreeBSD source tree on an rpi, 15
> On 11. Jun 2021, at 00:42, Cameron Katri via freebsd-current
> wrote:
>
> On 6/10/21 6:26 PM, Kevin Oberman wrote:
>> I have never seen it return anything from /usr/src.
>
> It seems to return stuff from /usr/src for me
> > whereis cc
> cc: /usr/bin/cc /usr/share/man/man1/cc.1.gz
>
> On 11. Jun 2021, at 00:28, Kevin Oberman wrote:
>
> On Wed, Jun 9, 2021 at 2:02 AM Michael Gmelin wrote:
>
>>
>>
>>>> On 9. Jun 2021, at 01:15, Ian Lepore wrote:
>>>
>>> On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wro
; if it can't find the sources
directly, so e.g., in case of `whereis -s ls', it will get through the
results of `locate '*'/ls` and see if they match "^/usr/src" (or
whatever you gave as source dir using -S).
Therefore if
locate '*'/ntp.conf | grep "^/usr/src"
gives you a result, then `whereis -s ntp.conf' will too.
See also
https://cgit.freebsd.org/src/tree/usr.bin/whereis/whereis.c#n607
Michael
(re-sent, as the previous mail bounced from the list)
--
Michael Gmelin
> On 9. Jun 2021, at 04:17, grarpamp wrote:
>
> On 4/17/20, Ryan Moeller wrote:
>>
On Apr 17, 2020, at 4:56 PM, Pete Wright wrote:
>>>
>>> On 4/17/20 11:35 AM, Ryan Moeller wrote:
OpenZFS brings many exciting features to FreeBSD, including:
* native encryption
>>> Is there
> On 9. Jun 2021, at 01:15, Ian Lepore wrote:
>
> On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote:
>>> On Tue, 8 Jun 2021 09:41:34 +
>>> Mark Linimon wrote:
>>>
On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> Sometimes it's a real interesting exercise
On Thu, 3 Jun 2021 15:09:06 +0200
Michael Gmelin wrote:
> On Tue, 1 Jun 2021 13:47:47 +0200
> Michael Gmelin wrote:
>
> > Hi,
> >
> > Since upgrading servers from 12.2 to 13.0, I get
> >
> > Fssh_packet_write_wait: Connection to 1.2.3.4 por
being "September 2020".
> >
> > So: 2020-Oct through 2021-Apr are completely missing.
> >
> > Then, going for more detail for 2020-Sep and 2021-May . . .
> >
> > https://lists.freebsd.org/archives/freebsd-hackers/2021-May/date.html
> > shows "Starting Tue May 18 2021 - 21:07:44 UTC".
> >
> > https://lists.freebsd.org/pipermail/freebsd-hackers/2020-September/date.html
> > shows "Ending: Tue Sep 15 14:12:20 UTC 2020".
> >
> > So there are about 2 more half-months missing.
> >
> > Some other lists have other date ranges, some similar,
> > some not.
>
> This missing month are being populated right now
Will historic links still work though (so that old references work and
current google results are ok)?
Just stumbled over this one:
https://lists.freebsd.org/archives/freebsd-jail/2017-March/003360.html
Cheers
Michael
>
> Best regards,
> Bapt
--
Michael Gmelin
> On 6. Jun 2021, at 01:44, Warner Losh wrote:
>
>
>
>
>> On Sat, Jun 5, 2021, 5:29 PM Steve Kargl
>> wrote:
>> On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
>> >
>> > p.s. If you go to https://lists.fr
> On 6. Jun 2021, at 01:00, Michael Gmelin wrote:
>
>
>
>
>>> On 6. Jun 2021, at 00:53, Steve Kargl
>>> wrote:
>>>
>> It seems someone has tried to migrate the mailing list archives
>> from mailman to some new fangle code. This ha
> On 6. Jun 2021, at 00:53, Steve Kargl
> wrote:
>
> It seems someone has tried to migrate the mailing list archives
> from mailman to some new fangle code. This has broken the archives
> for at least freebsd-numerics@, freebsd-office@, freebsd-net@
>
> As a comparison, simply go to
>
>
On Fri, 28 May 2021 20:50:52 +0200
Michael Gmelin wrote:
> On Fri, 28 May 2021 20:37:14 +0200
> Mathieu Arnold wrote:
>
> > On Wed, May 19, 2021 at 07:32:43PM +0200, Michael Gmelin wrote:
> > >
> > >
> > > On Wed, 19 May 20
On Tue, 1 Jun 2021 13:47:47 +0200
Michael Gmelin wrote:
> Hi,
>
> Since upgrading servers from 12.2 to 13.0, I get
>
> Fssh_packet_write_wait: Connection to 1.2.3.4 port 22: Broken pipe
>
> consistently, usually after about 11 idle minutes, that's with and
> wi
, same everything). On 12.2
before the update: Connection stays open for hours. After the update
(same server): connections breaks consistently after < 15 minutes (this
is with unaltered configurations, no *AliveInterval configured on
either side of the connection).
Thanks
Michael
--
Michael Gmelin
On Fri, 28 May 2021 20:37:14 +0200
Mathieu Arnold wrote:
> On Wed, May 19, 2021 at 07:32:43PM +0200, Michael Gmelin wrote:
> >
> >
> > On Wed, 19 May 2021 19:09:06 +0200
> > Kurt Jaeger wrote:
> >
> > > Hi!
> > >
> > >
What about using "."? Or "/" (which would match the muscle memory of "search"
in less/more/vi/some browsers)?
-m
> On 7. May 2021, at 23:05, Maxim Sobolev wrote:
>
> Replace '*' with ^T perhaps and catch SIGINFO? 樂
>
> -Max
>
>> On Fri., May 7, 2021, 10:11 a.m. Shawn Webb,
>> wrote:
>>
On Wed, 28 Apr 2021 21:45:03 +0200
Michael Gmelin wrote:
> > On 28. Apr 2021, at 21:37, Stefan Esser wrote:
> >
> > Am 28.04.21 um 20:44 schrieb Michael Gmelin:
> >>
> >>
> >>> On Wed, 28 Apr 2021 20:00:38 +0300
> >>> Yuri P
> On 28. Apr 2021, at 21:37, Stefan Esser wrote:
>
> Am 28.04.21 um 20:44 schrieb Michael Gmelin:
>>
>>
>>> On Wed, 28 Apr 2021 20:00:38 +0300
>>> Yuri Pankov wrote:
>>>
>>> Not sure if it's just me, but I'm seeing a bit of git wei
nts?
> ___
> 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"
--
Michael Gmelin
__
t carefully
> chosen, but haven't found any sound/audio specific mailing lists.
>
Just out of curiosity: Going to chrome://settings/content/microphone
won't allow you to select the input device to use? (it seems like having
the select box in there is platform specif
> On 16. Apr 2021, at 19:29, Rodney W. Grimes
> wrote:
>
>
>>
>> n Fri, Apr 16, 2021 at 11:36 AM Rainer Hurling wrote:
>>>
>>> While viewing sys/sys/param.h I noticed that the comment of the
>>> definition of __FreeBSD_version is probably out of date.
>>>
>>> Since the switch to Git,
> ___
> 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"
--
Michael Gmelin
_
cally "whatever Mozilla did", as the certificates are
> imported from NSS.
>
> Regards,
> Christoph
>
--
Michael Gmelin
___
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"
he one busy.
> dtrace -x stackframes=100 -n 'profile-99 /arg0 && pid == 31/ {
> @[stack()] = count(); } tick-60s { exit(0); }'
>
> One striking thing is how many times hpet_get_timecount is present...
Does tuning of
- vfs.zfs.scrub_delay
- vfs.zfs.resilver_min_time_ms
-
> On 26. Mar 2021, at 04:30, Scott Long wrote:
>
> Hi everyone,
>
> Speaking on behalf of Core, i wanted to let you know that 13.0 RC4 might be
> delayed. Glen has an emergency to attend to, and might be unavailable or
> slow to respond for a few more days.
Fingers crossed, whatever it
lowest
- different kern.eventtimer.timer
Try running with powerd disabled.
Try disabling acpi_thermal (debug.acpi.disabled="thermal") as stated in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455#c9
Certainly someone else has better ideas though.
Best,
Michael
--
Michael G
o the first difficulty is to find
> man page in which possible tunable may be explained. If the problem is
> releted to some device, it is most hopeful to check its man page. But
> in this case, even after reading the commit message, I had no idea
> which man page to check.
>
see
> On 4. Feb 2021, at 10:47, Yasuhiro Kimura wrote:
>
> It's a bit off topic from the first question, but please let me ask
> another one.
>
> When everything is default, devel/git and textproc/docproj are
> installed in chroot environment after building userland and installing
> it to chroot
> On 3. Feb 2021, at 13:50, Thomas Laus wrote:
>
> On 2/2/21 8:16 AM, David Wolfskill wrote:
>> You might want to see if this ports/UPDATING entry:
>>
>> 20200320:
>> AFFECTS: users of x11/libxkbcommon
>> AUTHOR: zeis...@freebsd.org
>>
>> The libxkbcommon library (x11/libxkbcommon), used
gt; ---
> Kazuhiko Kiriyama
> ___
> 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"
--
Michael Gmelin
___
l to (re)start daemons (plus, as a safety measure, configure
"_fib=2" within the jail's /etc/rc.conf).
Cheers,
Michael
--
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
> On 2. Jan 2021, at 19:44, Graham Perrin wrote:
>
> FreeBSD mowa219-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT #0
> main-c530-g8b4c3a03f: Fri Jan 1 15:27:15 GMT 2021
> root@mowa219-gjp4-8570p:/usr/obj/usr/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG
> amd64
>
>
> On 15. Dec 2020, at 08:44, Matthias Apitz wrote:
>
> El día lunes, diciembre 14, 2020 a las 10:16:21a. m. +0100, Matthias Apitz
> escribió:
>
>> I did a step by step down grading with 'svn up -r. hdaa.c hdaa.h'
>> (only these two files), starting from r368166 down to the following
>>
> On 11. Dec 2020, at 15:51, Jakob Alvermark wrote:
>
>
>> On 12/11/20 8:06 AM, Matthias Apitz wrote:
>>> El día miércoles, diciembre 09, 2020 a las 11:55:18a. m. +0100, Hans Petter
>>> Selasky escribió:
>>>
>>> On 12/9/20 11:48 AM, Matthias Apitz wrote:
El día miércoles, diciembre
kern/elf_load_obj.c off the top of my head), looked at mailing
> >> list archives and forums etc, all to no avail.
> >>
> >> I have / on UFS+J and /usr on ZFS and nothing in /etc/src.conf. I
> >> had /etc/malloc.conf with the recommended symlink from UPDATING,
> >> but the same happens with that moved out of the way. Nothing seems
> >> to help.
> >>
> >> Do I need to go back further to get into a usable state or is
> >> there something else I should be doing?
> >
> > With very few exceptions (bug 250897, 2020/11/6), I've found
> > 13-current bootable since 10/26 (up through my current system, 13.0
> > r368388 (2020/12/6). You obviously need to make sure that an extra
> > drivers you add in are compiled against the kernel, but ZFS is
> > typically one of those.
>
> I think we covered that.
>
> Thanks for the help and the pointers, but unfortunately the mystery
> remains.
>
Do you have anything in /boot/modules?
(wild shot)
-m
--
Michael Gmelin
___
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 26. Nov 2020, at 19:21, Gary Jennejohn wrote:
>
> On Thu, 26 Nov 2020 10:44:19 -0700
> Warner Losh wrote:
>
>>> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote:
>>>
>>>
>>>
>>> On Thu, 26 Nov 2020 10:12:06 +0100
>&
simple
> > > searches.
> >
> > For SAS drives, there's a mode page that controls this behavior.
> >
> > You might see if the sysutil/ataidle port/package does what you
> > want.
>
> Thanks, Warner, but that port is not in my HEAD ports tree. It's
>
> On 16. Sep 2020, at 22:53, Michael Gmelin wrote:
>
>
>
>>> On 16. Sep 2020, at 22:45, mike tancsa wrote:
>>>
>>> On 9/16/2020 2:07 PM, sth...@nethelp.no wrote:
>>> # override default of no subsystems
>>> -Subsystemsftp/u
> On 16. Sep 2020, at 22:45, mike tancsa wrote:
>
> On 9/16/2020 2:07 PM, sth...@nethelp.no wrote:
>> # override default of no subsystems
>> -Subsystemsftp/usr/libexec/sftp-server
>> +Subsystemsftpinternal-sftp -l INFO
>
> Hi,
>
> What is the difference between these two ?
> On 16. Sep 2020, at 20:08, sth...@nethelp.no wrote:
>
>
>>
>> FTP is (becoming?) a legacy protocol, and I think it may be time to
>> remove the ftp server from the FreeBSD base system - with the recent
>> security advisory for ftpd serving as a reminder.
>>
>> I've proposed adding a
> On 12. Sep 2020, at 11:06, Hartmann, O. wrote:
>
> On Sat, 12 Sep 2020 10:03:18 +0200
> Michael Gmelin wrote:
>
>>> On 12. Sep 2020, at 09:55, Hartmann, O.
>>> wrote:
>>> On Fri, 11 Sep 2020 07:18:33 -0600
>>> Alan Somers wrote
> On 12. Sep 2020, at 09:55, Hartmann, O. wrote:
>
> On Fri, 11 Sep 2020 07:18:33 -0600
> Alan Somers wrote:
>
>>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
>>> wrote:
>>>
>>> On Thu, 10 Sep 2020 10:44:08 -0600
>>> Alan Somers wrote:
>>>
No, it's devfs. I'll fix it.
> On 11. Sep 2020, at 22:12, Yasuhiro KIMURA wrote:
>
> Hello,
>
> I made regular update of my 13-CUREENT amd64 environment from r365330
> to r365634. Host OS is successfully updated with regular steps written
> in /usr/src/Makefile. But update of poudriere jail is failed with
> error.
> On 6. Sep 2020, at 21:09, Yoshihiro Ota wrote:
>
> On Sun, 6 Sep 2020 14:47:00 +0200
> Michael Gmelin wrote:
>
>>
>>
>>>> On 6. Sep 2020, at 12:00, Niclas Zeising
>>>> wrote:
>>>
>>> 〓On 2020-09-06 09:00, grarp
> On 6. Sep 2020, at 12:00, Niclas Zeising wrote:
>
> On 2020-09-06 09:00, grarpamp wrote:
>>> On 9/6/20, Kevin Oberman wrote:
>>> On Sat, Sep 5, 2020 at 8:04 PM Yoshihiro Ota wrote:
Is "403 Forbidden" an intended response for a brower access to
> On 24. Aug 2020, at 17:20, Shawn Webb wrote:
>
> Hey FreeBSD peeps,
>
> The zfs(8) manpage says that the maximum length of a dataset name is
> MAXNAMELEN (256 bytes). I've created a ZFS volume that has a dataset
> name length of 62. I don't see the ZFS volume in /dev/zvol and I
> noticed
> On 29. Jul 2020, at 21:29, Poul-Henning Kamp wrote:
>
> ----
> Michael Gmelin writes:
>
>> I meant which xorg driver - modesetting or Intel?
>
> It looks like "modesetting":
>
You could try installing xf86-video-intel and see if that makes a d
> On 29. Jul 2020, at 21:18, Poul-Henning Kamp wrote:
>
> ----
> Michael Gmelin writes:
>
>> Which driver are you using?
>
> drm-devel-kmod-5.3.g20200724
>
I meant which xorg driver - modesetting or Intel?
-m
> dmesg:
>
>drmn0: on vgap
> On 29. Jul 2020, at 21:02, Poul-Henning Kamp wrote:
>
>
> Ed Maste writes:
>>> On Wed, 29 Jul 2020 at 06:20, Poul-Henning Kamp wrote:
>>>
>>> I just noticed that KiCad's scroll-bars flash a lot whenever the mouse
>>> pointer is moved, that sounds like it could be the
1 - 100 of 214 matches
Mail list logo