On 4/23/21 11:23 PM, Xin Li via freebsd-stable wrote:
I think loader do not support the native OpenZFS encryption yet.
However, you can encrypt non-essential datasets on a boot pool (that is,
if com.datto:encryption is "active" AND the bootfs dataset is not
encrypted, you can still boot from it)
On 4/5/21 8:27 PM, Roger Leigh wrote:
Can I ask, for those who do enable it, why isn’t “sftp” acceptable (or “scp”)?
Because it's an *incompatible* replacement.
While I never enabled ftpd, I was once asked to.
I refused and enabled sftp instead: the problem was that for 99% of the
customers
On 4/5/21 5:28 PM, sth...@nethelp.no wrote:
- replace DNS lookups with DoH and/or DoT. Why let your ISP see your DNS
traffic?
Because I trust my (European) ISP significantly more than I trust big
US companies? Yes, I have a pretty good idea what Cloudflare, Google
etc have said about the queri
On 2020-07-09 16:15, Mark Johnston wrote:
This is a different bug, unfortunately.
:-(
The one fixed by the patch is described in PR 242913.
Thanks for the info, anyway.
bye
av.
___
freebsd-stable@freebsd.org mailing list
https://lis
On 2020-07-09 10:31, Niclas Zeising wrote:
I am unsure, but it seems mostly related to using X forwarding, when
looking at the errata notice.
Which I'm using heavily...
What issues are you seeing, on which hardware?
I've extensively wrote about this on x11@, e.g.:
https://lists.freebsd.o
On 2020-07-08 23:06, FreeBSD Errata Notices wrote:
II. Problem Description
A bug in one of the LinuxKPI subroutines could cause a kernel panic.
Hello.
Can we get any reference to this? E.g. a sample stack trace?
I've been experiencing panics with the latest x.org and had to revert to
an o
On 2019-11-24 21:01, Chris Gordon wrote:
Just my 2c...
Since updating to Catalina, I've found lots of problems dealing with SMB using
the Finder window and the items under the Locations side bar. For instance:
- Mount a share. At some point overnight when nothing is using it, the share
is u
On 5/15/19 6:16 PM, Matt Garber wrote:
Exactly. If batching 8 (or more) individual bugs/issues together into
one release is really causing admin/manpower overload and angst,then
maybe it’s time in your situation to use the binary updates (which
would only be a single `freebsd-update` and reboot,
On 4/30/19 2:41 AM, Michelle Sullivan wrote:
The system was originally built on 9.0, and got upgraded through out the
years... zfsd was not available back then. So get your point, but maybe you
didn’t realize this blog was a history of 8+ years?
That's one of the first things I thought abou
On 10/4/18 7:38 PM, Warner Losh wrote:
I'd also suggest that rl stands in stark contrast to the cs, wb, sn, smc,
sf, tl, tx and vr drivers, which nobody has mentioned in this thread, and
which I doubt are in use in any FreeBSD system of any age today.
I still have a vr integrated on an old Mot
On 05/09/18 01:51, Jack L. wrote:
I use crontab @daily (/sbin/gmirror status | grep -q COMPLETE) || mail
-s "gmirror failure" email addy
Or you could simply add the following to /etc/periodic.conf[.local]:
daily_status_gmirror_enable="YES"
bye
av.
On 03/25/17 19:02, Andriy Gapon wrote:
Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors with
FreeBSD?
Will an equivalent Athlon do or is this Opteron specific?
What would that Athlon be?
bye
av.
___
freebsd-stable@fr
On 10/20/16 22:12, Peter wrote:
Hello.
Basically You have two options: A) fire up kgdb, go into the code and
try and understand what exactly is happening. This depends
if You have clue enough to go that way; I found "man 4 gdb" and
especially the "Debugging Kernel Problems" pdf by Greg Lehey
Hello.
Last week I upgraded a 9.3/amd64 box to 10.3: since then, it crashed and
rebooted at least once every night.
The only exception was on Friday, when it locked without rebooting: it
still answered ping request and logins through HTTP would half work; I'm
under the impression that the di
On 08/02/16 21:25, Konstantin Belousov wrote:
Below is the merge of some high-profile virtual memory subsystem bug
fixes from stable/10 to 10.3. I merged fixes for bugs reported by
users, issues which are even theoretically unlikely to occur in real
world loads, are not included into the patch se
On 08/02/16 21:25, Konstantin Belousov wrote:
Below is the merge of some high-profile virtual memory subsystem bug
fixes from stable/10 to 10.3. I merged fixes for bugs reported by
users, issues which are even theoretically unlikely to occur in real
world loads, are not included into the patch se
On 01/19/16 15:19, Matthew Seaman wrote:
On 01/19/16 13:13, Andrea Venturoli wrote:
Two days ago I upgraded a (perfectly working) 9.3/i386 box to 10.2p10
Since then I've had two panics with the following message:
panic: assertion "lp->busy_itl==0&&lp->busy_itlq==0&qu
On 07/18/13 21:31, Charles Swiger wrote:
Updating the firmware and increasing the timeout before these spin down
> automagically is likely to help, but as Andrea noted, such drives do
> have quite a history of timeout problems due to excessive head parking
> and their power conservation attem
On 07/18/13 21:13, Dr Josef Karthauser wrote:
b) try different controllers and/or different OS releases.
I'm committed to FreeBSD, as the machine is already rolled out and in a data
centre ;).
I said different "OS releases", not different "OS"!
I wouln't say such a blasphemy :)
bye
On 07/18/13 10:25, Bob Bishop wrote:
Me too (over a long period, with various hardware).
There is a general problem with energy-saving drives that controllers don't
understand them. Typically the drive decides to go into some power-saving mode,
the controller wants to do some operation, the d
On 11/26/12 23:09, Bas Smeelen wrote:
Probable addition
8.8 I get a lot of 'spurious interrupts detected' messages on a modified
i386 build kernel and my computer does not work right. What did I do wrong?
You have a single processor computer, build your own customized kernel
and disabled
option
On 11/23/12 10:25, Lars Engels wrote:
I've seen that on almost every USB MP3 player, Android mobile phones and
on other USB devices that export an internal memory card.
BTW, my disk drive is SCSI attached, so it's not an USB-only issue.
But it would be really really really great if someone(
On 11/19/12 18:44, Eitan Adler wrote:
Hey all,
The FAQ for FreeBSD needs a significant amount of updating and
changing. The first step in that process is to figure out what needs
to be changed.
If you can a take a moment and thoroughly review just one
question and add your comments and concern
On 11/19/12 18:44, Eitan Adler wrote:
Hey all,
The FAQ for FreeBSD needs a significant amount of updating and
changing. The first step in that process is to figure out what needs
to be changed.
If you can a take a moment and thoroughly review just one
question and add your comments and concern
On 11/17/12 21:04, Kevin Oberman wrote:
Looks like everything is back up again.
Thanks for the good work.
Yes, but don't bet that csup and cvs will be around long.
I'm aware of this and I'm (adimttedly slowly) moving away from csup.
The outage
was the result of an intrusion into core Fre
On 11/16/12 18:08, Eitan Adler wrote:
There are known problems with the cluster at this time. The machines
were recently moved, upgraded, and generally manipulated. We are
working to fix this as fast as possible.
Looks like everything is back up again.
Thanks for the good work.
bye
On 02/17/11 22:06, Andrea Venturoli wrote:
I
seem to remember a similar problem I had a long time ago. I opted to
use a consistent, not-used port and haven't seen the problem since
(this was years ago, so I can't remember if the error you're seeing
was identical to mine)
On 02/17/11 04:28, Jeremy Chadwick wrote:
On Wed, Feb 16, 2011 at 09:46:37PM -0500, Michael Proto wrote:
On Wed, Feb 9, 2011 at 9:20 AM, wrote:
Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up
(with rpc.statd and rpc.lockd enabled in rc.conf), I get:
Feb 4 07:31:11 won
On 02/09/11 15:20, george+free...@m5p.com wrote:
Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up
(with rpc.statd and rpc.lockd enabled in rc.conf), I get:
Feb 4 07:31:11 wonderland rpc.statd: bindresvport_sa: Address already in use
Feb 4 07:31:11 wonderland root: /etc/r
Scott Long ha scritto:
Hello.
The following configurations are known to be affected:
VMWare ESX
VMWare Fusion
(using bt or lsilogic controller options)
HP CISS RAID
Some MPT-SAS combinations with SATA drives attached
(Includes Dell SAS5/ir, but not PERC5/PERC6).
Does it holds for
Don't know if this is the right place to post: I encountered a non
critical error on a 6.2 i386 box and I found no reference to it on the web.
Here's the log:
Aug 1 10:33:28 soth kernel:
kdb_backtrace(e8f18848,c053df25,c0663543,c0663590,cbace6cc,...) at
kdb_backtrace+0x29
Aug 1 10:33:28 so
Kostik Belousov wrote:
In a previous (quite old) thread it was in fact suggested I might be
seeing some LOR, but only recently I activated all the debugging stuff.
The (usual) consequence of the LOR is lock up.
Mhh, yes, that's right. But I stopped having locks during file system
snapshootin
Hello.
I'm experiencing the above mentioned LOR on a 6.2p1/amd64 box (running
gmirror and SMP if that matters).
With reference to your question on
http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/031048.html:
What application you run that triggers the LOR ?
Bacula, I guess
33 matches
Mail list logo
