search for: bsds

Hi, I've seen some chatter on NFS boards about kqueue being more reliable than inotify when used in NFSv3 and NFSv2. The chatter is a bit old so I don't know if it is true anymore. Anyone have pro/con experience with dovecot on the inotify/kqueue question when using NFS storage? I realize that kqueue is probably a bit slower and causes some delay with IDLE. Also, it may not really

Pardon me if this is already known -- Theo, at least, had never heard of a Unix doing this. mkstemp() under Linux claims to conform to BSD4.3, but BSDs (FreeBSD and OpenBSD, at least) seem to have a slightly different behavior. Under Linux, new files are created with mode 0666, while under BSDs new files are created with mode 0600. A user need only set his umask to 0 and he will be able to write to temp files created with mkstemp() by suid root...

...s are all configured to use systemd. That?s just skimming the surface. The real hard bits come from the way systemd hooks into the whole FreeDesktop infrastructure and vice versa. (e.g. dbus is now inextricably part of systemd, and many FreeDesktop interactions happen via dbus.) This is why the BSDs are either dropping GNOME and KDE (e.g. Lumina in TrueOS) or have badly lagging ports compared to the upstream version. I suspect it?s probably easier to start with C6, then backport as much as is possible without dragging in any systemd stuff, the same way the BSDs are doing. Good luck to y?all....

...mportant and (b) does not mean that the speaker did not massively over-simplify the opposition to systemd , i.e. he effectively claimed that it was all to do with fear of change when, as you agree, there in fact are substantive, real and objective issues which are widely recognised. > The major BSDs are fundamentally conservative at the project management level, so I believe this tendency is stronger in the BSD user population than elsewhere in the IT world. It?s a form of self-selection bias: the BSDs are run conservatively, so they attract a user base that is also technologically conservati...

The BSDs don't seem as much of an issue. FreeBSD 10 and 11 both have LLVM 3.9 and GCC 4.9. NetBSD 6.1.5 and 7.0 both have GCC 5.3 and LLVM 3.8. Open BSD has a very old GCC, but distrowatch claims that it also has LLVM 3.8. Going back to what Joerg said earlier. http://distrowatch.com/table.php?distri...

...tecture and quality of > systemd, not merely objections to change with no deeper reason. While there certainly are objective problems with systemd?s design and implementation, it is basic human psychology that many people will not move to a newer system despite piles of advantages. The major BSDs are fundamentally conservative at the project management level, so I believe this tendency is stronger in the BSD user population than elsewhere in the IT world. It?s a form of self-selection bias: the BSDs are run conservatively, so they attract a user base that is also technologically conservati...

...st skimming the surface. >> >> The real hard bits come from the way systemd hooks into the whole >> FreeDesktop infrastructure and vice versa. (e.g. dbus is now >> inextricably part of systemd, and many FreeDesktop interactions happen >> via dbus.) This is why the BSDs are either dropping GNOME and KDE >> (e.g. Lumina in TrueOS) or have badly lagging ports compared to the >> upstream version. >> >> I suspect it?s probably easier to start with C6, then backport as much >> as is possible without dragging in any systemd stuff, the sa...

...essage. Initially I had omitted “--arch x64” when compiling the file, but even after specifying the architecture, the error persists. However, I definitely need to be able to run my code on the 64 version. Kind regards Laurent ________________________________ [http://www.vito.be/e-maildisclaimer/bsds.png] <http://bsds.vito.be> VITO Disclaimer: http://www.vito.be/e-maildisclaimer [[alternative HTML version deleted]]

...didn't handle properly the case when both input and output I/O handlers were added to the same file descriptor with different callbacks. This is done commonly in Dovecot, so I'm wondering why more people didn't complain about problems with it.. :) I don't anyway have access to any BSDs so the code is completely untested. Please test how it works before 1.0rc7 :) http://dovecot.org/nightly/dovecot-latest.tar.gz I'd guess the hangs caused by recent RC versions were because the default was to use notify=kqueue instead of notify=none. I changed this back to none unless --with-i...

...Actually it is possible on FreeBSD -- from install(1): ENVIRONMENT The install utility checks for the presence of the STRIPBIN environment variable and if present, uses the assigned value as the program to run if and when the -s option has been specified. I'm not aware of other BSDs having this though, and supporting a collection of command options and environment settings on various platforms seems like it would be rather awkward. However, FreeBSD will likely soon migrate to strip, nm, size and such from the elftoolchain project, and those tools are natively cross-arch so st...

