FreeBSD Quarterly Status Report - First Quarter 2021

, Daniel Ebdrup Jensen, with a status hat on. ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration

Re: Deprecating base system ftpd?

My vote is for no. Reasoning is simple... at what point does it stop?  By continuously moving stuff from base to ports, FreeBSD slowly becomes just a Kernel. 😉 On 4/3/2021 4:39 PM, Ed Maste wrote: I propose deprecating the ftpd currently included in the base system before FreeBSD 14, and open

Re: current make world brakes if HESIOD enabled

1 error generated. > > Warner > > On Sat, Apr 3, 2021 at 12:18 AM Daniel Braniss <mailto:da...@cs.huji.ac.il>> wrote: > I must be the last person on earth to use Hesiod :-) > this are the diffs: > > diff --git a/lib/libc/gen/getgrent

current make world brakes if HESIOD enabled

I must be the last person on earth to use Hesiod :-) this are the diffs: diff --git a/lib/libc/gen/getgrent.c b/lib/libc/gen/getgrent.c index afb89cab3..5832cb8c6 100644 --- a/lib/libc/gen/getgrent.c +++ b/lib/libc/gen/getgrent.c @@ -971,7 +971,7 @@ dns_group(void *retval, void *mdata, va_list ap)

Re: qlnxe driver not in 13.0 arm64

/unibia/freebsd/misc/arm64/qlnxe_13.0-RC4-arm64.log On 3/30/21 2:31 PM, John-Mark Gurney wrote: Daniel Morante via freebsd-stable wrote this message on Sun, Mar 28, 2021 at 03:23 -0400: I installed 13.0-RC3 ARM64 from the DVD ISO image (FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso <h

Re: qlnxe driver not in 13.0 arm64

e-with "${LINUXKPI_C}" dev/qlnx/qlnxe/qlnx_ioctl.c optional qlnxe pci \ compile-with "${LINUXKPI_C}" dev/qlnx/qlnxe/qlnx_os.c optional qlnxe pci \ compile-with "${LINUXKPI_C}"| On 3/30/21 3:00 PM, Hans Petter Selasky wrote: On 3/30/21 8:31 PM, John-Mark Gurney wr

qlnxe driver not in 13.0 arm64

I installed 13.0-RC3 ARM64 from the DVD ISO image (FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso ). There is no "if_qlnxe" kernel model present on the install media, or on the system after install

FreeBSD Quarterly Status Report - Fourth Quarter 2020

thank them, as otherwise, we wouldn't have anything to do. Please note that the deadline for submissions covering the period between January and March is March 31st. We hope you'll enjoy reading as much as we enjoyed compiling it. Daniel Ebdrup Jensen, on behalf o

LSI 53c1020 (mpt) troubles

o arrive :) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubs

Re: kqueue and NFS

ed, it had nothing to do with the upgrades but instead I had installed ‘watchdog.py’ which flaks->werkseig->reload decided to use :-( rabbit hole indeed. thanks, danny > Regards, > Ronald. > > Van: Daniel Braniss > Datum: woensdag, 11 november 2020 09:40 > Aa

kqueue and NFS

Hi, I have a vague recollection that kqueue does not work for NFS files, any chance that this will be made possible? cheers, danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscri

FreeBSD Quarterly Status Report - Third Quarter 2020

#x27;ve been in making it. Daniel Ebdrup Jensen, on behalf of the quarterly team. __ FreeBSD Team Reports * FreeBSD Foundation * FreeBSD Release Engineering Team * Cluster Administration Team * Continu

Re: EFISYS shortcuts on Xfce desktops

> On 18 Aug 2020, at 18:48, Guido Falsi wrote: > On 18/08/20 05:23, O'Connor, Daniel wrote: >> >>> On 18 Aug 2020, at 11:29, O'Connor, Daniel wrote: >>> I think it would make sense to patch the port to add another stanza which >>> matches

Re: EFISYS shortcuts on Xfce desktops

> On 18 Aug 2020, at 11:29, O'Connor, Daniel wrote: > I think it would make sense to patch the port to add another stanza which > matches EFISYS as well as EFI. > > What do you think? I was going to file a bug but bugzilla is having a nap right now. This patch works f

Re: EFISYS shortcuts on Xfce desktops

> On 18 Aug 2020, at 11:23, O'Connor, Daniel wrote: > >> On 8 Aug 2020, at 18:03, Guido Falsi via freebsd-stable >> wrote: >> Hope this helps. > > Thanks for this, I got it working by specifying block.device (twice, once for > /dev/msdosfs/EFISYS and

Re: EFISYS shortcuts on Xfce desktops

/dev/gptid/). Is there a way it can key off (say) the volume name or UUID instead? I tried a few keys like volume.uuid and volume.label but they don't work. Perhaps that is because they are only filled in after the preprobe, hence the rules don't match until after the

