Re: How to make 'named' rc script invokded earlier at boot time

[Chris]

On 2021-04-30 00:30, Yasuhiro Kimura wrote:

I installed dns/bind916 on my home server and configured it so it
worked as both authoritative and recursor. Then I added
'nameserver 127.0.0.1' to /etc/resolv.conf and everything worked fine.

But after updating OS from 12.2-RELEASE to 13.0-RELEASE I noticed
execution of some rc scripts fails at boot time because of DNS lookup
error. And I also found these scripts are executed earlier than
'named'.

I've been plagued with this for years (well, a couple anyways) on several
of my servers. As I never saw anyone else mention it. I assumed it was just
"me". ;-)
rc(8) has a mountlate. Seems to me there ought to be a "startlate" key as
well. While this won't fix the cause introduced. It might at least solve
the problem.
create an /etc/rc.conf.local and move your host/nic related things into
it followed by your "named" entry. Leaving everything else in /etc/rc.conf
This (should) source all the rc.conf.local entries ahead of the rc.conf
entries. Thereby providing name resolution before ntpdate(8)/time sync
service(s)

HTH

--Chris


Now let me use 'ntpdate' as an example.

If I run `rcorder /etc/rc.d/* /usr/local/etc/rc.d/*` on 12.2-RELEASE,
then I get following result.