...ded by the USA, using the Pakistani intelligence service, to give the Russian invaders of Afghanistan a bad time. Bin Laden was a frequent guest of honour at USA military bases in the US of A. Inoculation against illnesses is important. As for security, the cess pit is weak security not on Linux, BSDs and others etc. but on M$. It seems to be incredibly easy for one malicious person to launch attacks from machines they control all over the world - and those machines just happen to be running M$. Breaking into M$ machines seems to be t-o-o easy so I suspect it is not password weaknesses that are...

Working with different Linux Distributions makes the life harder. So far I have found out that 'poweroff' & 'reboot' has the same behaviour on Linux/Unix/BSDs. Best Regards, Strahil Nikolov ?? 15 ??? 2020 ?. 5:22:28 GMT+03:00, John Pierce <jhn.pierce at gmail.com> ??????: >On Sun, Jun 14, 2020 at 6:19 PM Pete Biggs <pete at biggs.org.uk> wrote: > >> >> > I'm quite sure that in original Berkeley Unix, as on the VAX &...

...CentOS anyways, /bin/sh is a symlink to >>> /bin/bash... >>> >>> last OS I can think of with an actual Bourne shell was Solaris. >>> >>> >> The various *BSD's have & use the actual Bourne shell .... >> >> > Which one? All the BSDs I know of use the Almquist Shell except for > OpenBSD which uses a patched version of the Public Domain Korn Shell > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos NetBSD...

...them as well. Laurent Franckx, PhD VITO NV Boeretang 200, 2400 MOL, Belgium Tel. + 32 14 33 58 22 Skype: laurent.franckx laurent.franckx at vito.be Visit our website: www.vito.be/english and http://www.vito.be/transport ________________________________ [http://www.vito.be/e-maildisclaimer/bsds.png] <http://bsds.vito.be> VITO Disclaimer: http://www.vito.be/e-maildisclaimer

These days, sshd.c has: static void grace_alarm_handler(int sig) { ... if (getpgid(0) == getpid()) { signal(SIGTERM, SIG_IGN); killpg(0, SIGTERM); } sigdie(...); } however (really) old BSDs do not have getpgid(). They do have getpgrp(), which does what we want here. The question is what to do if we have neither: return the pid (and thus terminate nothing) or return -1 and kill everything wihout getting to the sigdie(). I vote for the latter (since they're unlikely to be able to...

...it already caused uproar, so changing it back might only make matters worse. > > > > The tarballs were changed? > > r172208 I finally updated the FreeBSD ports yesterday and today a user complained about distfile changes. IMO, this revision should be reverted or all the other BSDs will have to chase checksums as well. If you really want to remove the directory, ship a 3.2.1 tarball rather than screwing all the downstream consumers who's infrastructure exists to detect trojan'd tarballs. -- Brooks -------------- next part -------------- A non-text attachment was scr...

On 04/26/16 21:13, John R Pierce wrote: > On 4/26/2016 6:45 PM, Jack Bailey wrote: >> >> Today someone in a meeting claimed the Bourne shell is deprecated, >> one of the reasons being it supposedly has security issues. Well >> that's all news to me, and I cannot find anything online to >> corroborate the claim. Is this true, is it a bash vs. Bourne FUD, or

On Mon, Oct 03, 2016 at 09:04:15AM +0200, Joerg Sonnenberger via llvm-dev wrote: > On Sun, Oct 02, 2016 at 11:09:08PM +0000, Zachary Turner via llvm-dev wrote: > > The BSDs don't seem as much of an issue. FreeBSD 10 and 11 both have LLVM > > 3.9 and GCC 4.9. NetBSD 6.1.5 and 7.0 both have GCC 5.3 and LLVM 3.8. > > Open BSD has a very old GCC, but distrowatch claims that it also has LLVM > > 3.8. > > NetBSD 6.1.5 has GCC 4.5 in base, 7.0...

...>> ENVIRONMENT >> The install utility checks for the presence of the STRIPBIN environment >> variable and if present, uses the assigned value as the program to run if >> and when the -s option has been specified. >> >> I'm not aware of other BSDs having this though, and supporting a >> collection of command options and environment settings on various >> platforms seems like it would be rather awkward. > > For NetBSD, it is STRIP. > > Joerg >

...orthless to do so. > >If we are going to enforce passphrase quality it should be for all OSes. >The world does not revolve around Linux. No matter what the press may >think. The Linux community didn't invent PAM, Sun did. Many more systems than Linux have PAM, Solaris, HP-UX some BSDs for a start. Having said that I agree with the comment ssh-keygen shouldn't be pamified, what you might want to do though is follow the pam model and have a pluggable set of rules that guide a user into choosing a good passphrase. -- Darren J Moffat