Re: vmware/vmx causing problems

> On 10 Aug 2020, at 09:46, Rainer Duffner wrote: > > > >> Am 10.08.2020 um 07:27 schrieb Daniel Braniss : >> >> hi, >> suspend/resume/migrate works fine up to 11.3, >> in 12.1 it usually becomes very unresponsive, ping can take several minutes &

vmware/vmx causing problems

hi, suspend/resume/migrate works fine up to 11.3, in 12.1 it usually becomes very unresponsive, ping can take several minutes after a suspend/migrate. switching to em works fine. any ideas on how to save this? danny ___ freebsd-stable@freebsd.org mai

FreeBSD Quarterly Status Report - Second Quarter 2020

@, who decided to take down his shingle. His contributions not just the quarterly reports themselves, but also the surrounding tooling to many-fold ease the work, are immeassurable. We hope you find the report as interesting as we have, Daniel Ebdrup Jensen (debdrup@), on behalf of the

Re: IPMI KVM mouse in absolute/tablet mode?

't immediately find anything about support for the absolute/tablet > mode. Currently ums doesn't grok absolute mice, however you can use utouch instead - check out the misc/utouch-kmod port. I've successfully used it with Supermicro IPMI - good luck :) -- Daniel O'Connor "

Re: CARP under Hyper-V: weird things happen

/troubleshooting-high-availability-clusters.html#hypervisor-users-especially-vmware-esx-esxi <https://docs.netgate.com/pfsense/en/latest/highavailability/troubleshooting-high-availability-clusters.html#hypervisor-users-especially-vmware-esx-esxi> Daniel > On 31 May 2020, at 19:07,

no output from lua boot

Hi, my last kernel where all works ok is 357067, somewhere since lua boot appeared, I’m not seeing it’s messages, at the moment I’m on release 361071, i’ll try to update later, but what am I missing? hints? danny ___ freebsd-stable@freebsd.org mailing l

watch(4) and [USB] serial

t now. I think this is a bug but I am not sure how the snp stuff is hooked up to find the cause, any one know? Thanks. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum

Re: Audio mixer and mixer control

not as native as I prefer > things. Yes, it does - I haven't used it but it looks like what you want. cuse is for allowing device drivers in user land, I don't think it's required for virtual_oss, just that the same author wrote both :) > Unfortunately, I don't have

Re: Audio mixer and mixer control

on a desktop for quite a while.. What does this output? cat /dev/sndstat If you just want to play some audio out to the S/PDIF you can tell your audio program to use that particular device (eg /dev/dsp1 or whatever it is) -- Daniel O'Connor "The nice thing about standards is that there

Re: Running FreeBSD on M.2 SSD

Is TRIM still on? I understand the quirks patch indicates the drive has some trouble with 4K aligned writes. If memory serves it I also indicated broken TRIM so to be safe you need both. Daniel > On 29 Feb 2020, at 2:46, Mario Olofo wrote: > > Hello guys, a little update that le

Re: Running FreeBSD on M.2 SSD

pronounced on “server” drives that keep certain buffer capacity on the driv eunused for precisely that purpose. But why should a drive without TRIM wear more quickly? Daniel > On 25 Feb 2020, at 16:07, Pete French wrote: > > > > On 25/Feb/2020 13:28, Mario Olofo wrote: >

Re: Running FreeBSD on M.2 SSD

, because it will spot any flaky hardware/setup easily. Daniel > On 25 Feb 2020, at 15:28, Mario Olofo wrote: > > Good morning all, > > @Pete French, you have trim activated on your SSDs right? I heard that if > its not activated, the SSD disc can stop working very quickly.

Re: Running FreeBSD on M.2 SSD

eeBSD is more agressive with your motherboard/chipset or does not implement known quirk of that — which might trigger some edge cases for the SSD. Ultimately, if you can move that SSD to another motherboard and test it, it would confirm where the issue is. Daniel > On 25 Feb 2020, at 3:35, Mar

Re: limit process memory usage