--
root@rolling-vm-freebsd3[474]# uname -a
FreeBSD rolling-vm-freebsd3.home.utahime.org 12.2-RELEASE-p6 FreeBSD
12.2-RELEASE-p6 GENERIC  amd64
root@rolling-vm-freebsd3[475]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/*
/etc/rc.d/growfs
/etc/rc.d/sysctl
/etc/rc.d/hostid
/etc/rc.d/zvol
/etc/rc.d/dumpon
(snip)
/etc/rc.d/static_arp
/etc/rc.d/bridge
/etc/rc.d/route6d
/etc/rc.d/NETWORKING
/etc/rc.d/mountcritremote
/etc/rc.d/devfs
/etc/rc.d/ipmon
/etc/rc.d/kdc
/etc/rc.d/mdconfig2
/etc/rc.d/newsyslog
/etc/rc.d/syslogd
/usr/local/etc/rc.d/tcsd
/usr/local/etc/rc.d/named
/etc/rc.d/watchdogd
/etc/rc.d/savecore
/etc/rc.d/archdep
/etc/rc.d/linux
/etc/rc.d/sysvipc
/etc/rc.d/SERVERS
/usr/local/etc/rc.d/tpmd
/usr/local/etc/rc.d/stunnel
/etc/rc.d/accounting
/etc/rc.d/ntpdate
/etc/rc.d/rpcbind
/etc/rc.d/nfsclient
/etc/rc.d/nisdomain
(snip)
--

As you can see, while 'named' is executed before SERVERS, 'ntpdate' is
done after it.

On the other hand I get following result on 13.0-RELEASE.

--
root@rolling-vm-freebsd2[332]# uname -a
FreeBSD rolling-vm-freebsd2.home.utahime.org 13.0-RELEASE FreeBSD 
13.0-RELEASE #0

releng/13.0-n244733-ea31abc261f: Fri Apr  9 04:24:09 UTC 2021
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
root@rolling-vm-freebsd2[333]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/*
/etc/rc.d/dhclient
/etc/rc.d/dumpon
/etc/rc.d/growfs
/etc/rc.d/natd
(snip)
/etc/rc.d/netwait
/etc/rc.d/blacklistd
/etc/rc.d/local_unbound
/etc/rc.d/NETWORKING
/etc/rc.d/pppoed
/etc/rc.d/kdc
/etc/rc.d/kfd
/etc/rc.d/nfsuserd
/etc/rc.d/iscsid
/etc/rc.d/ipropd_slave
/etc/rc.d/nfscbd
/etc/rc.d/iscsictl
/etc/rc.d/ipropd_master
/etc/rc.d/kadmind
/etc/rc.d/kpasswdd
/etc/rc.d/mountcritremote
/etc/rc.d/wpa_supplicant
/etc/rc.d/motd
/etc/rc.d/accounting
/etc/rc.d/cleartmp
/etc/rc.d/dmesg
/etc/rc.d/archdep
/etc/rc.d/gptboot
/etc/rc.d/hostapd
/etc/rc.d/virecover
/etc/rc.d/mdconfig2
/etc/rc.d/devfs
/etc/rc.d/os-release
/etc/rc.d/newsyslog
/etc/rc.d/linux
/etc/rc.d/syslogd
/etc/rc.d/sysvipc
/etc/rc.d/watchdogd
/etc/rc.d/savecore
/etc/rc.d/ntpdate
/etc/rc.d/localpkg
/etc/rc.d/auditd
/etc/rc.d/bsnmpd
/etc/rc.d/pwcheck
/etc/rc.d/power_profile
/etc/rc.d/rpcbind
/etc/rc.d/auditdistd
/usr/local/etc/rc.d/named
/etc/rc.d/nfsclient
/etc/rc.d/hastd
/etc/rc.d/SERVERS
/etc/rc.d/nisdomain
/usr/local/etc/rc.d/stunnel
/usr/local/etc/rc.d/tpmd
/usr/local/etc/rc.d/tcsd
(snip)
--

Now both 'named' and 'ntpdate' are executed before SERVERS. And
unfortunately the latter is earlier than the former. So it is natural
that execution of 'ntpdate' fails with DNS lookup failure.

I compared ntpdate rc script between releng/12.2 and releng/13.0 but
there is no difference.

--
yasu@rolling-vm-freebsd2[1035]% pwd
/usr/src
yasu@rolling-vm-freebsd2[1036]% git diff origin/releng/12.2 
origin/releng/13.0  --

libexec/rc/rc.d/ntpdate
yasu@rolling-vm-freebsd2[1037]%
--

And of cource there is no difference with /usr/local/etc/rc.d/named
either. So it seems evaluation of rcorder(8) is changed between
12.2-RELASE and 13.0-RELEASE.

Then is there any way to make 'named' rc script invoked earlier at
boot time on 13.0-RELEASE?

Best Regards.

---
Yasuhiro Kimura
___
freebsd-po...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any m

Re: clocked speed not showing in dev.cpu.[0-7].freq

[Chris]

On 2021-04-27 11:28, Ian Lepore wrote:

On Tue, 2021-04-27 at 19:22 +0100, tech-lists wrote:

Hi,

Not sure where to put this. system is amd64/stable/13. It's running
powerd but with no additional flags.

CPU is Intel(R) Core(TM) i7-4770K CPU. Has 32GB RAM

The system is clocked in the bios at 4.251 GHz. I never see this
value
in sysctl dev.cpu.[0-7].freq though. Here's the output:

[...]
sysctl dev.cpu.0
dev.cpu.0.cx_method: C1/hlt
dev.cpu.0.cx_usage_counters: 100878534
dev.cpu.0.cx_usage: 100.00% last 185us
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_supported: C1/1/0
dev.cpu.0.freq_levels: 3400/84000 3200/77169 3100/73848 2900/67388
2700/61182 2500/55201 2400/52298 2200/46677 2000/41272 1800/36091
1700/34277 1500/29407 1300/24752 1100/20312 1000/18167 800/14031
dev.cpu.0.freq: 3400
dev.cpu.0.temperature: 68.0C
dev.cpu.0.coretemp.throttle_log: 0
dev.cpu.0.coretemp.tjmax: 100.0C
dev.cpu.0.coretemp.resolution: 1
dev.cpu.0.coretemp.delta: 32
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo: _HID=none _UID=0 _CID=none
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%driver: cpu
dev.cpu.0.%desc: ACPI CPU

Here's the cpu string on boot:

CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (4251.32-MHz K8-class
CPU)

So, is it really clocked? or does the sysctl show what is right?

thanks,


The same is true on my system:

CPU: Intel(R) Xeon(R) CPU  W3680  @ 3.33GHz (4250.09-MHz K8-class CPU)

dev.cpu.0.freq_levels: 3334/143000 /13 3200/117000 3067/105000
2933/94000 2800/85000 2667/76000 2533/68000 2400/61000 2267/54000
2133/48000 2000/43000 1867/39000 1733/35000 1600/32000

I've clocked this cpu at various speeds between 4.25 - 5.0 ghz over the
years (faster when it was younger, more conservative now that it's
old).  The value in parens (4250.09) changes accordingly, but the
values in the sysctl never do.  I'm sure this is running at the
overclocked speed (various benchmark values change as they should when
changing the OC values in the bios).

FWIW on all my AMD CPUs that top out @4.25-4.50Ghz FreeBSD reports
3.8Ghz. I get the idea the FreeBSD returns the average (running) top
speed on CPU0

--Chris


-- Ian


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

clean update 12.2 > 13.0

[Chris]

Wow.. Best update I have done in years. At least for me 12.2 > 13.0 was 
great.  Great job !

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

clean update 12.2 > 13.0

[Chris]

Wow.. Best update I have done in years. At least for me 12.2 > 13.0 was 
great.  Great job !


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-14 19:28, Andy Farkas wrote:

I think this is an excellent start. My shopping list includes:

- remove ftp(1)
- remove ftpd(8)
- remove telnet(1)
- remove telnetd(8)
- remove ftp:// and http:// from libfetch. This is 2021 and we should all
use https://.
- replace DNS lookups with DoH and/or DoT. Why let your ISP see your DNS
traffic?



I wonder how many people use YP/NIS (man 8 yp)?
It's a nifty concept; I played around with it last century...
I believe there is still an open PR in bugzilla I created (can't find it
right now, used a diffent email address back then, although same
username).

LOL I did the same a year or so ago. I felt much the same as you describe.
But I've since discovered it can be leveraged in ways that it did not
originally intend to do. So I've since decided that given in whole
it's small footprint, along with a proven track record. It has value
enough that it ought to remain.


Removing it from base (if it should be done at all) looks very complicated
and therefore creating a port equally so.

I know this topic (removing ftpd) is closed, so perhaps this should be
a new one (removing YP/NIS)?  ie. no development on yp has been
done for over a decade.

My view: remove neither

I concur. :-)



-andyf

--Chris



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: using interface groups in pf tables stopped working in 13.0-RELEASE

[Chris]

On 2021-04-14 11:04, Chris wrote:

On 2021-04-14 10:44, Peter Ankerstål wrote:

const { trusted:network mgmt:network dmz:network

guest:network edmz:network \
   admin:network iot:network client:network }
If I reload the configuration I get the following:
# pfctl -f /etc/pf.conf
/etc/pf.conf:12: cannot create address buffer: Invalid argument
pfctl: Syntax error in config file: pf rules not loaded

Some changes in the pf source have been made over the last couple
of months. The error returned appears to be related. It appears
that your running into a table size/count and memory allocation
related error. The first change moved/changed memory allocation to
kernel space, requiring one to increase allocation via loader.conf(5).
It was recently moved back to userspace allowing one to make changes
to a running system via sysctl.conf(5) or the commandline.
IOW if your on the recent change you should be able to simply
increase your table count by executing something like:
# echo "set limit table-entries " | pfctl -m -f -
OTOH if your stuck with the change in kernelspace, increase
net.pf.request_maxcount=
by some amount in loader.conf(5). If you are on the newer userspace
change, you can issue the sysctl(8) command at your terminal for
net.pf.request_maxcount=
as well.


I dont think so. Everything works normally if I switch from group name to 
interface name

in the config.
Sure. I only mentioned it because 1) the error you received looked almost 
exactly
the same as the one I encountered after the (pf source) changes, 2) alot of 
work

has been done recently (as I mentioned above). :-)
I'll defer to kp@ (Kristof Provost) for more insightful possibilities. As 
he's done

most all the recent work. :-)

--Chris

CC'ing pf@ for better coverage of your problem.



It seems to me that pf for some reason changed how it interprets group 
names

differently from
12.2-RELEASE-p4 and 13.0-RELEASE.

I dont really get how "anchor in from trusted:network” can resolve to 
"anchor in inet6 all”


/Peter.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: using interface groups in pf tables stopped working in 13.0-RELEASE

[Chris]

On 2021-04-14 10:44, Peter Ankerstål wrote:

const { trusted:network mgmt:network dmz:network

guest:network edmz:network \
   admin:network iot:network client:network }
If I reload the configuration I get the following:
# pfctl -f /etc/pf.conf
/etc/pf.conf:12: cannot create address buffer: Invalid argument
pfctl: Syntax error in config file: pf rules not loaded

Some changes in the pf source have been made over the last couple
of months. The error returned appears to be related. It appears
that your running into a table size/count and memory allocation
related error. The first change moved/changed memory allocation to
kernel space, requiring one to increase allocation via loader.conf(5).
It was recently moved back to userspace allowing one to make changes
to a running system via sysctl.conf(5) or the commandline.
IOW if your on the recent change you should be able to simply
increase your table count by executing something like:
# echo "set limit table-entries " | pfctl -m -f -
OTOH if your stuck with the change in kernelspace, increase
net.pf.request_maxcount=
by some amount in loader.conf(5). If you are on the newer userspace
change, you can issue the sysctl(8) command at your terminal for
net.pf.request_maxcount=
as well.


I dont think so. Everything works normally if I switch from group name to 
interface name

in the config.
Sure. I only mentioned it because 1) the error you received looked almost 
exactly
the same as the one I encountered after the (pf source) changes, 2) alot of 
work

has been done recently (as I mentioned above). :-)
I'll defer to kp@ (Kristof Provost) for more insightful possibilities. As 
he's done

most all the recent work. :-)

--Chris


It seems to me that pf for some reason changed how it interprets group names
differently from
12.2-RELEASE-p4 and 13.0-RELEASE.

I dont really get how "anchor in from trusted:network” can resolve to 
"anchor in inet6 all”


/Peter.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: using interface groups in pf tables stopped working in 13.0-RELEASE

[Chris]

On 2021-04-14 07:16, Peter Ankerstål wrote:

In pf I use the interface group syntax alot to make the configuration more
readable. All interfaces are assigned to a group representing its use/vlan 
name.


For example:

ifconfig_igb1_102="172.22.0.1/24 group iot description 'iot vlan' up"
ifconfig_igb1_102_ipv6="inet6 2001:470:de59:22::1/64"

ifconfig_igb1_300="172.26.0.1/24 group mgmt description 'mgmt vlan’ up"
ifconfig_igb1_300_ipv6="inet6 2001:470:de59:26::1/64”

in pf.conf I use these group names all over the place. But since I upgraded 
to
13.0-RELEASE it no longer works to define a table using the :network syntax 
and

interface groups:

tableconst { trusted:network mgmt:network dmz:network
guest:network edmz:network \
admin:network iot:network client:network }

If I reload the configuration I get the following:
# pfctl -f /etc/pf.conf
/etc/pf.conf:12: cannot create address buffer: Invalid argument
pfctl: Syntax error in config file: pf rules not loaded

Some changes in the pf source have been made over the last couple
of months. The error returned appears to be related. It appears
that your running into a table size/count and memory allocation
related error. The first change moved/changed memory allocation to
kernel space, requiring one to increase allocation via loader.conf(5).
It was recently moved back to userspace allowing one to make changes
to a running system via sysctl.conf(5) or the commandline.
IOW if your on the recent change you should be able to simply
increase your table count by executing something like:
# echo "set limit table-entries " | pfctl -m -f -
OTOH if your stuck with the change in kernelspace, increase
net.pf.request_maxcount=
by some amount in loader.conf(5). If you are on the newer userspace
change, you can issue the sysctl(8) command at your terminal for
net.pf.request_maxcount=
as well.

HTH

--Chris


I have tried to use just one network, double check the interface group 
setting and

so on, but with no luck.

to use actual interface works just fine:

table{ igb1.300:network }

but using the group fails:

# ifconfig -g mgmt
igb1.300

table{ mgmt:network }

# pfctl -f /etc/pf.conf
/etc/pf.conf:12: cannot create address buffer: Invalid argument
pfctl: Syntax error in config file: pf rules not loaded

Any ideas?

Thanks!

/Peter.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-07 23:27, aventa...@fastmail.fm wrote:
I think folks have different definitions of what an operating system should 
be.

Agreed.


An Operating System (OS) is an interface between a computer user and 
computer
hardware. An operating system is a software which performs all the basic 
tasks
like file management, memory management, process management, handling input 
and

output, and controlling peripheral devices such as disk drives and printers.

If you add or take away from the above definition, then there is your 
misunderstanding.
IMHO many refer to Linux as an Operating System. When in fact it is a Kernel. 
Which

is also what you describe above.
OTOH, UNIX as an OS has a defined set of commands available, as well as 
servers to

facilitate running a fully installed server. Which is what I believe he was
referring to.

At this point I think this thread is becoming tiresome. ;-)

--Chris


Best Regards,
Vic Thacker


On Wed, Apr 7, 2021, at 21:17, tech-lists wrote:

Hi, I'm a bit late to the discussion

On Mon, Apr 05, 2021 at 07:44:59AM -0700, Cy Schubert wrote:

>I think this is an excellent start. My shopping list includes:
>
>- remove ftp(1)
>- remove ftpd(8)
>- remove telnet(1)
>- remove telnetd(8)
>- remove ftp:// and http:// from libfetch. This is 2021 and we should all
>use https://.
>- replace DNS lookups with DoH and/or DoT. Why let your ISP see your DNS
>traffic?

Very firmly against this, and this sort of thing, for the following 
reasons:


1. I want an OS, not a kernel. If I just want a kernel, then why not go
with linux? FreeBSD is meant to be, I think, (generally), a server OS.
So, would you agree that it needs the ability to have server protocols
easily configured, with a minimum of fuss, without packages?

2. a lot of infrastructure depends on ftpd. it's easy to configure
securely ftpd in base.

3. there are some networks, like internal ones, where encryption is not
a requirement, or appropriate.

4. there are some places where encryption is in fact illegal.

>Personally, I'd suggest we remove the ftpd server *AND* ftp client and rely
>on ports. Having worked on UNIX, Internet security, and firewalls over the
>last 3/5 of my almost 50 year career, I have lamented the existence of the
>FTP protocol back in 1995 and I hate the FTP protocol with greater a
>passion today. Let's simply remove all vestiges of FTP from the base
>system, including libfetch, sooner than later. We don't need it now that we
>have HTTPS and POST; and sftp.

5. some services commonly don't use https. Lots of internet radio
stations don't. If https is enforced then the user will have to jump
through more hoops than they already do in order to, in this case,
listen to internet radio. Or face a loss of functionality.

6. not everywhere will have constant internet access. Not everyone will
want to use pkgs or have space for the ports tree.

>I think we should make it our goal to remove any and all unencrypted
>protocols from FreeBSD by 2025.

I think you should carefully think of the consequences of removing
functionality in the default install. It will make it less useful, not
more.
--
J.

Attachments:
* signature.asc

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-05 13:43, Ed Maste wrote:

On Sat, 3 Apr 2021 at 16:39, Ed Maste  wrote:


I propose deprecating the ftpd currently included in the base system
before FreeBSD 14, and opened review D26447
(https://reviews.freebsd.org/D26447) to add a notice to the man page.


I posted this as a proposal for community feedback, and there's
clearly a strong objection to removing the base system ftpd. So, I'm
not going to pursue this any further.

I like to take the time to extend a massive _Thank You_ for your
chosen course for handling this. I'm also grateful for it's outcome. :-)

Thanks!

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-05 12:01, Patrick M. Hausen wrote:

Hi all,


Am 03.04.2021 um 22:39 schrieb Ed Maste :
I'm happy to make a port for it if anyone needs it. Comments?


A bit late to the party, but my take is: please just don't.

I absolutely freaked out when Apple removed the telnet and ftp clients
from Mac OS and I needed to reinstall them via MacPorts.

That route uses an inferior (opinion) version of ftp(1) && ftpd(8).
It might interest you to know that the FreeBSD versions that (currently)
already come with FreeBSD can be copied over to your Mac. I *too*
became upset when I found MacOS w/o these, and on a hunch tried it,
and worked as intended/expected. The FreeBSD version(s) are more
"featurefull" than those that originally came on the Mac, or the GNU
one that is supplied w/MacPorts.



People who manage any larger collection of networking gear *depend*
on these outdated but simple services. Client and server side alike.

TFTP is not going away, neither is FTP. I'm dead serious. Remote media
via Supermicro IPMI in 2021? SMB1. Firmware updates for my UPS? FTP.
Scanner/printer/fax all-in-one thingy? Uploads received fax transmissions
via FTP. PBX? Uploads usage reports via FTP. This stuff is here to stay.
In local networks, of course.

But still even on "the Internet", FTP is the most used method for customers
of static website hosting. You cannot teach these people what an SSH key is.
Just my experience, but backed by a load of customer interactions over more
than 20 years ...

Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

--Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-05 11:27, Roger Leigh wrote:

On 3 Apr 2021, at 22:21, Eugene Grosbein  wrote:


04.04.2021 3:39, Ed Maste wrote:


I propose deprecating the ftpd currently included in the base system
before FreeBSD 14, and opened review D26447
(https://reviews.freebsd.org/D26447) to add a notice to the man page.
I had originally planned to try to do this before 13.0, but it dropped
off my list. FTP is not nearly as relevant now as it once was, and it
had a security vulnerability that secteam had to address.

I'm happy to make a port for it if anyone needs it. Comments?


I'm strongly against remove of stock ftpd. FTP is fastest protocol for both 
testing
and daily file transfer for trusted isolated segments, and even for WAN 
wrapped in IPSec.


Our stock ftpd has very short backlog of security issues comparing with 
other FTP server implementations,

mostly linked with libc or other libraries and not with ftpd code itself.

Please don't fix what ain't broken. Please.


How would you draw the line between something that must be part of the base 
system
vs. something that would be better off as part of the ports tree?  What bar 
should

ftpd have to meet to warrant remaining in base vs moving to ports?

Personally, I’ve never enabled it nor had any desire to.  FTP is, at this 
point in
time, thoroughly obsolescent, and I cannot imagine that it is something that 
most
people enable, if they are even aware of its existence.  Why can’t it simply 
be

installed from the ports for the occasional user who still requires it?  Why
should the base system contain obsolete stuff that few people will use?  
Surely

the ports tree serves this need better?

Can I ask, for those who do enable it, why isn’t “sftp” acceptable (or 
“scp”)?
Sure. Because it's part of a one-time task. It might be part of a server 
setup. Or
might a task that must be done on thousands of machines. It needs to be 
available
out-of-the-box, and needs no overhead for setup (key exchange, config, 
etc...).

This scenario may also be on machines w/o any external sources/packages. IOW
everything should be available out of the box, with little to no additional
setup overhead. ftp(1), and ftpd(8) provide everything required at no 
additional

cost. :-)

Both provide a similar function, securely, which also works with a basic
installation without any ports.  SSHFXP, the protocol underlying sftp is 
better
specified, less ambiguous and more fault tolerant and safe than the FTP 
protocol

ever was.  The client is better than most ftp clients, and the server
(/usr/libexec/sftp-server) is started on demand on a per-connection basis.  
What
makes FTP more desirable than a service over SSH which is (from a technical 
and

usability point of view) a better FTP than FTP ever was?

Kind regards,
Roger


--Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-05 07:44, Cy Schubert wrote:

In message 
, Ed Maste writes:

I propose deprecating the ftpd currently included in the base system
before FreeBSD 14, and opened review D26447
(https://reviews.freebsd.org/D26447) to add a notice to the man page.
I had originally planned to try to do this before 13.0, but it dropped
off my list. FTP is not nearly as relevant now as it once was, and it
had a security vulnerability that secteam had to address.


I think this is an excellent start. My shopping list includes:

- remove ftp(1)
- remove ftpd(8)
- remove telnet(1)
- remove telnetd(8)
- remove ftp:// and http:// from libfetch. This is 2021 and we should all
use https://.
- replace DNS lookups with DoH and/or DoT. Why let your ISP see your DNS
traffic?

You've clearly never worked on extremely large networks. Or at least not
considered them in this statement -- think LAN/intranet in large corporate
settings. ftp(1) as well as ftpd(8) are lightweight, and utilitarian. It's
because of this that gives them such great value. They require nothing to
use. They just work with no setup required. With very little setup you can
manage something a little more sophisticated. I can easily script ftp for
complex situations needing nothing more than sh(1) and ftp(1), and it's all
available right-out-of-the-box. This isn't true of the others.
In an internet public facing scenario. It's enough to utilize one specific
line in inetd(8) and 2 in hosts.allow(2). This simplicity and lack of
overhead is not available with the other options.

Because something is old and un-featured does not make it valueless.





I'm happy to make a port for it if anyone needs it. Comments?

A port would be a nice option. But it should remain an option; as in
one _should_ be allowed to get ftp || ftpd out of the box if they so
choose.



I've started working on splitting ftp and ftpd into an external git repo.
The problem I've encountered is that though only ftp and ftpd are left the
resultant repo is still 1.2 GB. If my last attempt fails, there is a choice
between a 1.2 GB repo and burning ftp forever then the choice is clear:
burn it forever.

Adding the following as an option:

Also note that the tnftp ports are the NetBSD ftp and ftpd. The FreeBSD ftp
and ftpd are simply copies of tnftp and tnfpd. Would it make more sense to
share our customizations with NetBSD and we simply reply on NetBSD for the
client and server in our ports? This last option might be simpler than
creating a port.

Personally, I'd suggest we remove the ftpd server *AND* ftp client and rely
on ports. Having worked on UNIX, Internet security, and firewalls over the
last 3/5 of my almost 50 year career, I have lamented the existence of the
FTP protocol back in 1995 and I hate the FTP protocol with greater a
passion today. Let's simply remove all vestiges of FTP from the base
system, including libfetch, sooner than later. We don't need it now that we
have HTTPS and POST; and sftp.

This assumes your willing to expend all the time and overhead to setup a web
server for a simple but absolutely mandatory one time task. When none of the
boxes you're working on are slated for or perhaps are even capable of running
as much. I (or anyone) should be able to have a FULLY functional system 
WITHOUT

the need to get additional sources to build additional functionality -- this
ain't Linux.



I think we should make it our goal to remove any and all unencrypted
protocols from FreeBSD by 2025.

Not everyone works exclusively "in the wild". Many also work within safe
environments, where such things, while nice, are unnecessary.

--Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-04 12:10, Ian Lepore wrote:

On Sat, 2021-04-03 at 16:39 -0400, Ed Maste wrote:

I propose deprecating the ftpd currently included in the base system
before FreeBSD 14, and opened review D26447
(https://reviews.freebsd.org/D26447) to add a notice to the man page.
I had originally planned to try to do this before 13.0, but it
dropped
off my list. FTP is not nearly as relevant now as it once was, and it
had a security vulnerability that secteam had to address.

I'm happy to make a port for it if anyone needs it. Comments?



I would find the removal of ftpd to be very inconvenient unless there
was a port/pkg to install it from.

If there is a port, it would only be useful if I could set PREFIX=/usr
when building/installing it, so that its behavior when installed as a
port/pkg would be identical to how it was when it was part of base (in
terms of where its config files are located).

I like the sound of that. Except that I'd like to do it one better and
suggest something along the lines of PORTS_MODULES in make.conf(5).
Maybe
PORTS_DAEMONS= ftpd sshd rpcbind nfsd ypbind inetd etc...

That might make it a tenable for situation for everyone. ;-)

--Chris


-- Ian

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Deprecating base system ftpd?

[Chris]

On 2021-04-03 13:45, Warner Losh wrote:

On Sat, Apr 3, 2021 at 2:40 PM Ed Maste  wrote:


I propose deprecating the ftpd currently included in the base system
before FreeBSD 14, and opened review D26447
(https://reviews.freebsd.org/D26447) to add a notice to the man page.
I had originally planned to try to do this before 13.0, but it dropped
off my list. FTP is not nearly as relevant now as it once was, and it
had a security vulnerability that secteam had to address.

I *strongly* object. MacOS also did this. Which made me discover that I
could simply copy my already built FreeBSD version over to all my MacOS
laptops and now enjoy an even better version than had previously existed.
This fact has made my use and need for FreeBSD' ftp even more important.
It has also made FreeBSD more popular with the Mac folks.
I depend upon ftp(1) && ftpd(8). I have on FreeBSD, for as many years as
FreeBSD has existed. I find the ssh and related ports are probed and
hammered on constantly. Whereas the ftp ports are quite rare by comparison.
So keeping sshd(8) and friends ports closed removes overhead. I have no
difficulty managing ftpd(8) via inet(8) && hosts.allow(5). Ftp && ftpd
are both trivial programs and should not be considered for removal.
If the reason for their suggested removal is "development overhead".
Please allow me to maintain both. I will happily assume full
responsibility for them.

Thank you for listening. :-)

--Chris


I'm happy to make a port for it if anyone needs it. Comments?



I already use one of the ports ftpd's for my needs, so this is fine by me.
I'm agnostic about whether we need a port for what was in base, but suspect
that's likely the path of least resistance.

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

[Chris]

On 2021-03-26 07:22, Ed Maste wrote:

On Thu, 25 Mar 2021 at 15:09, Chris  wrote:


I can only state that I use it only occasionally, and that when I do. I
have had no problems with it. I'm glad that it's there when I need it.


Thanks for the reply. Can you comment on your use cases - in
particular, did you use mirror, stripe, or raid5? If the first two
then gmirror, gconcat, gstripe, and/or graid are suitable
replacements.

Thank you for the reply. :-)
Sure. My only needs have been for:
gstripe gmirror or gconcat.


I'm not looking to deprecate it just because it's old, but because of
a mismatch between user and developer expectations about its
stability.

Sure. I understand. Thanks for mentioning it.

--Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

[Chris]

On 2021-03-25 10:25, Ed Maste wrote:

Vinum is a Logical Volume Manager that was introduced in FreeBSD 3.0,
and for FreeBSD 5 was ported to geom(4) as gvinum. gvinum has had no
specific development at least as far back as 2010 and it is not clear
how well it works today. There are open PRs with reports of panics
upon removing disks, etc. And, it also imposes an ongoing cost as it
must be updated when other work is done (such as the recent MAXPHYS
work). I suspect that by now all users have migrated to either
graid(8) or ZFS.

I plan to add a deprecation notice after a short discussion period,
assuming no reasonable justification is made to retain it. The notice
would suggest graid and ZFS as alternatives, and would be merged in
advance of FreeBSD 13.1. Then, gvinum would be removed in advance of
FreeBSD 14.0.

Please follow up if you have experience or input on vinum in FreeBSD,
including past use but especially if you are still using it today and
expect to continue doing so.

I can only state that I use it only occasionally, and that when I do. I
have had no problems with it. I'm glad that it's there when I need it.
Further; I find it easier to setup and use, as compared to the
alternatives. It is also "lighter" than the alternatives.
While it wouldn't be "the end of the world" if it disappeared. I'm
really glad it's there.

--Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: When did pkg(8) drop support for 12-stable?

[Chris]

On 2021-02-23 19:30, Mark Millard via freebsd-stable wrote:

On 2021-Feb-23, at 18:08, Chris  wrote:


On 2021-02-23 17:42, Mark Millard wrote:

(Warner is only CC'd here.)
Warner Losh imp at bsdimp.com wrote on
Wed Feb 24 01:04:13 UTC 2021 :

On Tue, Feb 23, 2021, 4:51 PM Chris  wrote:
> Given this is a pkg(8) error, I brought it up on ports@
> but it was suggested I (also?) bring it up here on stable@
>
> OK awhile back I installed a copy of 12 stable from the
> usb stick image. I tweaked it to my wishes then got called
> away and haven't been able to get back to it until the other
> day. This is still a fresh install which has a populated /usr/src.
> So I
> svnlite co svn://svn.freebsd.org/ports/head /usr/ports
> followed by a
> cd /usr/ports/ports-mgmt/pkg/ && make install clean
> which returns
> make
> /!\ ERROR: /!\
>
> Ports Collection support for your FreeBSD version has ended, and no ports
> are
> guaranteed to build on this syst
em. Please upgrade to a supported release.
>
> No support will be provided if you silence this message by defining
> ALLOW_UNSUPPORTED_SYSTEM.
>
> *** Error code 1
>
> Stop.
> Err what? Ok while I think this was from stable 12.1, it's still still 12,
> and it's on stable. So what gives?
>
12.1 has reached EOL now that 12.2 has been out a while.
From release/12.1.0/ :

"Tag releng/12.1@r354233 as release/12.1.0 (12.1-RELEASE)"
I think that implicit in Warner's response is that
versions of stable/12/ that are not after r354233 are
also EOL. One needs to have stable/12/ material from
after -r354233 in order for it to be supported.
He might even mean that stable/12/ material from before:
"Tag releng/12.2@r366954 as release/12.2.0 (12.2-RELEASE)"
would also be considered as not supported.
To be safe you should be using stable/12/ material from
on or after -r366954 in order to have a supported
context.
(I'm not sure if anything is explicit about the status
of stable/12/ material between releng/12.1@r354233
and releng/12.2@r366954 .)

A HUGE thanks for all of this, Mark. This is EXACTLY what I needed.

# uname -apKU
FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC  amd64 
amd64 1201522 1201522

which pretty well confirms what you deduced.
I'm still a bit confused. It seems to me that it didn't _used_
to be that way. But my brain isn't using ECC. So a couple of
bits may be flipped.


The implication of all of stable/12/ being supported
would be support of stable/12/ from on or after its
creation:

QUOTE
Revision 339434 - Directory Listing
Modified Fri Oct 19 00:09:24 2018 UTC (2 years, 4 months ago) by gjb
Copied from: head revision 339432
Copy head@r339432
 to stable/12 as part of the 12.0-RELEASE cycle.

Additional post-branch commits will follow.
END QUOTE

Such does not seem likely to me. What would be the
point of dropping 12.0-RELEASE support and
12.1-RELEASE support if such stable/12/ history was
covered, some of that history being minor variations
on the 12.0-RELEASE or 12.1-RELEASE ?

Note:
Despite some claims in other messages, svn -r363918
is not 12.1-RELEASE ( not -r354233 ) and -r363918
is shown as (only) in stable/12/ by svn. Your
claim of 12-STABLE was correct, just not detailed
enough.

Thanks. I really appreciate your taking the time to
clear things up for me. It also seems clear that I've
somehow mixed the purpose of RELEASE vs STABLE. :-/

Thanks again, Mark!

--Chris



===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: When did pkg(8) drop support for 12-stable?

[Chris]

On 2021-02-23 17:42, Mark Millard wrote:

(Warner is only CC'd here.)

Warner Losh imp at bsdimp.com wrote on
Wed Feb 24 01:04:13 UTC 2021 :


On Tue, Feb 23, 2021, 4:51 PM Chris  wrote:

> Given this is a pkg(8) error, I brought it up on ports@
> but it was suggested I (also?) bring it up here on stable@
>
> OK awhile back I installed a copy of 12 stable from the
> usb stick image. I tweaked it to my wishes then got called
> away and haven't been able to get back to it until the other
> day. This is still a fresh install which has a populated /usr/src.
> So I
> svnlite co svn://svn.freebsd.org/ports/head /usr/ports
> followed by a
> cd /usr/ports/ports-mgmt/pkg/ && make install clean
> which returns
> make
> /!\ ERROR: /!\
>
> Ports Collection support for your FreeBSD version has ended, and no ports
> are
> guaranteed to build on this syst
em. Please upgrade to a supported release.
>
> No support will be provided if you silence this message by defining
> ALLOW_UNSUPPORTED_SYSTEM.
>
> *** Error code 1
>
> Stop.
> Err what? Ok while I think this was from stable 12.1, it's still still 12,
> and it's on stable. So what gives?
>

12.1 has reached EOL now that 12.2 has been out a while.



From release/12.1.0/ :


"Tag releng/12.1@r354233 as release/12.1.0 (12.1-RELEASE)"

I think that implicit in Warner's response is that
versions of stable/12/ that are not after r354233 are
also EOL. One needs to have stable/12/ material from
after -r354233 in order for it to be supported.

He might even mean that stable/12/ material from before:

"Tag releng/12.2@r366954 as release/12.2.0 (12.2-RELEASE)"

would also be considered as not supported.

To be safe you should be using stable/12/ material from
on or after -r366954 in order to have a supported
context.

(I'm not sure if anything is explicit about the status
of stable/12/ material between releng/12.1@r354233
and releng/12.2@r366954 .)

A HUGE thanks for all of this, Mark. This is EXACTLY what I needed.

# uname -apKU
FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC  amd64 
amd64 1201522 1201522

which pretty well confirms what you deduced.
I'm still a bit confused. It seems to me that it didn't _used_
to be that way. But my brain isn't using ECC. So a couple of
bits may be flipped.



Since you did not provide the output from the
likes of "uname -apKU" (or some rough equivalent)
I've no direct clue which version you were trying.
But you should be able to compare to the above to
see which range the material is from.


Thanks again!

--Chris


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: When did pkg(8) drop support for 12-stable?

[Chris]

On 2021-02-23 17:07, Brian W. wrote:

12-stable is not what you're running if you got that error.

# uname -apKU
FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC  amd64 
amd64 1201522 1201522

Looks pretty STABLE to me.

--Chris

Run freebsd-update with appropriate args to get to a later release is the
easiest option.

Brian

On Tue, Feb 23, 2021, 5:04 PM Warner Losh  wrote:


On Tue, Feb 23, 2021, 4:51 PM Chris  wrote:

> Given this is a pkg(8) error, I brought it up on ports@
> but it was suggested I (also?) bring it up here on stable@
>
> OK awhile back I installed a copy of 12 stable from the
> usb stick image. I tweaked it to my wishes then got called
> away and haven't been able to get back to it until the other
> day. This is still a fresh install which has a populated /usr/src.
> So I
> svnlite co svn://svn.freebsd.org/ports/head /usr/ports
> followed by a
> cd /usr/ports/ports-mgmt/pkg/ && make install clean
> which returns
> make
> /!\ ERROR: /!\
>
> Ports Collection support for your FreeBSD version has ended, and no ports
> are
> guaranteed to build on this system. Please upgrade to a supported
release.
>
> No support will be provided if you silence this message by defining
> ALLOW_UNSUPPORTED_SYSTEM.
>
> *** Error code 1
>
> Stop.
> Err what? Ok while I think this was from stable 12.1, it's still still
12,
> and it's on stable. So what gives?
>

12.1 has reached EOL now that 12.2 has been out a while.

Warner

Thanks in advance for any enlightenment.
>
> --Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

When did pkg(8) drop support for 12-stable?

[Chris]

Given this is a pkg(8) error, I brought it up on ports@
but it was suggested I (also?) bring it up here on stable@

OK awhile back I installed a copy of 12 stable from the
usb stick image. I tweaked it to my wishes then got called
away and haven't been able to get back to it until the other
day. This is still a fresh install which has a populated /usr/src.
So I
svnlite co svn://svn.freebsd.org/ports/head /usr/ports
followed by a
cd /usr/ports/ports-mgmt/pkg/ && make install clean
which returns
make
/!\ ERROR: /!\

Ports Collection support for your FreeBSD version has ended, and no ports are
guaranteed to build on this system. Please upgrade to a supported release.

No support will be provided if you silence this message by defining
ALLOW_UNSUPPORTED_SYSTEM.

*** Error code 1

Stop.
Err what? Ok while I think this was from stable 12.1, it's still still 12,
and it's on stable. So what gives?

Thanks in advance for any enlightenment.

--Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: lots of "no such file or directory" errors in zfs filesystem

[Chris Anderson]

On Tue, Feb 23, 2021 at 4:53 AM Andriy Gapon  wrote:

> On 23/02/2021 05:25, Chris Anderson wrote:
> > so I can't ls -i the file since that triggers the no such file warning.
> if I run
> > zdb - on the inode of a directory which contains one of those
> missing files,
> > I can get the inode of the file from that, but I don't get anything
> particularly
> > interesting in the output.
> >
> > most of the files that are missing are in directories with a large
> number of
> > files (the largest has 180k) but I managed to find a directory which had
> a
> > single file entry that is missing:
> >
> > Dataset tank/home/cva [ZPL], ID 196, cr_txg 163, 109G, 908537 objects,
> rootbp
> > DVA[0]=<0:13210311000:1000> DVA[1]=<0:18b9a02c000:1000> [L0 DMU objset]
> > fletcher4 uncompressed LE contiguous unique double size=800L/800P
> > birth=46916371L/46916371P fill=908537
> > cksum=11fdd21d1d:13cb24c87a6e:da0c9bf1b5df3:715ab2ec45b7b09
> >
> >
> > Object  lvl   iblk   dblk  dsize  dnsize  lsize   %full  type
> >
> >  382681   128K 1K  0512 1K  100.00  ZFS directory
> >
> >264   bonus  ZFS znode
> >
> > dnode flags: USED_BYTES USERUSED_ACCOUNTED
> >
> > dnode maxblkid: 0
> >
> > uid 1001
> >
> > gid 1001
> >
> > atime   Sun Aug  6 02:00:41 2017
> >
> > mtime   Wed Apr 15 12:12:42 2020
> >
> > ctime   Wed Apr 15 12:12:42 2020
> >
> > crtime  Sat Aug  5 15:10:07 2017
> >
> > gen 23881023
> >
> > mode40755
> >
> > size3
> >
> > parent  38176
> >
> > links   2
> >
> > pflags  4080144
> >
> > xattr   0
> >
> > rdev0x
> >
> > microzap: 1024 bytes, 1 entries
> >
> >
> >
> > hash_test.go = 38274 (type: Regular File)
> >
> >
> > # zdb - tank/home/cva 38274
> >
> > Dataset tank/home/cva [ZPL], ID 196, cr_txg 163, 109G, 908537 objects,
> rootbp
> > DVA[0]=<0:13210311000:1000> DVA[1]=<0:18b9a02c000:1000> [L0 DMU objset]
> > fletcher4 uncompressed LE contiguous unique double size=800L/800P
> > birth=46916371L/46916371P fill=908537
> > cksum=11fdd21d1d:13cb24c87a6e:da0c9bf1b5df3:715ab2ec45b7b09
> >
> >
> > Object  lvl   iblk   dblk  dsize  dnsize  lsize   %full  type
> >
> > zdb: dmu_bonus_hold(38274) failed, errno 2
>
> So, this looks like a "simple" problem.
> Unfortunately, it is very hard to tell retrospectively what bug caused it.
> The directory has an entry for the file, but the file does not actually
> exist
> (or has a different ID).
> This is a logical inconsistency, not a data integrity issue.
> So, a scrub, being a data integrity check, would not detect such an issue.
> Hypothetical zfs_fsck is needed to find and repair such logical problems.
>

ah, I see. that makes sense.


> Does that pool and filesystem have any special history?
> I mean upgrades, replication via send/recv, moving between OS-s, etc.
>

nope, it led a pretty boring life. that zfs filesystem was created on that
server and has been on the same two mirrored disks for its lifetime. it has
had freebsd upgrades applied as they became available. zfs upgrades were
for the most part avoided until quite recently (though the problem existed
prior to the upgrades) the server does have a relatively modest amount of
ram (2GB). dunno if that makes it more likely that these kinds of issues
get triggered.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: lots of "no such file or directory" errors in zfs filesystem

[Chris Anderson]

On Mon, Feb 22, 2021 at 9:13 AM Andriy Gapon  wrote:

> On 22/02/2021 16:20, Chris Anderson wrote:
> > On Mon, Feb 22, 2021 at 1:36 AM Andriy Gapon  > <mailto:a...@freebsd.org>> wrote:
> >
> > On 22/02/2021 09:31, Chris Anderson wrote:
> > > None of these files are especially important to me, however I was
> wondering
> > > if there would be any benefit to the community from trying to
> debug this
> > > issue further to understand what might be going wrong.
> >
> > Yes.
> >
> >
> > Could you offer any guidance about what kind of debugging information I
> could
> > collect that would be of use?
>
> You can start with picking a single file that demonstrates the problem.
> Then,
> ls -li the-file
> zdb - file's-filesystem file's-inode-number
> The filesystem can be found out from df output, the inode number is in ls
> -li
> output -- if the command prints anything at all.
> If it does not, then do ls -lid on the file's directory and then zdb -
> for
> the directory's inode number.  In the output there should be the file name
> and
> its number (I think that it's in hex, but not sure).
>

so I can't ls -i the file since that triggers the no such file warning. if
I run zdb - on the inode of a directory which contains one of those
missing files, I can get the inode of the file from that, but I don't get
anything particularly interesting in the output.

most of the files that are missing are in directories with a large number
of files (the largest has 180k) but I managed to find a directory which had
a single file entry that is missing:

Dataset tank/home/cva [ZPL], ID 196, cr_txg 163, 109G, 908537 objects,
rootbp DVA[0]=<0:13210311000:1000> DVA[1]=<0:18b9a02c000:1000> [L0 DMU
objset] fletcher4 uncompressed LE contiguous unique double size=800L/800P
birth=46916371L/46916371P fill=908537
cksum=11fdd21d1d:13cb24c87a6e:da0c9bf1b5df3:715ab2ec45b7b09


Object  lvl   iblk   dblk  dsize  dnsize  lsize   %full  type

 382681   128K 1K  0512 1K  100.00  ZFS directory

   264   bonus  ZFS znode

dnode flags: USED_BYTES USERUSED_ACCOUNTED

dnode maxblkid: 0

uid 1001

gid 1001

atime   Sun Aug  6 02:00:41 2017

mtime   Wed Apr 15 12:12:42 2020

ctime   Wed Apr 15 12:12:42 2020

crtime  Sat Aug  5 15:10:07 2017

gen 23881023

mode40755

size3

parent  38176

links   2

pflags  4080144

xattr   0

rdev0x

microzap: 1024 bytes, 1 entries



hash_test.go = 38274 (type: Regular File)


# zdb - tank/home/cva 38274

Dataset tank/home/cva [ZPL], ID 196, cr_txg 163, 109G, 908537 objects,
rootbp DVA[0]=<0:13210311000:1000> DVA[1]=<0:18b9a02c000:1000> [L0 DMU
objset] fletcher4 uncompressed LE contiguous unique double size=800L/800P
birth=46916371L/46916371P fill=908537
cksum=11fdd21d1d:13cb24c87a6e:da0c9bf1b5df3:715ab2ec45b7b09


Object  lvl   iblk   dblk  dsize  dnsize  lsize   %full  type

zdb: dmu_bonus_hold(38274) failed, errno 2


>
> --
> Andriy Gapon
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: lots of "no such file or directory" errors in zfs filesystem

[Chris Anderson]

On Mon, Feb 22, 2021 at 1:36 AM Andriy Gapon  wrote:

> On 22/02/2021 09:31, Chris Anderson wrote:
> > None of these files are especially important to me, however I was
> wondering
> > if there would be any benefit to the community from trying to debug this
> > issue further to understand what might be going wrong.
>
> Yes.
>

Could you offer any guidance about what kind of debugging information I
could collect that would be of use?


>
> --
> Andriy Gapon
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

lots of "no such file or directory" errors in zfs filesystem

[Chris Anderson]

I'm in the process of decommissioning an old zfs based file server and I
noticed that around a dozen files with directory entries which fail with
"No such file or directory" when trying to read them.

I can't remember what the original version of freebsd installed was, but
it's been in production for at least 7 years and has been upgraded with
freebsd-update as new FreeBSD releases came available (it is currently on
12.2-RELEASE-p3).

The behavior is perplexing since I've never had any scrub failures on the
pool those files reside in yet from looking at old security run outputs,
the number of files in that state has increased over time.

None of these files are especially important to me, however I was wondering
if there would be any benefit to the community from trying to debug this
issue further to understand what might be going wrong.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How to handle the pack files now we have switched to git?

[Chris]

On 2021-01-05 03:08, Pete French wrote:
So, for me the switch to git went very smoothly. I havent moved to etcupdate 
yet,
but will probably do that soon. Hopwever I did hit one issue. What I do is 
to
build on a single machine, and then send that to a number of places using 
rsync.


But what seems to happen wuth git is that it has a big pack file of objects, 
and
the name of the opack file is the SHA1 of whatever is inside it. So if 
something
chnages then the filename chnages - and thus rsync tries to move the entire 
lot

all over again, even if the change is tiny.

Does anyone have a solution to this ? Currently I am telling rsync to ignore 
.git

when it sends the source, but am not entirely happy with that.

But apart from that, git works fine ;)

Brilliant minds think alike. I use nearly the same routine. ;-)
Have been doing so on svn(1) as well. FWIW the only difference between 
passing

the archive with vs without the .git. Is that getting the details of what rev
the source is at will not be available without the .git. Same on svn.
For me this is only a minor inconvenience. To help overcome this in the past.
I issued a 'svn info /usr/src >./SRC-REV'. Then simply passed that file along
to the receiving host(s).
OTOH it won't be (easily) possible to "up" the repo(s) from the receiving 
hosts

w/o the .git.

HTH

--Chris


-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: The spkr driver

[Chris]

On 2020-08-28 09:25, Warner Losh wrote:

Greetings,

I'd like to retire the spkr driver. It was a cute hack before sound cards
were ubiquitous, but it's not been kept up to date, and it's not clear that
it still works It is still Giant locked, and though it's not a huge
effort to do the locking I literally have no way to test it that I trust...

Is anybody using it these days for anything? If not, I'd propose we
de-orbit it before 13. If so, I need people to test patches to remove
Giant...

I still use it for important events, as alerts that something needs attention
on any one of my servers. It's easier to distinguish, and while many boards
include more complex sound. The speaker is "cheap" and easy to use.
I should be able to help test.

Thanks for the heads-up!

--Chris


Warner

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: net.pf.request_maxcount: UNDESIRABLE_OID

[Chris]

On Fri, 21 Aug 2020 08:56:12 +0200 Kristof Provost k...@freebsd.org said


On 21 Aug 2020, at 8:53, Chris wrote:
> On Fri, 21 Aug 2020 08:33:16 +0200 Kristof Provost k...@freebsd.org said
>
>> Hi Chris,
> Hello, Kristof. Thanks for the reply.
> Nice name BTW. ;-)
>>
>> On 21 Aug 2020, at 2:40, Chris wrote:
>> > We've been developing an appliance/server based on FreeBSD &&
>> > pf(4). We started some time ago, and have been using a very
>> > early version of 12. We're now collecting some 20,000,000
>> > IP's /mos. So we're satisfied we're close to releasing. As
>> > such, we needed to bring the release up to a supported
>> > (freebsd) version (12-STABLE). We would have done so sooner.
>> > But we need a stable (unchanging) testbed to evaluate what
>> > we're working on.
>> > We built and deployed a copy of 12-STABLE @r363918 that
>> > contained our work with pf(4). Booting into it failed
>> > unexpectedly with: cannot define table nets: too many
>> > elements. Consider increasing net.pf.request_maxcount.
>> > pfctl: Syntax error in config file: pf rules not loaded
>> > OK this didn't happen on our testbed prior to the upgrade
>> > with a combined count of ~97,000,900 IPs. In fact the OID
>> > mentioned didn't exist.
>> > For reference; our testbed provides DNS, www, mail for
>> > ~60 domains/hosts, as well as our pf(4) testing. We can
>> > happily load our tables, and run these services w/8Gb
>> > RAM.
>> > This OID is more a problem than a savior. Why not simply
>> > return ENOMEM?
>> >
>> To quote the commit message:
>>
>> pf ioctls frequently take a variable number of elements as 
>> argument. This can
>> potentially allow users to request very large allocations.  These 
>> will fail,
>> but even a failing M_NOWAIT might tie up resources and result in 
>> concurrent
>> M_WAITOK allocations entering vm_wait and inducing reclamation of 
>> caches.

>>
>> Limit these ioctls to what should be a reasonable value, but 
>> allow users to

>> tune it should they need to.
>>
>> Now that pf can be used in vnet jails there’s a possibility of an 
>> attacker using pf to deny service to other jails (or the host) by 
>> exhausting memory. Imposing limits on pf request sizes mitigates 
>> this.

> Hadn't considered vnet. Thanks for mentioning it.
> But why must it be a read-only OID?
>
It doesn’t have to be, and in CURRENT it’s not: 
https://svnweb.freebsd.org/base?view=revision=355744

That hasn’t been MFC’d for the excellent reason that I forgot.

Good news!


I’ll try to do that today, after I fix my dev-VM.

Hope it turns out to be an easy fix for you.

Thanks for all your time!


Best regards,
Kristof


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: net.pf.request_maxcount: UNDESIRABLE_OID

[Chris]

On Fri, 21 Aug 2020 08:33:16 +0200 Kristof Provost k...@freebsd.org said


Hi Chris,

Hello, Kristof. Thanks for the reply.
Nice name BTW. ;-)


On 21 Aug 2020, at 2:40, Chris wrote:
> We've been developing an appliance/server based on FreeBSD &&
> pf(4). We started some time ago, and have been using a very
> early version of 12. We're now collecting some 20,000,000
> IP's /mos. So we're satisfied we're close to releasing. As
> such, we needed to bring the release up to a supported
> (freebsd) version (12-STABLE). We would have done so sooner.
> But we need a stable (unchanging) testbed to evaluate what
> we're working on.
> We built and deployed a copy of 12-STABLE @r363918 that
> contained our work with pf(4). Booting into it failed
> unexpectedly with: cannot define table nets: too many
> elements. Consider increasing net.pf.request_maxcount.
> pfctl: Syntax error in config file: pf rules not loaded
> OK this didn't happen on our testbed prior to the upgrade
> with a combined count of ~97,000,900 IPs. In fact the OID
> mentioned didn't exist.
> For reference; our testbed provides DNS, www, mail for
> ~60 domains/hosts, as well as our pf(4) testing. We can
> happily load our tables, and run these services w/8Gb
> RAM.
> This OID is more a problem than a savior. Why not simply
> return ENOMEM?
>
To quote the commit message:

pf ioctls frequently take a variable number of elements as 
argument. This can
potentially allow users to request very large allocations.  These 
will fail,
but even a failing M_NOWAIT might tie up resources and result in 
concurrent
M_WAITOK allocations entering vm_wait and inducing reclamation of 
caches.


Limit these ioctls to what should be a reasonable value, but allow 
users to

tune it should they need to.

Now that pf can be used in vnet jails there’s a possibility of an 
attacker using pf to deny service to other jails (or the host) by 
exhausting memory. Imposing limits on pf request sizes mitigates this.

Hadn't considered vnet. Thanks for mentioning it.
But why must it be a read-only OID?



> Isn't that what it used to do? pf.conf(5)
> already facilitates thresholds, and they aren't _read
> only_. Is there any way to turn this OID off; like using
> a -1 value? Or will we need to simply back out the commit?
>
You can functionally disable it by setting a very large value. Try 
setting 4294967295.

Thanks. When I was confronted with the message. I simply chose an
arbitrarily high number of 8. Which allowed the tables to load.
But I felt I should look closer into this for a better understanding. :-)
Thank you very much for taking the time to reply!



Best regards,
Kristof


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

net.pf.request_maxcount: UNDESIRABLE_OID

[Chris]

We've been developing an appliance/server based on FreeBSD &&
pf(4). We started some time ago, and have been using a very
early version of 12. We're now collecting some 20,000,000
IP's /mos. So we're satisfied we're close to releasing. As
such, we needed to bring the release up to a supported
(freebsd) version (12-STABLE). We would have done so sooner.
But we need a stable (unchanging) testbed to evaluate what
we're working on.
We built and deployed a copy of 12-STABLE @r363918 that
contained our work with pf(4). Booting into it failed
unexpectedly with: cannot define table nets: too many
elements. Consider increasing net.pf.request_maxcount.
pfctl: Syntax error in config file: pf rules not loaded
OK this didn't happen on our testbed prior to the upgrade
with a combined count of ~97,000,900 IPs. In fact the OID
mentioned didn't exist.
For reference; our testbed provides DNS, www, mail for
~60 domains/hosts, as well as our pf(4) testing. We can
happily load our tables, and run these services w/8Gb
RAM.
This OID is more a problem than a savior. Why not simply
return ENOMEM? Isn't that what it used to do? pf.conf(5)
already facilitates thresholds, and they aren't _read
only_. Is there any way to turn this OID off; like using
a -1 value? Or will we need to simply back out the commit?

Thanks in advance for any advice.

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How to get mouse configured in X(org)?

[Chris]

On Fri, 31 Jul 2020 18:03:17 -0700 bsd-li...@bsdforge.com said


All bitching aside. My conclusion is the

Option  "AutoAddDevices" "Off"

Line below is responsible for permitting/activating the
mouse.


server-layout.conf
Section "ServerLayout"
Identifier  "X.org Configured"
Option  "AutoAddDevices" "Off"
Option  "Log"  "sync"
EndSection
driver-nvidia.conf
Section "Device"
Identifier  "Card0"
Driver  "nvidia"
BusID   "PCI:2:0:0"
EndSection
screen-layout.conf
Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection
keyboard-zap.conf
Section "InputClass"
Identifier  "KeyboardDefaults"
Driver  "keyboard"
MatchIsKeyboard "on"
Option  "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How to get mouse configured in X(org)?

[Chris]

On Fri, 31 Jul 2020 21:36:33 + Mark Linimon lini...@lonesome.com said


What is the output of the script mentioned in:

 https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025004.html


Thanks for the prompt, and thoughtful reply, Mark! :-)

OK I've been following CURRENT, and was aware of that. As I
needed it the first time around with the new Xorg. But I
hadn't imagined I would require any outside helpers on STABLE. :(
Anyway. I managed to get a working xorg.conf.new running against
Xorg -config. So I added only what I thought I absolutely needed
to /usr/local/X11/xorg.conf.d/ and fired up startx with my chosen
DE in .xinitrc. Only to find I _still_ had no mouse, nor control
of the WM. My only recourse was to bounce the box. :-(
I had to scrub the pool, and blow away all the X related things
in ~/ && try again. I was finally successful after creating the
following 4 files:
server-layout.conf
Section "ServerLayout"
Identifier  "X.org Configured"
Option  "AutoAddDevices" "Off"
Option  "Log"  "sync"
EndSection
driver-nvidia.conf
Section "Device"
Identifier  "Card0"
Driver  "nvidia"
BusID   "PCI:2:0:0"
EndSection
screen-layout.conf
Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection
keyboard-zap.conf
Section "InputClass"
Identifier  "KeyboardDefaults"
Driver  "keyboard"
MatchIsKeyboard "on"
Option  "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

Altho the keyboard-zap.conf is probably unnecessary. I added
it in hopes of being able to bail out as opposed to bouncing
the box.

I can't believe what a disappointment X has become. It's almost
a different incantation for every install. I'd understand on
CURRENT/release. But not on STABLE.

I'm very grateful for your lending a hand, Mark. I don't
mean to point any of my frustration at/towards you. :-)

Thanks, again! :-)

--Chris


mcl



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

How to get mouse configured in X(org)?

[Chris]

Greetings all,
I just installed a copy of 12@363433 from the install media.
I then pkg installed everything I intended to use.
After installing Xorg-server,nvidia-driver,xf86-input-keyboard,
xf86-input-mouse. I fired
Xorg -configure
examined the output in both /var/Xorg.o.log && ~/xorg.conf.new
everything appeared to be in order. So I fired off a
Xorg -config ~/xorg.conf.new -retro

While I got the familiar background mesh (-retro), and the
keyboard functioned correctly. The mouse doesn't work.


From Xorg.0.log:

[85.337] (II) config/udev: Adding input device IntelliMouse Explorer 
(/dev/input/event4)
[85.337] (II) No input driver specified, ignoring this device.
[85.337] (II) This device may have been added with another device file.

Relevant excerpt from xorg.conf.new:
Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/sysmouse"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

I appear to have covered all the bases in the entry of the handbook at:
https://www.freebsd.org/doc/handbook/x-config.html

Thanks in advance for any assistance.

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: swap space issues

[Chris]

 if you've
never worked on "bare metal" (at the "chip" level). Those w/o knowledge in
assembler never really fully understand what their doing.
Sorry. Couldn't resist.


Another problem, especially with programmers whose memories have not
yet
accumulated many painful experiences, is the attraction toward newer, more
exciting
features accompanied by a disinterest in tracking down and fixing existing
bugs,
even fairly critical bugs.  This problem, if left unchecked by management,
can lead
to terrible predicaments like the one FreeBSD is in now, namely, having no
production releases being supported.  DragonflyBSD, NetBSD, and OpenBSD do
not,
AFAIK, suffer from this predicament at present.  They are behind to varying
degrees
in terms of newer, more exciting features, but at least they appear to work. 
For

example, sdf.org has well over 70,000 users and runs quite a few servers to
do so.
It runs

NetBSD miku 8.1_STABLE NetBSD 8.1_STABLE (GENERIC) #0: Wed Sep 11 03:47:45
UTC 2019  root@ol:/sdf/sys/NetBSD-8/sys/arch/amd64/compile/GENERIC amd64

at present.  (miku.sdf.org is one of the servers.)  Its uptime is currently
306 days.
They run several VMs of FreeBSD, OpenBSD, LINUX, and possibly others on some
of the
servers.  ZFS appeared in NetBSD 9.0.  I don't know the sysadmin's reasons
for not
upgrading to it so far, but I suspect they have to do with the number of
systems to
upgrade, the fact that it is a .0 release, and that root on ZFS and ZFS boot
environments are not yet supported, as used to be the case with FreeBSD.  I'm
not
ready to switch to NetBSD quite yet and would not enjoy doing so, but it has
been
a steadily improving alternative to FreeBSD of late, and if FreeBSD does not
release
a production system in the meantime, NetBSD may become a better choice for
many of
us who want to run a production OS.  It also offers an alternative to
Micro$lop for
the so-called "Internet of Things", which no other FOSS OS does, AFAIK,
although I
don't know enough about LINUX to be sure.
>
> Those who live on -CURRENT are used to OOPS, but the rest of us get paid 
> not to have them.


I've been using -STABLE for the last several major releases, but because
of
the vast numbers of conflicts and failures buried throughout the ports tree
and
the horrendous amount of time it takes to rebuild most of my installed ports
I am
considering surrendering to using -RELEASE and using quarterly packages, in
spite
of the loss of features that doing so entails.  That would still not deal
with the 
dependency conflicts or the installation of identically named files by

different
ports, but it would reduce the time spent on building ports that fail to
install.
>
> I am happy with what the Core Team gives us, AND of course we want 
> ['more','better','faster','STABLE']. :D

>
As Mark Linimon pointed out, the Core Team only does that indirectly. 
However,

it is the Core Team's job to give firm direction or redirection to those who
do the
designing and coding to avoid regressions, avoid ignoring the introduction of
bugs,
especially those that render a system unfit for production use, enhance
testing,
and so on.


 Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at sdf.org   *xor*   bennett at freeshell.org  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld and buildkernel with very slow compilation, recently

[Chris Nehren]

On Sunday, June 21, 2020 8:11:15 AM EDT Michael Grimm wrote:
> Hi,
> 
> I am following FreeBSD 12.1-STABLE.
> 
> Clang has been upgraded to version 10.0.0 on May, 1st, and ever since that
> time, I do observe a dramatic increase in compilation times of building
> world, kernel and ports. I didn't benchmark the exact times, but
> compilation times are at least increased by a factor of 1.5. Nothing has
> changed of the last month besides upgrading 12.1-Stable every other week.
> 
> Has anyone else been bitten by this?

I don't have measurements to corroborate this, but here's a mailing list 
thread where folks are talking about it (split across two URLs, the OP posted 
in April and then there was a followup in May):

http://lists.llvm.org/pipermail/llvm-dev/2020-April/140938.html 
https://lists.llvm.org/pipermail/llvm-dev/2020-May/141482.html 

So there definitely seems to be *something* going on, and you are indeed not 
crazy. :)




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: LUA ERROR: memory allocation error: block too big

[Chris]

On Wed, 3 Jun 2020 05:00:13 + (UTC) Roderick hru...@gmail.com said


LUA Error!

I would real want hear, why was the boat loader spoiled with Lua?

Bwcause lua is so cool?

Rodrigo


On Tue, 2 Jun 2020, Budi Janto wrote:

> Hi Folks,
>
> Now, I'am running FreeBSD 12.1-STABLE, suddenly after restart system can
> not able to booting (boot to single user only).
>
> ...
> Loading /boot/defaults/loader.conf
> Loading /boot/device.hints
> Loading /boot/loader.conf
> efipart_readwrite: rw=1, blk=5656992 size=40 status=7
> Startup error in /boot/lua/loader.lua:
> LUA ERROR: memory allocation error: block too big.
>
> can't load 'kernel'
>
> Type '?' for a list of commands. 'help' for more detailed help
> OK
> ...
>
> Anyone could give some clue to fixing this booting issue? -- Thank You.

Boot single user if possible, tho it's probably not.
Failing that; boot from the install media. Mount the root slice
of your failing system. cd to its /boot folder
rm ./loader
ln loader_4th loader
cd /
unmount the system
remove the install media you just booted from, and reboot.
It should (hopefully) work now.

--Chris

>
>
> -- 
> Regards,

>
>
> Budi Janto
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Loader hangs on the latest -STABLE

[Chris]

On Thu, 23 Apr 2020 22:24:00 -0700 bsd-li...@bsdforge.com said


On Fri, 24 Apr 2020 08:26:13 +0400 Igor Pokrovsky i...@unixway.org said

> Hello all,
> 
> I haven’t been using FreeBSD since 8-STABLE times. Recently I tried to

> install latest 12-STABLE on my old computer.
> But even during initial boot up loader hangs. Eventually I was able to
> proceed with installation after replacing loader in 
> the installation disk with one found in my old system 8-STABLE. The same

> happened when I tried zfs on root partition.
A lot of things are moving around in /boot over the last year.
Pure speculation; if you're using a usb stick. Mount it from your
currently running system, and

cd /boot
rm ./loader
cp -p ./loader.efi ./loader

STRIKE THAT!
I meant
cp -p ./loader.4th ./loader

sorry!

OH, and you will, of course need to do it as root. :)

--Chris

umount 

Then see if it doesn't work for you. Like I said, pure speculation.
But you indicated an old box. So I think you might find this works.

Best wishes!

--Chris
> 
> I used MBR partition on PATA hard drive. Motherboard was ASUS A8V

> (Athlon64).
> 
> ip
> 
> ___

> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Loader hangs on the latest -STABLE

[Chris]

On Fri, 24 Apr 2020 08:26:13 +0400 Igor Pokrovsky i...@unixway.org said


Hello all,

I haven’t been using FreeBSD since 8-STABLE times. Recently I tried to
install latest 12-STABLE on my old computer.
But even during initial boot up loader hangs. Eventually I was able to
proceed with installation after replacing loader in 
the installation disk with one found in my old system 8-STABLE. The same

happened when I tried zfs on root partition.

A lot of things are moving around in /boot over the last year.
Pure speculation; if you're using a usb stick. Mount it from your
currently running system, and

cd /boot
rm ./loader
cp -p ./loader.efi ./loader
umount 

Then see if it doesn't work for you. Like I said, pure speculation.
But you indicated an old box. So I think you might find this works.

Best wishes!

--Chris


I used MBR partition on PATA hard drive. Motherboard was ASUS A8V
(Athlon64).

ip

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: support of PCIe NVME drives

[Chris]

On Fri, 17 Apr 2020 08:17:56 +0200 Miroslav Lachman 000.f...@quip.cz said


Chris wrote on 04/17/2020 05:51:
> On Thu, 16 Apr 2020 19:57:21 -0700 Mel Pilgrim 
> list_free...@bluerosetech.com said
> 
>> On 2020-04-16 12:30, Miroslav Lachman wrote:

>> > Pete Wright wrote on 04/16/2020 20:23:
>> >>
>> >>
>> >> On 4/16/20 11:12 AM, Miroslav Lachman wrote:
>> >>> Kurt Jaeger wrote on 04/16/2020 20:07:
>> > >> I would try booting via UEFI if you can.  I just installed a 
>> laptop >> yesterday which has a nvme root device, it was detected by 
>> the >> 12-STABLE snapshot I used to boot from.  no other modifications 
>> were >> necessary on my end.
>> > > I changed BIOS settings to use UEFI boot method, booted 12.1 
>> installer > ISO but without luck. Still no NVME disks :(

>> > > You can see it on printscreen from iDRAC https://ibb.co/tPnymL7
>> > > Anything more I can test?
>>
>> Looking at server specs, the R6515's NVME support is only through the 
>> PERC S150 RAID controller.  If that's the case, I'm pretty sure you're 
>> out of luck.  The PERC S-series controllers are software-based RAID 
>> that require Dell's Windows or Linux drivers.  You'd need a PERC 
>> H-series card to get support in FreeBSD.


That's something I didn't expect at all. So there is nothing which can 
be fixed on FreeBSD side? :(


>> Someone please correct me if I'm wrong?
> As I mentioned. I was suspicious of this. He should be able to flash the 
> card,
> making it a pass. I do a lot of them. If someone doesn't beat me to it. 
> I'll
> dig through what I have, and see if I can't find the right image(s), and 
> program(s).


This is rented dedicated machine. I cannot flash anything on it.

Apologies for the late reply. Unfortunately $JOB requires me to $WORK. :(
OK Given these are rentals. Probably the most I could supply for your
needs are images that allow you to poll, and change settings of the
controller(s). I have cd9660, and USB flash images of the utilities
for the 100-300 series HBAs as provided by LSI/AvGO. They boot to (MS)DOS,
or to an (U)EFI prompt. Having read what I can; the S150 controller is
Software controlled (likely explaining the "S" in it's model number), and as
I understand it *shouldn't* require any flashing. As I also understand you
*should* be able to access control of it through UEFI configs. I *think*
accessed via F2.
Apologies if this comes too late, or you've already solved this.
If you're still interested in the management software I have for the 100-300
series. Let me know, and I'll attach a copy, or provide a link for you as
needed.

--Chris



I can ask the provider if they can install some card. Do you have some 
recommendation? What is supported by Dell and FreeBSD for ZFS?


I really appreciate your help!

Kind regards
Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: support of PCIe NVME drives

[Chris]

On Thu, 16 Apr 2020 19:57:21 -0700 Mel Pilgrim list_free...@bluerosetech.com 
said


On 2020-04-16 12:30, Miroslav Lachman wrote:
> Pete Wright wrote on 04/16/2020 20:23:
>>
>>
>> On 4/16/20 11:12 AM, Miroslav Lachman wrote:
>>> Kurt Jaeger wrote on 04/16/2020 20:07:
> 
>> I would try booting via UEFI if you can.  I just installed a laptop 
>> yesterday which has a nvme root device, it was detected by the 
>> 12-STABLE snapshot I used to boot from.  no other modifications were 
>> necessary on my end.
> 
> I changed BIOS settings to use UEFI boot method, booted 12.1 installer 
> ISO but without luck. Still no NVME disks :(
> 
> You can see it on printscreen from iDRAC https://ibb.co/tPnymL7
> 
> Anything more I can test?


Looking at server specs, the R6515's NVME support is only through the 
PERC S150 RAID controller.  If that's the case, I'm pretty sure you're 
out of luck.  The PERC S-series controllers are software-based RAID that 
require Dell's Windows or Linux drivers.  You'd need a PERC H-series 
card to get support in FreeBSD.


Someone please correct me if I'm wrong?

As I mentioned. I was suspicious of this. He should be able to flash the card,
making it a pass. I do a lot of them. If someone doesn't beat me to it. I'll
dig through what I have, and see if I can't find the right image(s), and 
program(s).


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: support of PCIe NVME drives

[Chris]

On Thu, 16 Apr 2020 22:57:10 +0200 Miroslav Lachman 000.f...@quip.cz said


Chuck Tuffli wrote on 04/16/2020 22:29:
> On Thu, Apr 16, 2020 at 12:30 PM Miroslav Lachman <000.f...@quip.cz> wrote:
>>
>> Pete Wright wrote on 04/16/2020 20:23:
>>>
>>>
>>> On 4/16/20 11:12 AM, Miroslav Lachman wrote:
>>>> Kurt Jaeger wrote on 04/16/2020 20:07:
>>
>>> I would try booting via UEFI if you can.  I just installed a laptop
>>> yesterday which has a nvme root device, it was detected by the 12-STABLE
>>> snapshot I used to boot from.  no other modifications were necessary on
>>> my end.
>>
>> I changed BIOS settings to use UEFI boot method, booted 12.1 installer
>> ISO but without luck. Still no NVME disks :(
>>
>> You can see it on printscreen from iDRAC https://ibb.co/tPnymL7
>>
>> Anything more I can test?
> 
> Fair warning, I don't deal much with Dell, but it's curious that iDrac

> lists the device protocol as MI
>> Device Protocol:  NVMe-MI1.0
> 
> MI or the Management Interface is defined by NVMe, but it isn't the

> same as a block interface. MI typically uses SMBUS and not PCIe to
> communicate with the device. So it's possible that the device is
> visible to iDrac via SMBUS but may not be on the PCIe bus for
> $reasons. Does iDrac have any tools to interact with the device via
> MI?

iDRAC does not allow me to do anything with the drives.
But I booted Linux SystemRescueCd and nvme devices are there visible in 
/dev/

printscreen https://ibb.co/sj22Nwg

So I think the HW is OK, but FreeBSD does not recognize the controller?


Does mps(4) or any of the other (often Dell) rebranded LSI drivers expose 
anything?



Kind regards
Miroslav Lachman


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make kernel ignore broken SATA disk

[Chris]

On Sun, 12 Apr 2020 16:37:06 +0200 Stefan Bethke s...@lassitu.de said


I have a server I don't have physical access to right now, which has a broken
SATA disk that produces mostly errors (but not entirely).

The disk has two partitions that are part of a zpool each. I can't bring the
system up with this disk being online, because ZFS is trying its darndest to
use it.

I already renamed the GPT partitions in the hope that ZFS would not find them
anymore, but it does.

I can't gpart destroy -f ada1 because "device busy".

FTR it's gpart destroy -F (note the case difference) :-)



Is there a way, ideally in the loader, to tell the kernel to ignore ada1
and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do
have a spare disk I can use to replace the failed one, but I can't get the
machine into a state where I could even issue the zpool replace command.


Stefan


--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS server has gone crazy slow

[Chris Ross]

> On Apr 12, 2020, at 01:48, Eugene Grosbein  wrote:
> 
> There is very simple way to prevent such problem, use: zfs set reservation=1G
> for single "root" file system of the pool.
> 
> This way ZFS won't allow applications to fill the pool to the point it starts 
> crawling.
> Instead, writing applications would obtain ENOSPC error when pool's free 
> space hits the limit.

Done.  Thank you for that good advice!  In case this system develops the
same issue in another year or three and I’ve forgotten this, it will yell at me
before getting so logged down.

  - Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Why is the console a graphic/bitmapped console, and not text/character by default

[Chris]

On Sun, 12 Apr 2020 12:55:47 +0700 Eugene Grosbein eu...@grosbein.net said


12.04.2020 11:41, Chris wrote:

> Sorry for the ling title. But wasn't sure how make my
> question more concise.
> Why did we begin making an initial console "graphics mode"
> by default. My understanding has always been that (Free)BSD
> has been a "Server by default", and a Desktop after an initial
> install if that's one chosen target.
> It's near impossible to perform initial configuration
> in graphics mode, using a mouse to cut/copy/paste does *not*
> work as intended. Which requires one to make the necessary
> changes "breaking to the new system" after install completes
> to change initiation to test-mode before bouncing the box.
> While this "works" for long-time users. It's an *extra*, and
> seemingly *unnecessary* step. It is also likely to behoove
> first-time/new users -- except those already targeting a
> Desktop.
> 
> Thanks for any insight into this! :)


There are now many new hardware incapable of booting in legacy mode.
It runs in UEFI mode only that needs newer console driver vt(4)
that defaults to pixel rendering mode but supports text mode, too.
Sadly, some UEFI-based hardware does not support text mode even with vt(4)
and there is no option other than using pixel mode then.


That explains it. Thanks Eugene! :)
Even if the answer is a bit disappointing. ;)

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Why is the console a graphic/bitmapped console, and not text/character by default

[Chris]

Sorry for the ling title. But wasn't sure how make my
question more concise.
Why did we begin making an initial console "graphics mode"
by default. My understanding has always been that (Free)BSD
has been a "Server by default", and a Desktop after an initial
install if that's one chosen target.
It's near impossible to perform initial configuration
in graphics mode, using a mouse to cut/copy/paste does *not*
work as intended. Which requires one to make the necessary
changes "breaking to the new system" after install completes
to change initiation to test-mode before bouncing the box.
While this "works" for long-time users. It's an *extra*, and
seemingly *unnecessary* step. It is also likely to behoove
first-time/new users -- except those already targeting a
Desktop.

Thanks for any insight into this! :)

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS server has gone crazy slow

[Chris Ross]

> On Apr 11, 2020, at 14:33, Eugene Grosbein  wrote:
> 
> 12.04.2020 0:36, Chris Ross wrote:
> 
>> I have a FreeBSD 11.3-STABLE server that is my router, using a ZFS mirror 
>> (of two GPT disks) as it’s disk.  It’s many years old, and has only been 
>> misbehaving like this for a day or so.  I’m trying to figure out what’s 
>> wrong.
>> 
>> […]
>> 
>> I _think_ this is a filesystem problem.  It’s very hard to diagnose because 
>> logging in, and doing anything, takes many seconds per command.  zpool 
>> status shows my mirror as online, so I’m not sure where I should check.
>> 
>> I’d appreciate any help!  Thanks much…
> 
> First of all you should check if any of your ZFS pools is low on space.

Wow.  I’m so embarrassed that I didn’t notice that myself.  You mentioned it, 
and now I look back at df output and see that the filesystems are all very 
nearly full!

It’s very slowly booting now, but assumedly after it comes online, I’ll be able 
to rectify that situation and hopefully that will be the issue.  Thanks, and 
sorry that I hadn’t seen that myself!

- Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

ZFS server has gone crazy slow

[Chris Ross]

I have a FreeBSD 11.3-STABLE server that is my router, using a ZFS mirror (of 
two GPT disks) as it’s disk.  It’s many years old, and has only been 
misbehaving like this for a day or so.  I’m trying to figure out what’s wrong.

I confirmed that internet connectivity isn’t the problem, and a reboot didn’t 
fix it.  (The reboot took 10-15 minutes to finish going multi-user, starting 
daemons, due to the underlying problem described below.)

Truss’ing a very basic command (date), I can see that close() and exit() calls 
are taking 1-2 seconds.  All of the files being opened are on ZFS, but I don’t 
know if that’s for sure related.  Similarly, using shell builtin “echo foo” 
always is immediate, but “/bin/echo” sometimes works quickly, but sometimes the 
close() on /var/run/ld-elf.so.hints takes 3-5 seconds.

I _think_ this is a filesystem problem.  It’s very hard to diagnose because 
logging in, and doing anything, takes many seconds per command.  zpool status 
shows my mirror as online, so I’m not sure where I should check.

I’d appreciate any help!  Thanks much…

   - Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: efi: WARNING: Unable to alias diskid/DISK-... to enc@n306168... - path too long

[Chris]

On Wed, 18 Mar 2020 11:37:34 -0600 Alan Somers asom...@freebsd.org said


On Wed, Mar 18, 2020 at 10:56 AM Chris  wrote:

> On Wed, 18 Mar 2020 10:48:08 -0600 Alan Somers asom...@freebsd.org said
>
> > On Wed, Mar 18, 2020 at 10:37 AM Chris  wrote:
> >
> > > I'm getting the following message on a fresh install of 12.1:
> > > WARNING: Unable to alias diskid/DISK-WD-WCANM2154600 to
> > >
> > > enc@n3061686369656d30/type@0/slot@1/elmdesc@Slot_00
> /diskid/DISK-WD-WCANM2154600
> > > - path too long
> > > Actually, there are several similar messages. Which required me to
> > > perform several disk related tasks in order to get a successful boot
> > > into the new system. It's GPT/UFS(2) if it matters. But I suspect
> > > it's more related to fbsd' implementation of EFI, as it relates to my
> > > BIOS' implementation (Intel Sandy Bridge). What can I do to make
> > > everything happy?
> > >
> > > Thanks!
> > >
> > > --Chris
> > >
> > When did you see that message?  Was it printed from the bootloader, or
> > after you booted?  If it happened after boot, then they're probably
> > harmless, but you can make them go away by setting
> > kern.geom.label.disk_ident.enable=0.
> Thanks for the reply!
> It's during boot, and found in dmesg.boot. I wouldn't care so much,
> except I was unable to boot into the system until I performed a
> gpart modify -i  -l  on all the slices, and modify
> fstab(5) accordingly. Kind of a rough start for an install IMHO. :)
>
> Thanks again, for the reply, Alan!
>
> --Chris
>
How did you setup your zroot?  This shouldn't matter unless you used those
long aliases as the vdevs for your zroot pool.

Thanks for the reply, Alan.
As mentioned above; the disk is GPT/UFS(2). I chose "custom" from the disk
layout dialog from the install media. I chose UFS/softupdates, and later,
after getting a successful boot onto the drive. I added journaling.
But that's it. Nothing fancy.

Thanks again.

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: efi: WARNING: Unable to alias diskid/DISK-... to enc@n306168... - path too long

[Chris]

On Wed, 18 Mar 2020 10:48:08 -0600 Alan Somers asom...@freebsd.org said


On Wed, Mar 18, 2020 at 10:37 AM Chris  wrote:

> I'm getting the following message on a fresh install of 12.1:
> WARNING: Unable to alias diskid/DISK-WD-WCANM2154600 to
>
> 
enc@n3061686369656d30/type@0/slot@1/elmdesc@Slot_00/diskid/DISK-WD-WCANM2154600
> - path too long
> Actually, there are several similar messages. Which required me to
> perform several disk related tasks in order to get a successful boot
> into the new system. It's GPT/UFS(2) if it matters. But I suspect
> it's more related to fbsd' implementation of EFI, as it relates to my
> BIOS' implementation (Intel Sandy Bridge). What can I do to make
> everything happy?
>
> Thanks!
>
> --Chris
>
When did you see that message?  Was it printed from the bootloader, or
after you booted?  If it happened after boot, then they're probably
harmless, but you can make them go away by setting
kern.geom.label.disk_ident.enable=0.

Thanks for the reply!
It's during boot, and found in dmesg.boot. I wouldn't care so much,
except I was unable to boot into the system until I performed a
gpart modify -i  -l  on all the slices, and modify
fstab(5) accordingly. Kind of a rough start for an install IMHO. :)

Thanks again, for the reply, Alan!

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

efi: WARNING: Unable to alias diskid/DISK-... to enc@n306168... - path too long

[Chris]

I'm getting the following message on a fresh install of 12.1:
WARNING: Unable to alias diskid/DISK-WD-WCANM2154600 to 
enc@n3061686369656d30/type@0/slot@1/elmdesc@Slot_00/diskid/DISK-WD-WCANM2154600 
- path too long
Actually, there are several similar messages. Which required me to
perform several disk related tasks in order to get a successful boot
into the new system. It's GPT/UFS(2) if it matters. But I suspect
it's more related to fbsd' implementation of EFI, as it relates to my
BIOS' implementation (Intel Sandy Bridge). What can I do to make
everything happy?

Thanks!

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

what 3rd party boot mgr is required to boot multiple freebsd versions?

[Chris]

I'm attempting to boot multiple versions of FreeBSD.
I started with an install of older 11 with a (u)efi
boot partition installed. I then grabbed an current 11
usbstick, and installed that. Which stated it needed to
install a (u)efi boot partition. I let it do it. But the
new (additional) install doesn't show up at boot. Altho
my UEFI BIOS sees it.
I guess there are just too many uefi bios versions,
and too many changes in the FreeBSD uefi boot code
to expect consistent results over the long haul.
Should I just convert the 1st efi (GPT) boot partition
to a PMBR, and delete the second efi partition. Or is
there a recommended bootmanager I can use to boot multiple
versions of FreeBSD? Windows?

Thank you!

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

[Chris]

On Mon, 9 Mar 2020 07:06:31 +1000 Andy Farkas an...@andyit.com.au said


On 2020-03-09 04:15, bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235564
>
> --- Comment #8 from commit-h...@freebsd.org ---
> A commit references this bug:
>
> Author: emaste
> Date: Sun Mar  8 18:14:45 UTC 2020
> New revision: 358758
> URL: https://svnweb.freebsd.org/changeset/base/358758
>
> Log:
>MFC r355585: remove nonexistent from-* entries from vt INDEX.keymaps


Is anyone actually working on the vt(4) driver?  Will it ever

become feature-parity with the old sc(4) driver?


I've noticed some weird things happening on my console recently...

like psychedelicly-colour-coded kernel messages.. far out, man.


Just wondering,


-andyf

Thanks for bringing this up. I've been meaning to ask similar.
When building a custom kernel, and including sc(4). Then adding
kern.vt=sc to loader.conf(5). I'm presented with rainbow text. I
wouldn't mind so much *except* that it's color choices, and places
are simply *random*

Thanks in advance for any insight on this. :)

--Chris



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Running FreeBSD on M.2 SSD

[Chris]

On Fri, 28 Feb 2020 21:44:45 -0300 Mario Olofo mario.ol...@gmail.com said


Hello guys, a little update that let me more confused

I reinstalled the FreeBSD with 4k pages using the sysctl
vfs.zfs.min_auto_ashift = 12 and no errors after a lot of stress I put on
it.
One thing that I noticed is that with the pool as 4k, the disk fill up very
fast, recompiling the kernel used my 8GB space and didn't even completed.
But now I don't know if the 4k is the correct answer or if this just delays
the problem as the pages are bigger.

The TLDR of 4k vs 512 largely has to do with the size of the files going
onto your medium. Many files of a smaller size fit better on a 512 boundary.
Whereas larger mp3s or archives fair better on a 4k boundary. BTW these are
called SECTOR sizes. Not pages. :) 4k blocks typically read faster, than the
512 blocks (sectors). Because more data can be consumed in one read/write.
So really, your going to have to decide how best to "tune" your disk to best
suite it's intended use. Many small files. Or big files, and storage.

HTH

--Chris
FreeBSD 14.0-FUTURE #0.000 cray256


Mario

Em sex., 28 de fev. de 2020 às 13:18, Mario Olofo 
escreveu:

> Yes, tried 4k quirk but not on install because don't know how to, I did a
> clean install then patch and rebuild the kernel, but
> the volume was already configured for 512bytes, I think I would need to
> create manually the volume, but don't remember how to anymore xD
> But I'll search some tutorials and try. From what I saw, the patch
> suggested on bugzilla got merged into the stable branch, so the quirk will
> be
> detected to use 4k in the installer in a near future.
>
> Mario
>
> Em sex., 28 de fev. de 2020 às 12:52, Theron 
> escreveu:
>
>> On 2020-02-28 09:14, Mario Olofo wrote:
>> > Thanks!
>> >
>> > The only thing that I didn't checked was the questions of Theron, about
>> > misaligned data.
>> > The layout of the disk is as follows:
>> >
>> > Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores
>> > Unidades: setor de 1 * 512 = 512 bytes
>> > Tamanho de setor (lógico/físico): 512 bytes / 512 bytes
>> > Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes
>> > Tipo de rótulo do disco: gpt
>> > Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A
>> >
>> > DispositivoInício   Fim   Setores Tamanho Tipo
>> > /dev/sdb12048   1023999   1021952499M Windows ambiente de
>> > recuperação
>> > /dev/sdb2 1024000   1228799204800100M Sistema EFI
>> > /dev/sdb3 1228800   1261567 32768 16M Microsoft reservado
>> > /dev/sdb4 1261568 532482047 531220480  253,3G Microsoft dados básico
>> > /dev/sdb5   532482048 549257215  16775168  8G FreeBSD ZFS
>> > /dev/sdb6   549257216 937719807 388462592  185,2G Linux sistema de
>> arquivos
>> >
>> > The zfsroot was configured automatically by the installer, so I think
>> that
>> > it align the volume automaticaly right?
>> >
>> > Mario
>>
>> Yes, I don't see any potential alignment issue here.  I would wonder if
>> this drive is misrepresenting its physical sector size, deceiving ZFS
>> and the SATA driver into making small writes that the drive does not
>> actually support, but it looks like you may have already tried the
>> relevant workaround:
>>
>> On 2020-02-27 23:44, Mario Olofo wrote:
>> > Maybe the problem really is a combination of factors, for the person
>> that
>> > filed a bug on bugzilla the fix was setting the quirks 4k and
>> broken_trim,
>> > but for me the real block size is 512bytes and only setting the flag
>> > broken_trim didn't help...
>> >
>> > Mario
>> Did you try 4k quirk ?
>>
>> Theron
>>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Long-shot: repeatable macOS samba share unmounting during Lightroom import

[Chris Gordon]

ll of the network browsing and 
discovery and  is the code path that was impacted by the NetBIOS change.  Any 
mount tied in with this path gets impacted, and when this goes south, it takes 
the mounts with it.  Mounting via other means doesn't bring in the associated 
path.

I will check each new OS X update to see if this issue goes away.  Until then, 
I just mount my shares via "Go- > 'Connect to Server'".   Also note that you 
can re-enable NetBIOS support in Catalina 
(https://medium.com/@gobinathm/how-to-access-smb-printer-shares-in-macos-catalina-10-15-17ea91d2c10b).
  I've not done nor tested that.

Hopefully a minor tweak to how you mount the SMB share will save you the huge 
hassle of changing out tools.

Hope that helps.

Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI ISO boot not working in 12.1 ?

[Chris Ross]

> On Nov 9, 2019, at 16:07, Toomas Soome  wrote:
>> On 9. Nov 2019, at 22:42, Chris Ross  wrote:
>> 
>> On Sat, Nov 09, 2019 at 11:24:49AM -0600, Kyle Evans wrote:
>>> Hi,
>>> 
>>> That helps- thanks! I'm CC'ing tsoome@, as this is basically just
>>> r353501 in that range. Can you give the latest -CURRENT snapshot boot
>>> as another data point?
>> 
>> Thanks.  And yeah, happily, I was already in the process of building
>> a -current to test.  I am happy (in a way?) to report that it fails in
>> the same way as 12.1-RELEASE and stable-12 after Oct 15.
>> 
>> Thanks.
>> 
>>  - Chris
>> 
>> for tsoome, the description of boot messages from the top of the thread:
>> https://u13739864.ct.sendgrid.net/wf/click?upn=hQ0vnUG1MhNJP-2B3V0tQS3X7emL4YkSUT2tPN1FH-2B97trcjJ-2BpJTmk0YS1Syuo2dzEgthbm6esr-2F7g51EhfIu-2FRKPX9ALsGd2rGBcgTMu-2ByHTR5seO4J-2BMjDv1jXVelnC_Q1G7K8cYCrLWsp3rtsmPRmehVLbUy52d-2BfbfYGlvl9NQI4m-2FwzZopJkgCxdhMRbWmFftXh2uS-2B-2BSajUZUYeDDKIqa-2BkmcDAEvzUwBDvIkJ68RHhHwrawZGSusvYISZywqilQnr9pHQM76aMYLdRwAVYqyTEPcAf5A5HUkYd-2BCJMlUHK2yaZZCEthT1ABNUcX5NJKB-2B9bcz-2B5MfT94enkwpJ0wn19Bm-2BHJ58K1WRS9QQ-3D
> 
> Going to investigate tomorrow with fresh head as it is getting close to 
> midnight here…

I had some email server problems lately, but I haven’t seen any more about this.
Any update, Toomas?

- Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

On Sat, Nov 09, 2019 at 04:51:38PM -0500, Chris Ross wrote:
> > > Can you provide some guidance of what I need to do to get the mrsas
> > > driver to identify it when booting the install ISO?
> > 
> > See the "PRIORITY" section of
> > 
> > https://www.freebsd.org/cgi/man.cgi?query=mrsas=4
> > 
> > You can also set that tunable via the loader
> 
> Hmm.  Okay.  I know I was messing with that parameter on one of these
> machines, I though I'd tried it on this one.  But, maybe that was the
> older box with the HBA in it.

Alright, my bad.  Apologies to all.  So, it turns out that this controller
is not recognized in 12.0, but is recognized by later stable-12 builds.
I have another problem that prevented 12.1 from booting at all, and I tried
investigating both at the same time.  This caused me to confuse things.
My error.

Thanks to all, and this seems to be working in stable-12 in the neighborhood
of Oct 2019, perhaps earlier.

 - Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

On Sat, Nov 09, 2019 at 04:48:10PM +, Gary Palmer wrote:
> > Hi Doug!  Thanks.  Okay, I infer from that that the mpr driver is for
> > HBAs that aren't raid?  Grepping through the sources for 3516 found me
> > only mpr.  Looking more carefully, at mrsas while knowing specifically
> > what I'm looking for, I find the PCI device ID (0x0014) as "AVAGO Ventura
> > SAS Controller".  And, that code (mrsas) is about the same in stable-12 as
> > is it in -current.
> > 
> > Can you provide some guidance of what I need to do to get the mrsas
> > driver to identify it when booting the install ISO?
> 
> See the "PRIORITY" section of
> 
> https://www.freebsd.org/cgi/man.cgi?query=mrsas=4
> 
> You can also set that tunable via the loader

Hmm.  Okay.  I know I was messing with that parameter on one of these machines,
I though I'd tried it on this one.  But, maybe that was the older box with
the HBA in it.

While I try that, I have a question.  I understood that tunable to be a way
to get the mfi(4) driver to allow the mrsas(4) driver to be used for
devices they both would recognize.  But, in this case, it's clear that the
mfi(4) driver has now knowledge of this device.  Is that tunable being
set necessary to have the mrsas(4) driver even find the devices it knows
how to support that mfi(4) doesn't?   If so, that's a very unfortunate 
situation.  Because there will be a significant set of controllers, like
the one I have in this system, that totally fail to present themselves
when installing from the install media.  Maybe this is a political issue,
and I should stop thinking about it, but.  Let me know if I'm understanding
the technical side, that there are cards mfi(4) has no support for, but
this tunable prevents mrsas(4) from attaching them?

   - Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI ISO boot not working in 12.1 ?

[Chris Ross]

On Sat, Nov 09, 2019 at 11:24:49AM -0600, Kyle Evans wrote:
> Hi,
> 
> That helps- thanks! I'm CC'ing tsoome@, as this is basically just
> r353501 in that range. Can you give the latest -CURRENT snapshot boot
> as another data point?

Thanks.  And yeah, happily, I was already in the process of building
a -current to test.  I am happy (in a way?) to report that it fails in
the same way as 12.1-RELEASE and stable-12 after Oct 15.

Thanks.

   - Chris

for tsoome, the description of boot messages from the top of the thread:
https://docs.freebsd.org/cgi/getmsg.cgi?fetch=98224+0+current/freebsd-stable
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI ISO boot not working in 12.1 ?

[Chris Ross]

On Thu, Nov 07, 2019 at 02:53:25PM -0500, Chris Ross wrote:
> > > On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer  wrote:
> > >> You could try some bisection back along the  12 branch..
> 
> Yeah.  I was hoping for an easier path, but.  I can try slogging back
> through stable-12 a month or two at a time.

Okay.  I spent a bunch of time moving around stable-12 by date, and
an ISO build from stable-12 as of 2019-10-14 works (rev 353483), and
2019-10-15 (rev 353541) does not.

The svn update across that day shows:

Updating '.':
Ustand/efi/boot1/boot1.c
Ustand/efi/include/efilib.h
Ustand/efi/libefi/devpath.c
Ustand/efi/libefi/efinet.c
Ustand/efi/libefi/efipart.c
Ustand/efi/libefi/libefi.c
Ustand/efi/loader/arch/i386/efimd.c
Ustand/efi/loader/efi_main.c
Ustand/efi/loader/framebuffer.c
Ustand/efi/loader/main.c
Ustand/libsa/stand.h
Ustand/libsa/zalloc.c
Ustand/libsa/zalloc_defs.h
Ustand/libsa/zalloc_malloc.c
Ustand/libsa/zalloc_mem.h
Ustand/libsa/zalloc_protos.h
 U   .
Updated to revision 353541.

So, there's the commit/commits.  Can someone else who knows the intra-branch
process better help me determine where the original change came from,
what it was meant to accomplish, then hopefully we can find out what went
wrong for at least my hardware?

Thanks all!

 - Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

On Fri, Nov 08, 2019 at 02:28:17PM -0800, Doug Ambrisko wrote:
> On Tue, Nov 05, 2019 at 09:44:36PM +0100, Miroslav Lachman wrote:
> | Chris Ross wrote on 11/05/2019 21:19:
> | > On Tue, Nov 05, 2019 at 08:20:15PM +0100, Miroslav Lachman wrote:
> | >> Chris Ross wrote on 11/05/2019 19:34:
> | >>> Hello.  I have a Cisco UCS C220-M5 with a RAID controller.  It calls 
> itself
> | >>> "Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5.
> | >>> Looking at the CIMC, it shows the PCI vendor/device ids 1000:0014, which
> | >>> looks to be an LSI MegaRAID Tri-Mode SAS3516.  It looks like this should
> | >>> be supported by the mpr(4) driver, but it doesn't seem to recognize it
> | >>> at boot time.
> | 
> | mpr_load="YES" goes to /etc/loader.conf
> | 
> | If you need to load mpr manually in boot prompt I am not sure if it 
> | should be:
> | load mpr
> | or
> | load mpr.ko
> | of full path
> | load /boot/kernel/mpr.ko
> 
> This should be a mrsas card and not an HBA!  mrsas supports all current
> UCS RAID cards ... and the next unreleased UCS system :-)  You might need
> the one in -current for that.  I'm not sure what is in 12.1.

Hi Doug!  Thanks.  Okay, I infer from that that the mpr driver is for
HBAs that aren't raid?  Grepping through the sources for 3516 found me
only mpr.  Looking more carefully, at mrsas while knowing specifically
what I'm looking for, I find the PCI device ID (0x0014) as "AVAGO Ventura
SAS Controller".  And, that code (mrsas) is about the same in stable-12 as
is it in -current.

Can you provide some guidance of what I need to do to get the mrsas
driver to identify it when booting the install ISO?

  - Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI ISO boot not working in 12.1 ?

[Chris Ross]

On Thu, Nov 07, 2019 at 10:56:00AM +1000, George Michaelson wrote:
> On Thu, Nov 7, 2019 at 10:21 AM Julian Elischer  wrote:
> >
> > I suspect a separate bug because the OP specified that it worked in
> > 12.0 where those bugs go back to 9.x
> 
> Oh, I didn't realize I updated a PXE boot PR. I am not PXE: I tested
> with real media in a Dell, and with Dell iDRAC virtualized media, and
> with USB.
> 
> I absolutely represent a user who has h/w which I can reproducably
> show cannot load UEFI from true and virtualized local media, not PXE.
> 
> And, this state has existed for some time.

Yeah, but I think it's not related.  That bug and the screenshots show
a kernel booting, then failing to mount.  Are you seeing a failure in
the initial loader, George?  And as noted, the issue I'm seeing is
new in 12.1, as compared to the loader in 12.0

> > On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer  wrote:
> >> You could try some bisection back along the  12 branch..

Yeah.  I was hoping for an easier path, but.  I can try slogging back
through stable-12 a month or two at a time.  Is moving through svn by
date the easiest path, or are there [stable] revision tags that would make
it easier?

Thanks all.

 - Chris

ps, somewhere earlier in this thread that I lost right now someone asked
if I could put an alternate versions loader on an ISO.  I don't know that
I know how, but I'd be happy to try it.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support ?

[Chris Ross]

On Tue, Nov 05, 2019 at 05:04:41PM -0500, Chris Ross wrote:
> > However, if you've already placed
> > mpr_load="YES" in your /etc/loader.conf and rebooted your device, then you
> > probably need to move into a diagnostic phase.
> 
> Yeah.  I think I see what PCI id is missing in the driver, after digging
> around in the sources.  I was just hoping it was a process/human error.
> I'll get another machine running a build, and see if I can stub it in.

Okay.  Well, the simple try didn't magically work.  I added a few lines in
dev/mpr/mpr_pci.c in releng/12.0, built a new ISO, and booted.  Now it
recognizes the part, but says the following:

pcib7:  [...]
pci7:  numa-domain 0 on pcib7
mpr0:  port 0x7000-0x70ff mem 
0xb800-0xb80f,0xb7f0-0xb7ff,0xb7e0-0xb7ef at device 0.0 
numa-domain 0 on pci7
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting

There is about a 4 second pause between each of the "in fault state, resetting"
lines.
 
This may not be a freebsd-stable converstion any longer.  I'm going to
switch over to freebsd-drivers, unless someone has a suggestion of a
better list for trying to figure out if small adjustments can be made to
the mpr driver to accept this device.

Thanks all.

 - Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI ISO boot not working in 12.1 ?

[Chris Ross]

On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote:
> 
> Hi there.  I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system
> here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso
> did work on that same system.  [Systems were configured to boot in UEFI mode]
> 
> And continues on from there.   However, the attempt to boot 12.1-RELEASE
> never loads the loader and allows it to boot.  The console output
> for 12.1-RELEASE is below.  Can anyone help me figure out if it's something
> I need to do?  How has 12.1 changed w.r.t. 12.0 for UEFI?

More information.  A stable/12 ISO that I built fails in the same way the
12.1-RELEASE ISO did.  But, I just grabbed releng/12.0, and built a release
ISO, and it boots.  So, something seems definately to have changed in the way
the UEFI bits are on the boot ISOs?  Or maybe a change in the loader?  
Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12.

Let me know what to try next.

- Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI ISO boot not working in 12.1 ?

[Chris]

On Wed, 6 Nov 2019 14:17:11 -0500 Chris Ross cross+free...@distal.com said


Hi there.  I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system
here, which didn't work, and I found that
FreeBSD-12.0-RELEASE-amd64-disc1.iso
did work on that same system.  Another [older] system I had was working with
FreeBSD-12.1-RELEASE-amd64-disc1.iso, but after I had reason to change that
older system to UEFI boot mode, I found it also would not boot the 12.1 
ISO any longer


A successul UEFI boot of 12.0-RELEASE-amd64-disc1 shows many lines of EFI
information to the console, and nearing the bottom:

  BootOrder: 0001 0002 0003 0004[*]
  BootInfo Path:
PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1)
  BootInfo Path: VenHw(,)
Ignoring Boot0004: No Media Path
Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)
Setting currdev to cd3:
-

And, that last line is a spinning cursor, after which becomes:

Loading /boot/defaults/loader.conf

And continues on from there.   However, the attempt to boot 12.1-RELEASE
never loads the loader and allows it to boot.  The console output
for 12.1-RELEASE is below.  Can anyone help me figure out if it's something
I need to do?  How has 12.1 changed w.r.t. 12.0 for UEFI?

The 12.1-RELEASE shows the same as above until starting with "Trying ESP":

Trying ESP:
PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1)
Setting currdev to cd4:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x1)
Setting currdev to cd0:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x2)
Setting currdev to cd1:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)
Setting currdev to cd2:
Trying:
PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x0)
Setting currdev to cd3:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x4)
Setting currdev to cd5:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x5)
Setting currdev to cd6:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x6)
Setting currdev to cd7:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x7)
Setting currdev to cd8:
Failed to bind bootable partition
press any key to interrupt reboot in 5 seconds

Let me know why 12.1-RELEASE is not behaving the same way on my systems...

Thank you.

       - Chris


Not trying to hijack this thread,
But on a similar note; Wile I'm able to boot/install from them.
None of the October (12.1) install images will produce a bootable install.
So I'm stuck on RELENG-12. This is on a Core 13 second gen.
IOW my problem is the inverse of yours.

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

UEFI ISO boot not working in 12.1 ?

[Chris Ross]

Hi there.  I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system
here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso
did work on that same system.  Another [older] system I had was working with
FreeBSD-12.1-RELEASE-amd64-disc1.iso, but after I had reason to change that
older system to UEFI boot mode, I found it also would not boot the 12.1 
ISO any longer

A successul UEFI boot of 12.0-RELEASE-amd64-disc1 shows many lines of EFI
information to the console, and nearing the bottom:

   BootOrder: 0001 0002 0003 0004[*]
   BootInfo Path: 
PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1)
   BootInfo Path: VenHw(,)
Ignoring Boot0004: No Media Path
Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)
Setting currdev to cd3:
-

And, that last line is a spinning cursor, after which becomes:

Loading /boot/defaults/loader.conf

And continues on from there.   However, the attempt to boot 12.1-RELEASE
never loads the loader and allows it to boot.  The console output
for 12.1-RELEASE is below.  Can anyone help me figure out if it's something
I need to do?  How has 12.1 changed w.r.t. 12.0 for UEFI?

The 12.1-RELEASE shows the same as above until starting with "Trying ESP":

Trying ESP: 
PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1)
Setting currdev to cd4:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x1)
Setting currdev to cd0:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x2)
Setting currdev to cd1:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)
Setting currdev to cd2:
Trying: 
PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x0)
Setting currdev to cd3:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x4)
Setting currdev to cd5:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x5)
Setting currdev to cd6:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x6)
Setting currdev to cd7:
Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x7)
Setting currdev to cd8:
Failed to bind bootable partition
press any key to interrupt reboot in 5 seconds

Let me know why 12.1-RELEASE is not behaving the same way on my systems...

Thank you.

    - Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

On Wed, Nov 06, 2019 at 08:44:35AM +1100, Dewayne Geraghty wrote:
> Chris,
> After you've booted the kernel, the correct way to load a module that isn't
> already in the kernel, is to:
> kldload mpr
> To check if mpr is loaded, try
> kldstat -v|grep mpr

Thanks for this.  I was able to boot and verify that pci/mpr is already
loaded, and trying "kldload mpr" reports that it's already loaded from the
kernel.  So, device just not recognized.

> However, if you've already placed
> mpr_load="YES" in your /etc/loader.conf and rebooted your device, then you
> probably need to move into a diagnostic phase.

Yeah.  I think I see what PCI id is missing in the driver, after digging
around in the sources.  I was just hoping it was a process/human error.
I'll get another machine running a build, and see if I can stub it in.

Thanks all.

 - Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

On Tue, Nov 05, 2019 at 12:29:00PM -0800, Freddie Cash wrote:
> > I tried "load", but wasn't able to devine how to load the mpr module with
> > that.  Is that needed, or should 'mpr_load="YES"' have accomplished the
> > desired result?
> 
> modulename_load="YES" is the syntax used in the loader.conf file.
> "load modulename" (without the quotes) is the syntax used at the loader
> prompt.
> 
> So at the loader prompt, try the following:  load mpr
> Or possibly:  load mpr.ko
> Or, to get right finicky:  load /boot/kernel/mpr.ko

Thanks Freddie and Miroslav.

I tried "load mpr" earler, but it complained it couldn't find it.  I tried
again a few minutes ago using "load /boot/kernel/mpr.ko", which spun for
a bit then complained it couldn't load it before the kernel.  I then
loaded the kernel (by full path), and tried again, with no response.  Just
an immediate prompt.  I tried "load /boot/kernel/zfs.ko" as well, in case
mpr.ko was already still in memory, but that also returned an immediate prompt
without saying anything.  So, I think I still have something wrong with my
attempts to "load".  Should loading the mpr.ko before the kernel work?  It
didn't with my last attempt (which I realize now was 12.0-RELEASE,
not 12.1-RELEASE).

   - Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

On Tue, Nov 05, 2019 at 08:20:15PM +0100, Miroslav Lachman wrote:
> Chris Ross wrote on 11/05/2019 19:34:
> > Hello.  I have a Cisco UCS C220-M5 with a RAID controller.  It calls itself
> > "Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5.
> > Looking at the CIMC, it shows the PCI vendor/device ids 1000:0014, which
> > looks to be an LSI MegaRAID Tri-Mode SAS3516.  It looks like this should
> > be supported by the mpr(4) driver, but it doesn't seem to recognize it
> > at boot time.
> 
> Do you have mpr_load="YES" in loader.conf?
> Or for ISO booting you can manually load kernel modules at boot prompt.

I dropped to boot prompt in ISO boot, and entered 'mpr_load="YES"'.

I tried "load", but wasn't able to devine how to load the mpr module with
that.  Is that needed, or should 'mpr_load="YES"' have accomplished the
desired result?

  - Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Cisco 12G SAS RAID support (FreeBSD 12.1-RELEASE) ?

[Chris Ross]

Hello.  I have a Cisco UCS C220-M5 with a RAID controller.  It calls itself
"Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5.
Looking at the CIMC, it shows the PCI vendor/device ids 1000:0014, which
looks to be an LSI MegaRAID Tri-Mode SAS3516.  It looks like this should
be supported by the mpr(4) driver, but it doesn't seem to recognize it
at boot time.  Is there some magic I need to perform for the 12.1-RELEASE
image ISO boot to get this driver loaded, or will some internal changes
be needed to support this particular part due to quirks?

Let me know any information I can provide that will help diagnose.  Thank
you.

      - Chris

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: P5 bork

[Chris]

hahaha.. So I gotta patch the patch with a patch if its patched 
already.  :)


On 5/15/2019 11:56 PM, Chris wrote:

Thank you Pete :)

On 5/15/2019 10:58 PM, Pete Wright wrote:



On 5/15/19 10:15 PM, Chris wrote:
I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at 
home doing DoT TLS1.3


Thats all I do on the machine. Its a very clean boring typical 
install. X86.


FreeBSD-update fetch
freebsd-update install
reboot

BORKED. Just loops duing boot.

Backed up to kernal.old - works perfect..

If anyone cares I could go grab logs and things, but, I would assume 
this is already known and I will just wait for P6, hehehe..


Sorry im not deeper on the subject.


should be fixed now:
https://www.freebsd.org/security/advisories/FreeBSD-SA-19:07.mds.asc

"v2.0 2019-05-15 Rerelease 12.0-RELEASE patch as -p5 due to i386 
panic bug."


-pete





___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: P5 bork

[Chris]

Thank you Pete :)

On 5/15/2019 10:58 PM, Pete Wright wrote:



On 5/15/19 10:15 PM, Chris wrote:
I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at 
home doing DoT TLS1.3


Thats all I do on the machine. Its a very clean boring typical 
install. X86.


FreeBSD-update fetch
freebsd-update install
reboot

BORKED. Just loops duing boot.

Backed up to kernal.old - works perfect..

If anyone cares I could go grab logs and things, but, I would assume 
this is already known and I will just wait for P6, hehehe..


Sorry im not deeper on the subject.


should be fixed now:
https://www.freebsd.org/security/advisories/FreeBSD-SA-19:07.mds.asc

"v2.0 2019-05-15 Rerelease 12.0-RELEASE patch as -p5 due to i386 panic 
bug."


-pete



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

P5 bork

[Chris]

I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at home 
doing DoT TLS1.3


Thats all I do on the machine. Its a very clean boring typical install. 
X86.


FreeBSD-update fetch
freebsd-update install
reboot

BORKED. Just loops duing boot.

Backed up to kernal.old - works perfect..

If anyone cares I could go grab logs and things, but, I would assume 
this is already known and I will just wait for P6, hehehe..


Sorry im not deeper on the subject.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS...

[Chris]

Sorry t clarify, Michelle I do believe your tail of events, just I
meant that it reads like a tale as its so unusual.

I also agree that there probably at this point of time should be more
zfs tools written for the few situations that do happen when things
get broken.

Although I still standby my opinion I consider ZFS a huge amount more
robust than UFS, UFS always felt like I only had to sneeze the wrong
way and I would get issues.  There was even one occasion simply
installing the OS on its defaults, gave me corrupted data on UFS (9.0
release had nasty UFS journalling bug which corrupted data without any
power cuts etc.).

In future I suggest you use mirror if the data matters.  I know it
costs more in capacity for redundancy but in todays era of large
drives its the only real sensible option.

On the drive failures you have clearly been quite unlucky, and the
other stuff is unusual.

Best of luck

On Sat, 4 May 2019 at 09:54, Pete French  wrote:
>
>
>
> On 04/05/2019 01:05, Michelle Sullivan wrote:
> > New batteries are only $19 on eBay for most battery types...
>
> Indeed, my problem is actual physical access to the machine, which I
> havent seen in ten years :-) I even have a relacement server sitting
> behind my desk which we never quite got around to installing. I think
> the next move it makes will be to the cloud though, so am not too worried.
>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS...

[Chris]

Your story is so unusual I am wondering if its not fiction, I mean all
sorts of power cuts where it just so happens the UPS fails every time,
then you decide to ship a server halfway round the world, and on top
of that you get a way above average rate of hard drive failures.  But
aside from all this you managed to recover multiple times.

ZFS is never claimed to be a get out of jail free card, but it did
survive in your case multiple times, I suggest tho if you value
redundancy, do not use RAIDZ but use Mirror instead.  I dont know why
people keep persisting with raid 5/6 now days with drives as large as
they are.

I have used ZFS since the days of FreeBSD 8.x and its resilience
compared to the likes of ext is astounding and especially compared to
UFS.

Before marking it down think how would UFS or ext have managed the
scenarios you presented in your blog.

Also think about where you hosting your data with all your power
failures and the UPS equipment you utilise as well.

On Mon, 29 Apr 2019 at 16:26, Michelle Sullivan  wrote:
>
> I know I'm not going to be popular for this, but I'll just drop it here
> anyhow.
>
> http://www.michellesullivan.org/blog/1726
>
> Perhaps one should reconsider either:
>
> 1. Looking at tools that may be able to recover corrupt ZFS metadata, or
> 2. Defaulting to non ZFS filesystems on install.
>
> --
> Michelle Sullivan
> http://www.mhix.org/
>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

[Chris Rees]

Hi people, (and thanks Alan for copying me in)

On 2018-12-17 01:42, Mark Linimon wrote:

On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote:

I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC)
on my eMac.


I don't know of anyone else who has tried to run it.

The server-class ports on powerpc64 have been in good shape for several
years.  However, the desktop ports are lagging way behind.  For 
instance,
we are still working to get gnome and kde working properly.  Other 
desktop
environments are going to require more people to take up working on 
them.


I personally would like to see powerpc64 ports at (near-) parity with
amd64, but we have a lot of work to go yet.


I'm not sure if it's supported on PowerPC at all anyway by the 
developers (although obviously it used to work, perhaps not on FreeBSD 
though).


Was it a straightforward error?

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Can't upgrade past 10.4-STABLE (interrupt storm?)

[Chris H]

Hello,
I've got an older laptop that I attempted to install 12 on w/o success.
Well, it installed. But was unusable. Typing anything at the console
frequently doesn't output on the screen w/o tapping one of the arrow
keys. But doing that causes other problems. As I can't really use the
output. :(
I suspected an interrupt storm of some type. But really can't say for
sure. a vmstat -i seems to show unusually high numbers for irq1: atkbd0
often ~1/3rd the number for CPU0. I can easily realize all this during
the install process from the install media. So it's easy to test.
This is a i386 based Pentium M. FreeBSD 10.4-STABLE runs like a dream.
But I'm going to need to move forward at some point, and I'd like that
some point to be now. :)
Any thoughts on how I might discover /what/ change was made from
10.4-->11* to cause this?
It has a trackpad. Should that make any difference.

Thanks!

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: jail related inconsistencies in FreeBSD tools parameters

[Chris H]

On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.f...@quip.cz> said

I don't know if it is better to discuss it in jail@ or stable@ list so a 
do cross-post.


FreeBSD has many jail aware utilities but they are inconsistent in 
taking JID as parameter.


For example "sockstat" takes -j JID "Show only sockets belonging to the 
specified jail ID" and it means numeric ID only.
On the other hand "ps" takes -J JID "This may be either the jid or name 
of the jail.  Use -J 0 to display only host processes."
The same apply for "top", it understands jid as a number or name of the 
jail too.

Then again "cpuset" takes only numerical ID of the jail...

Shouldn't it be consistent across all FreeBSD base utilities so all of 
them can use numerical ID and name?

Good idea! Are you offering to create a patch? ;-)
It'd be my guess that given they weren't all created at the same time, nor
the same individual; that (quite probably?) the "jail" additions were also
added at different times, and by different people. So I'd imagine that
unless someone with a commit bit decides one day they'd like to take that
on. Someone(tm) maybe you? will need to propose a patch. :-)

--Chris


Should I file a PR for it?

Miroslav Lachman

PS: I am on FreeBSD 10.4 so I don't know if something is different in 
newer branches

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Console is broken after updating to 11.2-RELEASE

[Chris H]

On Fri, 22 Jun 2018 20:42:18 +0900 (JST) "Yasuhiro KIMURA"  
said


From: Warner Losh 
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 05:03:43 -0600

> UEFI or legacy boot? Is a BMC involved?

Legacy boot. And BMC is not involved.

Try adding the following to your loader.conf(5) file (/boot/loader.conf):

# Load SysCons driver
kern.vty=sc
# noisy boot
boot_verbose="YES"

Hope this helps!

--Chris


---
Yasuhiro KIMURA
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Two NIC's inside a Jail

[Chris Kiakas]

Hi,

Sorry that I am coming to the conversation a little late. I have several 
systems Which run with multiple IP connections where the jail responds to 
multiple IPs

I set /etc/rc.conf to just control the ips of the host.  as an example;

ifconfig_igb1="inet AAA.AAA.AAA.1 netmask 255.255.255.0"
defaultrouter=“AAA.AAA.AAA.1”
ifconfig_igb2="inet 192.168.10.1 netmask 255.255.255.0"
ifconfig_igb4="UP"
ifconfig_igb5="UP"
ifconfig_igb6="UP"
ifconfig_igb7="UP"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport igb4 laggport igb5 laggport igb6 
laggport igb7 192.168.12.14/24”


The jail is then set with it’s jail.conf file as such;
jailname {
host.hostname   =  “jailname";
ip4.addr=  “igb1|AAA.AAA.AAA.2/24”;
ip4.addr+= “igb2|192.168.10.21/24”;
ip4.addr+=  "lagg0|192.168.12.32/24";
path=  "/usr/jail/jailname";
exec.start  =  "/bin/sh /etc/rc";
exec.stop   =  "/bin/sh /etc/rc.shutdown";
exec.consolelog =  "/var/log/jail.jailname.console.log";
mount.devfs;
}


My interfaces are igb# your's are em0
Apache is set to listen to;

Listen :80

If the Apache setup is not complex it should just work on all IP. If you are 
running vhosts you will need to specify ServerName and/or ServerAliases in 
apache.

If the jail requires a different gateway than the defaultrouter then you will 
need to setup fibs.


Chris


> On Mar 23, 2018, at 3:17 PM, joerg_surmann <joerg_surm...@elektropost.org> 
> wrote:
> 
> Hi,
> 
> thanks for yor help.
> 
> I can't find a solution.
> 
> But i have find a starnge ip config.
> 
> in rc.conf on Host(not jail)
> 
> ifconfig_vmx0_alias1="inet 192.168.100.2  netmask 255.255.255.0"
> ifconfig_em0="inet 213.70.80.92 netmask 255.255.255.0"
> 
> ifconfig on host say:
> inet 213.70.80.92 netmask 0x broadcast 213.70.80.92
> inet 192.168.100.2  netmask 0x broadcast 192.168.100.2
> 
> ifconfig say to both ip's /32.
> 
> Maby that's the reason for unavailable the apache.
> 
> ifconfig iside the jail say the same.
> 
> I'm a little bit confused.
> 
> 
> 
> Am 23.03.2018 um 18:25 schrieb Marek Zarychta:
>> On Fri, Mar 23, 2018 at 04:01:30PM +0100, Joerg Surmann wrote:
>>> Hi all,
>>> 
>>> I have a Problem to understund how to manage 2 Networks inside a Jail.
>>> 
>>> i have create a jail (using ezjail) with a alias IP.  in rc.conf (on
>>> Host):
>>> 
>>> ifconfig_vmx0="inet 192.168.100.1 netmask 255.255.255.0"
>>> ifconfig_vmx0_alias0="inet 192.168.100.2 netmask 255.255.255.0"  <-
>>> this is the jail ip
>>> 
>>> Inside the jail running apachhe24.
>>> 
>>> Now i add a new NIC to the System.  in rc.conf (on Host):
>>> ifconfig_em0="inet 213.70.80.92 netmask 255.255.255.0"
>>> 
>>> in /usr/local/etc/ezjail/myjail.conf: i add the new ip export
>>> jail_myjail_ip="192.168.100.2,213.70.80.92"
>>> 
>>> Restart the jail and ifconfig looks fine.  vmx0 -> inet 192.168.100.2
>>> em0  -> inet 213.70.80.92
>>> 
>>> Apache Listen on all NIC's () But i can see my
>>> Website only via 192.168.100.2 from intern Network.
>>> 
>>> The Host is behind a Firewall.  The IP  213.70.80.92 is enabled for
>>> incomming Traffic.
>>> 
>>> When i give the Hostname in a Browser i become "connection Timeout".
>>> 
>>> What is to do that the Host is accessable from Inet?
>>> 
>> Hi Joerg,
>> 
>> I guess your host has default gw reachable via vmx0 and second interface
>> em0 is connected and was reachable at least from firewall protecting
>> address 213.70.80.92? If it is true then you should add:
>> 
>> to /usr/local/etc/ezjail/myjail.conf
>> export jail_myjail_ip="lo1|127.0.1.1,vmx0|192.168.100.2,em0|213.70.80.92"
>> export jail_myjail_fib="1"
>> 
>> to /etc/rc.conf
>> static_routes="net_jails"
>> route_net_jails="default 213.70.80.x -fib 1"
>> 
>> to /boot/loader.conf
>> net.fibs="2"
>> 
>> Eventually take a look at setfib(1) and also consider migrating em
>> adapter to second vmx which shuld be faster and more flexible.
>> 
>> IMHO this questions should be asked rather on freebsd-net list than
>> here.
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: Odd behaviour on recent boot of 11.1 with timecounters

[Chris H]

On Tue, 2 Jan 2018 16:45:26 + "Gary Palmer"  said


On Sun, Dec 31, 2017 at 06:47:38PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 31, 2017 at 03:49:13PM +, Gary Palmer wrote:
> > On Sun, Dec 31, 2017 at 04:51:47PM +0200, Konstantin Belousov wrote:
> > > On Sun, Dec 31, 2017 at 02:17:08PM +, Gary Palmer wrote:
> > > > 
> > > > Hi,
> > > > 
> > > > I recently updated to 11.1-RELEASE-p6 and on the most recent reboot 
> > > > (after rebuilding all the necessary packages) the clock was running 
> > > > slow and NTP wouldn't sync.  I looked in /var/log/messages and I found

> > > > that for some reason, on this latest boot, it got the frequency of
> > > > TSC-low wrong.
> > > > 
> > > > Aug 24 04:55:35 my kernel: Timecounter "TSC-low" frequency 1746073190

> Hz quality 1000
> > > > Aug 26 03:11:38 my kernel: Timecounter "TSC-low" frequency 1746070760
> Hz quality 1000
> > > > Aug 26 14:12:46 my kernel: Timecounter "TSC-low" frequency 1746075204
> Hz quality 1000
> > > > Nov 19 16:01:09 my kernel: Timecounter "TSC-low" frequency 1746070746
> Hz quality 1000
> > > > Dec 27 22:28:00 my kernel: Timecounter "TSC-low" frequency 1746074808
> Hz quality 1000
> > > > Dec 27 22:51:12 my kernel: Timecounter "TSC-low" frequency 1746071892
> Hz quality 1000
> > > > Dec 28 12:50:46 my kernel: Timecounter "TSC-low" frequency 1746069704
> Hz quality 1000
> > > > Dec 28 14:03:52 my kernel: Timecounter "TSC-low" frequency 1937876448
> Hz quality 1000
> > > > 
> > > > Until the December reboots the machine was running 10.x.  Dec 27 and

> later
> > > > are part of the process to get up to 11.x.
> > > > 
> > > > Any idea why the TSC-low frequency jumped 191,806,744Hz on the last

> > > > measurement?
> > > > 
> > > > I switched to HPET temporarily via sysctl and ntp seems happy.  I'm

> just
> > > > concerned that the problem might recur on later reboots as TSC-low
> seems
> > > > to be the preferred timecounter.
> > > 
> > > Show first 100 lines of the dmesg from a verbose boot.

> > > Also check BIOS settings related to overclocking and powersaving.
> > > 
> > 
> > Hi Konstantin,
> > 
> > BIOS settings haven't been changed in 4+ years.  No overclocking, and

> > all powersaving options are at "auto" or "disabled".
> > 
> > The first 100 lines of verbose dmesg didn't seem that interesting so

> > I've included up to the end of "Device configuration finished"
> > 
> > Note that this boot didn't have the TSC-low problem, and the boot

> > that had it wasn't verbose unfortunately.
> 
> It is really the CPU identification which I wanted to see.  You have

> IvyBridge, which is known to have good TSC.

Ah

> Try to obtain verbose dmesg with mis-identified frequency.

Tried, and failed after 20+ reboots.  I've left

boot_verbose=" -v"

I believe that should read:

boot_verbose="YES"
but maybe just the occurrence of something makes it a positive.



in /boot/loader.conf to catch any boot-time wonkiness and undone it at
runtime with 


debug.bootverbose=0

in /etc/sysctl.conf as I found that the snd_hda driver is ... chatty
at runtime.

Thanks,

Gary
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: D-Link DGE530T issue

[Chris H]

On Wed, 15 Nov 2017 23:00:33 +0300 Mike Black <amdm...@gmail.com> wrote

> Hello
> 
> I've got old PCI NIC D-Link DGE530T Rev 11 with SysKonnect chip on it.
> Years ago it worked in FreeBSD 8/9 Stable with if_sk driver.
> 
> Now I'm runnig
> 11.1-STABLE FreeBSD 11.1-STABLE #1 r323214: Sat Nov 11 19:06:20 MSK 2017
>  amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64  amd64 1101502
> 1101502
> 
> But recently I plugged this card back and it's not being recognized by a
> driver.
> 
> pciconf says that is
> none0@pci0:5:1:0:   class=0x02 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
> vendor = 'J. Bond Computer Systems'
> class  = network
> subclass   = ethernet
> bar   [10] = type Memory, range 32, base 0xfebec000, size 16384, enabled
> bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
> cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> cap 03[50] = VPD
> 
> According /usr/share/misc/pci_vendors this D-link should have 4b011186 not
> 4b011086.
Just a hunch; But maybe it was simply a typo?
You can probably omit the additional "1" on your local copy of the source,
and try to build it again. My guess is you'll have success.
NOTE: I'm not an authority on this driver. I'm only attempting to
provide a possible solution. :)

If you *are* successful. I would advise opening a PR for this. :)

--Chris
> I looked into driver code  (if_sk) and it expects 1186 card also.
> I googled about this issue but found no one similar in a recent years
> So I'd like to know what's wrong - some changes in driver in a recent years
> or smth going wrong while OS detecting this NIC. But that's confusing,
> because this exact NIC worked years ago...
> 
> -- 
> amd_miek
> Think different.
> Just superior.
> 
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaig
> n=sig-email_content=webmail> Без
> вирусов. www.avast.ru
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaig
> n=sig-email_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: console-only freebsd

[Chris H]

On Sat, 7 Oct 2017 09:49:40 -0700 Freddie Cash <fjwc...@gmail.com> wrote

> On Oct 7, 2017 7:21 AM, "tech-lists" <tech-li...@zyxst.net> wrote:
> 
> Hi,
> 
> I have a freebsd 11-stable installation on a (gutless) netbook. What I'd
> like is full functionality via the console[1]. One of the things it needs
> is some graphics capability but without xorg. So I'm thinking, svga or
> libSDL. For example, let's say to view a jpg file. If this is possible from
> the console, what program or port would one use to view a gif or jpg file?
> 
> [1] by console, I mean the consoles accessed via alt-f1 to alt-f7 [2]
> [2] can the number of consoles be increased?
> 
> 
> Tmux or screen will give you an unlimited number of virtual terminals using
> only a single TTY. And give you the ability to split the console into
> multiple windows.

You might also find this article by Warren Block of value:

http://www.wonkity.com/~wblock/docs/html/hiresconsole.html

--Chris
> 
> Cheers,
> Freddie
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Mirror the freebsd-update server?

[Chris Gordon]

> On Sep 12, 2017, at 11:03 AM, rai...@ultra-secure.de wrote:
> 
> Hi,
> 
> is it possible or even allowed to just mirror one of the freebsd-update 
> servers locally?
> 
> I don't want to build the patches myself (I have no custom kernels, but best 
> I can do is not completely f' it up - so why bother?).
> 
> I have between 100 und 200 servers that need updates - and on upgrades, it 
> kind of pulls on my nerves.
> 
> 
> Unfortunately, I'm not in a position to cache them via squid or so.

Take a look at https://www.freebsd.org/doc/en/articles/hubs/index.html.  This 
doc discusses setting up a mirror (found via quick Google search).

Chris  
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Chris Rees]

Cassiano Peixoto wrote:

Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
with when I need to restart a service without upgrading? Reaper
functionnality is a trouble for many administrators who made meta ports to
manage their servers. I really think it could be a option to be
enabled/disabled. Can you see this possibility?

Thanks.

On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin <b...@freebsd.org>
wrote:


On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote:

Hi Baptiste,

Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.

It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in
freebsd
kernel appeared in 10.2

Cron is just an example, I manage more than 50 FreeBSD servers, and I've
been using ports for years to update some configs and restart the service
on all of them. Many times I need to change nginx config, ldap, etc. I

just

need to restart the service.

HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart
anything rc script provide once the package containing it is upgrading.

This is off by default because in many cases it is dangerous (database
upgrades,
dovecot like things upgrade etc). But if you know what you are doing it
does the
job.

Best regards,
Bapt





Hey,

I think you also want process supervision given your other comments.  
You can do this easily using daemon -P to run your scripts (but you'd 
need to rewrite the rc script...)


Or use runit or similar?  You could implement "runlevels" with that if 
that's REALLY what you want :)


Cheers,

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pefs not working

[Chris Watson]

Pefs is in ports under security I believe. Gleb wrote it several years ago. I 
don't know if he is maintaining it or someone else now but a quick look at the 
Makefile for it in ports should tell you who to bug about you're problem. 

Chris 
http://open-systems.net

Sent from my iPhone 5

> On Jul 6, 2017, at 5:14 PM, Kevin Oberman <rkober...@gmail.com> wrote:
> 
>> On Thu, Jul 6, 2017 at 12:32 PM, Walther <walt...@rodconit.com> wrote:
>> 
>> Hello
>> Testing FreeBSD 11.1 RC1 i386 version I found the following:
>> I am not able to load pefs (pefs.ko) I am not receiving an error but it
>> can not be loaded
>> I added pefs_load="YES" to the /boot/loader.conf and I also tried running
>> kldload but it ois always failing
>> Thanks
>> 
>> Walther
>> 
> 
> pefs does not seem to be part of the base OS. Is it installed by a port?
> And, if so, which one?
> 
> If it is installed from  port, it MUST be rebuilt when the kernel is
> updated. It may be installed as a package only if you are running a RELEASE
> version and release candidates are not releases, so you MUST rebuild them
> from sources.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Compile-time check for clock_nanosleep()

[Chris Ross]

> On Jul 3, 2017, at 14:46, Kurt Jaeger <li...@opsec.eu> wrote:
> 
> Use __FreeBSD_version from sys/param.h:
> 
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/versions.html

  Thanks.  That looks great.  Also, for my specific case of the addition of 
clock_nanosleep(), it looks from time.h like I could use "__POSIX_VISIBLE >= 
200112”.  Maybe that isn’t safe, since later looking at time.h on 11.0 and on 
11.1, the latter has a definition for clock_nanosleep() in that block, but the 
former does not.

  Yeah, digging around it appears that stable/11/sys/sys/param.h at r316498 had 
__FreeBSD_version at 1100512, and it was raised to 1100513 in revision 318197.  
And, clock_nanosleep was MFC’d into 11-stable in-between the two, at revision 
317618.  So, not a precise match there, but >= 1100513 should be safe.

  Thanks!

  - Chris



signature.asc
Description: Message signed with OpenPGP

Compile-time check for clock_nanosleep()

[Chris Ross]

  Some time ago, I ported a linux program that was using clock_nanosleep().  I 
see now that the extra code I’d put in isn’t needed anymore in 11-stable, as it 
appears this call was added in 11.1.  My question is, to properly protect these 
changes, what is the best way to know at compile time, either (a) that that 
call is in libc, or (b) that I’m compiling on FreeBSD 11.1 or later ?

  Thanks.

   - Chris


signature.asc
Description: Message signed with OpenPGP

Re: CAM timeouts at startup

[Chris H]

): READ(10). CDB: 28 00 6f c8 1a af 00 00 01 00 
> (da6:mpr0:0:25:0): CAM status: Command timeout
> (da6:mpr0:0:25:0): Retrying command
> (da6:mpr0:0:25:0): READ(10). CDB: 28 00 6f c8 1a af 00 00 01 00 
> (da6:mpr0:0:25:0): CAM status: SCSI Status Error
> (da6:mpr0:0:25:0): SCSI status: Check Condition
> (da6:mpr0:0:25:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset,
> or bus device reset occurred) (da6:mpr0:0:25:0): Retrying command (per
> sense data) (noperiph:mpr0:0:4294967295:0): SMID 6 Aborting
> command 0xfe0002617fa0 mpr0: Sending reset from mprsas_send_abort for
> target ID 26 mpr0: Unfreezing devq for target ID 26
> (da7:mpr0:0:26:0): READ(10). CDB: 28 00 6f c8 1a af 00 00 01 00 
> (da7:mpr0:0:26:0): CAM status: Command timeout
> (da7:mpr0:0:26:0): Retrying command
> (da7:mpr0:0:26:0): READ(10). CDB: 28 00 6f c8 1a af 00 00 01 00 
> (da7:mpr0:0:26:0): CAM status: SCSI Status Error
> (da7:mpr0:0:26:0): SCSI status: Check Condition
> (da7:mpr0:0:26:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset,
> or bus device reset occurred) (da7:mpr0:0:26:0): Retrying command (per
> sense data) 
>
> 
> --
> Mahlon E. Smith  

In the past, when I've run into this issue. I add the following to
loader.conf(5)

kern.cam.boot_delay=""
You'll want to tune it to find a "sweet spot".
fe; on one of my boxes, it reads:
kern.cam.boot_delay="7000"
which is 7 seconds.

HTH

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: if_iwm crashes kernel when loaded from /boot/loader.conf

[Chris H]

On Fri, 07 Apr 2017 14:38:40 + Tommi Pernila <tommi.pern...@gmail.com>
wrote

> On Fri, 7 Apr 2017 at 16.27, Tomasz CEDRO <to...@cedro.info> wrote:
> 
> > Hello,
> >
> > I noticed a problem when loading if_iwm from /boot/loader.conf kernel
> > crashes as it cannot load module firmware dead loop occurs. Adding
> > iwm8000Cfw before if_iwm does not help.
> >
> > Loading if_iwm on a running system works fine and gives operational wifi.
> >
> > Intel Corporation Wireless 8260 class=0x028000 card=0x10108086
> > chip=0x24f38086 rev=0x3a hdr=0x00
> >
> > --
> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> 
> 
> This has been happening to my Intel 8260 as well.
> It seems to be a known bug.
Has anyone opened a pr(1)?
At least that way, it would be recorded as a problem.

--Chris
> 
> I circumvent it by manually loading the wifi modules after boot. This
> doesn't crash the system.
> 
> As a dirty hack? You could add the loading as a script and automatically
> load the modules when the FreeBSD is fully up and running.
> 
> Br,
> 
> Tommi
>


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: how can I make freebsd wait for usb to become active? Or delay mountroot?

[Chris H]

On Mon, 13 Feb 2017 19:00:39 + tech-lists  wrote

> Hello stable@,
> 
> system: 11-stable r313553
> 
> In the kernel there is an option for scsi delay.
It should be enough to bump the kern.cam.scsi_delay=
a couple hundred at a time, until you find the "sweet spot".
You might also try the autoboot_delay= option instead. It
might give your USB port enough time to come ready.

> Is there also one for
> usb? Perhaps not in the kernel but elsewhere. I can't find it.
> 
> The problem is seen especially where the bootable device is usb. The
> boot process starts and dumps me at mountroot where I wait for a short
> time until the usb stick is properly detected (bright white writing at
> the console). The usb stick is plugged into a usb3 port. For example:
> 
> [snip]
> 
> usbus0: 5.0Gbps Super Speed USB v3.0
> usbus1: 12Mbps Full Speed USB v1.0
> usbus2: 480Mbps High Speed USB v2.0
> usbus3: 12Mbps Full Speed USB v1.0
> ugen0.1: <0x1022 XHCI root HUB> at usbus0
> uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
> ugen1.1:  at usbus1
> uhub1:  on usbus1
> ugen2.1:  at usbus2
> uhub2:  on usbus2
> ugen3.1:  at usbus3
> uhub3:  on usbus3
> usbus4: 480Mbps High Speed USB v2.0
> ugen4.1:  at usbus4
> uhub4:  on usbus4
> acpi_tz0: _CRT value is absurd, ignored (255.1C)
> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
> ada0:  ACS-2 ATA SATA 3.x device
> cd0 at ahcich1 bus 0 scbus1 target 0 lun 0
> cd0:  Removable CD-ROM SCSI device
> cd0: Serial Number 1415TP277450E0H6H
> cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> - tray open
> ada0: Serial Number JA1006103G0ALV
> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 953869MB (1953525168 512 byte sectors)
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #2 Launched!
> Timecounter "TSC" frequency 1597045198 Hz quality 1000
> Trying to mount root from ufs:/dev/da0p2 [rw]...
> uhub3: 5 ports with 5 removable, self powered
> uhub1: 5 ports with 5 removable, self powered
> uhub0: 4 ports with 4 removable, self powered
> Root mount waiting for: usbus4 usbus2 usbus0
> ugen0.2:  at usbus0
> umass0 on uhub0
> umass0: 
> on usbus0
> umass0:  SCSI over Bulk-Only; quirks = 0x8100
> umass0:3:0: Attached to scbus3
> uhub2: 5 ports with 5 removable, self powered
> uhub4: 5 ports with 5 removable, self powered
> ugen0.3:  at usbus0
> ukbd0 on uhub0
> ukbd0:  on usbus0
> kbd2 at ukbd0
> Root mount waiting for: usbus4
> ugen4.2:  at usbus4
> mountroot: waiting for device /dev/da0p2...
> Mounting from ufs:/dev/da0p2 failed with error 19.
> 
> Loader variables:
>   vfs.root.mountfrom=ufs:/dev/da0p2
>   vfs.root.mountfrom.options=rw
> 
> Manual root filesystem specification:
>   : [options]
>   Mount  using filesystem 
>   and with the specified (optional) option list.
> 
> eg. ufs:/dev/da0s1a
> zfs:tank
> cd9660:/dev/cd0 ro
>   (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
> 
>   ?   List valid disk boot devices
>   .   Yield 1 second (for background tasks)
>   Abort manual input
> 
> mountroot> Trying to mount root from ufs:/dev/da0p2 []...
> mountroot: waiting for device /dev/da0p2...
> Mounting from ufs:/dev/da0p2 failed with error 19.
> 
> mountroot>
> 
> [snip]
> 
> Then this happens:
> 
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: < USB DISK 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
> da0: Serial Number 070B4722335D3288
> da0: 400.000MB/s transfers
> da0: 30176MB (61800448 512 byte sectors)
> da0: quirks=0x3
> 
> so now at the mountroot prompt I enter ufs:/dev/da0p2 (which is a value
> that mountroot already had) and carry on booting:
> 
> mountroot> Trying to mount root from ufs:/dev/da0p2 []...
> re0: link state changed to DOWN
> re0: link state changed to UP
> ums0 on uhub0
> ums0:  on usbus0
> ums0: 16 buttons and [XYZT] coordinates ID=2
> uhid0 on uhub0
> uhid0:  on usbus0
> 
> [...]
> 
> The same sort of thing happens on an 11-stable r313043 desktop, only
> this time I'm not booting from usb. The system comes up, I get a login
> prompt, then five or ten seconds later usb wakes up having detected the
> usb3 external HD.
> 
> How can I fix this?
> 
> thanks,
> -- 
> J.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send 

Re: pkg upgrade problem with Perl 5.24

[Chris H]

On Fri, 13 Jan 2017 16:38:59 + Matthew Seaman <matt...@freebsd.org> wrote

> On 2017/01/13 16:31, Chris H wrote:
> > As a general rule:
> > install from pkg(8) remove with pkg(8)
> > install from ports(7), remove with ports(7)
> > 
> 
> Sorry -- this is completely bogus.
Not entirely.

>  You can freely mix and match either
> way. Just make sure that the package names match up.
> 
> In fact the ports removes packages using pkg(8), so it all comes down to
> the same thing in the end.
That is the *intended* outcome, to be sure. *But* as noted in the OP[1],
and from some edge cases I've personally run into; the "general rule"
I listed, does apply. :)
> 
> Cheers,
> 
> Matthew

I have now removed the package using pkg delete -f -n perl5-5.24.1.r4_1 and was
then able to install from ports without problems:

[1] root@gw2:/usr/ports/lang/perl5.24 # pkg info perl5.24-5.24.1.r5_1
perl5.24-5.24.1.r5_1
Name   : perl5.24
Version: 5.24.1.r5_1
Installed on   : Thu Jan 12 17:53:45 2017 CET
Origin : lang/perl5.24

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg upgrade problem with Perl 5.24

[Chris H]

On Fri, 13 Jan 2017 15:43:41 + Holger Kipp <holger.k...@alogis.com> wrote

> Dear all,
> 
> I upgraded Perl to 5.24(1.r4_1) (via pkg upgrade).
> When I now try to install the latest version from ports (1.r5_1), the system
> can’t install the new version because of the older version, but can’t
> deinstall(*) the older version (eg. via make deinstall && make reinstall).
> 
> 
> 
> root@gw2:/usr/ports/lang/perl5.24 # pkg info | grep perl
> p5-Data-Dumper-2.161   Stringified perl data structures, suitable for
> both printing and eval p5-Pg-2.1.1_4,1Interface for using
> perl5 to access PostgreSQL databases p5-Scalar-List-Utils-1.45,1Perl
> subroutines that would be nice to have in the perl core perl5-5.24.1.r4_1
>  Practical Extraction and Report Language 
>
> so currently via pkg upgrade I got perl5-5.24.1.r4_1, which perl itself
> confirms: root@gw2:/usr/ports/lang/perl5.24 # perl -v
> 
> This is perl 5, version 24, subversion 1 (v5.24.1) built for
> amd64-freebsd-thread-multi (with 1 registered patch, see perl -V for more
> detail) 
>
> This is then obviously the version from FreeBSD repository.
> 
> If I try to install the latest version from ports (perl5-5.24.1.r5_1), I get
> the following (make install just to get the messages): 
>
> 
> root@gw2:/usr/ports/lang/perl5.24 # make install
> ===>  Installing for perl5.24-5.24.1.r5_1
> ===>  Checking if perl5.24 already installed
> ===>   Registering installation for perl5.24-5.24.1.r5_1
> Installing perl5.24-5.24.1.r5_1...
> pkg-static: perl5.24-5.24.1.r5_1 conflicts with perl5-5.24.1.r4_1 (installs
> files into the same place).  Problematic file: /usr/local/bin/perl5.24.1
> *** Error code 70
> 
> Stop.
> make[1]: stopped in /usr/ports/lang/perl5.24
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/lang/perl5.24
> 
> 
> Deinstalling the existing version does not work:
> 
> root@gw2:/usr/ports/lang/perl5.24 # make deinstall
> ===>  Deinstalling for perl5.24
> ===>   perl5.24 not installed, skipping
> 
> But according to pkg info it is installed:
> 
> root@gw2:/usr/ports/lang/perl5.24 # pkg info perl5
> perl5-5.24.1.r4_1
> Name   : perl5
> Version: 5.24.1.r4_1
> Installed on   : Thu Jan 12 12:51:03 2017 CET
> Origin : lang/perl5.24
> 
> 
> This sees to be a bit strange.
> 
> (*) I have now removed the package using pkg delete -f -n perl5-5.24.1.r4_1
> and was then able to install from ports without problems: 
>
> root@gw2:/usr/ports/lang/perl5.24 # pkg info perl5.24-5.24.1.r5_1
> perl5.24-5.24.1.r5_1
> Name   : perl5.24
> Version: 5.24.1.r5_1
> Installed on   : Thu Jan 12 17:53:45 2017 CET
> Origin : lang/perl5.24
> 
> 
> Any ideas what happened here? I’m not sure if this is expected behaviour.
> 
> Many thanks and best regards,
> Holger
As a general rule:
install from pkg(8) remove with pkg(8)
install from ports(7), remove with ports(7)

That said; I didn't notice any evidence of which version of
FreeBSD, you're running (uname -a) --
It's important where Perl is concerned.

How about make.conf(5)? Anything interesting in there;
DEFAULT_VERSIONS+=
or
WITH_PKGNG=

HTH

--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: suspend/resume on Skylake (Lenovo T460s) with FreeBSD11 stable

[Chris Ernst]

On Wed, Dec 14, 2016 at 05:15:12PM +0100, Chris Ernst wrote:


i have been hardly trying to get my Lenovo T460s to suspend *and to resume
again*.

Eventually the system suspends when i close the lid.
The power LED is slowly blinking on and off.

That is it! I am not able to resume my system anymore.
When I push the power button once the power LED *keeps* slowly blinking on
and off. :(


What was the last revision where suspend/resume worked on your T460s?

Approximately two months ago, I tried the then HEAD of drm-next-4.7
of the FreeBSDDesktop repo [1] and had no success.

-- Christian

[1] https://github.com/FreeBSDDesktop/freebsd-base-graphics



Hi Christian
Hi all

it never worked.
I tried using the FreeBSD 11-STABLE (Revision 310008).
As i pointed out in my first post. Suspend is working but i am unable to 
resume again.


Actually i am interested in having an exchange of experiences which 
kernel modules and configs are needed and which one should be avoided to 
successfully enable suspend/resume.


I already found "Suspend/Resume on FreeBSD-Wiki" [1]. Unfortunately the 
information provided there is not valuable for me.


Anyone interested in sharing experiences?

best regards
Chris


[1]https://wiki.freebsd.org/SuspendResume

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

suspend/resume on Skylake (Lenovo T460s) with FreeBSD11 stable

[Chris Ernst]

Hi everybody!

i have been hardly trying to get my Lenovo T460s to suspend *and to 
resume again*.


Eventually the system suspends when i close the lid.
The power LED is slowly blinking on and off.

That is it! I am not able to resume my system anymore.
When I push the power button once the power LED *keeps* slowly blinking 
on and off. :(


Has anyone of you been able to setup suspend/resume with a notebook 
equipped with current Intel chipset?

on FreeBSD 11.0-STABLE or
on FreeBSD 12.0-CURRENT?

Any hints or help is highly appreciated.
Below you'll find my pciconf -lv if needed i am happy to hand in dmesg 
aswell.


best regards
Chris


-- snipp --

root@fb:~ # pciconf -lv
hostb0@pci0:0:0:0:class=0x06 card=0x223317aa chip=0x19048086 
rev=0x08 hdr=0x00

vendor = 'Intel Corporation'
device = 'Skylake Host Bridge/DRAM Registers'
class  = bridge
subclass   = HOST-PCI
vgapci0@pci0:0:2:0:class=0x03 card=0x223317aa chip=0x19168086 
rev=0x07 hdr=0x00

vendor = 'Intel Corporation'
device = 'HD Graphics 520'
class  = display
subclass   = VGA
none0@pci0:0:8:0:class=0x088000 card=0x223317aa chip=0x19118086 
rev=0x00 hdr=0x00

vendor = 'Intel Corporation'
device = 'Skylake Gaussian Mixture Model'
class  = base peripheral
xhci0@pci0:0:20:0:class=0x0c0330 card=0x223317aa chip=0x9d2f8086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP USB 3.0 xHCI Controller'
class  = serial bus
subclass   = USB
none1@pci0:0:20:2:class=0x118000 card=0x223317aa chip=0x9d318086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP Thermal subsystem'
class  = dasp
none2@pci0:0:22:0:class=0x078000 card=0x223317aa chip=0x9d3a8086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP CSME HECI'
class  = simple comms
none3@pci0:0:22:3:class=0x070002 card=0x223317aa chip=0x9d3d8086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
class  = simple comms
subclass   = UART
pcib1@pci0:0:28:0:class=0x060400 card=0x223317aa chip=0x9d108086 
rev=0xf1 hdr=0x01

vendor = 'Intel Corporation'
class  = bridge
subclass   = PCI-PCI
pcib2@pci0:0:28:2:class=0x060400 card=0x223317aa chip=0x9d128086 
rev=0xf1 hdr=0x01

vendor = 'Intel Corporation'
class  = bridge
subclass   = PCI-PCI
pcib3@pci0:0:28:4:class=0x060400 card=0x223317aa chip=0x9d148086 
rev=0xf1 hdr=0x01

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP PCI Express Root Port'
class  = bridge
subclass   = PCI-PCI
isab0@pci0:0:31:0:class=0x060100 card=0x223317aa chip=0x9d488086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP LPC Controller'
class  = bridge
subclass   = PCI-ISA
none4@pci0:0:31:2:class=0x058000 card=0x223317aa chip=0x9d218086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP PMC'
class  = memory
hdac0@pci0:0:31:3:class=0x040300 card=0x223317aa chip=0x9d708086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP HD Audio'
class  = multimedia
subclass   = HDA
none5@pci0:0:31:4:class=0x0c0500 card=0x223317aa chip=0x9d238086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-LP SMBus'
class  = serial bus
subclass   = SMBus
em0@pci0:0:31:6:class=0x02 card=0x223317aa chip=0x156f8086 
rev=0x21 hdr=0x00

vendor = 'Intel Corporation'
device = 'Ethernet Connection I219-LM'
class  = network
subclass   = ethernet
none6@pci0:2:0:0:class=0xff card=0x223317aa chip=0x522a10ec 
rev=0x01 hdr=0x00

vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTS522A PCI Express Card Reader'
iwm0@pci0:4:0:0:class=0x028000 card=0x01308086 chip=0x24f38086 
rev=0x3a hdr=0x00

vendor = 'Intel Corporation'
device = 'Wireless 8260'
class  = network
nvme0@pci0:5:0:0:class=0x010802 card=0xa801144d chip=0xa804144d 
rev=0x00 hdr=0x00

vendor = 'Samsung Electronics Co Ltd'
class  = mass storage
subclass   = NVM
root@fb:~ #

-- snipp --







___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: zfs, a directory that used to hold lot of files and listing pause

[Chris Watson]

While I have yet to encounter this with PG on ZFS, knock on wood, this 
obviously is not an isolated issue and if possible those experiencing it should 
do as much investigation as possible and open a PR. This seems like something 
I'm going to read about FreeBSD and PG/ZFS over at Hacker News from a Linux 
switcher as they explain why they went back to Linux in the future. It's not a 
show stopper but it's obviously an issue. 

Chris

Sent from my iPhone 5

> On Oct 20, 2016, at 4:18 PM, Jonathan Chen <j...@chen.org.nz> wrote:
> 
>> On 21 October 2016 at 09:09, Peter <p...@citylink.dinoex.sub.org> wrote:
>> [...]
>> 
>> I see this on my pgsql_tmp dirs (where Postgres stores intermediate
>> query data that gets too big for mem - usually lots of files) - in
>> normal operation these dirs are completely empty, but make heavy disk
>> activity (even writing!) when doing ls.
>> Seems normal, I dont care as long as the thing is stable. One would need
>> to check how ZFS stores directories and what kind of fragmentation can
>> happen there. Or wait for some future feature that would do
>> housekeeping. ;)
> 
> I'm seeing this as well with an Odoo ERP running on Postgresql. This
> lag does matter to me as this is huge performance hit when running
> Postgresql on ZFS, and it would be good to see this resolved.
> pg_restores can make the system crawl as well.
> 
> Cheers.
> -- 
> Jonathan Chen <j...@chen.org.nz>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Source upgrade to 10.3: Undefined symbol "__set_error_selector"

[Chris Stankevitz]

FYI (issue is resolved so I'm just reporting for posterity)...

I have four offline ("air gapped") FreeBSD systems with nearly identical 
hardware.  Two started life as 10.1-RELEASE and the other two started 
life as 10.2-RELEASE.


All are kept up to date by bringing over /usr/src for their associated 
releases (using 'svn co https://svn.freebsd.org/base/releng/10.x') and 
make/buildworld.


All were upgraded to 10.3-p5 and failed 'make installworld' with:

/lib/libthr.so.3: Undefined symbol "__set_error_selector"

All resolved with 'cd /usr/src/lib/libc && make install && cd /usr/src 
&& make installworld'


Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vt console driver and default vga mode: breaking POLA

[Chris H]

On Fri, 9 Sep 2016 11:59:45 +0200 Borja Marcos <bor...@sarenet.es> wrote

> Hi
> 
> I apologise for being late on this, but I just noticed. The new vt console
> driver has a very important change in behavior, replacing the ancient
> “BIOS” text mode with a graphic VGA mode. 
>
> I don’t know how many people relies on BIOS serial redirection for
> consoles, but at least HP’s iLO system offers the possibility of accessing
> the console through a ssh connection instead of requiring a bloated Java
> console, and it’s a very convenient feature. But it only works in pure
> “BIOS text mode” (the old sc console driver used this mode as a default).
> 
> I would rather change the default behavior of vt to hw.vga.textmode=1 so that
> its behavior mimics the old sc driver.
> 
> I know the current fad is to hide boot messages with panda bears and
> beautiful butterflies revolving around them, but boot messages are critical
> when diagnosing problems. 
LOL
>
> I should have chimed in earlier, I know. But anyway it’s a very minor
> change. 
>
> 
> 
> 
> What do you think?
+1
It might also be worth mentioning that (most?) NVIDIA card
users users will also suffer from this (non text mode).
> 
> 
> 
> 
> Borja.
> 
--Chris


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Benchmarks results for FreeBSD 11

[Chris]

On 29 August 2016 at 09:30, Fernando Herrero Carrón <elfe...@gmail.com> wrote:
> 2016-08-29 3:04 GMT+02:00 K. Macy <km...@freebsd.org>:
>
>> > I'm writing from my cellphone away from my computer, so take this with a
>> > grain of salt:
>> >
>> > -L/usr/local/llvm38/lib
>>
>> You're missing the point. If your webserver crashes every other day,
>> the fact that you can run a batch job to restart it doesn't make it
>> OK.
>>
>>
> Fair enough, I misunderstood the point as "clang, even from ports, cannot
> do omp at all [from a shell]".
>
>
>> [...] Requiring additional tweaking to build on FreeBSD
>> or requiring users to install gcc is kind of underwhelming.
>>
>
> Isn't that precisely what the ports infrastructure is supposed to do? What
> about compiler.mk? If it can provide an extra library-dirs argument to the
> port's configure then we're not that bad. And still I agree, this is far
> from an ideal situation, and we speaking about finding a library, we have
> still not touched having clang use the LLVM linker...
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

I have not looked at the article yet. but yes if one compiles FreeBSD
ports using a default make.conf (empty file) then the ports will not
be built optimised.
I dont go all out on optimisation like some people do but I consider
basic optimisation to be a modern version of gcc combined with the cpu
native flag.  Which will auto detect the processor used and add the
right flags correctly.  I dont fiddle with -O2 -O3 etc.

However there is a flipside to this on performance, ubuntu packages by
default are now built with PIE, BIND_NOW, SMACK, RELRO etc.  These
will all slow down performance but are modern expected hardening.
FreeBSD I think still does not do this by default? and as such ubuntu
is managing to beat FreeBSD whilst also adding exploit mitigations
which is impressive.

It is a real shame the default ports compile and base has not been
looked into but instead it all has been kept on conservative approach
which is no exploit protection and to compile for the lowest
denominator like a 486 cpu.  Hardened bsd has done some good work on
this but I see they were forced to fork away because their changes
were rejected on the base system.

As a final note I assumed clang no longer has a noticeable
disadvantage vs gcc, if it does then that's bad news for the base
files.

If I Am wrong on the above please feel free to correct me.

Chris
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Looking for libvgl users

[Chris H]

On Tue, 21 Jun 2016 09:33:11 -0400 Ed Maste <ema...@freebsd.org> wrote

> Prompted by a recent discussion of the vt(4) console I would like to
> send this query to -stable. When posted to -current about 1.5 years
> ago it received only one private reply pointing out an example vgl(3)
> consumer. Please see the original request and let me know if you use
> vgl(3).
FWIW I ran a quick
# cd /usr/ports; find . | xargs grep vgl
Which returned quite a few entries, as well as unrelated.
In case it helps. Some of the possibly notable ones include:
/devel/sdl12
/korean/man-doc/pkg-plist:share/man/ko_KR.eucKR/man3/vgl.3.gz
/games/digger-vgl
/japanese/groff/files/mdoc.local.in:.ds str-Lb-libvgl  Video Graphics
Library (libvgl, \-lvgl)
/misc/compat4x
/misc/compat5x
/misc/compat6x
/misc/compat7x
/x11/virtualgl

There were also matches in binary files; jdk, gnome(2|3), xorg, teX,
and ghostscript. But I didn't pursue it any further.

--Chris

> 
> On 27 October 2014 at 11:26, Ed Maste <ema...@freebsd.org> wrote:
> > vgl(3) is a graphics library for syscons(4) that provides some basic
> > graphics operations (e.g. some mode setting, bitmaps, boxes,
> > ellipses). Right now it does not support the newer vt(4) console.
> >
> > In order to help determine the priority of a porting effort to add
> > vt(4) support I'd like to better understand where vgl is being used
> > now. I'd be interested in hearing about both open source software
> > using vgl as well as proprietary or internal applications. So if
> > you're using vgl I'd appreciate a follow up (in private is fine) with
> > a brief description of your use case.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: unbound and ntp issuse

[Chris H]

I'm playing catchup on my INBOX, so apologies in advance, if this has
already been satisfactorily answered...
On Mon, 6 Jun 2016 16:50:18 +0300 Slawa Olhovchenkov <s...@zxy.spb.ru> wrote

> On Mon, Jun 06, 2016 at 09:33:02AM -0400, Lowell Gilbert wrote:
> 
> > Slawa Olhovchenkov <s...@zxy.spb.ru> writes:
> > 
> > > On Fri, Jun 03, 2016 at 02:34:18PM -0400, Lowell Gilbert wrote:
> > >
> > >> Slawa Olhovchenkov <s...@zxy.spb.ru> writes:
> > >> 
> > >> > Default install with local_unbound and ntpd can't be functional with
> > >> > incorrect date/time in BIOS:
> > >> >
> > >> > Unbound requred correct time for DNSSEC check and refuseing queries
> > >> > ("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime
> > >> > trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
> > >> >
> > >> > ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
> > >> > symbolic names like 0.freebsd.pool.ntp.org, as result -- can't
> > >> > resolve (see above, about DNSKEY).
> > >> 
> > >> I can't see how this would happen. DNSSEC doesn't seem to be required in
> > >> a regular install as far as I can see. Certainly I don't have any
> > >
> > > I don't know reasson for enforcing DNSSEC in regular install.
> > > I am just select 'local_unbound' at setup time and enter '127.0.0.1' as
> > > nameserver address.
> > 
> > That's not enough to configure unbound as a fully recursive DNS
> > server.
> 
> What I am missing?
> Need to fix unbound setup scripts? bsdinstall scripts?
> As I see unbound setup scripts detects 127.0.0.1 in resolv.conf and
> configured unbound as fully recursive DNS server.
May I suggest ntpdate(8)?
Find a reliable time server in your region, and once found add it
*early* in your rc.conf(5). Well, ahead of your unbound stanza. ie;

hostname="..."
ifconfig_re0="inet ... netmask ..."
defaultrouter="..."
ntpdate_enable="YES"
ntpdate_hosts="a reliable regional time server"

..

unbound_enable="YES"
..

ALSO. Since you're upstream will, in all likelihood have informed
you of a preferred set of 2 name servers. Place one of them in your
hosts(5) file. This will help ensure that ntpdate(8) can reliably
discover your regional time server.

That should get you where you want to go. :-)

--Chris
> 
> > If your system gets its address through DHCP, it is probably
> > getting DNS server addresses as well, and would work fine *without* your
> > configuring any of the DNS state.
> 
> I am have static address and don't getting DNS server address.
> 
> > >> problem on any of my systems, and I've never configured an anchor on the
> > >> internal systems.
> > >> 
> > >> > IMHO, ntp.conf need to include some numeric IP of public ntp servers.
> > >> 
> > >> Ouch; that's a terrible idea, for several different reasons.
> > >
> > > What else?
> > 
> > All the normal reasons that hard-coding IP addresses is a bad idea; they
> > can change, you're encouraging a lot of people to use the same ones, etc.
> 
> And how to resolve this issuse:
> 
> - default install with unbound as recursive DNS server (by default
>   enforcing DNSSEC)
> - ntp time synchronisation
> - stale CMOS time (2008 year)


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"