On Wed, 12 Mar 2025 05:28:13 -0700
David Wolfskill wrote:
> On Wed, Mar 12, 2025 at 09:18:06PM +0900, Tomoaki AOKI wrote:
> > ...
> > Tried (still before reverting, patched /etc/rc.d/ntpd) switching
> > command line option to corresponding statements in ntp.conf, and
&g
On Tue, 11 Mar 2025 17:08:46 -0700
Cy Schubert wrote:
> In message <20250312074100.17f51ecf414b2084def58...@dec.sakura.ne.jp>,
> Tomoaki
> AOKI writes:
> > On Tue, 11 Mar 2025 12:21:03 -0700
> > Cy Schubert wrote:
> >
> > > In message <20250312041
tpd: WARNING: failed to start ntpd
In this case, you'll find something like
Need MAC 'ntpd' policy enabled to drop root privileges
daemon child exited with code 255
in ntpd logfile (/var/db/ntpd.log in my case, but
possibly /var/log/messages by default).
--
Tomoaki AOKI
On Tue, 11 Mar 2025 12:21:03 -0700
Cy Schubert wrote:
> In message <20250312041554.48013af3d18e4a5672de3...@dec.sakura.ne.jp>,
> Tomoaki
> AOKI writes:
> > On Tue, 11 Mar 2025 12:08:10 -0700
> > Cy Schubert wrote:
> >
> > > In message <20250312040
On Tue, 11 Mar 2025 12:08:10 -0700
Cy Schubert wrote:
> In message <20250312040101.154420f993ed27966dfc1...@dec.sakura.ne.jp>,
> Tomoaki
> AOKI writes:
> > On Tue, 11 Mar 2025 08:13:51 -0700
> > Cy Schubert wrote:
> >
> > > In message <20250311011
On Tue, 11 Mar 2025 08:13:51 -0700
Cy Schubert wrote:
> In message <20250311011257.dd642ecbcd132ecb7142d...@dec.sakura.ne.jp>,
> Tomoaki
> AOKI writes:
> > On Mon, 10 Mar 2025 16:37:58 +0100
> > "Herbert J. Skuhra" wrote:
> >
> > > On Mo
On Mon, 10 Mar 2025 14:21:32 +0200
Marek Zarychta wrote:
>
> W dniu 10.03.2025 o〓14:17, Tomoaki AOKI pisze:
> > On Mon, 10 Mar 2025 05:06:25 -0700
> > David Wolfskill wrote:
> >
> >> On Mon, Mar 10, 2025 at 01:51:40PM +0200, Marek Zarychta wrote:
> >&g
bsd.org/archives/dev-commits-src-branches/2025-February/021315.html
https://lists.freebsd.org/archives/dev-commits-src-branches/2025-March/021327.html
Maybe order of some evaluations in /etc/rc.d/ntpd needs to be moved.
--
Tomoaki AOKI
modules
only and other components x11/linux-nvidia-libs installs are not
affected. But I'm not a nvidia insider and cannot be sure.
Anyway, currently we give "--extract-only" flag to *.run in
x11/linux-nvidia-libs/Makefile, so anything required to be run for
detecting GPU to choose module flavor (proprietary or open) shouldn't
work here.
--
Tomoaki AOKI
On Thu, 3 Oct 2024 17:30:57 +0300
Christos Margiolis wrote:
> Hello Tomasz,
>
> Tomoaki AOKI wrote:
> > Maybe what newbies want would be:
> > *Currently active audio device is always seen as exactly the same,
> >without device number or something.
>
> Wh
mplexed to implement (automate). But parts of those is
possible by virtual_oss, by letting it create /dev/dsp, without number.
And ports supporting base OSS to default to unnumbered device.
My basic assumption is that virtual_oss would be worth incorporated
in base at some time in the future.
Regards.
--
Tomoaki AOKI
ted ports also wants to be
reconfigured for new values.
What comes in mind is
adding (if needed) and selecting a new sink for pulseaudio.
(And of course resetting and deleteing on plugged out, too.)
--
Tomoaki AOKI
On Fri, 2 Aug 2024 22:04:37 +0100
Pontus Bramberg wrote:
> On 8/2/24 20:07, Tomoaki AOKI wrote:
> > On Fri, 2 Aug 2024 17:24:30 +0100
> > Pontus Bramberg wrote:
> >
> >> From: Pontus Bramberg
> >> To: stable@freebsd.org
> >> Subject: Nvidi
ies.
If anything changed between your previous and current firmware, trying
to restore the changed defaults to previous default could help.
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277827
[2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277364
[3] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277028
[4] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279539
--
Tomoaki AOKI
ld be strongly encouraged to run latest patch (-p*)
release of the point release they are using, kmod pkgs should be
provided for latest patch release only on single point releases.
(Means, when 14.0 is at 14.0-p3 and 14.1 is at 14.1-p1, and 14.0 is not
yet EOL'ed, kmod pkgs for 14.0-p3 and 14.1-p1 should be provided.)
>
> --
> Colin Percival
> FreeBSD Release Engineering Lead & EC2 platform maintainer
> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
--
Tomoaki AOKI
fficient.
[1]
https://forums.freebsd.org/threads/cant-log-in-with-graphics-drm-515-kmod.94155/#post-662490
>
> --
> Colin Percival
> FreeBSD Release Engineering Lead & EC2 platform maintainer
> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
--
Tomoaki AOKI
On Wed, 3 Jul 2024 08:24:14 +0900
Tomoaki AOKI wrote:
> On Tue, 02 Jul 2024 22:11:45 +
> j...@chen.org.nz wrote:
>
> > Hi,
> >
> > I updated my STABLE-14/amd64 to 1a0314d6e30554fc2b07caa5121b00956f416cc4
> > (ctladm: Fix a race), and it appe
ed to apply the patch attached at Bug 279539 [2] to build.
And if you want to test 555 series of nvidia-drm*-kmod driver, you need
to apply the diff at Differential revision D45400 of Phablicator [3],
too.
[1]
https://cgit.freebsd.org/src/commit/?h=stable/14&id=620a6a54bb7bb6e1c5607092b6ec49e353e0925f
[2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279539
[3] https://reviews.freebsd.org/D45400
--
Tomoaki AOKI
clunky but it keeps me behind my ISP’s
> spam filter.
>
> Cheers,
>
> Andrew
You'd better contacting postmas...@freebsd.org.
Or, this is not the case though, file a bug on bugzilla.freebsd.org
with Product = "Services" and Component = "Mailing Lists".
This is helpful is your emails are somehow rejected by freebsd.org mail
server.
--
Tomoaki AOKI
ves/freebsd-security/2024-March/000248.html
[2]
https://forums.freebsd.org/threads/backdoor-in-upstream-xz-liblzma-leading-to-ssh-server-compromise.92922/
--
Tomoaki AOKI
On Mon, 25 Mar 2024 09:56:53 -0700
Kevin Oberman wrote:
> On Mon, Mar 25, 2024 at 2:18〓AM Tomoaki AOKI
> wrote:
>
> > On Mon, 25 Mar 2024 01:01:50 -0700
> > Bakul Shah wrote:
> >
> > > On Mar 24, 2024, at 7:11 PM, Chris Torek wrote:
> > > &
phics/gpu-firmware-amd-kmod here?
If you're not sure, you can use metaport graphics/gpu-firmware-kmod.
[1]
https://cgit.freebsd.org/ports/commit/graphics/drm-61-kmod?id=e04b01217828bf06d36a02ad8e69dbb54c30b607
--
Tomoaki AOKI
rnel and userland.
This would force both kernel and userland to be built using the same
patchlevel, even if one of which is actually unchanged.
But maybe helpful to avoid confusion like this.
What was worse this time was that a non-in-kernel-but-in-tree module,
zfs.ko, is updated but kernel itself is not updated.
--
Tomoaki AOKI
all go through then life is good (this is what gets us to OK).
> >>
> >> BUT, if there is a power failure or crash and only some of them make it
> >> to disk, then you have a corrupt ESP and the BIOS may pick that ESP to boot
> >> off of, booting corrupt data.
> >>
> >> Since this is infrequently updated, you can use a safe sequence to update
> >> things one partition a time, then you might lose the file entirely, but it
> >> will either be there and good. Or it will be gone. You can't get into a bad
> >> situation. Either you boot old or new loader and can just quit from the
> >> boot loader if it's the old one and it can't boot. Efi will try the next
> >> one on the list.
> >>
> >> Here manual mirroring, if scripted, can be more reliable than gmirror.
> >>
> >> Warner
> >>
> >> -pete.
--
Tomoaki AOKI
uto-generated by bsdinstall, used on
initial installation, and kept for later use by `make installworld`.
bsdinstall should know how many, and which disk is configured for
FreeBSD.
And, maybe impossible for now, but if "Actually booted from at this
time" ESP is auto-mounted on default location, it could be helpful for
admins. Just a thought.
--
Tomoaki AOKI
t; on a single partition quite happily ?
>
>
> -pete.
This is just (casuall, though) discussed in Forums [1].
I've written comment #19.
[1]
https://forums.freebsd.org/threads/upgrading-bootloader-on-zfs-mirror.91198/
--
Tomoaki AOKI
l.
if ( -X zsh && -f ~/.Use_zsh ) exec zsh
This way, if zsh is executable in the path AND ~/.Use_zsh exists, zsh
is executed, otherwise tcsh keeps running as interactive shell.
If zsh accidentally (or intentionally) dissappears, base tcsh is used.
Assuming zsh is available and executable, I can intentionally create
~/.Use_zsh (`touch ~/.Use_zsh` is enough) to use zsh and delete it to
use base tcsh.
--
Tomoaki AOKI
mple pf.conf and some other vital files.
>
> Kind regards
> Miroslav Lachman
I don't think it hackery.
What should have been is that default sshf_config to be
in /etc/defaults and /etc/defaults/rc.conf points to it, and anyone
needs custom settings to create sshd_config in /etc/ssh (or in
somewhere else), like rc.conf case.
--
Tomoaki AOKI
of monotonic_buffer_resource.cpp
> > via the recent official snapshot build of stable/13 .
> >
> > I've not tried to test Qt5 or Qt6, sticking with the simpler/smaller
> > context that you also report as failing in the odd context. I suggest
> > avoiding Qt5/Qt6 testing until you have a context with the
> > monotonic_buffer_resource.cpp test working.
> >
> > ===
> > Mark Millard
> > marklmi at yahoo.com
Hi.
Do you have anything left under /usr/local/lib/compat/pkg?
If any, what happenes if you move the contents to any place outside
libraries are searched?
For example,
# mkdir /usr/local/00preserve ; mv /usr/local/lib/compat/pkg
/usr/local/00preserve \
&& mkdir /usr/local/lib/compat/pkg
as root.
I don't recommend deleting them unless confirming the above is safe.
Doing so, you can restore them once it does any harm.
Regards.
--
Tomoaki AOKI
svn://svn.freebsd.org/base
> >>
> >> Or visit the following URL, replacing NN with the revision number:
> >>
> >> https://svnweb.freebsd.org/base?view=revision&revision=NN>
> >> <https://svnweb.freebsd.org/base?view=revision&revision=NN>
> >>
> >> VII. References
> >>
> >> https://reviews.freebsd.org/D39973>
> >> <https://reviews.freebsd.org/D39973>
> >>
> >> The latest revision of this advisory is available at
> >> https://security.FreeBSD.org/advisories/FreeBSD-EN-23:09.freebsd-update.asc>
> >>
> >> <https://security.freebsd.org/advisories/FreeBSD-EN-23:09.freebsd-update.asc>
Hi.
sshd has option to specify "-f config_file" option to override
default /etc/ssh/sshd_config. See `man sshd` for details.
And in /etc/defaults/rc.conf, 3 lines (wrapped to 4 lines here) as below
exists.
sshd_enable="NO"# Enable sshd
sshd_program="/usr/sbin/sshd" # path to sshd, if you want a
different one.
sshd_flags="" # Additional flags for sshd.
You should already set at least 'sshd_enable="YES"' in
your /etc/rc.conf or /etc/rc.conf.local, if you are running sshd on
your system. Why not create customised sshd_config with other name or
other place and override default with sshd_flags, keeping vanilla one
intact, for example, copy /etc/ssh/sshd_config
to /etc/ssh/sshd_config_local, edit to fit your needs, and specify
sshd_flags="-f /etc/ssh/sshd_config_local" in your /etc/rc.conf[.]ocal]?
Keep in mind tracking any changes to vanilla one for
additins/changes/deletions of functuonality and edit yours when needed.
--
Tomoaki AOKI
7;m intentionally keep this opened, as
this problem randomly happenes on Qt5 updates (not everytime).
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268652
--
Tomoaki AOKI
}
Regards.
On Mon, 18 Sep 2023 09:26:56 -0400
Alexander Motin wrote:
> block_cloning feature is marked as READONLY_COMPAT. It should not
> require any special handling from the boot code.
>
> On 18.09.2023 07:22, Tomoaki AOKI wrote:
> > Really OK?
> >
> >
> > tunable does not even exist anywhere outside of FreeBSD base tree, I'd
> > propose to give this code another try here too. I see no point to
> > have it disabled at least in main unless somebody needs time to run
> > some specific tests first.
--
Tomoaki AOKI
3
Thanks in advance and hope you have nice remaining travel.
Regards.
> On Sun, Sep 17, 2023 at 1:39 AM Tomoaki AOKI
> wrote:
>
> > On Sun, 3 Sep 2023 13:33:28 +0900
> > Tomoaki AOKI wrote:
> >
> > > On Sat, 2 Sep 2023 22:47:53 -0500
> > > Jake F
On Sun, 3 Sep 2023 13:33:28 +0900
Tomoaki AOKI wrote:
> On Sat, 2 Sep 2023 22:47:53 -0500
> Jake Freeland wrote:
>
> > On Sat, Sep 2, 2023 at 10:40 PM Warner Losh wrote:
> >
> > >
> > >
> > > On Sat, Sep 2, 2023, 9:36 PM Jake Freeland
>
nored: 335 Fetched: 0
> Tobuild: 33800 Time: 00:30:41
>
>
> So 414 and and still building.
>
> More later. (It may be a while.)
>
> ===
> Mark Millard
> marklmi at yahoo.com
Would it planned to be MFC'ed to stable/14, and then releng/14.0 once
MFV'ed to main?
Regards.
--
Tomoaki AOKI
On Sun, 3 Sep 2023 13:33:28 +0900
Tomoaki AOKI wrote:
> On Sat, 2 Sep 2023 22:47:53 -0500
> Jake Freeland wrote:
>
> > On Sat, Sep 2, 2023 at 10:40 PM Warner Losh wrote:
> >
> > >
> > >
> > > On Sat, Sep 2, 2023, 9:36 PM Jake Freeland
>
On Sat, 2 Sep 2023 22:47:53 -0500
Jake Freeland wrote:
> On Sat, Sep 2, 2023 at 10:40 PM Warner Losh wrote:
>
> >
> >
> > On Sat, Sep 2, 2023, 9:36 PM Jake Freeland
> > wrote:
> >
> >> On Sat, Sep 2, 2023 at 10:31 PM Tomoaki AOKI
> >> w
On Sat, 2 Sep 2023 21:38:07 -0600
Warner Losh wrote:
> On Sat, Sep 2, 2023, 9:30 PM Tomoaki AOKI wrote:
>
> > Hi.
> >
> > There are discussions about deadlocks issue of ZFS on freebsd-current
> > ML, starting from [1] last month.
> > IIRC, at least some fi
ews.freebsd.org/D41641
--
Tomoaki AOKI
lge
You should forced to use vt when you start using PCs UEFI firmware
without CSM support.
Without CSM, UEFI firmware not only impossible to boot with legacy
(aka BIOS) mode, but also NOT supporting pure text mode that sc driver
mandates anymore. vt (efifb) is the only choice here.
--
Tomoaki AOKI
efault_mode="1920*1080"
efi_max_resolution="2160p"
# efi_max_resolution="1600x900" # Set the max resolution for EFI loader to use:
# 480p, 720p, 1080p, 2160p/4k, 5k, or
# specify WidthxHeight (e.g. 1920x1080)
vbe_max_resolution=1024x768
--
Tomoaki AOKI
new tree." is at line 255
(in function extract_tree()).
This is emitted when function build_tree() failed.
It could happen on some situation, but maybe likely happen when
working directory of etcupdate (/var/db/etcupdate by default)
is out of space, or missingly ran etcupdate with non-root user.
d the pdf file that explain how to install the graphical
> > system).
> >
> > I am asking here because you are supposed to be interested in 13.2
> > development at this time if I understood right.
> > But maybe I am suppose to ask to documentation team... unsure.
> >
> > My wish would be that the installer would install a text version of the
> > handbook.
> >
> >
>
>
--
Tomoaki AOKI
l reviewers listed in [1] approved the change.
Note that this is NOT MFC'ed to stable/12 and before, although all 13.x
has it (13.0 is released at Apr. 13,2021).
[1] https://reviews.freebsd.org/D26973
[2]
https://cgit.freebsd.org/src/commit/usr.bin/login/login.conf?id=09ef995baf45333d45ab214daf8c03e1a25f8fcc
--
Tomoaki AOKI
On Fri, 3 Feb 2023 12:36:47 -0500
George Mitchell wrote:
> On 2/3/23 11:06, Tomoaki AOKI wrote:
> > [...]
> > If this is the case like above, the only solution is to move to
> > character set containing ALL characters all over the world.
> >
> > AFAIK, the o
On Fri, 3 Feb 2023 17:31:55 +0100
Eivind Nicolay Evensen wrote:
> Den Sat, 4 Feb 2023 01:06:05 +0900
> skrev Tomoaki AOKI :
>
> > On Fri, 3 Feb 2023 15:18:53 +0100
> > Eivind Nicolay Evensen wrote:
> >
> > > Den Fri, 3 Feb 2023 19:12:
e 0x5c varied, varied and varied! Crazily.
If this is the case like above, the only solution is to move to
character set containing ALL characters all over the world.
AFAIK, the only candidates are only two, TRON code [1] and Unicode (UCS,
ISO/IEC 10646) [2]. And TRON code is very rarely used, actual candidate
would be Unicode only.
Note that Unicode is usually encoded to any of UTF-8, UTF-16 or UTF-32
for data transfer (sometimes raw UCS-2?).
[1] https://en.wikipedia.org/wiki/TRON_(encoding)
[2] https://en.wikipedia.org/wiki/Unicode
P.S.
On UTF-8, character ø was encoded to UTF-8: 0xC3 0xB8. So it should be
OK.
--
Tomoaki AOKI
\nøl\n" | grep ø
bø
øl
I'm using LC_ALL=ja_JP.UTF-8, LANG=ja_JP.UTF-8 as locale and shells/zsh
as command line shell.
What happenes if you switch locale to nb_NO.UTF-8?
--
Tomoaki AOKI
whether I can `zpool upgrade` or
current status is the last pool features I can have.
Regards.
[1] https://www.freebsd.org/releases/14.0R/schedule/
--
Tomoaki AOKI
ps ://
> www.aliexpress.com/item/1005003990581434.html
>
> Also, if you hook a couple back to back via xover cable, are you able to
> manually set the speed to 1G and pass traffic ? It doesnt work for me.
>
> ---Mike
FYI:
https://en.wikipedia.org/wiki/Medium-dependent_interface
Maybe you should use straight-through cable for 1G or faster.
--
Tomoaki AOKI
still ditected as 'em1'. Did I do something wroing?
>
> ---
> Yasuhiro Kimura
Even if disabling module, possibly automatically re-configured
via /etc/rc.conf using devmatch. Try placing
devmatch_blocklist="${devmatch_blocklist} if_em"
line in /etc/rc.conf.
See `man rc.conf`.
HTH...
--
Tomoaki AOKI
lists.freebsd.org/archives/freebsd-current/2022-February/001550.html
[2]
https://lists.freebsd.org/archives/freebsd-current/2022-February/001589.html
--
Tomoaki AOKI
able to boot from
MBR-patritioned disk but there would be some risk that they have the
same limitations as legacy BIOS in such situations.
Note that possibly I'm just lucky enough not to be bitten.
--
Tomoaki AOKI
dia drastically?
> >
> >
> > Or we could just compress the modules. We've supported loading compressed
> > modules for a long time
>
> AFAIK, kldload cannot load compressed modules, only loader can.
If so, kldload should support it as loader does.
> I suppose GEOM_UZIP is more effective solution, and more versatile.
--
Tomoaki AOKI
ing configuration
touching your ZFS pool?
If so, and the partition position problem is really the root cause,
it can cause loader to look for your ZFS root pool and fail.
(/boot/zfsloader is used instead of /boot/loader.)
Comment it out and let /etc/rc.d/zpool to import your now-non-root pool.
If (and only if) the import fails, possibly you need to delete
everything you moved to UFS from ZFS to avoid collision.
--
Tomoaki AOKI
rds have severe limitation
about DIMM slot usage, if not fully used.
For example, assuming slot No. are B0-0, 1, 2, 3 and B1-0, 1, 2, 3,
*Must use "interleaved. If 4 in 8 slots are to be used,
B0-0, B0-2, B1-0, B1-2 shall be used.
(Some forced B0-1, B0-3, B1-1, B1-3, IIRC)
*Must NOT use "interleaved.
B0-0, B0-1, B1-0, B1-1 shall be used.
*Must NOT use B1 unless B0 is full of DIMs.
B0-0. B0-1, B0-2, B0-3 shall be used.
and so on, depending on motherboard vendor (at worst, per model.)
--
Tomoaki AOKI
n it.)
You may feel it's unrelated reading the title, but actually it is
caused by the behaviour of Intel ThunderBolt controller.
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
>
> --
> Jerry
>
> "Eagles may soar, but weasels don't get sucked into jet engines."
>
--
Tomoaki AOKI
On Sun, 31 Oct 2021 18:15:25 +0100
Marek Zarychta wrote:
> W dniu 29.10.2021 o〓08:29, Andrea Venturoli pisze:
> >
> > On 10/29/21 00:47, Tomoaki AOKI wrote:
> >
> >> But possibly we need to delete current smbfs code from base and switch
> >> to ports (sysu
de from base and switch
to ports (sysutils/*?) if it require some code having incompatible
license for base.
Anyway, please don't remove it unless usable alternative appears.
> If I am "well informed" FreeBSD is the only widely used OS not
> supporting SMBv2. (MacOS, Linux, Sola
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
: PciRoot(0x0)/Pci(0x1f,
0x0)/Acpi(PNP0303,0x0),/VenHw(87c8ba12-5952-4012-8297-dede395f5d5b),/PciRoot(0x0)/Pci(0x1f,
0x0)/Acpi(PNP0f03,0x0),/VenHw(ea52f05f-ee81-45b7-807a-ceefbe9ba6c2),/PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/USB(0x3,0x0)/USB(0x0,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/USB(0x0,0x0)
--
Tomoaki AOKI
61 matches
Mail list logo