> On 31 Jan 2020, at 08:10, Gerrit Kühn wrote: > > Hello all, > > I have an application that sometimes develops some kind of memory leak > or similar and eats up all RAM within a few minutes until the system is > running out of memory and swap so the kernel starts randomly killing other > proc

Re: usb QR reader

> On 16 Jan 2020, at 12:26, Hans Petter Selasky wrote: > > On 2020-01-16 11:23, Daniel Braniss wrote: >> 63549 a.outCALL openat(AT_FDCWD,0x1045b,0x2) >> 63549 a.outNAMI "/dev/ttyU0" >> 63549 a.outRET openat -1 errno 6 Device not configu

Re: usb QR reader

> On 16 Jan 2020, at 12:26, Hans Petter Selasky wrote: > > On 2020-01-16 11:23, Daniel Braniss wrote: >> 63549 a.outCALL openat(AT_FDCWD,0x1045b,0x2) >> 63549 a.outNAMI "/dev/ttyU0" >> 63549 a.outRET openat -1 errno 6 Device not configu

Re: usb QR reader

> On 16 Jan 2020, at 12:12, Hans Petter Selasky wrote: > > On 2020-01-16 11:07, Daniel Braniss wrote: >>> On 16 Jan 2020, at 11:16, Hans Petter Selasky wrote: >>> >>> ktracing >> wrote a small c program, that just opens and tries to read, the open

Re: usb QR reader

> On 16 Jan 2020, at 11:16, Hans Petter Selasky wrote: > > ktracing wrote a small c program, that just opens and tries to read, the open fails with ‘’open: Device not configured” and the console shows: Jan 16 11:59:09 neo-black-1 kernel: umodem0: detached Jan 16 11:59:14 neo-black-1 k

Re: usb QR reader

> On 6 Jan 2020, at 00:32, Hans Petter Selasky wrote: > > On 2020-01-05 18:03, Daniel Braniss wrote: >>> On 5 Jan 2020, at 17:08, Hans Petter Selasky wrote: >>> >>> On 2020-01-05 15:32, Daniel Braniss wrote: >>>> status 0x6a1a3 >>>&

Re: nfs lockd errors after NetApp software upgrade.

> On 9 Jan 2020, at 05:24, Rick Macklem wrote: > > The attached patch changes the xid to be a global for all "connections" for > the krpc UDP client. > > You could try it if you'd like. It passed a trivial test, but I don't know why > there is that "misfeature" comment means, so I don't know i

Re: nfs lockd errors after NetApp software upgrade.

top posting NetAPP reply: … Here you can see transaction ID (0x5e15f77a) being used over port 886 and the NFS server successfully responds. 44806952020-01-08 12:20:54 132.65.116.111 132.65.60.56 NLM 0x5e15f77a (1578497914) 886 V4

Re: usb QR reader

> On 5 Jan 2020, at 17:08, Hans Petter Selasky wrote: > > On 2020-01-05 15:32, Daniel Braniss wrote: >> status 0x6a1a3 >> >> 16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 >> frame[0] WRITE 8 bytes

Re: usb QR reader

> On 3 Jan 2020, at 13:05, Hans Petter Selasky wrote: > > On 2020-01-03 11:56, Daniel Braniss wrote: >> Hi Hans, >> can you shed some light/help? >> thanks, >> danny >>> On 2 Jan 2020, at 11:11, Daniel Braniss wrote: >>> >>> H

Re: usb QR reader

Hi Hans, can you shed some light/help? thanks, danny > On 2 Jan 2020, at 11:11, Daniel Braniss wrote: > > Hi, > after connecting this QR reader I see a new /dev/ttyU but as soon as I try > tip, > the device disconnects. (BTW, it’s configured as a ‘Virtual Seria

usb QR reader

Hi, after connecting this QR reader I see a new /dev/ttyU but as soon as I try tip, the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’) dmsg: … Jan 2 10:54:57 pampero kernel: umodem0 on uhub1 Jan 2 10:54:57 pampero kernel: umodem0: on usbus0 Jan 2 10:54:57 pampero kernel

Re: nfs lockd errors after NetApp software upgrade.

> On 21 Dec 2019, at 19:32, Rick Macklem wrote: > > Daniel Braniss wrote: >>> On 20 Dec 2019, at 19:19, Rick Macklem >>> >>mailto:rmack...@uoguelph.ca>> wrote: >>> >>> Adam McDougall wrote: >>>> Try changing bool_t do_tcp

