Re: anyone had experience expanding uid_t and gid_t?
On 19/8/17 11:15 am, Julian Elischer wrote: at $JOB there are clients where 32bits is starting to chafe. Has anyone expanded them? Other than a few offline comments I haven't heard anyone directly respond to this. Does anyone have any comments on feasibility or suggestions? NFSV3 will definitely be screwed.. This is starting to become a serious limitation in some places. Especially large institutions with Samba active. Samba uses a map between SIDs (session IDs) and UIDS, but it's a sparse map and due to various issues the mapping is not able to re-use numbers well. ___ 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: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc
On 21 Aug 2017, at 20:52, O. Hartmannwrote: > > I just updated to r322769 and now I face this when trying to recompile > kernel/world again: > > make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version || > echo 0.0.0" > exited on a signal make: "/usr/src/share/mk/bsd.compiler.mk" line 155: Unable > to > determine compiler type for CC=cc. Consider setting COMPILER_TYPE. What is the output of "cc --version" ? -Dimitry signature.asc Description: Message signed with OpenPGP
Re: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc
O. Hartmannwrote: > I just updated to r322769 and now I face this when trying to recompile > kernel/world again: > > make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version || > echo 0.0.0" > exited on a signal make: "/usr/src/share/mk/bsd.compiler.mk" line 155: Unable > to > determine compiler type for CC=cc. Consider setting COMPILER_TYPE. > > > System has been recompiled previously with filemon loaded. > > So, how is this to be solved? Ideas, please. I do not want to wreck my whole > farm here ... > Well first off you want to find what 'cc' was invoked above. See if it cored - if it is something that should have run successfully on the host. The fact that the errors say 'make:' rather than 'make[1]:' indicates this is the initial instance, if it were a sub-make you could add .META to the target that ran the sub-make and thus see from .meta file which 'cc' was run. You could perhaps write a trivial makefile (m) to do that. Ie. give it something like: .MAIN: all all: it it: .META ${MAKE} -C ${.CURDIR} whatever You *may* need it: .META MAKELEVEL=0 ${MAKE} -C ${.CURDIR} whatever to reproduce the cirsumstances better. ___ 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"
r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc
I just updated to r322769 and now I face this when trying to recompile kernel/world again: make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version || echo 0.0.0" exited on a signal make: "/usr/src/share/mk/bsd.compiler.mk" line 155: Unable to determine compiler type for CC=cc. Consider setting COMPILER_TYPE. System has been recompiled previously with filemon loaded. So, how is this to be solved? Ideas, please. I do not want to wreck my whole farm here ... Thanks in advance, Oliver -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpZE4XuINmLR.pgp Description: OpenPGP digital signature
assigning priorities to swap partitions?
On an AZURE system there is a "local" device that is useful as swap. It is, I believe, faster than regular network based storage, but it is ephemeral, and may go away during a shutdown. It is in some machines a bit small so we'd like to add a bit more for safety. But we would like the ephemeral local storage to be used first. Can this be done at all? I can't see anything The last time I checked all swap was used in some balanced way. (the manual says so) One solution is to have a small cron job that only creates the added swap partition when the first one is (say) 70% full, but it'd be nice if there were some less hackish way. Another would be to occasionally wake up, and if the swap in use would all fit into the device we would like to be used, we do a swapoff on the other and force everything to be put on the fast drive.. but that sort of defeats the purpose as it's doing extra work.. Has anyone done any work on adding priority to swap? Julian ___ 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: mapping a device from device-id to /dev
On Mon, Aug 21, 2017 at 6:51 AM, Julian Elischerwrote: > > I have the following (Azure) device (disk) id: > > dev.storvsc..%pnpinfo: classid=32412632-86cb-44a2-9b5c-50d1417354f5 > deviceid=-0001-8899-- > > the question is: "how can I map that do /dev/da1".. > You can't. Partially because it's also da1p1, da1p2, etc as well. Partially because storvsc is a SIM and can have multiple devices, partially because there's no device_t to SIM mapping, let alone to the dev_t for the disk drive (and even then you have geom to worry about too). > I know that for my device it IS /dev/da1 > but how can I prove it? there are so many mappings from one space to > another I've totally lost track. > there are acpi mappings, pnpmappngs, /dev/ mappings, PCI space mappings, > things in sysctl, things in their own spaces, etc. etc. > In some architectures htere are fdt mappings and in some it's still pretty > random from what I see. > Yes. There's no way to map, generically, a device_t to a dev_t. In fact, the above sounds like a CAM device, which doesn't even have a device_t, just the device_t of the SIM. storvsc is the SIM that you're lucky has only one device attached. mpt can (and does) have a dozen attached to it. There's also the issue that we create separate devices for each way we present the device to the user: /dev/ufs/lable, /dev/ufsid/numbers, /dev/gpt/name, /dev/gptid/numbers, etc. > Is there a document that covers all of these? > /usr/src/sys, sadly I have a similar issue getting the full, physical map to drives for UEFI. Thankfully, I can use logical names for that. I'm slogging through implementing things, though, its tough going... Warner ___ 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"
mapping a device from device-id to /dev
I have the following (Azure) device (disk) id: dev.storvsc..%pnpinfo: classid=32412632-86cb-44a2-9b5c-50d1417354f5 deviceid=-0001-8899-- the question is: "how can I map that do /dev/da1".. I know that for my device it IS /dev/da1 but how can I prove it? there are so many mappings from one space to another I've totally lost track. there are acpi mappings, pnpmappngs, /dev/ mappings, PCI space mappings, things in sysctl, things in their own spaces, etc. etc. In some architectures htere are fdt mappings and in some it's still pretty random from what I see. Is there a document that covers all of these? ___ 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: [libelftc] internal library or not?
Thank you, David! __cxa_demangle works fine [1] :) Best regards, Michael. [1] https://github.com/z0nt/pstack/pull/2/commits/8f45f92c63d385cd523d67f6ccbc436c7669f9d3 On Tue, Aug 1, 2017 at 6:22 PM, David Chisnallwrote: > On 1 Aug 2017, at 12:36, Michael Zhilin wrote: > > > > Hi Ed, freebsd-current, > > > > I want to add C++ demangling into sysutils/pstack. In man pages I've > found > > eltfc_demangle, exact what I need. This function belongs to libelftc. > "make > > installworld" installs man pages and include files, but there is no > > installed library. As results compilation error is occuried. > > Is pstack written in C++ or linking anything that is? If so, you will get > __cxa_demangle[1] provided by the C++ ABI library (libcxxrt on FreeBSD, > which currently uses the libelftc implementation, though might switch > soon). If not, adding -lcxxrt will provide it. > > David > > [1] https://itanium-cxx-abi.github.io/cxx-abi/abi.html#demangler ___ 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"