Re: No coloring with colorls
On Mon, 25 Mar 2024 23:40:52 +0100, Karel Lucas wrote:
> After installing colorls and making some adjustments to the system, I
> still have no colored output from colorls. Below I have indicated the
> settings that have been made or are present by default. I would like
> to know what is wrong and what needs to be improved.
>
> Default environment:
> TERM=vt220
$ pkg_info -q colorls
ls(1) that can use color to display file attributes
This is a simple hack, taken from FreeBSD, to OpenBSD's ls(1) to
use ANSI sequences to display file attributes in color. There is
a -G flag (somewhat similar to the -F flag). Take a look at the
man page for details. The program is called "colorls", so you may
want to use an alias such as ls=/usr/local/bin/colorls.
Note that you need a color-capable terminal to enable colorls. This
means you should set your TERM to "wsvt25" on the wscons(4) console
and to "sun-color" when using the Sun console, not "vt220" and
"sun", respectively, which are not color-capable in termcap(5).
Maintainer: Christian Weisgerber
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Light is the left hand of darkness
and darkness the right hand of light.
Two are one, life and death, lying
together like lovers in kemmer,
like hands joined together,
like the end and the way.
-- Tormer's Lay [Ursula K. Le Guin, "The Left Hand of Darkness"]
Re: FAT names exceeding spec length
On Tue, 5 Dec 2023 16:46:38 +0100 (GMT+01:00), Nowarez Market wrote:
> so what is techinal explanation of the happening and the cut off to 8.3 ?
Well, for the given title, 8.3 yields:
"Tcl_Tk 8.5 P", but I imagine, for this case, that what it might do is
see an eight character filename and a dot, and expect that it will see
an extension after that. Since it's got not only eight characters and
the start of an extension, it's got another dot way down the way that
has a recognizable extension, and in the middle it's got loads of
whitespace. You haven't shown what the 8.3 result of shortening is
(what's the extension? pdf or 5\ P or 5pr or something else?) Does the
eight character name include whitespace? (since there's one at position
seven in the input filename).
You've presented your conclusion, that android can handle filenames
longer than 255 characters, but openbsd can't, and you've given an
example of an input filename, but not of the resultant 8.3
representation, and only one example. Have you, perhaps, misdiagnosed
the problem?
Amy!
--
Amelia A. Lewisamyzing {at} talsever.org
"Oh, fuck! You did it just like I told you to!" (The manager's lament)
(also the programmer's lament, directed toward a compiler)
Re: Feedback on redesigned OpenBSD.org
On Fri, 11 Aug 2023 20:11:02 -0600, Theo de Raadt wrote:
> When did it become an assumption that we would adopt any of these
> changes?
I don't think that it did become an assumption, but as a number of
people have responded to the initial design, to the point that the
designer offered a revision, I thought I might add to the discussion. I
apologize if it was out place to do so.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Never imagine yourself not to be otherwise than what it might appear to
others that what you were or might have been was not otherwise than what
you had been would have appeared to them to be otherwise.
-- The Duchess [Lewis Carroll]
Re: Feedback on redesigned OpenBSD.org
I'm going to add my couple bits worth.
Summary: I prefer v2 apart from line length; a max might be better.
I'm reading on a laptop with a fairly large display (1920x1200), using
Chrome.
On Fri, 11 Aug 2023 18:33:03 -0500, mich...@mlpdesign.com wrote:
[snip]
> What's Changed in v2:
>
[...]
> - Removed all web fonts (just system defaults now)
I can't tell if I like the system fonts better than the custom ones,
because they're not equal in size, so there are too many combined
differences to be sure.
> - Increased the line-height>
Specified in ex? Or something else?
[ ...]
> - Increased font-size (and specified it in 'em')
The overall change in font is much better for me. I recognize that
small and fancy seems to appeal more to those with a twenty-year old's
eyesight (20:20), but my eyes are presbyopic and larger fonts appeal
much more. Using em to specify relative sizes also means that my
default choices are consulted, and I like that.
> - Removed the max-width of 840px (now full-width)
Not too happy about this, though; it's definitely harder to track lines
as long as they end up being (I can solve that myself by narrowing the
window, of course, but I usually can't be bothered). I've found it
useful to specify line height in ex, and max width in em. For sites
with large blocks of text in paragraphs, setting the max width for p to
somewhere around 50-60 em tends to make the text fit the eight to ten
word English standard (it's maybe a little generous, but I find it
avoids the problem of lines so long one gets lost somewhere between
left margin and right).
> For what it's worth, here's my thoughts about the new design:
>
> Readability: Readability is significantly worse in v2 vs. v1
I will defer to other's sense of style, but for readability I have to
strongly disagree; at least within my setup v2 is much more readable
and (importantly, I think) gives more deference to my preferences on
default sizes and font choices.
> - Line Length, by making the line length unlimited in width, it makes it
> extremely difficult to read body text. Reason being, your eye needs to
> track to the next line. The rule of thumb is, the longer the line length
> the bigger the line-heigh needs to be. When the line length can be
> unlimited long, it's difficult to set an appropriate line-heigh which hurts
> readability.
Agreed. I think you ought to restore a max, also specified in em, with
a corresponding line height in ex.
>
> - Colors, the more colors that are present, the more distracting a website
> will become. That's ok if it's a marketing website, but a site that's
> primarily
> documentation - you want to reduce the color palette down to only 2 (3 max)
> colors. This is why technical manuals are mostly created in grayscale,
> because color very much distracts the eyes and makes it more difficult to
> read body text. I feel like v2 color palette, which are peoples ask
> to revert
> to the previous color palette causes that. (And I still haven't revert to
> all of the openbsd.org colors)
I'd kind of like to see a v2 with your typographically-selected colors
for text blocks restored (that is, mostly grayscale, so black on white
(or dark gray on cream, for that stylish effect, perhaps) in the light
theme. It might, though, be worthwhile to maintain project team's
colors for highlights and headings and accents and things. I dunno.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Money can't buy happiness, but poverty can't buy *anything*.
Re: Default partitioning scheme ran out of space for updates
On Sat, 13 May 2023 11:16:13 -0500, Allan Streib wrote:
> On Sat, May 13, 2023, at 09:19, Sylvain Saboua wrote:
>
>> Filesystem SizeUsed Avail Capacity Mounted on
>> /dev/sd1a 986M986M -49.1M 105%/
>
> You have something else using space on your root partition.
>
> From my machine, (7.3 amd64):
>
> /dev/sd0a 1005M214M740M23%/
Yup. Daily reports (I turned them back on when they got turned off a
few releases ago) from three machines installed in 6.something and
sysupgraded to 7.3 (all amd64 as well):
Filesystem 1K-blocks Used Avail Capacity iused ifree
%iused Mounted on
/dev/sd0a 102887811989285754413%2081 153821
2% /
Filesystem 1K-blocks Used Avail Capacity iused ifree
%iused Mounted on
/dev/sd0a 100942212736683158614%2064 153454
2% /
Filesystem 1K-blocks Used Avail Capacity iused ifree
%iused Mounted on
/dev/sd1a 102887811067686676012%2133 153769
2% /
OP prolly has a device file in /dev that's been turned into a regular
file and is growing out of bounds, or has a missing mount for something
that tried to write nearly a gigabyte and choked on it.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.org
The law, in its majestic equality, forbids the rich as well as the poor
to sleep under bridges, to beg in the streets, and to steal bread.
-- Anatole France, "Le Lys Rouge"
Re: libressl vs openssl
On Fri, 28 Jan 2022 14:43:04 +, dansk puffer wrote:
> Are there any major security differences between libressl and openssl
> nowadays? From what I read the situation for openssl improved and
> some Linux distros switched back to openssl again with mostly?
> OpenBSD remaining to use libressl.
Hmm. How could one know?
https://www.cvedetails.com/product/383/Openssl-Openssl.html?vendor_id=217
https://www.cvedetails.com/product/30688/Openbsd-Libressl.html?vendor_id=97
That's not the only place one could look, but it does seem a useful
starting point. OpenSSL clearly has made improvements: they're in
single-digit reports each year after 2017.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
It's is not, it isn't ain't, and it's it's, not its, if you mean it is.
If you don't, it's its. Then too, it's hers. It isn't her's. It isn't
our's either. It's ours, and likewise yours and theirs.
--OUP Edpress News
Re: Best practices mirroring large file-system hierarchies?
Per Google, most likely there's a symlink loop in the source.
See mkdirat(2) (it refers to ELOOP).
See also errno(2), which has: 31 EMLINK Too many links
It also has
62 ELOOP Too many levels of symbolic links
Your message has the text from EMLINK, but mkdirat only mentions ELOOP.
That's not dispositive, though (I should look at the code for mkdirat,
but not gonna).
In either case, the problem is almost certainly, as the error message,
indicates, too many links (hard or symbolic), not too few inodes.
On Mon, 7 Jun 2021 21:49:01 +0300, Michael Lowery Wilson wrote:
> mkdirat: Too many links
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
It is practically impossible to teach good programming to students that
have had a prior exposure to BASIC: as potential programmers they are
mentally mutilated beyond hope of regeneration.
-- Edsger Dijkstra
Re: sd0-n vs wd0-n
On Fri, 30 Oct 2020 16:42:18 -0700, Chris Cappuccio wrote:
> Amelia A Lewis [amyz...@talsever.com] wrote:
[snip]
>
> Perhaps the CMOS battery failed and the BIOS reverted to a default setting.
-and-
On Fri, 30 Oct 2020 15:05:23 -0700, obs...@loopw.com wrote:
> My guess is that the nvram of the bios somehow reset its
> configuration back to default. (corruption, power loss, etc. - these
> are cheap parts made with failure rates after all)
>
> The default of most x86 bioses up until the last few years was to
> bring up SATA ports in IDE compatible mode, which will have them show
> up as wd devices.
Thanks both! Quite right. Motherboard manual doesn't show a battery (it
might be there, but it's not in the diagrams). However, the BIOS manual
does take me straight to the place where SATA can be set to ACPI (or
RAID), which does default to IDE. Resetting it returns it to sd.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
There's someone in my head, but it's not me.
-- Pink Floyd
Re: sd0-n vs wd0-n
On Fri, 30 Oct 2020 14:43:12 -0600, John McGuigan wrote:
> Two things that jump to mind are weirdness with Apple hardware (not sure
> this is the case or not) but I recall that in Bootcamp mode the EFI displays
> IDE devices instead of SATA in some cases. I remember Theo(?) mentioning
> this about a MacBookAir some time ago.
Not that. Both machines are ITX tiny (-ish) boxen running amd64 kernels
on intel hardware.
> The other is if you've modified the kernel previously with config(8), as
> you've said you copied it over from another machine.
No, this happened before copying the kernel. On its original machine,
the kernel brings up a similar (2.5") SATA hard drive as sd0. And, in
fact, since I used that machine to investigate the SSDs in question, it
also finds them as USB-hosted SCSI devices, sd1.
I'm not sure what sort of hardware would have to fail on the system
board for it to decide SATA drives aren't scuzzy enough.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
I don't know that I ever wanted greatness, on its own. It seems rather
like wanting to be an engineer, rather than wanting to design something,
or wanting to be a writer, rather than wanting to write. It should be a
by-product, not a thing in itself. Otherwise, it's just an ego trip.
-- Merlin, son of Corwin, Prince of Chaos (Roger Zelazny)
sd0-n vs wd0-n
Heylas again,
So, I have a working machine again, after copying a kernel over from a
working machine, verifying it, and generating a new hash (I have a
whole long saga of investigation, but I'll spare you).
Can anyone suggest why a machine, with no activity but ssh logins and
then a syspatch of patches 2-3 on 6.8 would spontaneously start
considering the SATA disks in the machine (which were previously loaded
as sd0-sd2) as IDE (wd0-wd2)? This seems to have happened (it's the
lasting "scar" from my machine borkage, I guess). Seems a bit weird,
though.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Early to bed and early to rise
makes a man stupid and blind in the eyes.
Re: syspatch -> no partition found ; any simple fix?
Heylas again,
On Thu, 29 Oct 2020 21:40:05 -0700, Greg Thomas wrote:
> On Thu, Oct 29, 2020 at 8:42 PM Amelia A Lewis wrote:
[snip]
>
> If you were just running syspatch I'd be worried that a hardware failure
> showed up on reboot. I'm way out of practice for troubleshooting OpenBSD
> but booting the installer from a USB drive or CD, dropping to a shell and
> checking your disk info will answer the hardware question for you.
On Fri, 30 Oct 2020 09:21:23 - (UTC), Stuart Henderson wrote:
> "No active partition" sounds like no MBR partition is marked as active.
>
> I would boot the installer, shell, "fdisk sd0" and see how it looks, or
> possonly the MBR partition table is not written correctly or has been
> somehow overwritten.
>
Thanks to both of you; I followed up by cracking the case (partly
because the only drive the BIOS had in its boot order was the Toshiba,
and I was pretty sure the boot volume was on an Crucial SSD). With a
little fiddling (changing boot order (when it let me), switching
uefi+legacy to legacy only (and even uefi only, but the only drive that
has gpt is the big data drive (the Toshiba), which doesn't have
anything bootable).
What seems to have happened, weirdly enough, is that my SSDs have gone
from sd in 6.7 and before (at least 6.6) to wd in 6.8. I've got my
daily output from 29 Oct (I keep most recent daily output emails, in
case i need them), which lists everything as sd (sd0 [ssd, boot volume]
and sd2 [toshiba data drive]). Now everything but the boot volume is
disconnected, and it's not sd0, it's wd0. Which might explain its
disappearance ... no, wrong level.
I just brought it up using 'boot /bsd.sp', which bypasses the kernel
crash (which I didn't mention before because I hadn't seen it before):
apparently, when bsd.mp crashes, it drops into ddb, and something
happens that registers in bios: the disk stops being available to the
bios. Variations on unplugging and replugging it, and fiddling with
boot order and 'csm' options will make it find the bootloader again.
Since the behavior is rather strikingly weird (though prolly
irreproducible by sane mortals), I'm gonna open a bug report, on the
chance that I've triggered something that folks there might recognize.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.org
It is practically impossible to teach good programming to students that
have had a prior exposure to BASIC: as potential programmers they are
mentally mutilated beyond hope of regeneration.
-- Edsger Dijkstra
syspatch -> no partition found ; any simple fix?
Heylas,
So, I ran 6.8 syspatch (patches 002 and 003 together) for three systems
today (yesterday by the time anyone sees this, most likely). Two came
right back up as expected. The third didn't, but as it's local, I could
go retry at the console (all three were actually patched and rebooted
via ssh).
It won't start the boot, but displays "No active partition". Checking
online, this message seems to indicate a failed upgrade, with the
bootloader load incomplete, and (because I was distracted, and running
three updates in a state of fatigue), it's actually likely that what I
did was to Ctrl-B D out of tmux before it returned from kernel
relinking, and then hit doas reboot unthinkingly. Anyway, that's my
guess.
Is there a straightforward way to install kernel and bootloader without
requiring a system reinstall? Can I 'upgrade' with an install cd or usb
stick from (broken) 6.8+sp3 to 6.8, and then syspatch it up to date?
I'm trying to avoid full reinstall because that seems likely to wipe
out existing configuration. I figure my fallback is create install
stick/cd (from the other local 6.8, which was successfully updated),
boot from that, pull backups of all the configuration so I don't have
to reconfigure all the services (and double-check sizes and locations
of disk slices on the boot drive, and store that somewhere safe, then
reinstall and copy stuff back (it's all backed up, in fact, but it's
not backed up recently enough for confidence). So ... faster way to fix
my screwup, when I've probably borked my kernel and the bootloader,
somehow?
Or if it is entirely impossible that "No active partition" could be the
result of kernel relinking borkage, and it's obvious to someone that
something else (hardware failure showing up on a reboot?) happened, I'd
welcome clues. Thanks.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.org
Time and trouble will tame an advanced young woman, but an advanced old
woman is uncontrollable by any earthly force.
-- Sir Impey Biggs [Dorothy L. Sayers, "Clouds of
Witness"]
Re: Unbound Problems (Reverse Direction)
please disregard this. as expected, if one mentions 'typo' it is inevitable that one will embarrass themselves profoundly. as it happens i read the config too quickly and entirely wrongly. On Thu, 9 Jul 2020 15:21:27 -0400, Amelia A Lewis wrote: > On Thu, 9 Jul 2020 17:44:48 +, ken.hendrick...@l3harris.com wrote: >> name: 2.168.192.in-arpa.arpa. > ^ > > It's a mystery, as well, why you would set up nsd (an authoritative > sever) if you're not delegating to it in the recursive/caching server. > But if you're gonna replicate the content in unbound.conf, don't typo > your network number. 9 != 7 > > Amy!
Re: Unbound Problems (Reverse Direction)
On Thu, 9 Jul 2020 17:44:48 +, ken.hendrick...@l3harris.com wrote: > name: 2.168.192.in-arpa.arpa. ^ It's a mystery, as well, why you would set up nsd (an authoritative sever) if you're not delegating to it in the recursive/caching server. But if you're gonna replicate the content in unbound.conf, don't typo your network number. 9 != 7 Amy!
Re: More than 16 partitions
S 16" (whitespace varies, but the number doesn't).
So the standard/universal 16 partitions take up 256 bytes in the array
of struct partition. Therefore:
160 + 256 = 416 (which is, of course, less than 512)
The comment on MAXMAXPARTITIONS says that 22 is the utmost limit; 16*22
= 352. Add 352 to 160 and ta-da! 512. The limit, as repeated several
times.
Now for the question! If you're skipping over junior-dev-level
analysis, here's where I switch to whining piteously.
So, and I recognize that the answer might reasonably be "go read more
code and figure it out yourself," a question for Theo and others if you
have a moment: why couldn't an arch expand past sixteen? It seems, both
from the math calculating struct size (which may be mistaken, in which
case I apologize) and in the comment for MAXMAXPARTITIONS that more
*are* possible. Even if part of the reason is to preserve space within
the sector for future changes (for instance, to allow the size of the
global part of the struct to increase to 176 or 192 bytes, effectively
leaving reserved bits), couldn't MAXPARTITIONS increase to 20 on arches
where us misc-readers are whining about it?
No, I haven't a patch to offer. I'm not certain that increasing
MAXPARTITIONS without any other changes would break things, but with a
magic number in the disklabel, I'm guessing that there are expectations
of the content elsewhere that may require additional changes. But the
partitions array is final in its containing struct, which looks like
design for later expansion.
I'm also not asking that it be done, or that anyone do the research
*for* me, I'm really just wondering if someone knows the answer
off-hand. What are the obstacles to increasing MAXPARTITIONS to 20 on
amd64? (chosen because it's the arch I'm using)
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Never imagine yourself not to be otherwise than what it might appear to
others that what you were or might have been was not otherwise than what
you had been would have appeared to them to be otherwise.
-- The Duchess [Lewis Carroll]
Re: Selling things through the mailing list allowed? I have compatible THIN CLIENTS for Firewall / Router appliance use Available
On Fri, 31 Aug 2018 08:16:12 +0100, Maurice McCarthy wrote: > On 31/08/2018, Alexis wrote: >> >> Jon Tabor writes: >> >>> Yep, right there with ya. So, ah...what's everyone using for >>> mail >>> filtering these days? Spamassassin? ClamAV? Something else >>> entirely? >> >> i use maildrop: >> >> http://www.courier-mta.org/maildrop/ > > $ pkg_info fdm I like sieve, mostly because it's a publicly specified language. pkg_info shows three manage-sieve implementations. I think most sieve implementations are included with LDAs, which prolly means IMAP servers (I use Dovecot's, which is called pigeonhole; I don't have managesieve turned on so it's just a file in my home dir and sievec to compile/validate it). Amy!
Re: smtpd.conf new grammar
On Sun, 27 May 2018 00:43:02 +0200, viq wrote:
> Sorry, I've read the announcements, looked at man pages and examples,
> but still didn't manage to figure out how to translate "deliver via dovecot
> lmtp"
> (to have sieve working) into the new syntax. So far my config was:
>
> table vusers ldap:/etc/mail/ldap.conf
> table vdomains ldap:/etc/mail/ldap.conf
> table passwd ldap:/etc/mail/ldap.conf
>
> accept from local for local virtual deliver to lmtp
> "/var/dovecot/lmtp"
> accept from any for domain virtual deliver to lmtp
> "/var/dovecot/lmtp"
>
>
> I tried changing those into:
>
> action "lmtp-local" mda "/usr/libexec/mail.lmtp -d /var/dovecot/lmtp"
> virtual
> action "relay" relay
> match from local for local action "lmtp-local"
> match from any for domain action "lmtp-local"
> match from local for any action "relay"
>
>
> but delivery attempts fail with Error ("mail.lmtp: sender must be specified
> with -f")
>
> What would be the proper config for this?
Good point (and I'm going to need it, too, when I get to that point,
for dovecot lmtp on one machine and dspam lmtp on another).
Gilles, shouldn't there be a keyword 'lmtp' to go along with
mbox/maildir/mda/relay/forward-only/expand-only? Comparing old (6.2)
smtp.conf(5) with the updated one linked from your article, it seems to
be the only missing method of delivery.
Or perhaps it just got skipped in the man page? viq, have you tried
action "lmtp-local" lmtp "/var/dovecot/lmtp"
?
(yes, I should do it, but I'm not yet comfortable following -current,
even as I move more and more machines to openbsd, I am a Bad Person™)
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Life is a glorious cycle of song / a medley of extemporanea;
and love is a thing that can never go wrong;
and I am Marie of Roumania.
-- Dorothy Parker
Re: Checking my new smtpd.conf syntax
On Fri, 25 May 2018 16:15:00 +0300, Consus wrote:
> On 15:14 Fri 25 May, Gilles Chehade wrote:
>> On Fri, May 25, 2018 at 03:58:59PM +0300, Consus wrote:
>>> On 14:31 Fri 25 May, Gilles Chehade wrote:
>>>>
>>>> you need an additonal rule such as:
>>>>
>>>> match auth from any sender for any apply remote_users
>>>>
>>>> because:
>>>>
>>>>> #accept from local sender for any relay
>>>>
>>>> no longer matches authenticated users
>>>
>>> Ain't it "action local_users" instead of "apply local_users"? The man
>>> page states "action".
>>
>> oopsie, yes, action, forget about apply, it doesn't exist, I should not
>> answer mail while talking on the phone :-)
>
> Frankly, I like apply better :(
For what it's worth (this is *not* a democracy), I like apply better as
well. "action" to declare; "apply" to refer. There's then no
possibility that someone will attempt to create an action "inline" in a
match directive; the syntax of reference is 'keyword barename' while
the syntax of declaration is 'keyword uniquename activities'. Different
keywords makes it unambiguous for humans; can't use declaration syntax
where reference keyword is used.
I looked at your tests, Gilles, and was hopeful because they all use
'apply'. I found that easier to understand. However ... chances are, if
the tests were created early, that others have already argued in favor
of using the same keyword for declarations and references.
Amy!
Amelia A. Lewisamyzing {at} talsever.com
Light is the left hand of darkness
and darkness the right hand of light.
Two are one, life and death, lying
together like lovers in kemmer,
like hands joined together,
like the end and the way.
-- Tormer's Lay [Ursula K. Le Guin, "The Left Hand of Darkness"]
Re: /etc/netstart - order of operations (lo vs physical interfaces)
A read of the script itself shows loopback initialized prior to
hardware interfaces, at least in 6.2 (haven't upgraded yet).
On Fri, 27 Apr 2018 08:21:54 -0400, Gabriel Guzman wrote:
> Just a quick clarification, lo(4) says that the loopback interface
> should be configured last, and /etc/netstart seems to support this
> but netstart(8) says that the loopback interface is configured `before`
> physical interfaces:
Date in the man page for lo(4) is 2013. I'm guessing that the network
system has moved on since then, and it's actually the lo(4) source
that's out of date.
Or, possibly, the netstart authors aren't aware of the potential
problems, so started initializing loopback devices first, and ought to
change things.
:-)
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
There's someone in my head, but it's not me.
-- Pink Floyd
Re: mandoc output paper size
On Thu, 26 Oct 2017 16:14:36 +0200 (CEST), Walter Alejandro Iglesias
wrote:
> In the ps file generated by mandoc you should have this line:
>
> %%DocumentMedia: Default 595 841 0 () ()
>
> Where 595 841 correspond to A4. If you set output paper to "letter"
> that line will say:
>
> %%DocumentMedia: Default 612 790 0 () ()
So these measures are in points?
https://en.wikipedia.org/wiki/Point_(typography)
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Light is the left hand of darkness
and darkness the right hand of light.
Two are one, life and death, lying
together like lovers in kemmer,
like hands joined together,
like the end and the way.
-- Tormer's Lay [Ursula K. Le Guin, "The Left Hand of Darkness"]
Re: mandoc output paper size
On Thu, 26 Oct 2017 14:25:07 +0200, Jan Stary wrote:
> Yes it does. But why does it say e.g. "y841x595" instead of A4?
> (Maybe "A4" is just a shorthand for that, I don't know).
I don't think so. If that's the actual target size, it seems to be A1.
https://en.wikipedia.org/wiki/ISO_216#A_series
On the other hand, any A-series target should scale precisely without
stretching or distortion to any other A-series target, due to the
design of the series.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.com
Confidence: a feeling peculiar to the stage just before full
comprehension of the problem.
Re: "Re: stub-addr in unbound.conf & unbound man page wording"
On Thu, 27 Jul 2017 04:58:02 +1000 (AEST), Damian McGuckin wrote:
> On Wed, 26 Jul 2017, Damian Haehlen wrote:
>
>> do-not-query-localhost: no
That seems like one of those awkwardly-phrased directives.
"Do you not deny Satan and all his works?!"
"YES! Wait, what? I mean, no, NO! I mean, deny, deny DEN-urk"
...
"Will you not have cake, or death?"
"Cake, please. Wait! What are you doing with that knife! No! I want
*ca--*urk"
...
Possibly these are slightly hyperbolic examples, of course. But it's
generally awkward asking a question (even implicitly) with a negative,
because it can be ambiguous as to whether a negative response affirms
the negative in the question or rejects it.
Amy!
--
Amelia A. Lewisamyzing {at} talsever.org
Crap, I have levitation class at 25:131. Better set the alarm to
'cinnamon'.
-- xkcd 313
Re: IPPORT_RESERVED 'security' check in nfsd obsolete?
On Thu, 19 Jan 2017 15:51:53 +0100, Nicolas Schmidt wrote: > Am 19.01.2017 um 12:21 schrieb Theo de Raadt : > >>> Then may I suggest to add an option to disable this behaviour for specific >>> mounts? >> >> No. >> >> NFS always required reserved ports. > > Do you mean that the "reserved ports restriction" is required as part of the > NFS protocol spec? I took a look at > https://tools.ietf.org/html/rfc7530 , but > couldn't find anyhing related to that. https://utcc.utoronto.ca/~cks/space/blog/unix/NFSReservedPorts
OpenBSD 5.8 install; X clobbers virtual terminals
Heyo. dmesg attached at end of email. Short version: I've got an Intel D2500CCE mini-ITX board (Atom 2500; Atom D2000/N2000 Video; DVI and VGA outputs; attached to DVI; driving an Apple Cinema Display). The machine is mostly to be configured as a home (and work-from-home) router/firewall, so virtual terminal only is fine, but I also wanted to experiment with X figuring that I might bring some other machines up on OpenBSD. I'm running 5.8 installed from CD, AMD64, multiprocessor (matching the CPU). My problem: I start X (startx), and it comes up fine (well, it hates the Intel chipset, I think, but it comes up VESA, which is good enough for getting on with), but it clobbers the virtual terminals. That is, if I Ctrl-Alt-F1 (or -F2, etc.) from the X session, I have a "black" screen (it's more a dark gray: there's some power in, because if that display is up when I reboot, the change to no power is noticeable). The same is true for all the virtual consoles if I quit X (from the menu, or via Ctrl-Alt-Bksp, or ssh in and kill it by PID). I don't see mentions of exactly this on OpenBSD lists (MARC: misc, tech, bugs), or googling, but I might not have come up with the right search terms, so if there's an easy/obvious answer, please let me know, okay? I've got two theories about what's happening. Some of the hits that I found, googling, were from Linux (mostly Ubuntu) users who had a conflict between a graphical boot mode (splash screen and stuff) and their X display mode. It's possible that invoking startx puts the video card into a mode that makes it impossible to display the default 80x25 text mode (the virtual terminals go black-ish whether I'm already logged in there or not). If that's the case, is there some magic that would fix it? Changing the kernel's notion of video mode to more nearly match what the VESA driver has decided to use? (it's using 1600x1200 (0x15a), although it correctly recognizes the monitor at 1920x1200 ... should I spend time making X behave better first? but I'd rather have the virtual terminals) That's possibility one. Second possibility is that somehow, when it turns on X, it tries to switch the terminals over to the VGA connector. This seems less likely (I spent most of my time chasing this wild hare, though), because if that were the case, then the X display would go black as well, right? Well, and it's also possible that I've stupidly managed to overlook a firmware loading requirement. Any hints? Sorry to be annoying, but I'm hoping this is something that someone has experience of, so that I can be pointed at documentation that I should have been able to find on my own. Thanks for your time. Amy! (dmesg follows) OpenBSD 5.8 (GENERIC.MP) #1229: Wed Aug 5 08:08:22 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 8554905600 (8158MB) avail mem = 8291741696 (7907MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb8d0 (28 entries) bios0: vendor Intel Corp. version "CCCDT10N.86A.0037.2012.1217.1723" date 12/17/2012 bios0: Intel Corporation D2500CC acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC MCFG HPET acpi0: wakeup devices SLT1(S4) PS2M(S4) PS2K(S4) UAR1(S3) UAR2(S3) UAR3(S4) UAR4(S4) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU D2500 @ 1.86GHz, 1867.01 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 512KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU D2500 @ 1.86GHz, 1866.73 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu1: 512KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (P0P1) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 1 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpicpu0 at acpi0: C1(@1 halt!) acpicpu1 at acpi0: C1(@1 halt!) acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpivideo0 at acpi0: GFX