Re: nfs lockd errors after NetApp software upgrade.

ours of analysing the traffic, it seems that nlm is UDP. danny > rick > > On 12/19/19 9:21 AM, Daniel Braniss wrote: >> >> >>> On 19 Dec 2019, at 16:09, Rick Macklem wrote: >>> >>> Daniel Braniss wrote: >>> [stuff snipped] >>&

Re: nfs lockd errors after NetApp software upgrade.

> On 19 Dec 2019, at 16:09, Rick Macklem wrote: > > Daniel Braniss wrote: > [stuff snipped] >> all mounts are nfsv3/tcp > This doesn't affect what the NLM code (rpc.lockd) uses. I honestly don't know > when > the NLM uses tcp vs udp. I think rpc.statd stil

Re: nfs lockd errors after NetApp software upgrade.

sstat -m > will show you which version is actually in use for both FreeBSD and Linux. > all mounts are nfsv3/tcp the error is also appearing on freebsd-11.2-stable, I’m now checking if it’s also happening on 12.1 btw, the NetApp version is 9.3P17 cheers, danny > rick >

Re: nfs lockd errors after NetApp software upgrade.

(NetApp admin) > > On Wed, 18 Dec 2019 at 15:46, Daniel Braniss <mailto:da...@cs.huji.ac.il>> wrote: > > > > On 18 Dec 2019, at 16:55, Rick Macklem > <mailto:rmack...@uoguelph.ca>> wrote: > > > > Daniel Braniss wrote: > > > >&g

Re: nfs lockd errors after NetApp software upgrade.

> On 18 Dec 2019, at 16:55, Rick Macklem wrote: > > Daniel Braniss wrote: > >> Hi, >> The server with the problems is running FreeBSD 11.1 stable, it was working >> fine for >several months, >> but after a software upgrade of our NetAPP server it

nfs lockd errors after NetApp software upgrade.

Hi, The server with the problems is running FreeBSD 11.1 stable, it was working fine for several months, but after a software upgrade of our NetAPP server it’s reporting many lockd errors and becomes catatonic, ... Dec 18 13:11:02 moo-09 kernel: nfs server fr-06:/web/www: lockd not responding Dec

Re: Disabling speculative execution mitigations

> On 7 Dec 2019, at 00:52, Konstantin Belousov wrote: > > On Fri, Dec 06, 2019 at 03:51:04PM +1030, O'Connor, Daniel wrote: >> Hi, >> I am trying to track down a performance drop with the ASPEED xorg video >> driver between FreeBSD 11 and 12 (I'm not expe

Disabling speculative execution mitigations

FreeBSD 11 the performance (measured by a subset of x11perf benchmarks) went down 40% after updating to the latest BIOS (2.2a). Unfortunately on FreeBSD 12 rolling back to the original BIOS (2.2) did not improve performance. -- Daniel O'Connor "The nice thing about standards i

smartd, mfi, SAS and SATA

th Status check Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198 Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], is SMART capable. Adding to "monitor" list.

Re: linker.hints not being update for ARMs

> On 12 Nov 2019, at 18:41, Ian Lepore wrote: > > On Tue, 2019-11-12 at 12:03 +0200, Daniel Braniss wrote: >>> On 12 Nov 2019, at 11:32, Peter Jeremy wrote: >>> >>> On 2019-Nov-12 10:30:21 +0200, Daniel Braniss >>> wrote: >>>>

Re: linker.hints not being update for ARMs

> On 12 Nov 2019, at 11:32, Peter Jeremy wrote: > > On 2019-Nov-12 10:30:21 +0200, Daniel Braniss wrote: >> warning: KLD '/boot/kernel/wlan.ko' is newer than the linker.hints file >> warning: KLD '/boot/kernel/rtwn.ko' is newer than the lin

Re: linker.hints not being update for ARMs

> On 12 Nov 2019, at 10:30, Daniel Braniss wrote: > > hi, > well, at least for allwinner, even running /etc/rc.d/kldxref has no effect, > I noticed this when trying out a wifi dongle, > ... > Starting devd. > Autoloading module: if_rtwn_usb.ko >

linker.hints not being update for ARMs

hi, well, at least for allwinner, even running /etc/rc.d/kldxref has no effect, I noticed this when trying out a wifi dongle, ... Starting devd. Autoloading module: if_rtwn_usb.ko warning: KLD '/boot/kernel/wlan.ko' is newer than the linker.hints file warning: KLD '

