Bob Beck wrote:
On Tue, Oct 9, 2012 at 11:04 AM, Bob Beck b...@obtuse.com wrote:
I think Bob's point is that then you use 587 (with auth) for yourselves and
25 (without auth) for mail from the rest of the intertubes.
Yes, that's my point :)
Along with the fact that this is probably the
up these files, but I
suspect this is the areas you are looking for.
--Kurt Mosiejczuk
Inspired by the work I saw bcallah@ doing in cleaning up vi I started
hunting ifdefs for other operating systems and dead code that was ifdef'd
out.
First up is a cleanout of dead code in /usr/bin/pr. The patch kills code
that is ifdef'd out. Resulting binary is identical.
--Kurt
Index:
Here is some more ifdef cleanup. This patch kills all the gunk for PAM
which we don't need. Also gone is some stuff for other operating systems
like ultrix and NeXT.
--Kurt
Index: auth.c
===
RCS file:
On Mon, Apr 13, 2015 at 02:02:26PM -0400, Kenneth Gober wrote:
easier to read, but less useful may not be an improvement. for people
with
large filesystems they will start seeing output like:
/dev/sd0e 3.6T 2.3T 1.3T 66% (followed by inode info)
that's all well and good, but it's then
More ifdef trimming. This time tset is up.
Binary is still identical after this diff.
--Kurt
Index: tset.c
===
RCS file: /cvs/src/usr.bin/tset/tset.c,v
retrieving revision 1.36
diff -u -p -r1.36 tset.c
--- tset.c 18 Sep 2013
This is cleaning up completely redundant #defines housed in #ifdefs in
tset.c
This does not provide an identical binary, since it trims out redundant
information from speeds[]. The diff is fairly straightforward though.
I avoided trimming out the potentially redundant defines that use EXTA and
I came up with the following tweak to get the filesystem status in the daily
emails back into 80 columns. I liked the addition of the inodes in the emails,
but that addition started pushing many of the filesystems past the 80 column
mark, making them hard to read.
--Kurt
Index: daily
I have a console server that was using tip and pre-emptively switched to
cu now since tip is on its way out, and some of my connections didn't work
because I was using /dev/ttyXX entries instead of /dev/cuaXX entries. I
figure adding a mention of that might save some grief.
Here's a patch for
by 8am EDT on Thursday and Friday.
Sorry for the late notice, I sent it to mirrors-discuss first and someone
pointed out I should send it here, but I've been running around getting
ready for the shutdown.
--Kurt Mosiejczuk
I brought ftp5 back up this morning around 7:15am EDT and checked it was
working, it will be going down again around 4pm EDT since RIT is doing
the second half of their electrical substation work tonight from 5pm
until 7am. I'll bring it back up tomorrow morning shortly after 7am.
--Kurt
Due to a just-announced power outage happening this Sunday night,
ftp5.usa.openbsd.org will be going down around 7pm EDT (UTC-4) on
Sunday September 14th. I will bring it back up when the power comes
back at midnight EDT, so it should be back up by 1am EDT.
FYI
--Kurt Mosiejczuk
Due to a power outage happening this Sunday morning,
ftp5.usa.openbsd.org will be going down around 10pm EDT (UTC-4) on
Saturday September 24th. I will bring it back up when the power comes
back at 9:30am EDT on Sunday September 25th, so it should be back up by
11am EDT.
FYI
--Kurt
While reading up on portmap and rpcinfo, I noticed the BUGS section
of rpcinfo.8 talked about problems interacting with NFS on SunOS
versions < 3.0. While I suppose that fact might win a UNIX trivia
contest for someone some day, I'd think we can do without it.
Index: rpcinfo.8
I was out hunting for unused cruft in the source tree and found a
bunch of stuff in /usr/src/libssl/test that is unused. (Reference
to ULTRIX in bctest brought me there).
Each of the following files are not only ancient, but I can find no other
reference to them in the rest of the source tree,
--Kurt Mosiejczuk
On Fri, Jun 02, 2017 at 04:37:08PM +0200, Alexander Bochmann wrote:
> > to OpenBSD 6.1. I've found out that git will abort in one scenario
> > where there is a directory in the tree where the user has execute
> > permissions but not read permissions.
> Did you use the git version from ports
Was looking over the YP section of the FAQ and was intrigued to learn of
yptest(8). Except it was sent to the attic years ago. So this eliminates
its mention as a useful YP debugging tool.
Index: faq/faq10.html
===
RCS file:
Just recently converted the main user machines students and faculty use
to OpenBSD 6.1. I've found out that git will abort in one scenario
where there is a directory in the tree where the user has execute
permissions but not read permissions.
I traced down this abort to a getcwd(3) call where
RIT is turning off the power for electrical maintenance today and tomorrow.
ftp5 will be out 4pm EST until 1am EST. This dance will happen again
tomorrow, but the outage will last until 7am EST the following morning.
FYI
--Kurt Mosiejczuk
On Mon, Mar 05, 2018 at 08:07:53PM -0700, Theo de Raadt wrote:
> If we added the complete english language, /usr would be full.
> (Already a few people having trouble with multiple upgrades + the
> new kernel/library link kits)
If we had definitions, I might agree with you that it might fill
It was annoying me that "aspirational" wasn't in common spellcheck
dictionaries and afresh@ suggested I submit a patch to at least get
the situation corrected for OpenBSD.
Before getting around to this, I noticed "supremacist" wasn't there
either so added that.
Index: share/dict/web2
RIT is doing two overnight power outages again starting 5pm (EDT)
Monday May 13th. Accordingly, ftp5.usa.openbsd.org (which is also
ftp3.usa.openbsd.org and ftp.usa.openbsd.org) will be down from Monday
Afternoon until the power comes back on Wednesday morning on May 15th.
--Kurt Mosiejczuk
On Mon, May 13, 2019 at 07:37:36AM +0100, Stuart Henderson wrote:
> As far as plists go, unless the port only supports py2 or only
> supports py3, it ought to generate the plist with FLAVOR=python3
> and then prefix any lines ending in ${MODPY_PYCACHE}/ with
> ${MODPY_COMMENT}.
Yes. I was
On Sun, Dec 22, 2019 at 05:34:40PM -0800, Lev Lazinskiy wrote:
> Hi everyone,
> This is my first patch, so I apologize in advance if there are any
> errors. I have been reading every man page for my own benefit and I came
> across a typo in check-lib-depends(1). This patch fixes it.
> I plan
On Wed, Jan 01, 2020 at 09:15:14PM -0500, Ted Unangst wrote:
> Kurt Mosiejczuk wrote:
> > cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an
> > alias for -r to scp(1) for those assuming consistency with cp(1).
> But it doesn't implement cp -R semantics
On Wed, Jan 01, 2020 at 09:31:29PM -0500, Kurt Mosiejczuk wrote:
> On Wed, Jan 01, 2020 at 09:15:14PM -0500, Ted Unangst wrote:
> > Kurt Mosiejczuk wrote:
> > > cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an
> > > alias for -r to scp(1) for
cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an
alias for -r to scp(1) for those assuming consistency with cp(1).
--Kurt
Index: scp.1
===
RCS file: /cvs/src/usr.bin/ssh/scp.1,v
retrieving revision 1.87
diff
RIT is shutting down power to the building ftp.usa.openbsd.org resides
in today at 4pm. Accordingly, I will be shutting the mirror down at
3pm. This will be a short outage, and I will be turning things back on
by 9pm tonight.
(All times are EDT)
FYI
--Kurt Mosiejczuk
Learning how LDOMs work on this T4-1 and we only create 8 devices
(each /dev/ldom* and /dev/ttyV*) by default. The now-commonly-available
T4-1 machines can do far more than that pretty easily, so bump up the
number created by default from 8 to 16.
ok?
--Kurt
Index: MAKEDEV
On Wed, May 20, 2020 at 09:24:20AM -0600, Theo de Raadt wrote:
> Kurt Mosiejczuk wrote:
> > > Seems reasonable, what about adopting vmd(8) CAVEATS for ldomd(8)?
> > > Running out of devices with more guests can be nasty do debug.
> > Here's an attempt at doing t
On Wed, May 20, 2020 at 09:35:39AM -0600, Theo de Raadt wrote:
> Kurt Mosiejczuk wrote:
> > I suppose we could look at having ldomctl throw a warning if there are not
> > enough ldom and ttyV devices for the configuration file presented.
> Maybe it can test access to the
On Mon, May 18, 2020 at 08:43:25PM +0200, Otto Moerbeek wrote:
> On Mon, May 18, 2020 at 06:27:04PM -, Miod Vallat wrote:
> > > Learning how LDOMs work on this T4-1 and we only create 8 devices
> > > (each /dev/ldom* and /dev/ttyV*) by default. The now-commonly-available
> > > T4-1 machines
On Mon, May 18, 2020 at 08:12:00PM +0200, Klemens Nanni wrote:
> On Mon, May 18, 2020 at 01:20:07PM -0400, Kurt Mosiejczuk wrote:
> > Learning how LDOMs work on this T4-1 and we only create 8 devices
> > (each /dev/ldom* and /dev/ttyV*) by default. The now-commonly-available
> &
On Wed, Oct 14, 2020 at 02:41:51PM +0100, Stuart Henderson wrote:
> Just found this in my local tree still, iirc danj liked it but there
> wasn't much other enthusiasm. Any other comments? Should I just drop
> the diff? Change 'a' to use 2^10 minimum? Change to fixed 2^10 with
> no auto
On Fri, Oct 02, 2020 at 07:55:53PM +0200, Ingo Schwarze wrote:
> Daniel Jakots wrote on Thu, Oct 01, 2020 at 10:32:31PM -0400:
> > Currently daily(8) runs `df -ikl`.
> By default, it does not. It only does that if you set VERBOSESTATUS.
Actually, it does do it by default. One needs to set
Currently ldomctl init-system will error out in many situations. A number of
them involve requesting more resources than there are available. Right now
onw just gets error messages like:
resource_id larger than max_mblocks
resource_id larger than max_guests
not enough VCPU resources available
not
On Fri, May 22, 2020 at 11:05:21PM +0200, Klemens Nanni wrote:
> kmos noted that `-n' wouldn't bark at overallocation.
> Hoisting PRI reading and moving the `-n' check after constraint checking
> makes it bail on invalid configs just as expected:
> $ cat ldom.conf
> domain guest {
>
On Fri, May 22, 2020 at 04:39:03PM -0600, Theo de Raadt wrote:
> Why is VCPU upper case?
> I don't see any other place it is upper case.
I don't know. It was that way before the change. It's in the file twice
as uppercase, both times when using errx(3). It's not used as lowercase
when using
On Mon, Dec 07, 2020 at 10:55:29PM +0100, Stefan Sperling wrote:
> When announcing RSN (WPA2) capabilities in management frames such as
> association requests, we currently echo back all RSN (i.e. WPA2)
> capabilities which were announced by our peer.
> This is bad in case the peer announces
On Tue, Dec 08, 2020 at 12:11:07AM -0500, Kurt Mosiejczuk wrote:
> > With this patch we only echo the RSN capalibities which we actually support.
> > I am handling MFP and PBAR bits here as done elsewhere, but note that
> > neither of these features is enabled yet at run-tim
On Wed, Dec 30, 2020 at 08:37:49PM +, Miod Vallat wrote:
> Up until 6.5, sparc64 bsd.rd were gzipped kernels. This got lost during
> the Great Installation Media Unification of the 6.6 release cycle, and
> since then bsd.rd are uncompressed.
> The following diff ought to fix this and bring
On Sun, Jan 03, 2021 at 07:19:51PM +, Miod Vallat wrote:
> > Since this change went in, bsd.rd doesn't boot unless I uncompress it first.
> > upgrade detected: switching to /bsd.upgrade
> > Trying /bsd.upgrade...
> > NOTE: random seed is being reused.
> > Booting
On Wed, May 12, 2021 at 01:13:55AM +0200, Jeremie Courreges-Anglas wrote:
> I'd like to drop SWAT, unofficial and dropped by the samba project
> around the switch to samba4.
> > - moved smtps/465 to the standards section (rfc8314)
> The new service was named "submissions". I guess we should
On Thu, Apr 22, 2021 at 03:38:53PM +0200, Martin Pieuchot wrote:
> Diff below remove the KERNEL_LOCK()/UNLOCK() dance from uvm_fault() for
> both amd64 and sparc64. That means the kernel lock will only be taken
> for lower faults and some amap/anon code will now run without it.
> I'd be
On Thu, Apr 08, 2021 at 03:35:33AM +0200, Klemens Nanni wrote:
> This scratch has been itching me for far too long and concerns the
> funcionality behind those cwm(1) default bindings:
This fixes one of the few problems I have with cwm. Works well for me.
ok kmos
--Kurt
>CM-f
On Wed, Mar 16, 2022 at 04:11:41PM +0100, Stefan Sperling wrote:
> This patch adds initial 11ac support to the iwm(4) driver.
> It allows use of 80 MHz channels and VHT MCS.
> In net80211 I added a new rate control module to support VHT rates, as
> a new file called ieee80211_ra_vht.c, derived
This adds the IDs for the thunderbolt 3 controller parts in my T490
ok?
--Kurt
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.2004
diff -u -p -r1.2004 pcidevs
--- pcidevs 2 Sep 2022 10:34:07
On Thu, Sep 15, 2022 at 10:36:40AM +1000, Jonathan Gray wrote:
> On Wed, Sep 14, 2022 at 12:49:48PM -0400, Kurt Mosiejczuk wrote:
> > This adds the IDs for the thunderbolt 3 controller parts in my T490
> > ok?
> Shouldn't this be JHL6240 not JHL6420?
> https://downloadmirro
This adds Crucial to the PCI vendors list and the P5Plus NVMe.
ok?
--Kurt
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.2044
diff -u -p -r1.2044 pcidevs
--- pcidevs 6 Aug 2023 14:40:25 -
50 matches
Mail list logo
