Re: clocked speed not showing in dev.cpu.[0-7].freq
On Tue, Apr 27, 2021 at 12:28:53PM -0600, Ian Lepore wrote: The same is true on my system: CPU: Intel(R) Xeon(R) CPU W3680 @ 3.33GHz (4250.09-MHz K8-class CPU) Thank you Ian for confirming -- J. signature.asc Description: PGP signature
clocked speed not showing in dev.cpu.[0-7].freq
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, -- J. signature.asc Description: PGP signature
Re: Deprecating base system ftpd?
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. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
Hi, On Tue, Mar 30, 2021 at 12:52:59PM -0500, Doug McIntyre wrote: On Tue, Mar 30, 2021 at 05:54:03PM +0100, tech-lists wrote: it just threw me that the thing-that-was-updated didn't update its version information when queried. Absent sources, how can I tell it was updated (apart from freebsd-version -u) ? Comparing what the SA patch says it is doing at https://security.freebsd.org/patches/SA-21:07/openssl-12.patch appears to be only update the libcrypto library and not the openssl wrapper itself, you can verify that after the 12.2-p5 patch was installed that the file /lib/libcrypto.so.111 has been touched and is a newer date than what was on the machine prior to the patch. Yes, this takes some knowledge of the specific patch, and what parts contribute to what it is doing. I don't know the specific decisions on when RELEASE backports security patches vs. upgrading whole source trees. Thanks for the clear explanation. -- J. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
On Tue, Mar 30, 2021 at 12:07:41PM -0400, Karl Denninger wrote: Ok, that's fair; it DOES show -p5 for the user side. $ freebsd-version -ru 12.2-RELEASE-p4 12.2-RELEASE-p5 So that says my userland is -p5 while the kernel, which did not change (even though if you built from source it would carry the -p5 number) is -p4. I can live with that as it allows me to "see" that indeed the revision is present without having source on the box. it just threw me that the thing-that-was-updated didn't update its version information when queried. Absent sources, how can I tell it was updated (apart from freebsd-version -u) ? -- J. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
On Tue, Mar 30, 2021 at 11:55:24AM -0400, Karl Denninger wrote: How do I *know*, without source to go look at, whether or not the fix is present on a binary system? Yep, you understand my point exactly. -- J. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
On Tue, Mar 30, 2021 at 05:22:30PM +0200, Guido Falsi via freebsd-stable wrote: No, as you can see in the commit in the official git [1] while for current and stable the new upstream version of openssl was imported for the release the fix was applied without importing the new release and without changing the reported version of the library. So with 12.2p5 you do get the fix but don't get a new version of the library. [1] https://cgit.freebsd.org/src/commit/?h=releng/12.2=af61348d61f51a88b438d41c3c91b56b2b65ed9b On this url, near the top, there's this: "Fix multiple OpenSSL vulnerabilities. Add UPDATING and bump version." next to that, we have "releng/12.2". So, I'm expecting the version information pertaining to opensslto be bumped. Is this expectation unreasonable? I'm not a developer. -- J. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
Hi, On Tue, Mar 30, 2021 at 11:01:20AM -0400, Karl Denninger wrote: It is not updating; as I noted it appears this security patch was NOT backported and thus 12.2-RELEASE does not "see" it. ok, then I guess I need to post to -security? Because the notice suggests that it was. You cannot go to "-STABLE" via freebsd-update; to run -STABLE you must be doing buildworld/buildkernel from source. I can confirm that 12.2-STABLE *does* have the patch as I checked it recently. I know. The reason I mentioned -STABLE at all was for the purpose of comparative versioning of openssl. My 12-stable machines all update via source. The issue I'm posting about concerns systems following 12.2-R that *only* use freebsd-update to keep up-to-date. These do not have sources installed. As you've mentioned, it seems the security patch was not backported. thanks, -- J. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
On Tue, Mar 30, 2021 at 09:14:56AM -0500, Doug McIntyre wrote: Like the patch referenced in the SA. https://security.FreeBSD.org/patches/SA-21:07/openssl-12.patch Again, it seems like confusion over what happens in RELEASE, STABLE and CURRENT.. Hi, I'm not sure what you mean by this. In https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html it says 1) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # which I did. If openssl updated, would it not be logical to expect openssl version information to indicate it had in fact been updated? If not, then how am I able to tell that it has updated? On an un-upgraded 12.2-p4 system *and* on an upgraded one, openssl version reports 1.1.1h-freebsd -- J. signature.asc Description: PGP signature
Re: possibly silly question regarding freebsd-update
On Tue, Mar 30, 2021 at 04:05:32PM +0200, Ruben via freebsd-stable wrote: Hi, Did you mean 12.1-p5 or 12.2-p5 ? I'm asking because you refer to both 12.1-p5 and 12.2-p5 (typo?). yes, I meant 12.2-p5, sorry -- J. signature.asc Description: PGP signature
possibly silly question regarding freebsd-update
Hi, Recently there was https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html about openssl. Upgraded to 12.2-p5 with freebsd-update and rebooted. What I'm unsure about is the openssl version. Up-to-date 12.1-p5 instances report OpenSSL 1.1.1h-freebsd 22 Sep 2020 Up-to-date stable/13-n245043-7590d7800c4 reports OpenSSL 1.1.1k-freebsd 25 Mar 2021 shouldn't the 12.2-p5 be reporting openssl 1.1.1k-freebsd as well? thanks, -- J. signature.asc Description: PGP signature
Re: build failed for 12.2-p5
On Sat, Mar 27, 2021 at 02:52:09PM +0100, Miroslav Lachman wrote: The same error is there after make delete-old + delete-old-libs again. I am out of ideas. Hi, does it have a /etc/src.conf? if so, does it use ccache? The way i'd build 12.2-p5 from scratch would be like this: 1. rm -rf /usr/src 2. rm -rf /usr/obj 3. mkdir /usr/obj 4. cd /usr 5. git clone https://git.freebsd.org/src.git 6. cd src 7. git checkout releng/12.2 8. make cleanworld && make cleandir && make clean 9. make buildworld [...] you said you used https://github.com/freebsd/freebsd.git but I don't know if it's equivalent or in step with https://git.freebsd.org/src.git maybe this is the issue - I don't know. -- J. signature.asc Description: PGP signature
Re: Updating to 13-stable and existing ZFS pools: any gotchas?
On Sun, Mar 14, 2021 at 09:59:21AM +0100, Stefan Bethke wrote: I'm planning to upgrade three production machines with existing ZFS pools to 13-stable. Is there anything I need to pay attention to wrt OpenZFS? Or should it be fully transparent, apart from updating loader? My (limited) testing with VMs went without a hitch, but I want to make sure I don't paint myself into a corner. Hi, I'm interested in this as well. I'm not using root-on-zfs. The zpool is 5* spinning rust, the booting media is ssd/ufs2. Is updating the bootcode only relevant for root-on-zfs? I've not done that for a similarly configured desktop system, and it seems to be running stable/13 fine. (the desktop was a stable/12 to stable/13 upgrade). thanks, -- J. signature.asc Description: PGP signature
Re: where to upgrade 12-stable now, svn still, or git?
On Fri, Feb 12, 2021 at 06:11:25PM -0800, Mark Millard via freebsd-stable wrote: But I've no clue if such would be important to what you might need to do with 12. you're right, I should have been more detailed. My context is in looking after various 12-stable machines. Basically I'm asking "which is the source for truth now". I'm not a dev so this is non-obvious to me; all i'm interested in is keeping machines up-to-date. I knew stable/13 and current/14 were going to git, but never heard anything about stable/12 or earlier versions. I saw on cgit that stable/12 was there. These older systems weekly update their sources via svn till now, in a cron job. At the time I wrote my message, I saw that svn still works, so was wondering which to use, which has the latest updates. thanks, -- J. signature.asc Description: PGP signature
where to upgrade 12-stable now, svn still, or git?
Hi, As subject, where to get sources for 12-stable upgrade now? Is it still svn or is it git? thanks, -- J. signature.asc Description: PGP signature
mergemaster and etcupdate
Hi, I've used mergemaster for years like this: 1. mergemaster -p after the make installkernel step 2. mergemaster -Ui after the make installworld step Although I've seen nothing announced making etcupdate mandatory, I guess etcupdate will be the new way of doing things. My questions are: [a] what are the etcupdate equivalents of the above mergemaster commands? [b] do I need to do any prep before running make buildworld, or with any other step in the buildworld/installworld process? [c] when will mergemaster stop working? context: amd64 stable/13 thanks, -- J. signature.asc Description: PGP signature
Re: stable/13 and zfs <> openzfs
On Tue, Feb 09, 2021 at 03:40:43PM -0700, Alan Somers wrote: The new ZFS is backwards compatible with the old one. So your 12.2-p3 system will be able to zfs send, and the stable/13 will be able to zfs recv. You can go the other direction too, if you're careful to create the new pool using the old format, and don't turn on any of the new features. /etc/rc.conf shouldn't need any changes. Your upgrade plan sounds fine. But for the "backup all data" step, I would recommend using zfs send/recv to do the backup. That will do a better job of ensuring your files' integrity than something like rsync or cp. Hi, thanks for confirming. -- J. signature.asc Description: PGP signature
stable/13 and zfs <> openzfs
Hi, I need to build a new zpool (arch=amd64). The machine needs upgrading from stable/12 to stable/13. The process I envisaged following is: 1. backup all data to a non-zpool disk 2. upgrade the OS stable/12 to stable/13 3. destroy the original zpool [1] 4. build new zpool and restore data stable/13 seems to have openzfs as the default zfs. Is there anything more I need do? [2] The system is havdling remote zfs receive from a 12.2-p3 system that uses the earlier default FreeBSD zfs. [3] [1] the original zpool was going to be destroyed anyway due to wrong ashift for these new disks. [2] like, does /etc/rc.conf need modifying? Things like that. [3] is the newer openzfs compatible with the older one? I mean will the older one still be able to send zfs snapshots for backup, or does something need to be changed at either end? thanks, -- J. signature.asc Description: PGP signature
Re: Bug 237666 - repeated messages of "uhub_reattach_port: giving up port reset - device vanished"
On Wed, Aug 12, 2020 at 07:39:57AM -0400, Gerard E. Seibert wrote: Perhaps, if we could collect a list of the know systems that are affected by this bug, it might help the developers to discover the source of the problem. My System: Dell XPS 8930 32 GB DDR4 @ 2400MHz 9th Gen Intel Core i3-9 100 (4 core, 6MB Cache) I have quite a few 12.1-stable systems running on bare metal. The only one affected by this bug has the following spec: Supermicro X9DRE-TF+/X9DR7-TF+ board CPU: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz 384GB RAM hw.ncpu: 32 it's a headless server, didn't need usb at all, so it was an easy workaround for me. -- J. signature.asc Description: PGP signature
Re: Bug 237666 - repeated messages of "uhub_reattach_port: giving up port reset - device vanished"
On Tue, Aug 04, 2020 at 01:53:16PM -0400, Gerard E. Seibert wrote: I was told to resubmit this with the bug's title in the subject line. Therefore, I am. I am just inquiring to see if any progress had been made regarding bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 This bug affects both the 12.x and 13.x branches of FreeBSD. Fortunately, it does not affect <= 11.x branches. FreeBSD 12.2 is due out in October and version 13.0 only five months later. At present, this bug infects both the 12.x and 13.x branches making updating systems beyond 11.x impossible for users of the afflicted systems. The fact that this bug has gone unremedied for so long is somewhat disheartening. Hi, I encountered this bug sometime last year; this year in April it was bothersome enough to try to do something about it. I "fixed" it by compiling and installing a new kernel with everything USB-related removed. Fortunately the machine does not need a USB peripheral of any sort. I've only ever run 12-stable on this machine. And it gave the usb error messages with nothing usb attached, before installing the new kernel. -- J. signature.asc Description: PGP signature
Re: HOWTO donate CPU to the fight against the Corona-virus
Hi, Thanks for doing this :D Is it possible to use this with a cuda-compatible nvidia card and if so how would one go about it? -- J. signature.asc Description: PGP signature
Re: No sound in flashplayer with linux-c7
On Thu, Jul 18, 2019 at 02:14:57AM +0400, Serge Volkov via freebsd-stable wrote: Hi, All! I use www/flashplayer in Firefox on FreeBSD 12.0-RELEASE-p7 with KDE Plasma 5. This week I updated the linux_base-c6 with all linux packages to linux c7. After that, the sound disappeared in flashplayer. I also rebuilt the flashplayer from the ports. But nothing has changed. No sound. With the linux c6 the sound in flashplayer worked fine. Can anyone help to solve problem with sound in flashplayer on linux c7? Hi, Does any sound work? Do you have gsteamer plugins installed? -- J. signature.asc Description: PGP signature
Re: trying to expand a zvol-backed bhyve guest which is UFS
On Sun, May 19, 2019 at 10:17:35PM -0500, Adam wrote: On Sun, May 19, 2019 at 9:47 PM tech-lists wrote: Thanks very much to you both, all sorted now. I didn't realise there was a 2TB limit for MBR either. Can I shrink the 4TB to 2TB on the zfs side without scrambling the ufs on the guest? You can snapshot the zvol to be safe, but you should be able to shrink it to the existing partition size. If it's a sparse zvol, it may not may that much difference. The zvol has about 515GB data. Hopefully zfs is smart enough to shrink to the MBR boundary. -- J. signature.asc Description: PGP signature
Re: trying to expand a zvol-backed bhyve guest which is UFS
Thanks very much to you both, all sorted now. I didn't realise there was a 2TB limit for MBR either. Can I shrink the 4TB to 2TB on the zfs side without scrambling the ufs on the guest? thanks, -- J. signature.asc Description: PGP signature
trying to expand a zvol-backed bhyve guest which is UFS
Hi, context is 12-stable, zfs, bhyve I have a zvol-backed bhyve guest. Its zvol size was initially 512GB It needed to be expanded to 4TB. That worked fine. The problem is the freebsd guest is UFS and I can't seem to make it see the new size. But zfs list -o size on the host shows that as far as zfs is concerned, it's 4TB On the guest, I've tried running growfs / but it says requested size is the same as the size it already is (508GB) gpart show on the guest has the following # gpart show =>63 4294967232 vtbd0 MBR (4.0T) 63 1 - free - (512B) 64 4294967216 1 freebsd [active] (2.0T) 4294967280 15 - free - (7.5K) => 0 4294967216 vtbd0s1 BSD (2.0T) 0 10653532161 freebsd-ufs (508G) 1065353216 83885442 freebsd-swap (4.0G) 1073741760 3221225456 - free - (1.5T) I'm not understanding the double output, or why growfs hasn't worked on the guest ufs. Can anyone help please? thanks, -- J. signature.asc Description: PGP signature
nextcloud and collabora on freebsd-12-stable host
hi, Does anyone run nextcloud with collabora on freebsd? If so, please tell how you did it? Reading up on it, instructions are all in linux and use of docker which I'm not keen on as my nextcloud is already a bhyve instance. thanks, -- J. signature.asc Description: PGP signature
xorg with i915kms crashes with GLSL compile failure when xsane starts
Hi, I'm not sure whether this should go here or should I raise a bug or directly raise the issue with xorg? This almost exact bug (xorg/i915kms) was patched/resolved in 2016 on debian according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834054 my issue is slightly different in that I'm using FreeBSD and it happens only when xsane starts and regardless of whether the scanner is even plugged in. context: 12.0-STABLE r346338 GENERIC amd64 packages installed via pkg from default freebsd repos nothing xorg related has been manually defined drm-kmod-g20181126 (which has installed drm-fbsd12.0-kmod-4.16.g20190305) x11/xorg x11/mate graphics/xsane The machine itself is quite old (c. 2010) but xorg/i915kms works fine on it otherwise for stuff like firefox/libreoffice. It has 8GB ram and runs zfs. The crash happens shortly after xsane is started. xorg error: 0:13(14): error: operands to arithmetic operators must be numeric 0:13(13): error: operands to arithmetic operators must be numeric [ 1338.766] Program source: #define ATLAS_DIM_INV 0.0009765625 attribute vec2 primitive; attribute vec2 source; varying vec2 glyph_pos; uniform vec2 fill_offset; uniform vec2 fill_size_inv; varying vec2 fill_pos; uniform vec4 v_matrix; void main() { gl_Position.xy = primitive.xy * v_matrix.xz + v_matrix.yw; gl_Position.zw = vec2(0.0,1.0); glyph_pos = source.xy * ATLAS_DIM_INV; fill_pos = (fill_offset + primitive.xy + pos) * fill_size_inv; } [ 1338.766] (EE) Fatal server error: [ 1338.766] (EE) GLSL compile failure [ 1338.766] (EE) [ 1338.766] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 1338.766] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 1338.767] (EE) [ 1338.767] (II) AIGLX: Suspending AIGLX clients for VT switch [ 1338.772] (EE) Server terminated with error (1). Closing log file. in the meantime I'm going to try building xorg/xsane from the ports thanks, -- J. signature.asc Description: PGP signature
Re: about zfs and ashift and changing ashift on existing zpool
On Mon, Apr 08, 2019 at 09:25:43PM -0400, Michael Butler wrote: On 2019-04-08 20:55, Alexander Motin wrote: On 08.04.2019 20:21, Eugene Grosbein wrote: 09.04.2019 7:00, Kevin P. Neal wrote: My guess (given that only ada1 is reporting a blocksize mismatch) is that your disks reported a 512B native blocksize. In the absence of any override, ZFS will then build an ashift=9 pool. [skip] smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.2-RELEASE-p4 amd64] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST2400MM0129 Revision: C003 Compliance: SPC-4 User Capacity:2,400,476,553,216 bytes [2.40 TB] Logical block size: 512 bytes Physical block size: 4096 bytes Maybe it't time to prefer "Physical block size" over "Logical block size" in relevant GEOMs like GEOM_DISK, so upper levels such as ZFS would do the right thing automatically. No. It is a bad idea. Changing logical block size for existing disks will most likely result in breaking compatibility and inability to read previously written data. ZFS already uses physical block size when possible -- on pool creation or new vdev addition. When not possible (pool already created wrong) it just complains about it, so that user would know that his configuration is imperfect and he should not expect full performance. And some drives just present 512 bytes for both .. no idea if this is consistent with the underlying silicon :-( I built a ZFS pool on it using 4k blocks anyway. smartctl 7.0 2018-12-30 r4883 [FreeBSD 13.0-CURRENT amd64] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WDS100T2B0A-00SM50 Serial Number:1837B0803409 LU WWN Device Id: 5 001b44 8b99f7560 Firmware Version: X61190WD User Capacity:1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Form Factor: 2.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5 SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Mon Apr 8 21:22:15 2019 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM level is: 128 (minimum power consumption without standby) Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Unavailable Yeah it's weird isn't it. So it seems it's not an issue with zfs at all as far as I can see. This is one of the drives that was replaced, and it's identical to the other two making up the array. So not unreasonably ashift was 9, as all three drives making up the array were 512 logical/physical. === START OF INFORMATION SECTION === Model Family: Western Digital Black Device Model: WDC WD4001FAEX-00MJRA0 Firmware Version: 01.01L01 User Capacity:4,000,787,030,016 bytes [4.00 TB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Apr 9 12:47:01 2019 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled I replaced one of them with an 8tb drive: TART OF INFORMATION SECTION === Model Family: Seagate Archive HDD Device Model: ST8000AS0002-1NA17Z Firmware Version: AR13 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5980 rpm Device is:In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Apr 9 12:55:55 2019 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled so the 2nd drive is emulating 512. But ZFS seems to see through that and correctly determines it's a 4k drive. In any case, the fix was to make a new pool (which automatically set ashift to 12 when the 8Tb disk was added) then zfs send from the old pool to the new one, then destroy the old pool. Fortunately this was easy because the system had zfs installed as an afterthought. So no root-on-zfs. The OS is on a SSD. All I can say is that zpool performance of a 4k drive in an a9 zpool is non-ideal. The new pool feels quicker (even though the disks aren't built for speed), and I've learned something new :D -- J. signature.asc Description: PGP signature
about zfs and ashift and changing ashift on existing zpool
Hello, I have this in sysctl.conf on a desktop machine (12-stable): vfs.zfs.min_auto_ashift=12 this has not always been there. I guess the zpool pre-dates it. I only noticed it because have recently had to replace a disk in its zfs array when I saw this: % zpool status pool: storage state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Sun Apr 7 03:09:42 2019 3.46T scanned at 79.5M/s, 2.73T issued at 62.8M/s, 3.46T total 931G resilvered, 78.94% done, 0 days 03:22:41 to go config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 replacing-0 ONLINE 0 0 1.65K ada2 ONLINE 0 0 0 ada1 ONLINE 0 0 0 block size: 512B configured, 4096B native ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 What I'd like to know is: 1. is the above situation harmful to data 2. given that vfs.zfs.min_auto_ashift=12, why does it still say 512B configured for ada1 which is the new disk, or.. 3. does "configured" pertain to the pool, the disk, or both 4. what would be involved in making them all 4096B 5. does a 512B disk wear out faster than 4096B (all other things being equal) Given that the machine and disks were new in 2016, I can't understand why zfs didn't default to 4096B on installation thanks, -- J. signature.asc Description: PGP signature
Re: ufs to zfs conversion in a freebsd guest
On Sun, Mar 24, 2019 at 04:16:32PM -0600, Alan Somers wrote: Yes, but it's probably not worth the effort. Easier to spin up 2nd vm and copy everything over. Here is what you'd have to do: Yeah the problem we have is that option is unavailable to us and we don't have access to the host. 1) shrink the root filesystem with resizefs. 2) shrink it's partition with gpart. If it's not the last partition on the disk, then you'll have to relocate the last (presumably swap) partition. 3) create a new zfs partition. 4) create a new zfs pool. 5) create all of the various zfs datasets just like the installer does. 6) copy over everything from / to the zfs partition except for /boot. 7) configure loader.conf to boot from zfs. Assuming, that is, that your VM system even runs the regular boot loader. and that's a big assumption 8) reboot and pray. 9) spin up a new VM anyway, since you inevitably screwed up something. Good luck. Yeah you're right. It's a lot of work that could go wrong at any stage. At least there's mksnap_ffs ;) thanks for clarifying -- J. signature.asc Description: PGP signature
ufs to zfs conversion in a freebsd guest
Hi [context is freebsd-12R-p3] Is it possible to convert a running freebsd guest from UFS to ZFS? It would need to be done in-situ, in the guest as there is no access to the host. The guest filesystem is: /dev/gpt/rootfs / ufs rw 1 1 /dev/gpt/swapfs noneswapsw 0 0 thanks, -- J. signature.asc Description: PGP signature
Re: bhyve zfs resizing
On Mon, Mar 18, 2019 at 06:56:03PM +0100, Miroslav Lachman wrote: [...] Thanks for the example, I've saved it. Ok just one other question, which I might have found the answer to, or might not. I'm new to this virtualising on zfs even though ive used zfs for years. It's basically: I made a zvol, installed 12-R into it,. Where the disks option came up I chose the auto defaults for *ZFS* in the guest. I also selected encryption for both the virtual disk and swap. I think perhaps I shouldn't have done all this together in the same vm because with apache running in it, httpd got wedged (and then everything got wedged. sync wouldn't return). I think the top zfs layer and the encryption layer and the zfs underneath got too busy. Happily the server still responded to a shutdown -r and came back up. It's scrubbing the zpool to be on the safe side. Am I correct? In that I should have used UFS in the guest rather than zfs? Or was it the encryption? thanks, -- J. signature.asc Description: PGP signature
Re: bhyve zfs resizing
On Mon, Mar 18, 2019 at 09:08:31AM -0600, Alan Somers wrote: Do you mean using a zvol as the backing store for a VM? If so, then: 1) Yes. You can just do "zfs set volsize" on the host. 2) In theory no, but the guest may need to be rebooted to notice the change. And I'm not sure if the current bhyve code will expose the new size without a reboot or not. 3) Sure. But after you expand the zvol (or before you shrink it), you'll have to change the size of the guest's filesystem using the guest's native tools. Great, that's awesome. Thanks for clarifying -- J. signature.asc Description: PGP signature
bhyve zfs resizing
Hi, Apart from the performance benefit as per the section for bhyve in the handbook, can the size of the zfs-backed guest: 1. be resized from the host? 2. does the guest need to be inactive? 3. can linux guests (or even windows ones) be resized as well? thanks, -- J. signature.asc Description: PGP signature
Re: enforcing php56 in a poudriere build
On Mon, Mar 11, 2019 at 10:51:52AM +, tech-lists wrote: just in case anyone gets stuck[1] like I did, the easiest thing was to keep two ports trees, the default (current) one, build everything the servers need that isn't php in there, then have the other tree at r488745 and not update it. [1] rather than updating one tree. doh! -- 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"
enforcing php56 in a poudriere build
Hi, [context is building ports with poudriere. I need to keep these ports to maintain a legacy platform] The 'default' for php is now 72. It was 71 and before that, 56. How does one configure the 'default'. I can do it via make.conf like this: DEFAULT_VERSIONS+= php=5.6 php=56 and update my ports tree to 488740 but if I do this, I'll still get this error in poudriere logs for phpmyadmin: [00:00:03] Warning: (databases/phpmyadmin): Error: databases/phpmyadmin depends on nonexistent origin 'textproc/php72-xml' (moved to ); Please contact maintainer of the port to fix this. 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"
12-stable buildworld appears to be broken
Hi, My context is poudriere creating jails on freebsd12-stable. This procedure worked fine for some other jails I created a couple days ago (the 5th) but now, today I get buildworld failures with creating either amd64 or armv7 jails (the server is amd64) To try to see the failure, I set jobs to J1 like so: poudriere jail -x -J1 -c -j 12armv7 -a arm.armv7 -m svn+https -v stable/12 It bails when it's making rescue with this error: /data/poudriere/basefs/jails/12armv7/usr/src/sbin/fsck_ffs/pass1.c:454:13: error: too many arguments to function call, expected 0, have 1 inodirty(dp); ^~ /data/poudriere/basefs/jails/12armv7/usr/src/sbin/fsck_ffs/fsck.h:453:1: note: 'inodirty' declared here void inodirty(void); ^ 1 error generated. *** [pass1.o] Error code 1 I know that's probably not enough, so have pasted much more output at https://rpi3.zyxst.net/errors/poudriere-build-failure.txt not tried make buildworld yet on the host. The OS is at r344763 and /usr/src is at 344863 Just tried it on another 12-stable desktop, straightforward make buildworld, same sort of error: --- all_subdir_sbin/fsdb --- /usr/src/sbin/fsdb/fsdb.c:1042:14: error: too many arguments to function call, expected 0, have 1 inodirty(curinode); ^~~~ /usr/src/sbin/fsck_ffs/fsck.h:453:1: note: 'inodirty' declared here voidinodirty(void); the sources are at 344869 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"
Re: poudriere(-devel) ports updating question
On Wed, Mar 06, 2019 at 06:23:49PM +0100, Stefan Bethke wrote: Am 05.03.2019 um 15:09 schrieb tech-lists : Basically I'm looking for exclude mask functionality when updating a ports tree with poudriere ports. Do I need to do this manually or have I missed something? I don’t think it’s easy to do that. How would you handle dependencies? (For example, some ports require X11 libs and stuff, even though they’re in a different category.) You're right of course. My logic was wrong, and wrong premise[1] because I was stuck on thinking a bulk -a build. But I found how to do it (to remove categories) in case anyone is interested. The key is in the method used to update the tree, which is svn+https. so, from the top of the ports tree, svn update --set-depth=exclude biology would exclude the biology category permanently. svn update --set-depth=infinity biology would re-add it. svn update --set-depth=infinity would make it be like nothing was excluded in the first place. but on reflection, it breaks a little of the ports infrastructure and I don't want to do that. [1] used to use portupgrade -a but poudriere bulk -a is not equivalent!!! am just getting to grips with poudriere lol -- 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"
poudriere(-devel) ports updating question
Hi, There are several categories of ports I'd like to avoid for some architectures. For example, I don't want x11 for mips.mips64. Or astronomy. But let's say, for this architecture, I want to build everything else. I can't see a way of excluding categories with poudriere ports when updating the ports tree - the only workaround I can see is to download another tree, call it something and then manually edit that tree, and then set the build off with -p port-treename. Every time I want to make a bulk run. Basically I'm looking for exclude mask functionality when updating a ports tree with poudriere ports. Do I need to do this manually or have I missed something? 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"
Re: possibly silly binmiscctl question
On Mon, Mar 04, 2019 at 06:53:01PM +0100, Kurt Jaeger wrote: Hi! If I give binmiscctl the magic for arm6 and then for say mips64, will this break things? Let's say I'm using an amd64 box to cross-compile using poudriere for arm6 and mips64 ports. Can I do both on the same box at the same time? Or do I need to let's say the arm6 run to finish, then give binmiscctl its magic strings for mips64, and THEN run the build run for that arch? I used two archs in parallel in the past, that was no problem. oh that's great news, thanks (really I should have made sure before doing it, lol!) -- 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"
possibly silly binmiscctl question
Hi, If I give binmiscctl the magic for arm6 and then for say mips64, will this break things? Let's say I'm using an amd64 box to cross-compile using poudriere for arm6 and mips64 ports. Can I do both on the same box at the same time? Or do I need to let's say the arm6 run to finish, then give binmiscctl its magic strings for mips64, and THEN run the build run for that arch? 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"
does vtnet require iflib in the kernel?
Hi, Does vtnet require iflib in the kernel? 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"
Re: freebsd-12 and bhyve and the azure platform
On Sat, Jan 26, 2019 at 04:39:39PM +0100, Paul Vixie wrote: i would expect you to use dump | restore, or zfs dump | zfs restore, to move a system image from one container strategy (or bare metal) to another (such as azure), after first booting a rescue image inside the destination container. you'd then fine-tune your /etc/rc.conf file to have whatever settings were appropriate for the new container. i know that's somewhat old school, but, that's one reason to love bhyve. OK, thanks. I thought this might be the case. Just wanted to make sure I wasn't trying to reinvent the wheel ;) -- 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-12 and bhyve and the azure platform
Hello, Is it possible to migrate a byve freebsd instance/image to Azure? Or does one have to have the instance initially provisioned via their marketplace? 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"
apache protection
Hi, I already use sshguard to block woodpeckers on sshd. Is there something similar for apache? If so, would it work with sshguard? I use pf for firewall. Basically something that's causing 404s 5 times per second. How can I (automatically) block it? 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"
Re: which port installed what other port
On Mon, Jan 21, 2019 at 09:35:20AM -0700, Alan Somers wrote: Try "pkg info -r ". And to go the other direction, use "pkg info -d ". -Alan OK thank you, I'll try that -- 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"
which port installed what other port
Hi, Is there a command (or a port) I can use which, when fed an installed port name, can tell me what installed it? I don't mean libraries. I mean the actual port name. 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"
Re: php56
On Mon, Jan 14, 2019 at 02:28:00AM +0900, Yasuhiro KIMURA wrote: From: tech-lists Subject: php56 Date: Sun, 13 Jan 2019 12:29:36 + Is there a way of installing php56 and php56-extensions from ports or packages now? I know it's EoL, but need it because I need to support a (non-ports) program for the time being and said program will not work under php7* context is 11-stable/amd64 thanks, svn checkout -r 488893 /usr/ports Thanks very much for this. Although as posted it didn't work, it gave me enough of a clue to fix my problem. For the benefit of anyone else with a similar problem, what fixed it for me was svnlite co https://svn.freebsd.org/ports/head -r 488749 /usr/ports 488893 got php56 but not php56-extensions. So I searched in the deleted section on https://dev.freshports.org for php56-extensions, the entry gave the last svn number which was less (488749) and this got everything php56 I required. -- 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"
php56
Hi, Is there a way of installing php56 and php56-extensions from ports or packages now? I know it's EoL, but need it because I need to support a (non-ports) program for the time being and said program will not work under php7* context is 11-stable/amd64 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"
using wifi usbkey and ethernet on rpi3-b
Hi, context: freebsd-12-rc3, raspberry pi3-b, external usb-connected hd, 2.5A PSU Has anyone tried using a wifi interface (usb key format) and ethernet at the same time? There is also a usb connected hard drive. I was wondering if the wifi might interrupt the ethernet or the hard drive. Aren't they all the same interface electronically? ie the usb/ethernet is more like a usb bus. (originally asked in freebsd-arm but it's very quiet there) 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"
Re: device otus unknown
On Mon, Nov 12, 2018 at 09:33:01PM +, tech-lists wrote: On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote: If it's showing up like that then it's not an AR9170 device; it's a broadcom firmware device. :( yeah. In tiny lettering it has "v2" next to the WNDA3100 so this seems to be a completely different chipset But what about the otus(4) manpage? Says you can compile device otus into kernel, but buildkernel says device unknown. Seems WNDA3100 v2 has BCM4323 chip which is unsupported, drat. 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"
Re: device otus unknown
On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote: If it's showing up like that then it's not an AR9170 device; it's a broadcom firmware device. :( yeah. In tiny lettering it has "v2" next to the WNDA3100 so this seems to be a completely different chipset But what about the otus(4) manpage? Says you can compile device otus into kernel, but buildkernel says device unknown. 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"
device otus unknown
Hi, context: freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now with amd64 r340354. I have a Netgear WNDA3100 USB wireless key. Its man page has the following: SYNOPSIS To compile this driver into the kernel, place the following lines in your kernel configuration file: device ehci device uhci device ohci device usb device otus device wlan so I made sure all these were in my kernel config, but when I try building it, it bails in a second or two saying that otus is an unknown device: [snip] --- buildkernel --- make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined that CC=/usr/local/bin/ccache cc matches the source tree. Not bootstrapping a cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined that LD=ld matches the source tree. Not bootstrapping a cross-linker. --- buildkernel --- -- Kernel build for DESKTOP started on Mon Nov 12 17:49:52 GMT 2018 -- ===> DESKTOP mkdir -p /obj/usr/src/amd64.amd64/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/amd64/conf; PATH=/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/obj/usr/src/amd64.amd64\ /tmp/legacy/usr/bin:/obj/usr/src/amd64.amd64/tmp/legacy/bin:/obj/usr/src/\ amd64.amd64/tmp/usr/sbin:/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:\ /usr/sbin:/usr/bin config -d /obj/usr/src/amd64.amd64/sys/DESKTOP -I '/usr/src/sys/amd64/conf' '/usr/src/sys/amd64/conf/DESKTOP' config: Error: device "otus" is unknown config: 1 errors *** [buildkernel] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [buildkernel] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src [/snip] Maybe related to this problem: I *can* kldload otus. But when I plug in the device, only this shows up in dmesg: Nov 12 18:04:32 desktop kernel: ugen0.11: at usbus0 I thought it would come up as Atheros? kldstat Id Refs AddressSize Name 1 70 0x8020 136ada0 kernel 21 0x8156c000 f980 if_bridge.ko 32 0x8157c000 7588 bridgestp.ko 42 0x81584000 134cbd8 nvidia.ko 53 0x828d1000a7020 linux.ko 64 0x82979000 8e20 linux_common.ko 71 0x82982000 56ec60 vmm.ko 81 0x82ef1000 171d88 nvidia-modeset.ko 91 0x83063000 82a0 if_tap.ko 101 0x8306c000 2a38 nmdm.ko 111 0x83221000 24be60 zfs.ko 121 0x8346d000 7638 opensolaris.ko 131 0x83475000 4abc linprocfs.ko 141 0x8347a000 82a0 tmpfs.ko 151 0x83483000 1800 uhid.ko 161 0x83485000 2368 ums.ko 171 0x8348800033f60 linux64.ko 181 0x834bc000 1a00 fdescfs.ko 191 0x834be000 acf mac_ntpd.ko 201 0x834bf000 a340 if_otus.ko 211 0x834ca00041c48 wlan.ko usbconfig dump_device_description : ugen0.11: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0846 idProduct = 0x9011 bcdDevice = 0x0001 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <0> bNumConfigurations = 0x0001 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"
Re: base openssl fallout: ruby fails to build
On Wed, 7 Nov 2018 16:44:01 + tech-lists wrote: > Hi, I missed the UPDATING entry 20180214 concerning ruby. sorry for the noise! -- 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"
base openssl fallout: ruby fails to build
Hi, context is 12.0-BETA3 r340208 GENERIC amd64 ports is Revision: 484403 nothing pertaining to openssl in make.conf or src.conf I ran make check-old and yes | make delete-old and yes | make delete-old-libs then rebooted before attempting to upgrade ruby # openssl version OpenSSL 1.1.1-freebsd 11 Sep 2018 /usr/ports/lang/ruby23 # make [...] generating amd64-freebsd12-fake.rb amd64-freebsd12-fake.rb updated ./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb --extout=.ext -- --disable-gems -r./amd64-freebsd12-fake ./tool/rbinstall.rb --make="/usr/bin/make" --dest-dir="/usr/ports/lang/ruby23/work/stage" --extout=".ext" --mflags=" " --make-flags=" .MAKE.LEVEL.ENV=MAKELEVEL ARCH=amd64 CONFIGURE_MAX_CMD_LEN=262144 CONFIG_DONE_RUBY23=1 DESTDIR=/usr/ports/lang/ruby23/work/stage HAVE_COMPAT_IA32_KERN=YES\ OPSYS=FreeBSD OSREL=12.0 OSVERSION=1200086 _OSRELEASE=12.0-BETA3 _PERL5_FROM_BIN=5.26.2 _PKG_CHECKED=1" --data-mode=0644 --prog-mode=0755 --installed-list .installed.list --mantype="man" --install=all --rdoc-output=".ext/rdoc" /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require': Shared object "libssl.so.8" not found, required by "openssl.so" - /usr/local/lib/ruby/2.3/amd64-freebsd12/openssl.so (LoadError) from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/lib/ruby/2.3/openssl.rb:13:in `' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/security.rb:12:in `' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/package.rb:44:in `' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/installer.rb:10:in `' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/ports/lang/ruby23/work/ruby-2.3.8/lib/rubygems/core_ext/kernel_require.rb:55:in `require' from ./tool/rbinstall.rb:658:in `' from ./tool/rbinstall.rb:586:in `' *** Error code 1 Stop. make[2]: stopped in /usr/ports/lang/ruby23/work/ruby-2.3.8 *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/ruby23 *** Error code 1 Stop. make: stopped in /usr/ports/lang/ruby23 how can I fix please? 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"
boinc crunching on GPU with NVIDIA GPU GeForce GTX 960 (GM206-A)
Hi, context is recent freebsd-12-stable, amd64, NVIDIA GPU GeForce GTX 960 (GM206-A) GPU, boinc with WCG. ports are built from the ports tree. I had no luck with an AMD card, wondering if NVIDIA is better supported for this. I don't mind what drivers are used, although I'm having problems determining the best one [1]. Question from me is, has anyone managed to GPU crunch with boinc on the WCG project under freebsd-12 with an nvidia card? If so, please tell how you did it? [1] nvidia-driver-390.87 ? version 410.73 from nvidia themselves? drm-kmod? which ones? 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"
ioat(4) manual errors
Hi, man 4 ioat references ioatcontrol(8) in SEE ALSO but neither the manpage or executable for ioatcontrol exists. The man page also references /dev/ioat_test in the FILES section but that doesn't exist either. Context is FreeBSD 12.0-BETA2 #3 r339812 amd64 with GENERIC kernel ioat is loaded: [snip] > file /dev/ioat_test /dev/ioat_test: cannot open `/dev/ioat_test' (No such file or directory) > dmesg | grep ioat ioat0: mem 0xc7d1c000-0xc7d1 irq 31 at device 4.0 numa-domain 0 on pci0 ioat0: Capabilities: 2f7 ioat1: mem 0xc7d18000-0xc7d1bfff irq 39 at device 4.1 numa-domain 0 on pci0 ioat1: Capabilities: 2f7 ioat2: mem 0xc7d14000-0xc7d17fff irq 31 at device 4.2 numa-domain 0 on pci0 ioat2: Capabilities: f7 ioat3: mem 0xc7d1-0xc7d13fff irq 39 at device 4.3 numa-domain 0 on pci0 ioat3: Capabilities: f7 ioat4: mem 0xc7d0c000-0xc7d0 irq 31 at device 4.4 numa-domain 0 on pci0 ioat4: Capabilities: f7 ioat5: mem 0xc7d08000-0xc7d0bfff irq 39 at device 4.5 numa-domain 0 on pci0 ioat5: Capabilities: f7 ioat6: mem 0xc7d04000-0xc7d07fff irq 31 at device 4.6 numa-domain 0 on pci0 ioat6: Capabilities: f7 ioat7: mem 0xc7d0-0xc7d03fff irq 39 at device 4.7 numa-domain 0 on pci0 ioat7: Capabilities: f7 ioat8: mem 0xfbf1c000-0xfbf1 irq 55 at device 4.0 numa-domain 1 on pci9 ioat8: Capabilities: 2f7 ioat9: mem 0xfbf18000-0xfbf1bfff irq 63 at device 4.1 numa-domain 1 on pci9 ioat9: Capabilities: 2f7 ioat10: mem 0xfbf14000-0xfbf17fff irq 55 at device 4.2 numa-domain 1 on pci9 ioat10: Capabilities: f7 ioat11: mem 0xfbf1-0xfbf13fff irq 63 at device 4.3 numa-domain 1 on pci9 ioat11: Capabilities: f7 ioat12: mem 0xfbf0c000-0xfbf0 irq 55 at device 4.4 numa-domain 1 on pci9 ioat12: Capabilities: f7 ioat13: mem 0xfbf08000-0xfbf0bfff irq 63 at device 4.5 numa-domain 1 on pci9 ioat13: Capabilities: f7 ioat14: mem 0xfbf04000-0xfbf07fff irq 55 at device 4.6 numa-domain 1 on pci9 ioat14: Capabilities: f7 ioat15: mem 0xfbf0-0xfbf03fff irq 63 at device 4.7 numa-domain 1 on pci9 ioat15: Capabilities: f7 [/snip] 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"
Re: TP-LINK TL-WN321G
On 27/10/2018 18:50, Bjoern A. Zeeb wrote: The problem with these dongles is that sometimes there’s a rev A and a rev B which use entirely different chipsets and hence are entirely different drivers. That is rarely observable from online shopping sites or even product packaging. I haven’t checked this particular case but if you can send me a usbconfig dump_device_desc for it I can go an have a look. Sure! here it is: ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (450mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x148f idProduct = 0x5370 bcdDevice = 0x0101 iManufacturer = 0x0001 iProduct = 0x0002 <802.11 n WLAN> iSerialNumber = 0x0003 <1.0> bNumConfigurations = 0x0001 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"
TP-LINK TL-WN321G
Hi, context: 12-stable amd64 When TP-LINK TL-WN321G usb dongle is inserted, this appears in dmesg: ugen1.3: at usbus1 run0 numa-domain 0 on uhub3 run0: <1.0> on usbus1 run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R), address [REDACTED] but run(4) says it supports these: TP-LINK TL-WDN3200 TP-LINK TL-WN727N v3 and run0 appears, and works, yet: rum(4) says it supports this: TP-LINK TL-WN321G but no rum0 happens either on insertion (using standard GENERIC kernel) or with rum loaded. -- 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"
Re: FCP-0101: Deprecating most 10/100 Ethernet drivers
On 03/10/18 22:05, Brooks Davis wrote: We are solictiting feedback on the list of drivers to be excepted from removal. The current list of drivers slated for REMOVAL is: ae, bfe, bm, cs, dme, ed, ep, ex, fe, pcn, rl, sf, smc, sn, ste, tl, tx, txp, vx, wb, xe Please do not remove rl. I have two rl interfaces in a machine built in 2011 still in daily use. One rl interface is an aftermarket card bought new in *2016*. The other one is built into the motherboard. That's just the stuff I personally own. rl is in lots of machines which will probably still be running a decade from now. I'm astonished you're considering removing rl given how common it is. -- 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"
Re: Error validating server certificate
On 12/09/2018 15:37, Glen Barber wrote: On Wed, Sep 12, 2018 at 02:30:39PM +, Montgomery-Smith, Stephen wrote: I did svn up just now in my /usr/src directory. I got this message. Should I worry about this? Error validating server certificate for 'https://svn.freebsd.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.freebsd.org - Valid: from Aug 29 20:26:55 2018 GMT until Nov 27 20:26:55 2018 GMT - Issuer: Let's Encrypt Authority X3, Let's Encrypt, US - Fingerprint: DC:AE:39:82:F5:32:DB:61:86:9E:B4:C7:C0:9C:EA:8C:08:7E:43:5A You will not see this if you install the security/ca_root_nss port. Glen Hi Glen, Why is security/ca_root_nss not present in base? I mean, on a brand new install, one goes to update the sources, and just the sources. And this error is issued? I think it looks bad. Do you agree? 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"
Re: problems with installworld
On 18/08/2018 14:15, Polytropon wrote: Try to follow the instructions on top of /usr/src/Makefile (comment header). Before you perform "make installworld", make sure you have rebooted the system into single-user mode (with the new kernel). Also see "man 7 build" for details. yep, that fixed it, sorry for the noise ;) -- 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"
Re: lightly loaded system eats swap space
On 25/06/2018 18:28, tech-lists wrote: On 20/06/2018 06:08, Shane Ambler wrote: This review is aiming to fix this - https://reviews.freebsd.org/D7538 I have been running the patch on stable/11 and after eight days uptime I still have zero swap in use, I can't recall a time in the last few years that I have had no swap usage past the first hour or two uptime. will this work on a recent 12-current? Hi, Just to let the thread know - upgrading to 12-current (in this case r336037 but I guess it's not specific, just a recent version) fixed the problem. 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"
Re: Console is broken after updating to 11.2-RELEASE
Hi, On 22/06/2018 09:07, Yasuhiro KIMURA wrote: 1. BIOS message are displayed. 2. Boot menu of FreeBSD is displayed. 3. Kernel boot starts but after 'Booting...' no following messages are displayed. 4. After OS has booted console stays unusable. I've seen this effect elsewhere. Not exactly the same, but it's been happening with me on some systems since 11.1. The context I see it is when spinning up a bhyve instance in screen. I see a bit more than just booting, something like "unreferenced ps/2 interrupt" after "Booting...". The bhyve instance itself is fully functional. Logging into the bhyve instance through ssh I can see its dmesg and it all looks OK. However, if in syslogd.conf I enable console logging via console.log and reboot, *nothing gets written to it*. Have had this issue for about a year now, not been able to fix it. Frustratingly, it doesn't happen with all VMs. I've not seen it happen with a 12-current VM, just 11-stable. And even then, not *all* 11-stable VMs. -- 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"
Re: lightly loaded system eats swap space
On 18/06/2018 13:23, David Fullard wrote: I've noticed you've got a rather large ZFS ARC. You could try limiting the ZFS max ARC size by setting the vfs.zfs.arc_max sysctl. I'll try this as soon as I can. 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"
Re: lightly loaded system eats swap space
On 18/06/2018 09:08, Erich Dollansky wrote: Hi, On Sun, 17 Jun 2018 23:19:02 +0100 tech-lists wrote: freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse this might not be related but I noticed that your swap space is small compared to RAM size. I noticed on a much smaller Raspberry Pi, that it runs into trouble when there is no swap even there is enough RAM available. Is it easily possible for you to add some GB of swap space and let the machine run then? How much swap do the other machines have? Hi, Yes, the machine with the problem uses the default 4GB swap. That's all the swap it has. The machine without issue has a swapfile installed on a SSD in addition to the default 4GB swap. problematic machine: Device 512-blocks UsedAvail Capacity /dev/ada0p38388608 3.3G 714M83% machine without a problem, it has swapfile installed: Device 512-blocks UsedAvail Capacity /dev/ada0s1b 8262248 1.7G 2.2G44% /dev/md0 65536000 1.9G 29G 6% Total 73798248 3.7G 32G10% I added the swapfile a long time ago on this machine due to the same issue. But my problem isn't so much an out of swapspace problem; all this is, is a symptom. My problem is "why is it swapping out at all on a 128GB system and why is what's swapped out not being swapped back in again". 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"
Re: lightly loaded system eats swap space
On 18/06/2018 00:04, Adam wrote: Based upon the output neither ram nor swap seems like similar spec so I wonder if you could say what you mean by that. server with the problem: last pid: 62387; load averages: 0.07, 0.10, 0.08 up 30+01:30:01 12:46:40 48 processes: 1 running, 47 sleeping CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 5404K Active, 1218M Inact, 4927M Laundry, 117G Wired, 1392M Buf, 2116M Free ARC: 109G Total, 2982M MFU, 105G MRU, 288K Anon, 385M Header, 638M Other 104G Compressed, 105G Uncompressed, 1.01:1 Ratio Swap: 4096M Total, 3383M Used, 713M Free, 82% Inuse This server runs 1 bhyve instance using 16GB. It has 128GB RAM. server without a problem: last pid: 84491; load averages: 0.03, 0.02, 0.02 up 17+14:39:31 12:47:33 27 processes: 1 running, 26 sleeping CPU: % user, % nice, % system, % interrupt, % idle Mem: 2915M Active, 25G Inact, 9947M Laundry, 28G Wired, 1572M Buf, 59G Free ARC: 22G Total, 3379M MFU, 19G MRU, 781K Anon, 64M Header, 974K Other 22G Compressed, 29G Uncompressed, 1.33:1 Ratio, 121M Overhead Swap: 35G Total, 3747M Used, 32G Free, 10% Inuse This server runs 10 bhyve instances of various RAM sizes, from 4GB to 32GB. It also has 128GB RAM installed. This is what I mean by "similar spec", I mean in terms of RAM. This server doesn't usually show swap as being in use, but I can actually account for this, as there is memory overcommitment here. My point is that 'server with problem' should not show a resources issue with just one bhyve instance using 16GB RAM but apparently it is, and I don't know why. I am starting the VMs by hand, without any third-party application, and I'm not wiring memory on the command line. 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"
lightly loaded system eats swap space
Hello list, context is (server) freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, E5-2630 @2.3GHz, generic kernel. There's one bhyve guest on this server (using 4x cpu and 16GB RAM, also freebsd-11-stable) There have been no special options for zfs configuration on the server, apart from several datasets having the compressed property set (lz4). The server runs nothing else really apart from sshd and it uses ntpd to sync local time. How come such a lightly loaded server with plenty of resources is eating up swap? If I run two bhyve instances, i.e. two of the same size as indicated above, so 32GB used for the bhyves, I'll get out-of-swapspace errors in the daily logs: +swap_pager_getswapspace(24): failed +swap_pager_getswapspace(24): failed +swap_pager_getswapspace(24): failed Here's top, with one bhyve instance running: last pid: 49494; load averages: 0.12, 0.13, 0.88 up 29+11:36:06 22:52:45 54 processes: 1 running, 53 sleeping CPU: 0.4% user, 0.0% nice, 0.4% system, 0.3% interrupt, 98.9% idle Mem: 8664K Active, 52M Inact, 4797M Laundry, 116G Wired, 1391M Buf, 4123M Free ARC: 108G Total, 1653M MFU, 105G MRU, 32K Anon, 382M Header, 632M Other 103G Compressed, 104G Uncompressed, 1.00:1 Ratio Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse PID USERNAMETHR PRI NICE SIZERES STATE C TIMEWCPU COMMAND 49491 root 1 40 16444K 12024K select 9 0:12 6.49% ssh 32868 root 12 200 9241M 4038M kqread 2 23.2H 1.30% bhyve 49490 root 1 200 10812K 6192K sbwait 5 0:02 0.88% sftp From the looks of it, a huge amount of ram is wired. Why is that, and how would I debug it? A server of similar spec which is running freebsd-current with seven bhyve instances doesn't have this issue: last pid: 41904; load averages: 0.26, 0.19, 0.15 up 17+01:06:11 23:14:13 27 processes: 1 running, 26 sleeping CPU: 0.1% user, 0.0% nice, 0.3% system, 0.0% interrupt, 99.6% idle Mem: 17G Active, 6951M Inact, 41G Laundry, 59G Wired, 1573M Buf, 1315M Free ARC: 53G Total, 700M MFU, 52G MRU, 512K Anon, 182M Header, 958K Other 53G Compressed, 69G Uncompressed, 1.30:1 Ratio, 122M Overhead Swap: 35G Total, 2163M Used, 33G Free, 6% Inuse 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"
Re: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
On 31/05/2018 11:57, Rod Person wrote: I ended up having to rebuild everything single qt5 library installed on my system...pretty painful. Hi, Just to update, I fixed the problem by doing this: 1. portupgrade -f "qt4*" 2. portupgrade -f "qt5*" Hopefully others will find this useful. Thanks again for the tip. -- 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"
Re: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
On 31/05/2018 11:57, Rod Person wrote: I just fixed this a few week or two ago on my system. The problem is you have difference version numbers within the qt5 library, not having qt4 and qt5. Thanks for the tip. Yes, there are versions of all kinds of qt4/5 programs that are not in complete version number agreement, on this system. I don't usually run pkg installs although I think libreoffice was installed as a package. currently running portupgrade -f "qt4*" thanks again, -- 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"
Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
Hello lists, context: 11.2-PRERELEASE #0 r333458 / ports r471194 with xpdf I get the following error: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped) I seem to have both qt4-4.8.7 and qt5-5.10.1 installed. I didn't install these directly though, seems they've been installed as dependencies of other ports. I'm using MATE desktop. I've tried reinstalling xfdf via pkg and the port with the same result. Is this a known problem/how can I fix? Have found no fix yet from GIS, most seem to point to deleting and reinstalling everything. 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"
Re: problems with ssh-agent after running MATE desktop
Thanks everyone for their suggestions, I'll try both keychain and invoking ssh-agent as exec. -- 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"
problems with ssh-agent after running MATE desktop
Hello lists, For over a decade I've used windowmaker for my freebsd desktop. For easy ssh/sftp access to sites, before starting windowmaker with xinit, I run 'agent' which is a tcsh alias for the following: rm -f "$HOME"/.ssh/`hostname`.agent ; ssh-agent | grep -v echo > "$HOME"/.ssh/`hostname`.agent ; source "$HOME"/.ssh/`hostname`.agent ; ssh-add it prompts me for my ssh keyphrase. Then I start xinit, and all windows subsequently opened in xorg/windowmaker have this key in their environment loaded. Connecting to another server is as easy as ssh name@server. However, this does not happen if MATE is loaded from xinit. It is as if I had not loaded the key at all before starting MATE. I get this error: sign_and_send_pubkey: signing failed: agent refused operation If I then run 'agent', prompts me for the keyphrase, then it works normally. But I have to repeat this in every single opened terminal. What do I have to do to stop MATE from clobbering (or whatever it's doing - I don't know where to start with this) ssh-add? for context: recent freebsd-stable/amd64 and ports 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"
Re: trying to get sftp-only logins to work with a public keys
On 24/05/2018 12:09, tech-lists wrote: Hello list, I'm trying to get (chrooted) sftp login working with public keys. I made a sftp-only user which works fine, and is chrooted. I created a .ssh directory with 770 perms (root:user) and put their public key in there with 600 perms (user:user) however when trying pubkey auth it always falls back to keyboard-interactive (which will succeed when the password is applied). I don't know why in key exchange it says it sent a packet then didn't. Can anyone help please? Context is recent freebsd-11-stable, both client and server. I have this in /etc/ssh/sshd_config: Subsystem sftp internal-sftp Match User testsftp ChrootDirectory /usr/home/testsftp PubkeyAuthentication yes X11Forwarding no AllowTcpForwarding no AuthorizedKeysFile /usr/home/testsftp/.ssh/authorized_keys ForceCommand internal-sftp Solved this by setting perms on .ssh dir to be root:user 750 (and not 760 or 770) didn't see this documented anywhere so posting in the hope this helps others. -- 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"
trying to get sftp-only logins to work with a public keys
Hello list, I'm trying to get (chrooted) sftp login working with public keys. I made a sftp-only user which works fine, and is chrooted. I created a .ssh directory with 770 perms (root:user) and put their public key in there with 600 perms (user:user) however when trying pubkey auth it always falls back to keyboard-interactive (which will succeed when the password is applied). I don't know why in key exchange it says it sent a packet then didn't. Can anyone help please? Context is recent freebsd-11-stable, both client and server. I have this in /etc/ssh/sshd_config: Subsystem sftp internal-sftp Match User testsftp ChrootDirectory /usr/home/testsftp PubkeyAuthentication yes X11Forwarding no AllowTcpForwarding no AuthorizedKeysFile /usr/home/testsftp/.ssh/authorized_keys ForceCommand internal-sftp permissions in the test users .ssh dir are like this: drwxrwx--- 2 root testsftp 512B May 24 10:51 . drwxr-xr-x 5 root testsftp 512B May 24 10:35 .. -rw--- 1 testsftp testsftp 105B May 24 11:49 authorized_keys here is the -v -v debug output from ssh client: debug2: set_newkeys: mode 1 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug2: set_newkeys: mode 0 debug1: rekey after 134217728 blocks debug2: key: /home/REDACTED/.ssh/id_rsa (0x0) debug2: key: /home/REDACTED/.ssh/id_dsa (0x0) debug2: key: /home/REDACTED/.ssh/id_ecdsa (0x0) debug2: key: /home/REDACTED/.ssh/id_ed25519 (0x802015240) debug1: SSH2_MSG_EXT_INFO received debug1: Fssh_kex_input_ext_info: server-sig-algs=debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/REDACTED/.ssh/id_rsa debug1: Trying private key: /home/REDACTED/.ssh/id_dsa debug1: Trying private key: /home/REDACTED/.ssh/id_ecdsa debug1: Offering ED25519 public key: /home/REDACTED/.ssh/id_ed25519 debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey,keyboard-interactive debug2: we did not send a packet, disable method debug1: Next authentication method: keyboard-interactive debug2: userauth_kbdint debug2: we sent a keyboard-interactive packet, wait for reply debug2: input_userauth_info_req debug2: input_userauth_info_req: num_prompts 1 Password for testsftp@REDACTED: 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"
Re: ftpd in base
On 20/05/2018 18:35, Eugene Grosbein wrote: Our ftpd applies -u and by default instantly overrides it with login class setting. You should add your own login class to /etc/login.conf with 0111 value then run "cap_mkdb /etc/login.conf" and "pw usermod ftpusername -L ftploginclass" Hi, Thanks for this - have sorted it now. -- 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"
ftpd in base
Hi, context: 11.2-BETA2 #0 r333924/amd64 I'm trying to get chrooted ftpd (in base) to write files uploaded to the user dir as mode 666 (umask 111). I have a line in inetd.conf that looks like this: ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l -u 111 The user logs in OK and uploads OK but the perms are always 644. There is no login.conf overriding this. The users shell is /usr/sbin/nologin as these are ftp-only accounts. This exact config works fine on linux (specifically ubuntu) Why is ftpd ignoring -u ? How can I fix? 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"
Re: KBI unexpexted change in stable/11 ?
On 28/03/2018 14:39, Gregory Byshenk wrote: > You can do this manually, or by adding a PORTS_MODULES line to > /etc/make.conf. This will rebuild the listed modules from ports > when you build a new kernel. Hi, Are you sure it's in /etc/make.conf and not /etc/src.conf? -- 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"
Re: libreoffice fails to build [SOLVED]
On 24/03/2018 19:07, tech-lists wrote: > Hi, > > Building libreoffice (libreoffice-en_GB) complains about illegal > instruction and dumps core. Full script output is at > https://www.zyxst.net/errors/libreofficebuildfail.txt please ignore, libreoffice builds fine on a pristine installation. -- 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"
libreoffice fails to build
Hi, Building libreoffice (libreoffice-en_GB) complains about illegal instruction and dumps core. Full script output is at https://www.zyxst.net/errors/libreofficebuildfail.txt last few lines of make MAKE_JOBS_UNSAFE=yes -DBATCH ## [HIX] scalc/en-US S=/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1 && I=$S/instdir && W=$S/workdir && ( rm -rf $W/HelpTarget/scalc/en-US/scalc.idxl && LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program" $W/LinkTarget/Executable/HelpIndexer -dir $W/HelpTarget/scalc/en-US -lang en-US -mod scalc && touch $W/HelpIndexTarget/scalc/en-US.done ) || ( rm -rf scalc.* ; false ) Illegal instruction (core dumped) gmake[3]: *** [/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/solenv/gbuild/HelpTarget.mk:452: /usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/workdir/HelpIndexTarget/sbasic/en-US.done] Error 1 gmake[3]: *** Waiting for unfinished jobs Illegal instruction (core dumped) gmake[3]: *** [/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/solenv/gbuild/HelpTarget.mk:452: /usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/workdir/HelpIndexTarget/scalc/en-US.done] Error 1 gmake[3]: Leaving directory '/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1' gmake[2]: *** [Makefile:268: build] Error 2 gmake[2]: Leaving directory '/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1' *** Error code 1 Stop. make[1]: stopped in /usr/ports/editors/libreoffice *** Error code 1 Stop. make: stopped in /usr/ports/editors/libreoffice-en_GB context: no /etc/make.conf root@eggs:/root# uname -KU 1101512 1101512 root@eggs:/root# system: 11.1-STABLE #0 r331421 amd64 ports: root@eggs:/root# svnlite info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 465452 Node Kind: directory Schedule: normal Last Changed Author: gerald Last Changed Rev: 465452 Last Changed Date: 2018-03-24 14:15:56 + (Sat, 24 Mar 2018) shall I file a bug report? -- 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"
Re: Problem with USB <---> UPS management connection
On 07/03/2018 11:55, wishmaster wrote: > I have changed USB-cables, USB port on the server - without success. > On another server this problem is absent. It looks like a broken or shorting connection but you say you've tried different ports on the machine and changed cables. I dunno, maybe the usb subsystem/circuitry in that machine is at fault? The way I'd test is to install a usb card known to be good and test again. -- 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"
Re: zfs problems after rebuilding system [SOLVED]
On 03/03/2018 12:56, Bruce Evans wrote: > That won't work for the boot drive. In my case the workaround is fine because it's not a boot drive -- 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"
Re: zfs problems after rebuilding system [SOLVED]
On 03/03/2018 00:23, Dimitry Andric wrote: > Indeed. I have had the following for a few years now, due to USB drives > with ZFS pools: > > --- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100 > +++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100 > @@ -25,6 +25,8 @@ > > zfs_start_main() > { > + echo "Sleeping for 10 seconds to let USB devices settle..." > + sleep 10 > zfs mount -va > zfs share -a > if [ ! -r /etc/zfs/exports ]; then > > For some reason, USB3 (xhci) controllers can take a very, very long time > to correctly attach mass storage devices: I usually see many timeouts > before they finally get detected. After that, the devices always work > just fine, though. > > Whether this is due to some sort of BIOS handover trouble, or due to > cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate > disks!), I have no idea. I attempted to debug it at some point, but > a well-placed "sleep 10" was an acceptable workaround... :) That fixed it, thank you again :D -- 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"
Re: zfs problems after rebuilding system
On 03/03/2018 00:09, Freddie Cash wrote: > You said it's an external USB drive, correct? Could it be a race condition > during the boot process where the USB mass storage driver hasn't detected > the drive yet when /etc/rc.d/zfs is run? > > As a test, add a "sleep 30" in that script before the "zfs mount -a" call > and reboot. Yes it's an external usb3 drive. That's interesting and I'll test that tomorrow. I recently commented out a GENERIC kernel the USB debug line because the console was filling up with usb attach messages on boot. They were appearing after the login prompt. I have a couple of usb3 hubs attached and the disk is attached through one such hub. (although it was done this way because sometimes it'd be seen as /dev/da0 and others as /dev/da4. And possibly linked to this, when it came up as /dev/da0 it was always with a usb2 speed rather than usb3). thanks everyone for your input. -- 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"
Re: zfs problems after rebuilding system
On 02/03/2018 21:56, Alan Somers wrote: > dmesg only shows stuff that comes from the kernel, not the console. To > see what's printed to the console, you'll actually have to watch it. Or > enable /var/log/console.log by uncommenting the appropriate line in > /etc/syslog.conf. ok did that, chmodded it to 600 then gave a kill -1 to its process id, then rebooted. # cat /var/log/console.log | grep -i zfs # lots of info if I less the file, but nothing about zfs here's output of mount: # mount /dev/ada0s1a on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) linprocfs on /compat/linux/proc (linprocfs, local) tmpfs on /compat/linux/dev/shm (tmpfs, local) zpool0 on /zpool0 (zfs, local, nfsv4acls) zpool0/home on /zpool0/home (zfs, local, nfsv4acls) zpool0/usr on /zpool0/usr (zfs, local, nfsv4acls) zpool0/usr/local on /zpool0/usr/local (zfs, local, nfsv4acls) zpool0/vms on /zpool0/vms (zfs, local, nfsv4acls) zpool0/usr/oldsrc on /usr/oldsrc (zfs, local, nfsv4acls) zpool0/usr/ports on /usr/ports (zfs, local, nfsv4acls) zpool0/usr/src on /usr/src (zfs, local, nfsv4acls) # output of zfs mount # zfs mount zpool0 /zpool0 zpool0/home/zpool0/home zpool0/usr /zpool0/usr zpool0/usr/local /zpool0/usr/local zpool0/vms /zpool0/vms zpool0/usr/oldsrc /usr/oldsrc zpool0/usr/ports /usr/ports zpool0/usr/src /usr/src now I'll do zfs mount -a and then zfs mount # zfs mount -a # zfs mount zpool0 /zpool0 zpool0/home/zpool0/home zpool0/usr /zpool0/usr zpool0/usr/local /zpool0/usr/local zpool0/vms /zpool0/vms zpool0/usr/oldsrc /usr/oldsrc zpool0/usr/ports /usr/ports zpool0/usr/src /usr/src zpool1 /zpool1 zpool1/compressed /zpool1/compressed zpool1/important /zpool1/important and everything is there as it should be, after zfs mount -a. it's as if the /etc/rc.d/zfs either isn't running or I don't know, failing to run the main section, where it uses -av rather than just -a. Is this file the only one that's called to load zfs? I mean, in that file, zfs mount is never called without a parameter. To me, it doesn't look like the file is being run at all. 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"
Re: zfs problems after rebuilding system
On 02/03/2018 21:56, Alan Somers wrote: > dmesg only shows stuff that comes from the kernel, not the console. To see > what's printed to the console, you'll actually have to watch it. Or enable > /var/log/console.log by uncommenting the appropriate line in > /etc/syslog.conf. ok will do this asap, 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"
Re: zfs problems after rebuilding system
On 02/03/2018 21:38, Alan Somers wrote: > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have > you checked if /etc/rc.d/zfs is printing any errors to the console > during boot? Nothing much in dmesg -a # dmesg -a | egrep -i zfs ZFS filesystem version: 5 ZFS storage pool version: features support (5000) # cat /etc/rc.conf | egrep -i zfs zfs_enable="YES" very puzzling -- 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"
Re: zfs problems after rebuilding system
Hi, thanks for looking at this, On 02/03/2018 20:39, Alan Somers wrote: > This doesn't make sense. vdevs have nothing to do with mounting. You see > your vdevs by doing "zpool status". What are you expecting to see that you > don't? sorry, I was confusing terms. I was expecting to see similar to output of zfs list from both zpools instead of just zpool0. (just rebooted the system.) OK here's zpool status: # zpool status pool: zpool1 state: ONLINE scan: scrub repaired 0 in 0h39m with 0 errors on Mon Feb 5 22:55:31 2018 config: NAMESTATE READ WRITE CKSUM zpool1 ONLINE 0 0 0 diskid/DISK-NA7DKXXF ONLINE 0 0 0 errors: No known data errors pool: zpool0 state: ONLINE scan: scrub repaired 0 in 3h46m with 0 errors on Thu Mar 1 23:01:29 2018 config: NAMESTATE READ WRITE CKSUM zpool0 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1ONLINE 0 0 0 ada2ONLINE 0 0 0 ada3ONLINE 0 0 0 > >> Confusingly, I didn't need to and don't have to do any of that for >> zpool0. What am I doing wrong/what am I missing? Why is zpool0 >> automatically loading but zpool1 is not? Before ada0 (the failed disk) >> was replaced, both loaded on boot. >> > Please post the output of "zfs list -r -o name,mountpoint,canmount,mounted" > and also the contents of /etc/fstab. # zfs list -r -o name,mountpoint,canmount,mounted NAME MOUNTPOINT CANMOUNT MOUNTED zpool1 /zpool1 on no zpool1/compressed/zpool1/compressedon no zpool1/important /zpool1/important on no zpool0 /zpool0 on yes zpool0/home /zpool0/home on yes zpool0/usr /zpool0/usr on yes zpool0/usr/local /zpool0/usr/local on yes zpool0/usr/oldsrc/usr/oldsrc on yes zpool0/usr/ports /usr/portson yes zpool0/usr/src /usr/src on yes zpool0/vms /zpool0/vms on yes # cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ada0s1a/ ufs rw 1 1 /dev/ada0s1bnoneswapsw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 tmpfs/compat/linux/dev/shm tmpfs rw,mode=17770 0 fdescfs /dev/fd fdescfs rw,late 0 0 > Also, have you set "zfs_enable=YES" in /etc/rc.conf? yes. If I run zfs mount -a, everything zfs is mounted as expected. I'm wondering if at bootup, when zfs mount is called (I suppose it must be called from somewhere), whether it needs to specify -a. I would not know the first place to look though. 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"
zfs problems after rebuilding system
Hi, Importing two zpools after a hd crash, the first pool I imported auto-loads at boot. But the second one I'm always having to zfs mount (zpool name) then mount the zfs subdirs. The system was like this: ada0 (this had the OS on. It was replaced after it crashed. Not a member of any zpool, not zfs at all, no root-on-zfs). New freebsd-11-stable-snapshot was installed to this disk. ada1 \ ada2 -- these made up zpool0, a raidz pool. Each device is a 1TB disk. ada3 / zpool1 - this is striped, one 4TB disk, attached via usb3 zpool1/c - this is compressed with lz4 zpool1/important - this has copies=2 enabled I ran zpool import zpool0 and then zpool import zpool1 and both imported without error. However despite setting the mountpoint for zpool1 as /zpool1, on reboot I always have to: # zfs mount zpool1 or I won't see the drive in df -h or mount or zfs mount. But I *will* find it at its mountpoint /zpool1. If I do a ls -lah on that, I can see zpool1/c and zpool1/important as dirs but not in zfs mount or (normal) mount, nor can I see the other dirs that are not vdevs. If I then zfs mount zpool1 I can see all the dirs and vdevs on that disk off its root, in ls -lah. But I dont see the vdevs in zfs mount. I have to zfs mount zpool1/c and zfs mount zpool1/important to see the vdevs in zfs mount. Confusingly, I didn't need to and don't have to do any of that for zpool0. What am I doing wrong/what am I missing? Why is zpool0 automatically loading but zpool1 is not? Before ada0 (the failed disk) was replaced, both loaded on boot. 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"
Re: recent 11.1-stable oddness
On 02/03/2018 18:29, Freddie Cash wrote: > If you set hw.usb.no_shutdown_wait to 1 via sysctl, does it > shutdown/reboot normally? > yes it does! Many 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"
Re: recent 11.1-stable oddness
On 02/03/2018 18:29, Freddie Cash wrote: > If you set hw.usb.no_shutdown_wait to 1 via sysctl, does it > shutdown/reboot normally? thanks for the tip. I'll try it and let you know -- 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"
recent 11.1-stable oddness
Hello stable@ Over the last few weeks, I've noticed the following new behaviours from 11.1 stable [only took note of the revision from the last update which was r330243 unfortunately as I thought it was my config/fault initially]: shutdown -r now no longer works as it did (ie: shutdown and reboot). What happens now is that it gets to: "syncing disks, vnodes remaining...5 5 5 4 0 0 0 done All buffers synced Swap device [file] removed. <-- there is no swapfile installed! Uptime: (whatever the uptime was) ukbd0: detached ums0: detached uhid0: detached uhub6: detached ukbd1: detached uhub3: detached umass0: detached uhub0: detached ...and there it sits until a hard reset via the power button is applied. Reboot and poweroff still work as one would expect. also, why is it talking about a swapfile? There is a swap partition but no swapfile: # swapinfo Device 1K-blocks UsedAvail Capacity /dev/ada0s1b 39745800 3974580 0% # swapctl -l Device: 1024-blocks Used: /dev/ada0s1b3974580 0 # cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ada0s1a/ ufs rw 1 1 /dev/ada0s1bnoneswapsw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 tmpfs/compat/linux/dev/shm tmpfs rw,mode=17770 0 fdescfs /dev/fd fdescfs rw,late 0 0 any ideas? 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"
Re: is it possible to chroot into arm64 from amd64?
On 16/02/2018 08:21, Mikaël Urankar wrote: > Put /usr/local/bin/qemu-aarch64-static in > $SYSROOT/usr/local/bin/qemu-aarch64-static > you can use "service qemu_user_static start" to add the interpreter That did it! :D many thanks. I had a bit of a problem with ldconfig but it seems ok so far. Here's what I did from start to finish in case anyone else is interested: ### root@sm1:/# chflags -Rf noschg crossbuild/ root@sm1:/# rm -Rf crossbuild/* root@sm1:/# mkdir crossbuild/arm64 root@sm1:/# sh # SYSROOT=/crossbuild/arm64 # cd /usr/src # make -j96 cleandir && make -j96 clean && make -j96 clean # make -j96 TARGET=arm64 TARGET_ARCH=aarch64 buildworld # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 installworld # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 distribution # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/usr/local/bin/qemu-aarch64-static cp: /crossbuild/arm64/usr/local/bin/qemu-aarch64-static: No such file or directory # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/usr/local/bin/ cp: directory /crossbuild/arm64/usr/local/bin does not exist # ls -lah $SYSROOT/usr/local total 8 drwxr-xr-x 2 root wheel 512B Feb 16 12:28 . drwxr-xr-x 13 root wheel 512B Feb 16 12:28 .. # mkdir $SYSROOT/usr/local/bin # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/usr/local/bin/ # service qemu_user_static start Cannot 'start' qemu_user_static. Set qemu_user_static_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'. # echo "qemu_user_static_enable="YES"" >>/etc/rc.conf # service qemu_user_static start # mount -t devfs devfs ${DESTDIR}/dev # chroot -u root $SYSROOT root@sm1:/ # root@sm1:~ # file /usr/bin/file /usr/bin/file: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 (1101509), FreeBSD-style, stripped root@sm1:~ # service start ldconfig ps: empty file: Invalid argument start does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable root@sm1:~ # which ldconfig /sbin/ldconfig root@sm1:~ # /sbin/ldconfig root@sm1:~ # root@sm1:~ # exit # -- 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"
Re: is it possible to chroot into arm64 from amd64?
On 16/02/2018 01:22, Jonathan Chen wrote: > You've copied qemu-aarch64-static to $SYSROOT/sbin. binmiscctl(8) > should use /sbin/qemu-aarch64-static as its arm64 interpreter in the > arm64-chroot. arrrgh, thanks for spotting that. I'll try again -- 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"
is it possible to chroot into arm64 from amd64?
Hi, Is it possible to have on an amd64 system, a chrooted or jailed arm64 environment? It's possible to cross-compile an arm6 environment on amd64 and then chroot into the arm6 environment - is the same possible for arm64? I can cross-compile arm64 like this: # SYSROOT=/crossbuild/arm64 # cd /usr/src # make -j32 TARGET=arm64 TARGET_ARCH=aarch64 buildworld # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 installworld # make DESTDIR=$SYSROOT TARGET=arm TARGET_ARCH=armv6 distribution # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/sbin # /usr/sbin/binmiscctl add arm64 --interpreter "/usr/local/bin/qemu-aarch64" \ --magic "\x7f\x45\x4c\x46\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00" \ --mask "\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff" \ --size 20 --set-enabled # mount -t devfs devfs ${DESTDIR}/dev then: # chroot -u root $SYSROOT then I get the following error: chroot: /bin/csh: No such file or directory # so looked at the chroot, and bin/csh is there! # ls -lah $SYSROOT/bin |less total 9144 drwxr-xr-x 2 root wheel 1.0K Feb 16 00:43 . drwxr-xr-x 18 root wheel 512B Feb 16 00:44 .. -r-xr-xr-x 2 root wheel 195K Feb 16 00:43 [ -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 cat -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 chflags -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 chio -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 chmod -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 cp -r-xr-xr-x 2 root wheel 451K Feb 16 00:43 csh what am I doing wrong? -- 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"
Re: why does buildworld fail on stable/11 ?
On 25/01/2018 06:22, Scott Bennett wrote: > tech-lists <tech-li...@zyxst.net> wrote: > >> On 24/01/2018 08:51, Scott Bennett wrote: >>> hellas# mv /etc/make.conf{,.save} >>> hellas# mv /etc/src.conf{,.save} >>> hellas# cd /usr/src >>> hellas# make cleandir >>> "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional >>> (${.MAKE.MODE:Mmeta*} != "") >>> "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional >>> (${.MAKE.MODE:Mnofilemon} == "") >>> "/usr/src/share/mk/local.sys.mk", line 76: if-less else >>> "/usr/src/share/mk/local.sys.mk", line 79: if-less endif >>> "/usr/src/share/mk/sys.mk", line 476: if-less endif >>> bmake: fatal errors encountered -- cannot continue >>> *** Error code 1 >> >> Move the /usr/src somewhere else, make a new /usr/src dir and then >> >> svnlite co https://svn.FreeBSD.org/base/stable/11 /usr/src >> >> make sure it completes normally >> >> then cd into it and make cleandir. What happens? > > Before I do that, please answer my earlier question regarding svnlite > vs. svn. The make is failing on a clean checkout of /usr/src, as I stated *Was* it a *clean* checkout? Clearly, something is broken in at least /usr/local/share/mk if you're just running tools in base. > before. The only difference is that I used svn to do the checkout, not > svnlite. If they give identical checkout output, *If*. > then repeating that rather > lengthy download would give an identical result and thus would serve no > purpose. All I know is this: 1. You should be able to make buildworld et al with base tools, i.e. without any ports installed. You should be able to use ccache (I do) but for the purposes of debugging this, that's another uncontrolled variable. 2. I don't know the difference between svnlite and svn. All I know is that svnlite is in base and it will be in base for reasons and one of those reasons will be that it works reliably. I think svn in ports might be more featureful, but maybe it's more buggy because of it, maybe it does more - I don't know. In your position I'd like fewer unknowns. I mean, even make cleandir fails. In circumstances like that, the first thing I'd do is get fresh sources. I just ran a full checkout on 11.1-stable src which took about 9 minutes on a 19Mbit DSL: $ pwd /tmp/test $ date >>time.txt && svnlite co https://svn.FreeBSD.org/base/stable/11 /tmp/test && date >>time.txt [loads of output] Arescue/rescue/Makefile.depend Arescue/README ALOCKS U . Checked out revision 328393. $ cat time.txt Thu 25 Jan 2018 11:51:04 GMT Thu 25 Jan 2018 12:01:07 GMT $ make cleandir ===> lib (cleandir) ===> lib/csu (cleandir) ===> lib/csu/amd64 (cleandir) rm -f crt1.o crti.o crtn.o Scrt1.o gcrt1.o crt1.s gcrt1.s Scrt1.s rm -f .depend .depend.* GPATH GRTAGS GSYMS GTAGS ===> lib/libc (cleandir) rm -f tags gdtoa_strtorx.c gdtoa_dmisc.c gdtoa_dtoa.c gdtoa_gdtoa.c gdtoa_gethex.c gdtoa_gmisc.c gdtoa_hd_init.c gdtoa_hexnan.c gdtoa_misc.c gdtoa_smisc.c gdtoa_strtod.c gdtoa_strtodg.c gdtoa_strtof.c gdtoa_strtord.c gdtoa_sum.c gdtoa_ulp.c cancelpoints_sem.c cancelpoints_sem_new.c subr_acl_nfs4.c C99_Exit.c jemalloc [loads of output] $ which make /usr/bin/make $ file /usr/bin/make /usr/bin/make: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 11.1 (1101506), FreeBSD-style, stripped -- 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"
Re: why does buildworld fail on stable/11 ?
On 24/01/2018 08:15, Scott Bennett wrote: >> Hi, > > Thank you for responding with your thoughts on this. >> >> What I'd do is firstly to make things as simple as possible. First do >> the upgrade simply. Either delete or call make.conf & src.conf something > > Okay. > >> else. Then get a fresh src and ports tree via svnlite. Then do > > /usr/src has not been altered since I ran the checkout. Is there some reason > to use svnlite rather than svn, which is how I did the checkout? I use svnlite because it's in base, and in your type of situation I'd want to use base tools. When did you run the checkout? Did it complete without error? >> >> rm -rf /buildwork/ccache.freebsd >> mkdir /buildwork/ccache.freebsd > > I'm not following your thinking here. If I've eliminated /etc/make.conf > from the picture, then ccache is not involved at all, so why should I wipe out > the cache contents? that's the way it *should* work. But by doing this, we eliminate the possibility of ccache being in the equation at all. >> then cd into /usr/src as root, then do >> >> yes | make delete-old >> yes | make delete-old-libs > > What do you expect the above to accomplish on a freshly installed system > on which no obsolete directories or libraries from a previous release should > exist? *should* exist. What I'm suggesting makes *certain*. What we know is make is encountering a problem. What I'm suggesting removes things make might be picking up, for certain. It's how I've overcome similar issues in the past - elmiminate all the variables I can, then run it in a vanilla way, to see if it's still broken. -- 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"
Re: why does buildworld fail on stable/11 ?
On 24/01/2018 08:51, Scott Bennett wrote: > hellas# mv /etc/make.conf{,.save} > hellas# mv /etc/src.conf{,.save} > hellas# cd /usr/src > hellas# make cleandir > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional > (${.MAKE.MODE:Mmeta*} != "") > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional > (${.MAKE.MODE:Mnofilemon} == "") > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > "/usr/src/share/mk/sys.mk", line 476: if-less endif > bmake: fatal errors encountered -- cannot continue > *** Error code 1 Move the /usr/src somewhere else, make a new /usr/src dir and then svnlite co https://svn.FreeBSD.org/base/stable/11 /usr/src make sure it completes normally then cd into it and make cleandir. What happens? -- 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"
Re: why does buildworld fail on stable/11 ?
On 22/01/2018 09:17, Scott Bennett wrote: > Anyway, I'm stuck. Can someone please tell me what is going wrong and > how to fix it? I'd really like to be able to update my system, not only to > keep it reasonably current, but also to be able to customize a kernel. Thanks > in advance for any suggestions/solutions. Hi, What I'd do is firstly to make things as simple as possible. First do the upgrade simply. Either delete or call make.conf & src.conf something else. Then get a fresh src and ports tree via svnlite. Then do rm -rf /buildwork/ccache.freebsd mkdir /buildwork/ccache.freebsd then [/usr/src #] make cleandir && make clean && make buildworld && make buildkernel && make installkernel && mergemaster -p [make changes if needed] [/usr/src #] make installworld && mergemaster [make more changes if needed] reboot then cd into /usr/src as root, then do yes | make delete-old yes | make delete-old-libs reboot again then re-enable your extra lines in make.conf and src.conf, if you need them. It may be down to something in the ccache dir, I guess. -- 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"
Re: console-only freebsd
On Mon, Oct 09, 2017 at 07:58:12AM -0700, Chris H wrote: You might also find this article by Warren Block of value: http://www.wonkity.com/~wblock/docs/html/hiresconsole.html interesting, I guess that's another way of looking at it. Bear in mind though that the cpu really is low powered. On top of that, it's a netbook so keeping power consumption low is important In the meantime I've found that links2 might do what I want as it supports text and graphics in svga/framebuffer. thanks for the suggestion -- 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"