Re: python dameon coredumps when started from boot, but not by hand

ed at that point in the boot. This would also capture the stderr output, and should be pretty easy to shoe horn into the rc.d file. Nice thinking! -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___

Re: python dameon coredumps when started from boot, but not by hand

works, then this may not be something within BSD after all. It seems bad that the Python interpreter is calling abort, I would have thought that doing so is pretty tricky to do from pure Python so finding out why would be good.. -- Daniel O'Connor "The nice thing about standards is

Re: python dameon coredumps when started from boot, but not by hand

ld try and find the bit in the python where it starts the 2nd > process and chnage that to log any outout somehow maybe ? Hmm, does changing the command_args line to this work: command_args="start 2>/tmp/waagent.log" work? -- Daniel O'Connor "The nice thing about s

Re: python dameon coredumps when started from boot, but not by hand

that getting the output from that is how to find the issue. What does the rc.d file for it look like? -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebs

Re: python dameon coredumps when started from boot, but not by hand

hon is aborting (ie what Py_FatalError is complaining about). -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freebsd.org mailing list https://l

12.1 weirdness

hi, just trying out 12,1 on a DELL PowerEdge R710, and I see: ... Oct 16 22:52:12 store-08 kernel: bce3: bce_pulse(): Warning: bootcode thinks driver is absent! (bc_state = 0x0023600E) Oct 16 22:52:13 store-08 kernel: Limiting icmp unreach response from 3244 to 200 packets/sec Oct 16 22:52:13 sto

Re: missing date from version

> On 11 Oct 2019, at 11:47, Jamie Landeg-Jones wrote: > > Daniel Braniss wrote: > >> Hi, >> I just compiled r355429 for amd64, and noticed that the compilation date is >> missing from ‘name -a’. >> FreeBSD hp-600 12.1-STABLE FreeBSD 12.1-STABLE r3534

missing date from version

Hi, I just compiled r355429 for amd64, and noticed that the compilation date is missing from ‘name -a’. FreeBSD hp-600 12.1-STABLE FreeBSD 12.1-STABLE r353429 HUJI amd64 there is a now (maybe for a long time?) a -R option to newvers.sh. is there an option to change this? cheers, danny

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

> On 2 Sep 2019, at 16:33, O'Connor, Daniel wrote: > > > >> On 1 Sep 2019, at 16:20, O'Connor, Daniel wrote: >> I modified the driver on the working system to dump the values that >> ASTGetDRAMInfo extracts and hard coded them and it works(!) on th

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

> On 1 Sep 2019, at 16:20, O'Connor, Daniel wrote: > I modified the driver on the working system to dump the values that > ASTGetDRAMInfo extracts and hard coded them and it works(!) on the FreeBSD 12 > system. Obviously while this works for me it's not a long term solu

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

> On 27 Aug 2019, at 18:10, O'Connor, Daniel wrote: > >> On 27 Aug 2019, at 13:45, O'Connor, Daniel wrote: >> >> Although I could set uncacheable (no difference). >> >> Next stop will be obscure BIOS settings I suppose. > > I couldn&#

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

> On 27 Aug 2019, at 13:45, O'Connor, Daniel wrote: > > Although I could set uncacheable (no difference). > > Next stop will be obscure BIOS settings I suppose. I couldn't find anything useful there. I realised that my scfb failure was because I am booting BIOS rat

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

> On 24 Aug 2019, at 10:07, O'Connor, Daniel wrote: >> On 24 Aug 2019, at 02:23, Pete Wright wrote: >> On 8/23/19 7:30 AM, O'Connor, Daniel wrote: >>> Hi, >>> We have a Supermicro X11SSH-F motherboard which has a ASPEED AST2400 video >>&g

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

> On 24 Aug 2019, at 02:23, Pete Wright wrote: > On 8/23/19 7:30 AM, O'Connor, Daniel wrote: >> Hi, >> We have a Supermicro X11SSH-F motherboard which has a ASPEED AST2400 video >> chipset with FreeBSD 12.0-RELEASE r341666 GENERIC amd64 on it. >> Unfortunatel

FreeBSD 12 Xorg vs X11SSH-F / AST

ut it still doesn't work properly. Does anyone have any suggestions? Thanks. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freeb

Re: fsck vs zvol

