Re: which way to update export_args structure?
On Mon, Oct 22, 2018, at 11:05 AM, Brooks Davis wrote: > > This is the direction I'd been thinking. FWIW, the usecase is more that > once you've moved away from the struct it's easy to make incremental > changes then to use a 32-bit mountd on a 64-bit kernel. Moving toward > size-independent interfaces helps both causes though. > > -- Brooks > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) Brooks, What is the benefit or usecase for running a 32 bit mountd on a 64 bit kernel? -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
HEAD amd64 seems unhappy
--- all_subdir_lib/libngatm --- /usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal se [-Werror,-Wtautological-type-limit-compare] if (portno == 0 || portno > 0x) ~~ ^ ~~ 1 error generated. *** [cc_port.o] Error code 1 This code hasn't changed in ages so I can only assume it's clang or such. -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Call for testing VMware open-vm-tools update
VMware has been contributing to making FreeBSD a first class citizen for their open source vmware tools. As a continuing part of this contribution there's a new version of open-vm-tools in the works. The INO64 work in FreeBSD HEAD broke building open-vm-tools for HEAD/i386, and there was a kernel panic that affected HEAD/amd64. That has been addressed and vmware has started QA for the tools for FreeBSD 11.1-R and 10.3-R amd64 and i386. I've given this update a fair amount of testing and it gets a "works on my machine" certification from me. The new version is available as a port at https://people.freebsd.org/~jpaetzel/open-vm-tools.tar.gz . Feel free to give it a spin and please report any issues by filing a bug at https://bugs.freebsd.org/ If you tag the bug you create as ports emulators/open-vm-tools it will get auto-assigned to me. -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: mount_smbfs gives error when stored crypted pw is used
On Wed, Jun 7, 2017, at 12:29 PM, O. Hartmann wrote: > Am Wed, 7 Jun 2017 19:22:34 +0200 > Matthias Apitz schrieb: > > > El día miércoles, junio 07, 2017 a las 02:35:31p. m. +0200, Matthias Apitz > > escribió: > > > > > I have located the bug in /usr/src/contrib/smbfs/lib/smb/subr.c > > > > > > The printf(3C) calls have been added for debugging; the bug is the > > > addition of 13 after crypting every char which let the mask used in ^ > > > operation > > > exceeding 256, i.e. more than one byte, if the string to be crypted is > > > long > > > enough. The two lines added: > > > > > > if (pos > 256) > > > pos = pos-256; > > > > > > fixes this issue and the crypting/decypting works fine; see below; > > > > > > I'll later file a PR and propose the patch; > > > > The PR was already made in 2009: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132302 has a patch > > attached (nearly > > the same solution as I have found), but was never ci'ed :-( > > > > matthias > > > > > > Wow ... that is, simply ... not very good! :-( > > High quality! > > -- > O. Hartmann > > Ich widerspreche der Nutzung oder Übermittlung meiner Daten für > Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 > BDSG). > Email had 1 attachment: > + Attachment2 > 1k (application/pgp-signature) I've taken the bug and am testing it now. Should have it committed by this evening. With some luck we can get it in to 11.1 -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631
> Andriy: > > I am happy to report that the system no longer panics. As requested I > removed > the remaining logs (34G worth) and punished the file system as hard as I > could. > > A scrub of the pool completed without error > > Will the change be committed or do I need to open a PR? > > Please let me know if I can supply additional information or if there > are any > further tests you would like me to perform. > > Thanks again for you prompt reply and apparent solution. > > Regards, > > Michael Jung > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" Great news. I committed the fix this morning. Thanks for reporting the problem and testing the fix. -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r 310850: buildkernel failure: ip_carp.c:615:28: error: incomplete definition
Thanks for the catch ngie. I couldn't reproduce the problem, now I see why. On Fri, Dec 30, 2016, at 03:33 PM, Ngie Cooper (yaneurabeya) wrote: > > > On Dec 30, 2016, at 12:07, O. Hartmann wrote: > > > > > > [...] > > > > ===> cas (all) > > --- all_subdir_carp --- > > --- ip_carp.o --- > > /usr/src/sys/modules/carp/../../netinet/ip_carp.c:615:28: error: incomplete > > definition of > > type 'struct ip6_hdr' return (memcmp(&in6, &ip6->ip6_src, sizeof(in6)) == > > 0); > > ~~~^ > > /usr/src/sys/netinet6/in6.h:662:8: note: forward declaration of 'struct > > ip6_hdr' > > struct ip6_hdr; > > ^ > > --- all_subdir_cam --- > > Building > > /usr/obj/usr/src/sys/WALHALL/modules/usr/src/sys/modules/cam/scsi_pass.o > > --- all_subdir_carp --- > > 1 error generated. > > *** [ip_carp.o] Error code 1 > > Should be addressed in r310864. > Thanks, > -Ngie > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD Installer Roadmap
On Monday, February 21, 2011 08:38:03 pm Devin Teske wrote:
>
> Really, the crux of the issue is that our organization is **just now**
> migrating off of FreeBSD-4 (yes, it's true... there are over 1,000
> FreeBSD-4.11 machines running in production at this very moment spanning
> the entire United States, parts of India, and parts of the Indo-pacific
> rim). Worse? We just added yet-another 200+ to those ranks in the past 2
> months.
>
> My hat is off to you sir... as I envy your position that you can be so
> free-moving. We are encumbered by entrenched methods and do not have the
> luxury of trying new things for the sake of change (case in-point, since
> bsdinstall brings nothing new to the table that we rely upon, it truly
> would be change for the sake of change in our organization).
>
> Fin de dialectics.
>
>
>
>
> --
> Cheers,
> Devin Teske
Maintaining sysinstall for 4.x is indeed a NOOP, since features aren't being
added to it, and the featureset that sysinstall supports is pretty much in
line with the featureset in 4...no ZFS, no geom_*, etc etc etc.
On the other hand, maintaining sysinstall for the next N years of new FreeBSD
releases seems hard, when it's already missing features compared to what
FreeBSD supports, and that's likely to continue to grow.
I totally agree that for internal use, migrating thousands of lines of code
makes no sense whatsoever, especially if sysinstall meets your needs and you
don't care about the functionality it doesn't have. Exporting that to the
community seems to be a questionable use of resources.
I'm no stranger to large deployments. With my ${WORK} hat on we can install a
thousand FreeBSD systems in a week. In my 16+ years of involvement with
FreeBSD I've written three automated installers...quite frankly, ditching
sysinstall for that happened really fast.
I do admit to being a tad curious where you find systems that can run FreeBSD
4 at this point. A single socket intel shows up as 8 or 12 CPUs these days,
more than enough to tie 4.x into knots. Add in disk controllers, NICs, ACPI
(modern systems use that for nearly everything it seems) and suddenly an
installer seems the least of the concerns.
I suppose my last question is along the lines of, "If adding geom_mirror
support to sysinstall was easy, why has it been 6+ years since gmirror made
it's appearance in FreeBSD and you still can't create or install to a gmirror
with sysinstall?"
--
Thanks,
Josh Paetzel
signature.asc
Description: This is a digitally signed message part.
Re: FreeBSD Installer Roadmap
On Saturday, February 19, 2011 02:44:42 am Bruce Cran wrote: > On Saturday 19 February 2011 03:04:39 Devin Teske wrote: > > There are many reasons for this, and none of them are selfish (although > > it remains possible to drum-up some selfish reason, all of the reasons > > behind our motivation are in-fact unselfish). Truth-be-told, I welcome > > the replacement of sysinstall but am very wary that ANY replacement will > > be able to exactly replicate the hardware compatibility that sysinstall > > currently enjoys. I do indeed envision a great celebration as FreeBSD-9 > > bucks sysinstall but also at the same time have nightmares of receiving > > waves of calls from people having trouble (for example) "installing > > FreeBSD-9 on their AMD K6 based system, circa long-long-ago in a > > universe far-far-away." (yes, we do have data centers running that very > > equipment with uptime in the 1,000's of days). > > I think bsdinstall as it currently is is simple enough that there shouldn't > be any compatibility issues: it uses gpart for partitioning, runs tools > like tzsetup to configure settings etc. so there's far less to go wrong > than sysinstall's custom code which for example could crash on the > "probing devices" screen. pc-sysinstall has been used as the PC-BSD installer for quite a while now, and has done a lot of installs on a lot of different hardware platforms. I'll wager that the compatibility of the shell command gpart is a better bet than the "stick your thumbs in you ears and yell nananana while you scribble 1's and 0's to a disk and voila, there's a disklabel" approach that sysinstall uses. That being said, sysinstall holds FreeBSD back in a lot of ways, using GPT labeling, installing to ZFS, or gmirror, using geli, all require you to boot to a shell and do an install by hand. I'm sure more people can chime in to limitations in sysinstall than I can think of off the top of my head. So my question is: Given that everyone involved is very conscious of locking out FreeBSD from hardware platforms due to installer compatibility, wouldn't a better use of your time be investing in the future and ensuring that it works on legacy platforms as opposed to putting sysinstall on life support when it already has some fairly serious missing functionality, that is only likely to become more of an issue in the future? -- Thanks, Josh Paetzel signature.asc Description: This is a digitally signed message part.
Re: Trouble with a atapi-cam backup..
On Thursday 02 September 2010 15:23:46 Randy Stewart wrote: > Hi all: > > So I finally upgraded my 7.3stable main server to 8.1stable... > > And now my backup to atapi-cam is failing.. I get: > > r...@lakerest /usr/tmp]# /usr/local/bin/growisofs -Z /dev/cd0 -R -J > backup_init.08-31-2010.gz > > :-( unable to CAMGETPASSTHRU for /dev/cd0: Inappropriate ioctl for > > device > > > Now atapi-cam I have built into the kernel (not a loaded module).. and > so is scsibus.. and all > its friends. Cam control seems to see the device: > > [r...@lakerest /usr/tmp]# camcontrol devlist > at scbus0 target 1 lun 0 (cd0,pass0) > > Any suggestions of what I left out of the kernel would be most > helpful.. > > Oh my kern.conf is: > > * > include GENERIC > ident mymachine > deviceatapicam > options IPDIVERT > options IPFIREWALL > *** > > And its an i386 > > Thanks > > R > > - > Randall Stewart > rand...@lakerest.net > I've had pretty good luck in 8.1 with the ahci and ada drivers, which will present CDROMs as SCSI devices without ATAPICAM. device ahci device ada # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass# Passthrough device (direct SCSI access) And remove: # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering And ATAPICAM of course. -- Thanks, Josh Paetzel signature.asc Description: This is a digitally signed message part.
Re: ZFS v28 is ready for wider testing.
../sys/cddl/contrib/opensolaris/uts/common -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - I/usr/obj/usr/src/tmp/legacy/usr/include -static - L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o util.o -lctf -ldwarf -lelf -lz -lpthread -legacy strtab.o(.text+0x109): In function `strtab_print': /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:249: undefined reference to `MIN' strtab.o(.text+0x28d): In function `strtab_insert': /usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:119: undefined reference to `MIN' strtab.o(.text+0x3a1):/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt/strtab.c:145: undefined reference to `MIN' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error # uname -a FreeBSD head.tcbug.org 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Aug 31 16:30:57 UTC 2010 r...@head.tcbug.org:/usr/obj/usr/src/sys/HEAD amd64 -- Thanks, Josh Paetzel ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BTX halts installing 5.x
On Tue, Dec 02, 2003 at 11:31:12AM -0800, Don Lewis wrote: > On 2 Dec, Josh Paetzel wrote: > > I'm trying to install FreeBSD on a Dual Pentium Pro 200mhz 512K cache system and I > > am getting the > > following error: > > > > CD Loader 1.01 > > > > Building the boot loader arguements > > Looking up /BOOT/LOADER... Found > > Relocating the loader and the BTX > > Starting the BTX loader > > > > BTX loader 1.00 BTX version is 1.01 > > > > int=0005 err= efl=00019286 eip=0001c8a4 > > eax=00a3 ebx= ecx= edx= > > esi=cce65d00 edi= ebp= esp=0009407c > > cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 > > cs:eip=62 6f 6f 74 2e 6e 65 74-69 66 2e 69 70 00 62 6f > >6f 74 2e 6e 65 74 69 66-2e 6e 65 74 6d 61 73 6b > > ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > >00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > > BTX halted > > > > I've tried warm booting after this and I get the same results. I've tried > > 5.0-RELEASE, 5.0-DP1, > > 5.1-RELEASE, and three different snapshots, all of which work fine on my other > > machines, including one > > other SMP box. It's also worth noting that 4.8-RELEASE and 4.9-RELEASE install > > fine on this box. > > > > I can boot 4.9 and post a dmesg if that would help, but to briefly describe the > > hardware: > > > > Intel PR440FX Mainboard > > Dual Pentium Pro 200mhz 512K Cache CPUs > > Adaptec 7880 SCSI controller > > 4.3 gig IBM Wide SCSI-2 Disks > > Intel EtherExpress Pro LAN adapter > > I've tried a couple different video cards, Cirrus Logis and SIS PCI > > 320 Megs of Registered ECC SDRAM > > Could this be a result of the switch from emulated floppy bootable CDs > to 'no emulation' bootable CDs that happened with between the 4.x and > 5.x branches? > > If you can do a "make release" to create you own .iso images, try doing > it with the EMUL_BOOT variable defined, which will generate the .iso > images with the emulated-floppy boot code. Booting the install floppies worked fine. Thanks for the tip. :) Josh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BTX halts installing 5.x
I'm trying to install FreeBSD on a Dual Pentium Pro 200mhz 512K cache system and I am getting the following error: CD Loader 1.01 Building the boot loader arguements Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX version is 1.01 int=0005 err= efl=00019286 eip=0001c8a4 eax=00a3 ebx= ecx= edx= esi=cce65d00 edi= ebp= esp=0009407c cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=62 6f 6f 74 2e 6e 65 74-69 66 2e 69 70 00 62 6f 6f 74 2e 6e 65 74 69 66-2e 6e 65 74 6d 61 73 6b ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 BTX halted I've tried warm booting after this and I get the same results. I've tried 5.0-RELEASE, 5.0-DP1, 5.1-RELEASE, and three different snapshots, all of which work fine on my other machines, including one other SMP box. It's also worth noting that 4.8-RELEASE and 4.9-RELEASE install fine on this box. I can boot 4.9 and post a dmesg if that would help, but to briefly describe the hardware: Intel PR440FX Mainboard Dual Pentium Pro 200mhz 512K Cache CPUs Adaptec 7880 SCSI controller 4.3 gig IBM Wide SCSI-2 Disks Intel EtherExpress Pro LAN adapter I've tried a couple different video cards, Cirrus Logis and SIS PCI 320 Megs of Registered ECC SDRAM I've tried googling for a solution for this as well as perused the -CURRENT archives and haven't seen anything relevent to this issue. Thanks in Advance, Josh Paetzel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCSI Question
- Original Message - From: Robert Small To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Saturday, July 08, 2000 5:45 PM Subject: SCSI Question Damon Hammis wrote:> The jumpers are set wrong on the card. I had the exact same problem with> an aha-1542 and aha-1540 card recently. The docs on the jumpers that you> can get on Adaptec's site are kind of cryptic, but the card will work once> you get the jumpers placed correctly.>
Re: SCSI Question
- Original Message - From: "Robert Small" <[EMAIL PROTECTED]> To: "freebsd-questions@FreeBSD. ORG" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, July 07, 2000 6:49 AM Subject: SCSI Question > I installed an Adaptec AHA-1542 controller in my system tonight, and > hooked up a Sony SDT-5000 tape drive. > > When I try to boot into FreeBSD (5.0-2511-CURRENT FreeBSD > 5.0-2511-CURRENT #4: Thu Jul 6 20:31:41 CDT 2000) I receive: > > Waiting 15 seconds for SCSI devices to settle down > (approximately 30-45 seconds later) > (Probe0:aha0:0:0:0) CCB 0xc782c508 > (Probe0:aha0:0:0:0) CCB 0xc782c508 > aha0: aha_cmd: Timeout waiting for adapter idle > ahainitmboxes: Initialization command failed > aha0 no longer in timeout > (Probe6:aha0:0:6:0) CCB 0xc782c508 > (Probe6:aha0:0:6:0) CCB 0xc782c508 > aha0: aha_cmd: Timeout waiting for adapter idle > ahainitmboxes: Initialization command failed > aha0 no longer in timeout > > And it keeps repeating. I had to remove the card to boot into FreeBSD. > The card recognizes the tape drive. > > Any ideas? > Do you mean that the card recognizes the tape drive under some other OS? I have an adaptec 1542b that worked fine under win98, but wouldn't work worth anything under FreeBSD. I started playing with the jumpers and here there is about 4 places to set the IRQ on the card. If they aren't all set the same it doesn't seem to matter under win98, but Freebsd can't handle the card unless they are all set the same. I still can't get FBSD to boot off this card, but then it is from 1987 or something like that, so I try not to get too worked up about it. Josh > Robert > > > > Does killing time damage eternity? > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