> On 12 Jun 2019, at 22:21, Eugene Grosbein wrote: > > 12.06.2019 12:17, O'Connor, Daniel wrote: > >>>> The Samba 4 ZFS is from https://wiki.freebsd.org/Samba4ZFS (which I >>>> wrote..) > > You should correct this page and change the line f

Re: fsck vs zvol

> On 12 Jun 2019, at 15:47, Patrick M. Hausen wrote: >> Am 12.06.2019 um 03:04 schrieb O'Connor, Daniel : >> I have a small UFS partition that is the sysvol for Samba 4 (otherwise it >> doesn't work due to ACL issues). > > AFAIK this was fixed by iX Sy

Re: fsck vs zvol

> On 12 Jun 2019, at 15:51, Eugene Grosbein wrote: > >> >> Oh I see for the passno field.. It must be non-zero it fsck won't check it >> at all! > > And you don't need to change /etc/rc.d/fsck script at all. Yeah I reverted that change now. Thank

Re: fsck vs zvol

> On 12 Jun 2019, at 14:40, Eugene Grosbein wrote: > > 12.06.2019 8:04, O'Connor, Daniel wrote: > >> Hi, >> I have a small UFS partition that is the sysvol for Samba 4 (otherwise it >> doesn't work due to ACL issues). >> >> I found tha

fsck vs zvol

#x27;m not sure if marking this FS as 'late' would help (and/or break something else..) Has anyone else tried something like this? The Samba 4 ZFS is from https://wiki.freebsd.org/Samba4ZFS (which I wrote..) Thanks. -- Daniel O'Connor "The nice thing about standards is tha

Re: ZFS...

t is… and only ZFS complains that it reads things back it didn’t write. Before that, I would think UFS was ok… since then, I don’t build a single installation, that does not have at least a mirrored ZFS pool. And “archive servers” (stands for backup) have become the central focus of

Re: freebsd-stable Digest, Vol 820, Issue 6

Sent from my BlackBerry 10 smartphone.   Original Message From: freebsd-stable-requ...@freebsd.org Sent: Saturday, 27 April 2019 2:01 PM To: freebsd-stable@freebsd.org Reply To: freebsd-stable@freebsd.org Subject: freebsd-stable Digest, Vol 820, Issue 6 Send freebsd-stable mailing list submis

Re: ltmain.sh not found

d-file-ltmain_002esh-not-found.html > > That is, teach the script in question to run autoreconf, if you want > this to work. It would appear the port is broken, although FWIW it works for me.. Is your port tree up to date? Have you modified anything? etc.. -- Daniel O'Connor &quo

Re: hw.vga.acpi_ignore_no_vga=1 for installation media

> On 17 Mar 2019, at 19:34, Konstantin Belousov wrote: > > On Sun, Mar 17, 2019 at 10:10:45AM -0600, Warner Losh wrote: >> I generally like this idea... But two caveats... >> >> First, we'd need to update the docs so that folks doing serial installs can >> unset it Though serial installs

Re: Intel Xeon D-2146NT SoC Support

;t* work if 11.0 did (and it would be a regression and should be fixed) however it's not my money so.. :) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___

Re: FreeBSD update & custom kernel

> On 25 Jan 2019, at 21:19, Esa Karkkainen wrote: > > On Fri, Jan 25, 2019 at 05:03:32PM +1030, O'Connor, Daniel wrote: >> Hi everyone, > > Hi Daniel, > >> Is it feasible for freebsd-update to update the source before the >> first reboot so a cus

FreeBSD update & custom kernel

had to go into a separate directory to allow rollback to work it would be a worthwhile tradeoff. I have no idea how feasible such a thing would be though :) Thanks -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from."

Re: zfs on hardware raid array

> On 20 Jan 2019, at 06:28, Daniel Eischen wrote: > We thought it strange that Oracle would spec hardware (I think it's an LSI > controller) that didn't allow JBOD when they themselves recommend not using > hardware RAID for ZFS, and also don't support booting from

Re: zfs on hardware raid array

> On Jan 19, 2019, at 2:31 PM, Brian Bilbrey wrote: > > (Bcc’d to the OP) > > You *could* do what I’ve done in the past - make each disk into a single disk > volume presented by the array, then use the presented volumes to make your > mirrors, z2s, etc… I’m not running that anymore, but it wa

Re: php56

+1 on this request. I have a mission critical app server running an old PHP 5.6 application which will not work on PHP 7+. The system is effectively unmaintainable right now in terms of pkg/ports updates. Best, Daniel > On Jan 13, 2019, at 4:29 AM, tech-lists wrote: > > Hi, >

Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot

> Am So., 6. Jan. 2019 um 08:18 Uhr schrieb Daniel Braniss <mailto:da...@cs.huji.ac.il>>: > > > > On 5 Jan 2019, at 19:40, Ruben mailto:m...@osfux.nl>> wrote: > > > > Hi, > > > > Just to follow up, i've upgraded (freebsd-update

Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot

> On 5 Jan 2019, at 19:40, Ruben wrote: > > Hi, > > Just to follow up, i've upgraded (freebsd-update) one of my apu2c4 today > > - firmware upgrade to v4.8.0.7 (so switched from legacy to mainline) > - FreeBSD upgrade from 11.2 to 12.0 > > smooth sailing so far. > > Ill try updating an apu

pxeboot stuck

Hi, today’s latest 11.2 rev 341671, when booting off local disk all is fine, but pxeboot gets stuck after printing FreeBSD/x86 bootstrap loader. Revision 1.1 (Fri Dec 7 09:45:34 IST 2018 danny-pe-44) - older pxeboot get slightly further, but hang too. older root images w

Re: iSCSI booting with isboot

> On 6 Sep 2018, at 10:18, O'Connor, Daniel wrote: > BootNIC: em0 > Configure: IPv6 by NIC0 > CHAP Type: No CHAP > Attempting to login to iSCSI target and scan all LUNs. > soreceive BHS is not complete > do login failed > > The last two lines repeat many time

iSCSI booting with isboot

evice. It is a VM (ESXi defaults for 64 bit FreeBSD) if that matters. I did have to set kern.cam.ctl.iscsi.ping_timeout=0 on the iSCSI target machine because iPXE's initiator doesn't know how to respond to NOPs so it wouldn't connect. Thanks. -- Daniel O'Connor "The

Re: Yubico Security Keys

ys but have you tried checking the permissions of >> /dev/uhid0* and /dev/ugen1.4 (which will be a symlink to usb/1.4.0) ? >> You can chmod them for now and then if that works have a devd conf or devfs >> rule which sets the permissions appropriately when the device is connecte

Re: Yubico Security Keys

have a devd conf or devfs rule which sets the permissions appropriately when the device is connected. If permissions are the problem it would be nice to see if the error message can be improved too :) -- Daniel O'Connor "The nice thing about standards is that there are

Re: NFS 4.1 RECLAIM_COMPLETE FS failed error

e other commits, but that all seems to work fine now. If it helps, I'm not seeing any "OpenDownGrade"calls in a quick experiment mounting and browsing a test share (attached). Thanks again, Daniel On Sun, Jul 8, 2018, at 7:10 PM, Rick Macklem wrote: > Daniel Engel wrote: >

RE: NFS 4.1 RECLAIM_COMPLETE FS failed error

an alternate change already in SVN that does the same thing better, or is there some corner case preventing this patch from being finalized that I just haven't run into yet? Thanks, Daniel Engel ___ 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: Userland PPP on ADSL

nable verbose logs in > ppp.conf. Good idea, I need to re-set a system back to PPP to test and break it when there isn't someone around to complain about it which might take a while :( -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose fr

Userland PPP on ADSL

ould be nice if the base tool worked properly for what I feel is a not uncommon scenario :) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596

Re: What should do in chrooted environment?

tarting a run (be it buildworld, installworld or whatever). -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

Re: What should do in chrooted environment?

/dev/zero look like device nodes. I've made this mistake too and it produces some very confusing error messages :( -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766

annoying panic on boot

Stopped at vga_bitblt_one_text_pixels_block+0x13e: movl(%rax,%r13,4),%d db> bt Tracing pid 4 tid 100090 td 0xf8000c522620 vga_bitblt_one_text_pixels_block() at vga_bitblt_one_text_pixels_block+0x13e/fr0 vga_bitblt_text() at vga_bitblt_text+0xc0/frame 0xfe2d5160 vt_flush() a

Re: DDD hangs on start on 11.1-R

On Mon, 5 Mar 2018, Trond Endrest?l wrote: On Sat, 3 Mar 2018 18:09+0100, Holm Tiffe wrote: can anyone get ddd get to work in 11.1-R or stable? I've more or less given up on devel/ddd, since it relies on the old pty subsystem, now replaced by the new pts subsystem, to communicate with gdb.

  1   2   3   4   5   6   7   8   9   10   >