• Re: Back To CS Basics. Fuck AI

    From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 17 20:47:05 2026
    From Newsgroup: comp.unix.shell

    On 17 Oct 2026 08:40:24 GMT, St|-phane CARPENTIER wrote:

    Now, there are almost no more interpreted scripts.

    Shell scripts are still interpreted. Not only that, but the shell
    actually seeks through the source file to do a transfer of control.

    How do I know this? Try making changes to the script while it is
    running. ;)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 17 23:29:18 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-17 22:47, Lawrence DrCOOliveiro wrote:
    On 17 Oct 2026 08:40:24 GMT, St|-phane CARPENTIER wrote:

    Now, there are almost no more interpreted scripts.

    Shell scripts are still interpreted. Not only that, but the shell
    actually seeks through the source file to do a transfer of control.

    How do I know this? Try making changes to the script while it is
    running. ;)

    I've just done this ("a script change while it's running") [*]
    (with ksh and bash) and there was no change in behavior of the
    running script.

    You may want to provide an example what you've actually done
    to come to that conclusion (or reformulate your conclusion).

    BTW; I've in other (more complex?) contexts observed that some
    intrusions (tackling the shell program while it runs) do affect
    the running script, but back then I haven't examined the reason
    or circumstances of that effect, or whether it's some effect of
    an interaction with the OS. - So the principle question, what
    exactly happens in what circumstances, is still interesting.

    Janis

    [*] What I've done was to run the following script "dynchg.sh"

    while read ; do
    echo $REPLY
    done

    and change it (from another terminal) while it runs by

    sed -i '2p' dynchg.sh

    I could even remove that file from the directory and it still
    processes data as expected. And there's also no difference if
    that program is explicitly run with the interpreter or running
    it using a shebang interpreter as executable script.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.os.linux.misc,comp.unix.shell on Mon Oct 19 17:18:41 2026
    From Newsgroup: comp.unix.shell

    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:

    On 2026-10-17 22:47, Lawrence DrCOOliveiro wrote:
    On 17 Oct 2026 08:40:24 GMT, St|-phane CARPENTIER wrote:

    Now, there are almost no more interpreted scripts.

    Shell scripts are still interpreted. Not only that, but the shell
    actually seeks through the source file to do a transfer of control.
    How do I know this? Try making changes to the script while it is
    running. ;)

    I've just done this ("a script change while it's running") [*]
    (with ksh and bash) and there was no change in behavior of the
    running script.

    You may want to provide an example what you've actually done
    to come to that conclusion (or reformulate your conclusion).

    BTW; I've in other (more complex?) contexts observed that some
    intrusions (tackling the shell program while it runs) do affect
    the running script, but back then I haven't examined the reason
    or circumstances of that effect, or whether it's some effect of
    an interaction with the OS. - So the principle question, what
    exactly happens in what circumstances, is still interesting.

    Janis

    [*] What I've done was to run the following script "dynchg.sh"

    while read ; do
    echo $REPLY
    done

    and change it (from another terminal) while it runs by

    sed -i '2p' dynchg.sh

    I could even remove that file from the directory and it still
    processes data as expected. And there's also no difference if
    that program is explicitly run with the interpreter or running
    it using a shebang interpreter as executable script.

    If your remove the script while it's still running, chances are the
    interpreter still has it open, so the data is not removed until the file
    is closed---that is, you don't more free space until every reader and
    writer have closed the file. That's the typical UNIX semantics of open
    files. (If I understood the problem here correctly.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.unix.shell on Tue Oct 20 10:54:25 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-19 22:18, Anton Antimo wrote:
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:

    On 2026-10-17 22:47, Lawrence DrCOOliveiro wrote:
    On 17 Oct 2026 08:40:24 GMT, St|-phane CARPENTIER wrote:

    Now, there are almost no more interpreted scripts.

    Shell scripts are still interpreted. Not only that, but the shell
    actually seeks through the source file to do a transfer of control.
    How do I know this? Try making changes to the script while it is
    running. ;)

    I've just done this ("a script change while it's running") [*]
    (with ksh and bash) and there was no change in behavior of the
    running script.

    You may want to provide an example what you've actually done
    to come to that conclusion (or reformulate your conclusion).

    BTW; I've in other (more complex?) contexts observed that some
    intrusions (tackling the shell program while it runs) do affect
    the running script, but back then I haven't examined the reason
    or circumstances of that effect, or whether it's some effect of
    an interaction with the OS. - So the principle question, what
    exactly happens in what circumstances, is still interesting.

    Janis

    [*] What I've done was to run the following script "dynchg.sh"

    while read ; do
    echo $REPLY
    done

    and change it (from another terminal) while it runs by

    sed -i '2p' dynchg.sh

    I could even remove that file from the directory and it still
    processes data as expected. And there's also no difference if
    that program is explicitly run with the interpreter or running
    it using a shebang interpreter as executable script.

    If your remove the script while it's still running, chances are the interpreter still has it open, so the data is not removed until the file
    is closed---that is, you don't more free space until every reader and
    writer have closed the file. That's the typical UNIX semantics of open files. (If I understood the problem here correctly.)

    I have learned not to edit a script while it was running, weird things happened when I did. My theory was that bash kept an index pointing to
    the current line. Dunno if as byte or as line.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.unix.shell on Tue Oct 20 17:38:24 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-20, Carlos E.R. <robin_listas@es.invalid> wrote:
    I have learned not to edit a script while it was running, weird things happened when I did. My theory was that bash kept an index pointing to
    the current line. Dunno if as byte or as line.

    IIRC, here is how it works: bash reads the script via a buffered stream
    as it executes, thus some multi-kilobyte blocks of the script text. If
    you overwrite the script while it is running, it will not affect the
    script text that is already waiting in the buffer, but when bash
    reads to the end of the buffer, after that it will read the altered
    script. Therefore it is somewhat "unpredictable" where the discontinuity
    will occur: you have to know the buffer sizes and relate them to the
    script text.

    Earlier parts of the script are not re-read. Bash does not re-read code
    to iterate over a loop; the whole top-level command is parsed into an
    internal representation that is executed. If a script modifies its own
    source file, everything before and including that modifying command is
    "safe".

    There may be some subtleties with here docs. Suppose have
    a command ending in <<WORD followed by a large amount of here-doc
    data terminated by WORD. I don't know whether Bash reads all of it,
    or under what conditions. Probably when Bash runs on a system where
    here docs have to be done using temprary files, it does have to read
    all the data, put it into the temporary file and then launch the command
    with the <<WORD syntax replaced by the name of the temporary file.

    But on a system where the program can be given a /dev/fd/<n> syntax or
    whatever to refer to a file descriptor, bash can pipe the data to it.
    Maybe it is possible for the script to be modified after that command is launchedm such that the command receives different here doc data.
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Helmut Waitzmann@nn.throttle@erine.email to comp.os.linux.misc,comp.unix.shell on Wed Oct 21 00:54:07 2026
    From Newsgroup: comp.unix.shell

    Janis Papanagnou <janis_papanagnou+ng@hotmail.com>:
    On 2026-10-17 22:47, Lawrence DrCOOliveiro wrote:
    I've just done this ("a script change while it's running") [*]

    [*] What I've done was to run the following script "dynchg.sh"

    while read ; do
    echo $REPLY
    done

    and change it (from another terminal) while it runs by

    sed -i '2p' dynchg.sh

    As the "-i" option is not defined by the POSIX standard but by GNU
    sed, I assume that your example uses GNU sed.
    GNU sed's "-i" option does not edit the file in place.-a Rather it
    sends its output to a new file (instead of to standard output),
    then removes (or renames) the name of the original file.-a
    Finally, the name of the new file is renamed to be the no more
    existing name of the original file.
    GNU sed doesn't modify the original shell script, which has
    been opened by the shell.
    Therefore the shell won't see anything of the new file but rather
    stick to the already opened original file (even, if that original
    file hasn't got any file name).
    I could even remove that file from the directory and it still
    processes data as expected.

    Yes.-a As long as the shell doesn't close the file descriptor
    accessing the original file, it will continue to access the
    original unmodified file.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Fri Oct 23 18:50:09 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-21 00:54, Helmut Waitzmann wrote:
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com>:
    On 2026-10-17 22:47, Lawrence DrCOOliveiro wrote:
    I've just done this ("a script change while it's running") [*]

    [*] What I've done was to run the following script "dynchg.sh"

    -a-a while read ; do
    -a-a-a-a-a-a echo $REPLY
    -a-a done

    and change it (from another terminal) while it runs by

    -a-a sed -i '2p' dynchg.sh


    As the "-i" option is not defined by the POSIX standard but by GNU sed,
    I assume that your example uses GNU sed.

    Yes. (I've just used '-i' for simplicity.)

    A better example would have been to issue (from another shell window)
    the command

    echo "echo END" >> dynchg.sh

    and we then see that after terminating the above loop the "END" will
    be printed.

    (I'm testing with ksh but suppose that in bash it would be similar.)

    Janis

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 23 23:59:17 2026
    From Newsgroup: comp.unix.shell

    On 10/23/26 12:50, Janis Papanagnou wrote:
    On 2026-10-21 00:54, Helmut Waitzmann wrote:
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com>:
    On 2026-10-17 22:47, Lawrence DrCOOliveiro wrote:
    I've just done this ("a script change while it's running") [*]

    [*] What I've done was to run the following script "dynchg.sh"

    -a-a while read ; do
    -a-a-a-a-a-a echo $REPLY
    -a-a done

    and change it (from another terminal) while it runs by

    -a-a sed -i '2p' dynchg.sh


    As the "-i" option is not defined by the POSIX standard but by GNU
    sed, I assume that your example uses GNU sed.

    Yes. (I've just used '-i' for simplicity.)

    A better example would have been to issue (from another shell window)
    the command

    -a-a echo "echo END" >> dynchg.sh

    and we then see that after terminating the above loop the "END" will
    be printed.

    (I'm testing with ksh but suppose that in bash it would be similar.)


    KSH and BASH are "mostly compatible". Minor diffs but
    nothing hard to get around. Anything you can do in KSH
    can be done in BASH.

    There are MANY shells, of course. CSH and ZSH are 'more
    different' for example and it'd be a more complicated
    translation. Not impossible, just more work.

    If KSH works for you then stick with it. Note however
    that MOST distros default to BASH now - so if you plan
    to 'distribute' your work it'd be better to move your
    stuff over to BASH. Most distros, users would have to
    intentionally install KSH and scripts would need a
    shebang at the top to specify which shell to use.
    (good practice, always add the shebang)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 11:53:05 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-24 05:59, c186282 wrote:

    -a KSH and BASH are "mostly compatible". Minor diffs but
    -a nothing hard to get around. Anything you can do in KSH
    -a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    [...]

    -a If KSH works for you then stick with it.

    I use Ksh meanwhile for ~35 years, and since I use a lot of
    Ksh features that Bash just doesn't support there's certainly
    no reason to switch. (Also its speed is a criterion, BTW. And
    back then there were no Bash versions on commercial Unixes;
    but commercial Linuxes haven't the prevalence any more today,
    and play no role now in my private systems context.)

    Note however that MOST distros default to BASH now -

    Yes, Linux often has Bash as its default.

    so if you plan
    -a to 'distribute' your work it'd be better to move your
    -a stuff over to BASH.

    Certainly not.

    And this is short-sighted. If _portability_ is an issue you'd
    better stick with the POSIX subset of both, Ksh and Bash.

    (Sadly, as we observe, especially "Linux kiddies" often don't
    know what that POSIX subset actually is; in their scripts they
    are writing #!/bin/sh and using some bash-specific syntax not
    realizing that there's a difference, and that Bash is not the
    [portable] *standard*.)

    Most distros, users would have to
    -a intentionally install KSH and scripts would need a
    -a shebang at the top to specify which shell to use.

    I don't recall to have ever "intentionally installed" Ksh on
    Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
    you could use out of the box. Later they provided also the
    much better "original" [AT&T] Ksh, and meanwhile you find on
    (some?) Linuxes ksh93u+m, Martijn Dekker's improved version.

    Of course you can call shell scripts with the executable-flag
    set and with a she-bang line on top. Personally I run most
    shell scripts with the interpreter explicitly provided, as in
    ksh my-script flags arguments
    allowing easy debugging by adding '-x' without explicit 'set'
    command in the script. Only if some script gets the status of
    a "standard-command" I regularly use I set the shebang. YMMV.

    (So you don't "need" a shebang line, but it's useful.)

    -a (good practice, always add the shebang)

    Yes, if you are running your scripts executable script (or if
    you want to give your editor a hint for syntax highlighting,
    what shell is actually used, or just for specification purpose;
    but note, as said above, that we see many people have no clear
    idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
    differ from the standard.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 12:06:06 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-24, c186282 wrote:

    KSH and BASH are "mostly compatible". Minor diffs but
    nothing hard to get around. Anything you can do in KSH
    can be done in BASH.

    Now that sounds like something Greg Sullivan of Microsoft would say.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From gazelle@gazelle@shell.xmission.com (Kenny McCormack) to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 12:10:39 2026
    From Newsgroup: comp.unix.shell

    In article <11bhv61$1bjd2$2@dont-email.me>,
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
    On 2026-10-24 05:59, c186282 wrote:

    KSH and BASH are "mostly compatible". Minor diffs but
    nothing hard to get around. Anything you can do in KSH
    can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    I think you're taking Speedy way too seriously here. All of your points
    are valid, of course, but it should not be necessary to respond to the
    troll.

    BTW, you assert that there are (many) features of Ksh that are not (yet) present in bash. I'm not doubting you, but I am curious about examples.
    It seems to me that if you assert something like that, you should give examples.
    --
    Rich people pay Fox people to convince middle class people to blame poor people.

    (John Fugelsang)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?St=C3=A9phane?= CARPENTIER@sc@fiat-linux.fr to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 13:41:20 2026
    From Newsgroup: comp.unix.shell

    Le 24-10-2026, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> a |-crit-a:
    On 2026-10-24 05:59, c186282 wrote:
    Note however that MOST distros default to BASH now -

    Yes, Linux often has Bash as its default.

    I just keep this because I guess, if I don't consider it to be wrong
    because I know what it exactly means, I believe it's often a source of confusion. Because it can mean two different things and three different
    things must be considered when speaking about the default shell.

    Mostly, BASH is the default for the three things, one of them can be
    changed effortlessly, one of them would be very difficult to change in
    the long term and the last one depend on the interaction with others.

    The first thing is the way by which you interact directly with your
    SHELL, a kind of REPL. It's just a field in the /etc/passwd file, it's
    easy to change and if you prefer any SHELL, just install it, change the
    field and it rocks. It's just a matter of taste, nothing can go wrong by changing it.

    The second thing is the shell used by the distro to run its script. This
    one is clearly often BASH, changing it can be challenging. And things
    can go wrong in a lot of ways, from the shebang poorly defined to some specificities expected by the distro. But really, I'm not sure it's a
    real issue because I'm not sure there are reason to change it. The
    fact that systemd doesn't need any shell script is a reason why it's nit
    that important. One can want to change the default provided by the
    distro, but changing the script shell provided by the distro mean each
    time an update is done, the changes will be removed. And they will need
    special care. When there are ways to change the default without changing
    the scripts provided by the distro.

    The last one is the shell you choose to write your scripts. It doesn't
    need to be the same one than the one you are using to interact with your
    shell. As long as the shebang is correctly defined, it depends more on
    the people with whom you share it than with any default choice made by
    any distro. Because people can be more or less comfortable with
    different specificities, even if they can install any available shell.

    Unlike the choice of the default bootloader or the choice of the default
    init system can can have huge impacts, I really don't see how the choice
    of the default shell by a distro can be important (for the end user
    because for the contributor, it has some implications).
    --
    Si vous avez du temps |a perdre :
    https://scarpet42.gitlab.io
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 18:53:40 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-24 14:10, Kenny McCormack wrote:
    In article <11bhv61$1bjd2$2@dont-email.me>,
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
    On 2026-10-24 05:59, c186282 wrote:

    KSH and BASH are "mostly compatible". Minor diffs but
    nothing hard to get around. Anything you can do in KSH
    can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    I think you're taking Speedy way too seriously here. All of your points
    are valid, of course, but it should not be necessary to respond to the
    troll.

    Oh, I didn't knew that he's considered a troll. His post looked just uninformed, or opinionated, not trollish.


    BTW, you assert that there are (many) features of Ksh that are not (yet) present in bash. I'm not doubting you, but I am curious about examples.
    It seems to me that if you assert something like that, you should give examples.

    Mind that his post says "Minor diffs"; and I was not (not primarily)
    addressing the absolute number of features but those features that
    are hard(er) or in practice impossible [based on existing functions]
    to substitute. Off the top of my head I had been thinking of discipline functions, or the "type system" - these are very closely embedded in
    the shell.

    Note that while these features are probably not widely used there's
    also many often used details I used, functions and options, that Bash
    doesn't have as I noticed over the time. I've occasionally mentioned
    those in some posts that where about such functionality, but I'm too
    lazy to create a list or something, which would require to re-test
    every features whether one or another has meanwhile been implemented;
    that would be too much effort.[*])

    Janis

    [*] After finishing writing the post I remembered that we could ask
    a search machine AI, but strangely it had no or found any substantial information, not even the obvious examples; so we have to rely on the
    experts or own experience here.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 21:31:08 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-24 15:41, St|-phane CARPENTIER wrote:
    Le 24-10-2026, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> a |-crit-a:
    On 2026-10-24 05:59, c186282 wrote:
    Note however that MOST distros default to BASH now -

    Yes, Linux often has Bash as its default.

    I just keep this because I guess, if I don't consider it to be wrong
    because I know what it exactly means, I believe it's often a source of confusion. Because it can mean two different things and three different things must be considered when speaking about the default shell.

    Mostly, BASH is the default for the three things, one of them can be
    changed effortlessly, one of them would be very difficult to change in
    the long term and the last one depend on the interaction with others.

    The first thing is the way by which you interact directly with your
    SHELL, a kind of REPL. It's just a field in the /etc/passwd file, it's
    easy to change and if you prefer any SHELL, just install it, change the
    field and it rocks. It's just a matter of taste, nothing can go wrong by changing it.

    The second thing is the shell used by the distro to run its script. This
    one is clearly often BASH, changing it can be challenging. And things
    can go wrong in a lot of ways, from the shebang poorly defined to some specificities expected by the distro. But really, I'm not sure it's a
    real issue because I'm not sure there are reason to change it. The
    fact that systemd doesn't need any shell script is a reason why it's nit
    that important. One can want to change the default provided by the
    distro, but changing the script shell provided by the distro mean each
    time an update is done, the changes will be removed. And they will need special care. When there are ways to change the default without changing
    the scripts provided by the distro.

    I don't see any reason to change the shell used by system scripts. If
    the shebang is /bin/sh, and bad things happen if you uninstall bash and
    they are forced to use ksh, well, it is their fault and it is a bug.
    They should have specified the proper shebang. Just report it.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 24 22:36:52 2026
    From Newsgroup: comp.unix.shell

    On 24 Oct 2026 13:41:20 GMT, St|-phane CARPENTIER wrote:

    The second thing is the shell used by the distro to run its script.
    This one is clearly often BASH, changing it can be challenging. And
    things can go wrong in a lot of ways, from the shebang poorly
    defined to some specificities expected by the distro.

    Debian (and I guess its derivatives as well) long ago moved away from
    the assumption that rCL/bin/shrCY meant the same thing as rCL/bin/bashrCY.
    They introduced a new, very vanilla, POSIX-compliant shell called
    dash(1) <https://manpages.debian.org/dash(1)>, which is the shell that
    is invoked when your script says rCL/bin/shrCY.

    So if you want bash, you have to explicitly ask for bash.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Sun Oct 25 23:49:28 2026
    From Newsgroup: comp.unix.shell

    On 10/24/26 05:53, Janis Papanagnou wrote:
    On 2026-10-24 05:59, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    [...]

    -a-a If KSH works for you then stick with it.

    I use Ksh meanwhile for ~35 years, and since I use a lot of
    Ksh features that Bash just doesn't support there's certainly
    no reason to switch. (Also its speed is a criterion, BTW. And
    back then there were no Bash versions on commercial Unixes;
    but commercial Linuxes haven't the prevalence any more today,
    and play no role now in my private systems context.)

    -a-a Note however that MOST distros default to BASH now -

    Yes, Linux often has Bash as its default.

    -a-a so if you plan
    -a-a to 'distribute' your work it'd be better to move your
    -a-a stuff over to BASH.

    Certainly not.

    And this is short-sighted. If _portability_ is an issue you'd
    better stick with the POSIX subset of both, Ksh and Bash.

    (Sadly, as we observe, especially "Linux kiddies" often don't
    know what that POSIX subset actually is; in their scripts they
    are writing #!/bin/sh and using some bash-specific syntax not
    realizing that there's a difference, and that Bash is not the
    [portable] *standard*.)

    Delay does not necessarily equate with 'ignorance'.

    Different developers ... everyone had their own idea
    of a 'perfect shell' - but then had to adapt and adapt
    again as the Real Needs became more obvious. Now, most
    WILL do the same things - just slightly different syntax.

    I rather liked the 'c-shell' long back because it, well,
    'looked like C'. It was one of the things that attracted
    me to Unix/Linux in the first place. Now I'm happy (ok,
    that's not really the word) with BASH. Not much it
    can't do ... but the fudged-fudged-fudged syntax to add
    features over time CAN be a pain in the ass.

    If I want 'scripting' now, I do it with Python. BASH
    or whatever, maybe it just EVOKES the Python scripts,
    a one or two-liner. Wrote many rather long BASH scripts
    in the past, and while they worked they were, well, just
    TOO messy/cryptic.

    Last big BASH script I did was for backing up a bunch
    of on-network drives. Mount-checking (important), calls
    to rsync and openSSH and ftp, local AND 'cloud', all
    with some confirmation checks along the way. SEMI-repeating
    units but each was a bit 'special'.

    (ALWAYS pre-encrypt before sending to 'cloud' - I do
    NOT trust the providers one bit. Mine had an extension
    that 'suggested' some kind of ZIP, just to help them
    waste time)

    RE-did it in Python. MUCH shorter and more comprehensible
    and a nice easy CSV config file you could tweak in a text
    editor or spreadsheet. Python made it all BETTER.

    Had a 'C' version of that backup pgm earlier. Worked
    fine, but there was a lot of string checking/editing
    involved and 'C' is CLUNKY with string shit. Python
    stole the FORTRAN string-slicing stuff, good deal !

    Won't ever use BASH or any other 'shell script' for
    that kind of task again. Those might be "trad -IX"
    but IMHO they're just OVER. "Solutions" MOVED ON.

    -a-a Most distros, users would have to
    -a-a intentionally install KSH and scripts would need a
    -a-a shebang at the top to specify which shell to use.

    I don't recall to have ever "intentionally installed" Ksh on
    Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
    you could use out of the box. Later they provided also the
    much better "original" [AT&T] Ksh, and meanwhile you find on
    (some?) Linuxes ksh93u+m, Martijn Dekker's improved version.

    Um ... these days, almost all distros, you do have
    to "intentionally install" KSH or any rivals. BASH
    rules by default.

    Of course you can call shell scripts with the executable-flag
    set and with a she-bang line on top. Personally I run most
    shell scripts with the interpreter explicitly provided, as in
    -a ksh my-script flags arguments
    allowing easy debugging by adding '-x' without explicit 'set'
    command in the script. Only if some script gets the status of
    a "standard-command" I regularly use I set the shebang. YMMV.

    Direct spec of the shell IS useful, however the
    'shebang' trick works well too.

    (So you don't "need" a shebang line, but it's useful.)

    -a-a (good practice, always add the shebang)

    Yes, if you are running your scripts executable script (or if
    you want to give your editor a hint for syntax highlighting,
    what shell is actually used, or just for specification purpose;
    but note, as said above, that we see many people have no clear
    idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
    differ from the standard.

    I have, I think, FOUR shells on this machine. The
    shebang IS required/desired.

    Still kinda like 'tcsh', it's there in case I get
    a brain-worm and wanna fool around with olde-dayz
    stuff. Zsh ain't so bad either.

    But, as said, for 'scripting' now, Python is by
    far my #1 choice unless the script is like a
    simple little ten-liner. Tend to use those on
    my PIs.

    Fooled around a bit with Lua and Ruby for scripting,
    but, really, Python and the MASSIVE number of libs
    have them beat. Python will do ANYTHING these days,
    just not as fast as 'C'. However CPU speed is less
    of a thing these days - I/O ops drag things down
    more than the CPU - so Python and 'C' can usually
    compete pretty well.

    There are Python compilers too. The main issue there
    is all the sub-sub-versions of Python, so you always
    have to include the entire binaries into each compilation
    to ensure it'll work. But then space is also a minor
    issue now as well unless you're doing micro-controllers.
    Did my share of those - DO teach you how to really SQUEEZE
    shit in - all computer kiddies should learn MCs first.

    . . .

    ("Harry talks in his sleep, didn't you notice ?"
    Slight telling delay, then Hermonie says 'No' :-)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Sun Oct 25 23:59:11 2026
    From Newsgroup: comp.unix.shell

    On 10/24/26 07:06, Nuno Silva wrote:
    On 2026-10-24, c186282 wrote:

    KSH and BASH are "mostly compatible". Minor diffs but
    nothing hard to get around. Anything you can do in KSH
    can be done in BASH.

    Now that sounds like something Greg Sullivan of Microsoft would say.

    You "can do" most anything in COBOL or FORTRAN or 'C'
    in ANY other lang - just as anything in one shell script
    you can do in any other. The issue is 'how easily' - and
    that depends on your particular application.

    "Needs" eventually rule. So, EVERYONE winds up with kind
    of the same 'capabilities'. How nice/easy/clear, depends.

    Use Python for scripts over maybe 10 lines for everything
    these days. Infinitely capable and READABLE and DOCUMENTED.
    No real competition now. If you hate Python "just because"
    then reconsider.

    Yea yea ... the old shells are "Trad-IX" ... but IMHO
    their day is kinda OVER.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 00:28:00 2026
    From Newsgroup: comp.unix.shell

    On 10/24/26 12:53, Janis Papanagnou wrote:
    On 2026-10-24 14:10, Kenny McCormack wrote:
    In article <11bhv61$1bjd2$2@dont-email.me>,
    Janis Papanagnou-a <janis_papanagnou+ng@hotmail.com> wrote:
    On 2026-10-24 05:59, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    I think you're taking Speedy way too seriously here.-a All of your points
    are valid, of course, but it should not be necessary to respond to the
    troll.

    Oh, I didn't knew that he's considered a troll. His post looked just uninformed, or opinionated, not trollish.

    Thanks, I think :-)

    I never 'troll' - just relate MY experiences and what
    I've learned from them. I had my own path, own needs,
    my own 'environments', starting in the punch-card days.
    But what served ME best may not be what served YOU, what
    I learned may not be what YOU learned.

    A great purpose of groups like these is to bring in
    a LOT of experiences and perspectives. You MAY find
    something compatible/useful in all the diverse advice.
    I don't pretend to know-it-all, nothing close (though
    a few, well, SAY they do :-)

    As said elsewhere, "NEED" eventually supersedes all else.
    Earlier on, all the shells maybe started with a narrow
    'vision' but HAD to include capabilities the other people
    put in. Sometimes the additions were neat/clear, sometimes
    not so much, but they're THERE.

    A sort of 'functional convergence' due to NEEDS.

    Anyway, I reject 'religions' built around shells or
    langs and such. For each need, pick the best tools
    and approaches. "Best" - sometimes that's what most
    harmonizes with YOUR brand of thinking.

    BTW, you assert that there are (many) features of Ksh that are not (yet)
    present in bash.-a I'm not doubting you, but I am curious about examples.
    It seems to me that if you assert something like that, you should give
    examples.

    Mind that his post says "Minor diffs"; and I was not (not primarily) addressing the absolute number of features but those features that
    are hard(er) or in practice impossible [based on existing functions]
    to substitute. Off the top of my head I had been thinking of discipline functions, or the "type system" - these are very closely embedded in
    the shell.

    Note that while these features are probably not widely used there's
    also many often used details I used, functions and options, that Bash
    doesn't have as I noticed over the time. I've occasionally mentioned
    those in some posts that where about such functionality, but I'm too
    lazy to create a list or something, which would require to re-test
    every features whether one or another has meanwhile been implemented;
    that would be too much effort.[*])

    Janis

    [*] After finishing writing the post I remembered that we could ask
    a search machine AI, but strangely it had no or found any substantial information, not even the obvious examples; so we have to rely on the
    experts or own experience here.

    "AI"s aren't really as all-around 'smart' as their
    sellers suggest :-)

    You generally find that out AFTER you $ubscribe .....

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 00:57:26 2026
    From Newsgroup: comp.unix.shell

    On 10/24/26 08:10, Kenny McCormack wrote:
    In article <11bhv61$1bjd2$2@dont-email.me>,
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
    On 2026-10-24 05:59, c186282 wrote:

    KSH and BASH are "mostly compatible". Minor diffs but
    nothing hard to get around. Anything you can do in KSH
    can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    I think you're taking Speedy way too seriously here. All of your points
    are valid, of course, but it should not be necessary to respond to the
    troll.

    BTW, you assert that there are (many) features of Ksh that are not (yet) present in bash. I'm not doubting you, but I am curious about examples.
    It seems to me that if you assert something like that, you should give examples.

    I've mentioned (necessary) "Functional Convergence". If yer
    shell doesn't do something neat-o some other one does NOW,
    it WILL soon enough. Might get squeezed-in nice/neat, or
    maybe NOT. All great/pure ideas/visions eventually HAVE to
    converge somewhere - or vanish into the historical recycle bin.

    Anyway, for 'scripts', I'm 99% Python now. Does EVERYTHING
    and MUCH clearer than any old shell.

    Of note, did NOT use Python until P3 came out. It seemed
    interesting/versatile but why learn an obsolete version ?
    BASIC, skip the bile, became a fair 'script' lang after
    awhile - but, too clunky IMHO - meant for a different
    era, different environment, different mindset.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 06:04:59 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 04:49, c186282 wrote:
    On 10/24/26 05:53, Janis Papanagnou wrote:
    On 2026-10-24 05:59, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    [...]

    -a-a If KSH works for you then stick with it.

    I use Ksh meanwhile for ~35 years, and since I use a lot of
    Ksh features that Bash just doesn't support there's certainly
    no reason to switch. (Also its speed is a criterion, BTW. And
    back then there were no Bash versions on commercial Unixes;
    but commercial Linuxes haven't the prevalence any more today,
    and play no role now in my private systems context.)

    -a-a Note however that MOST distros default to BASH now -

    Yes, Linux often has Bash as its default.

    -a-a so if you plan
    -a-a to 'distribute' your work it'd be better to move your
    -a-a stuff over to BASH.

    Certainly not.

    And this is short-sighted. If _portability_ is an issue you'd
    better stick with the POSIX subset of both, Ksh and Bash.

    (Sadly, as we observe, especially "Linux kiddies" often don't
    know what that POSIX subset actually is; in their scripts they
    are writing #!/bin/sh and using some bash-specific syntax not
    realizing that there's a difference, and that Bash is not the
    [portable] *standard*.)

    -a Delay does not necessarily equate with 'ignorance'.

    Not sure why you bring up that statement; nobody said anything
    like that.

    My statement about the delayed adoption of Ksh features by Bash
    was just pointing to the fact that Bash users had to wait before
    they could use comfortable features that Ksh had already provided
    for (often many) years.

    (It's also a bit unfortunate that Bash implemented some features,
    and some of them IMO unnecessarily, in a slightly different way,
    so that you cannot easily switch between the two shells.)


    -a Different developers ... everyone had their own idea
    -a of a 'perfect shell' - but then had to adapt and adapt
    -a again as the Real Needs became more obvious. Now, most
    -a WILL do the same things - just slightly different syntax.

    Where not outright wrong, this is very fuzzy. (I don't think it
    makes sense to comment on that.)


    -a I rather liked the 'c-shell' long back because it, well,
    -a 'looked like C'. It was one of the things that attracted
    -a me to Unix/Linux in the first place. Now I'm happy (ok,
    -a that's not really the word) with BASH. Not much it
    -a can't do ... but the fudged-fudged-fudged syntax to add
    -a features over time CAN be a pain in the ass.

    If you think it's a good idea to use C-shell for scripting, and
    since for you it seems to be just a syntax-difference, well, do
    what you like in your private working context.


    -a If I want 'scripting' now, I do it with Python. BASH
    -a or whatever, maybe it just EVOKES the Python scripts,
    -a a one or two-liner. Wrote many rather long BASH scripts
    -a in the past, and while they worked they were, well, just
    -a TOO messy/cryptic.

    Yes, I share your valuation of shells being somewhat cryptic and
    also "messy".


    -a Last big BASH script I did was for backing up a bunch
    -a of on-network drives. Mount-checking (important), calls
    -a to rsync and openSSH and ftp, local AND 'cloud', all
    -a with some confirmation checks along the way. SEMI-repeating
    -a units but each was a bit 'special'.

    Well, that's what their task mostly is, to "glue" together tools,
    even if that glue is quite powerful (yet still somewhat "messy").


    -a (ALWAYS pre-encrypt before sending to 'cloud' - I do
    -a NOT trust the providers one bit. Mine had an extension
    -a that 'suggested' some kind of ZIP, just to help them
    -a waste time)

    I suppose you mean here that you encrypt your backups before you
    store them in the cloud. That's sensible. (I don't store my files
    or backups in the cloud in the first place.)


    -a RE-did it in Python. MUCH shorter and more comprehensible
    -a and a nice easy CSV config file you could tweak in a text
    -a editor or spreadsheet. Python made it all BETTER.

    I'm not too surprised that you say that.


    -a Had a 'C' version of that backup pgm earlier. Worked
    -a fine, but there was a lot of string checking/editing
    -a involved and 'C' is CLUNKY with string shit.

    Shell has higher abstractions compared to "C".

    Python
    -a stole the FORTRAN string-slicing stuff, good deal !

    Not sure what you are actually referring here to. (Shell has
    such things as well. Unless you mean something more fancy when
    you talk about Python or FORTRAN? My memories on FORTRAN are
    very faint after 40 years when I had last used it.)


    -a Won't ever use BASH or any other 'shell script' for
    -a that kind of task again. Those might be "trad -IX"
    -a but IMHO they're just OVER. "Solutions" MOVED ON.

    With the POSIX-Shells you have at least a standard language on
    Unixes.


    -a-a Most distros, users would have to
    -a-a intentionally install KSH and scripts would need a
    -a-a shebang at the top to specify which shell to use.

    I don't recall to have ever "intentionally installed" Ksh on
    Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
    you could use out of the box. Later they provided also the
    much better "original" [AT&T] Ksh, and meanwhile you find on
    (some?) Linuxes ksh93u+m, Martijn Dekker's improved version.

    -a Um ... these days, almost all distros, you do have
    -a to "intentionally install" KSH or any rivals. BASH
    -a rules by default.

    Mine has even ksh93u+m. Some years ago I've got original ksh. Yet
    more years ago I've seen PD-ksh. All in the standard distribution.
    As said, I've never had to "intentionally install" a Ksh.

    There's one exception; back in the days when there was only PD-Ksh
    provided in the distributions and that was the only existing Ksh,
    but AT&T released their ksh93 for free, I got that from the AT&T
    to replace the PD-thing. That *was* an intentional install. But
    all those who didn't want The Original they could just use the one
    that came with the distros.


    Of course you can call shell scripts with the executable-flag
    set and with a she-bang line on top. Personally I run most
    shell scripts with the interpreter explicitly provided, as in
    -a-a ksh my-script flags arguments
    allowing easy debugging by adding '-x' without explicit 'set'
    command in the script. Only if some script gets the status of
    a "standard-command" I regularly use I set the shebang. YMMV.

    -a Direct spec of the shell IS useful, however the
    -a 'shebang' trick works well too.

    (So you don't "need" a shebang line, but it's useful.)

    -a-a (good practice, always add the shebang)

    Yes, if you are running your scripts executable script (or if
    you want to give your editor a hint for syntax highlighting,
    what shell is actually used, or just for specification purpose;
    but note, as said above, that we see many people have no clear
    idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
    differ from the standard.

    -a I have, I think, FOUR shells on this machine. The
    -a shebang IS required/desired.

    -a Still kinda like 'tcsh', it's there in case I get
    -a a brain-worm and wanna fool around with olde-dayz
    -a stuff. Zsh ain't so bad either.

    I don't consider it a good idea to use 'csh' or 'tcsh' for shell
    *programming*. (Browse the web for the well known paper with the
    thoroughly explained rationales.)

    I know some folks use and prefer 'tcsh' as interactive shells.
    (Although the Bash, Zsh, or Ksh, are meanwhile quite comfortable
    to use also interactively.)


    -a But, as said, for 'scripting' now, Python is by
    -a far my #1 choice unless the script is like a
    -a simple little ten-liner. Tend to use those on
    -a my PIs.

    -a Fooled around a bit with Lua and Ruby for scripting,
    -a but, really, Python and the MASSIVE number of libs
    -a have them beat. Python will do ANYTHING these days,
    -a just not as fast as 'C'. However CPU speed is less
    -a of a thing these days - I/O ops drag things down
    -a more than the CPU - so Python and 'C' can usually
    -a compete pretty well.

    -a There are Python compilers too. The main issue there
    -a is all the sub-sub-versions of Python, so you always
    -a have to include the entire binaries into each compilation
    -a to ensure it'll work. But then space is also a minor
    -a issue now as well unless you're doing micro-controllers.
    -a Did my share of those - DO teach you how to really SQUEEZE
    -a shit in - all computer kiddies should learn MCs first.

    (I'm not the appropriate person to discuss Python, Lua, Ruby, and
    similar.)

    Janis


    -a . . .

    -a ("Harry talks in his sleep, didn't you notice ?"
    -a-a-a Slight telling delay, then Hermonie says 'No' :-)


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 06:20:48 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 05:28, c186282 wrote:
    On 10/24/26 12:53, Janis Papanagnou wrote:
    On 2026-10-24 14:10, Kenny McCormack wrote:
    In article <11bhv61$1bjd2$2@dont-email.me>,
    Janis Papanagnou-a <janis_papanagnou+ng@hotmail.com> wrote:
    On 2026-10-24 05:59, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    I think you're taking Speedy way too seriously here.-a All of your points >>> are valid, of course, but it should not be necessary to respond to the
    troll.

    Oh, I didn't knew that he's considered a troll. His post looked just
    uninformed, or opinionated, not trollish.

    -a Thanks, I think-a :-)

    -a I never 'troll' - just relate MY experiences and what
    -a I've learned from them. I had my own path, own needs,
    -a my own 'environments', starting in the punch-card days.

    (I've still a block of punch-cards in the cellar, so I've got an
    impression where you're coming from.)

    -a But what served ME best may not be what served YOU, what
    -a I learned may not be what YOU learned.

    Oh, in my previous reply I said something like that; that it's
    fine if it serves you in your private contexts.

    A discrepancy might appear when you are working in a larger area
    with rules that are not tailored to your personal likings but to
    experiences from a larger (or another) group of persons.


    -a A great purpose of groups like these is to bring in
    -a a LOT of experiences and perspectives. You MAY find
    -a something compatible/useful in all the diverse advice.
    -a I don't pretend to know-it-all, nothing close (though
    -a a few, well, SAY they do :-)

    Oh, I'm completely fine with that. - If statements are formulated
    as opinions, what else can we do than agree to those or disagree.
    A problem, though, is, when opinions are stated as facts, and if
    statements are even wrong, then they should be corrected. (Or
    clarified if it was just a communication or expression problem.)


    -a As said elsewhere, "NEED" eventually supersedes all else.
    -a Earlier on, all the shells maybe started with a narrow
    -a 'vision' but HAD to include capabilities the other people
    -a put in. Sometimes the additions were neat/clear, sometimes
    -a not so much, but they're THERE.

    -a A sort of 'functional convergence' due to NEEDS.

    -a Anyway, I reject 'religions' built around shells or
    -a langs and such. For each need, pick the best tools
    -a and approaches. "Best" - sometimes that's what most
    -a harmonizes with YOUR brand of thinking.

    (Unfortunately language topics are often presented with religious
    fervor.)

    Janis

    [...]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 06:41:38 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 04:59, c186282 wrote:
    On 10/24/26 07:06, Nuno Silva wrote:
    On 2026-10-24, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    Now that sounds like something Greg Sullivan of Microsoft would say.

    -a You "can do" most anything in COBOL or FORTRAN or 'C'
    -a in ANY other lang - just as anything in one shell script
    -a you can do in any other. The issue is 'how easily' - and
    -a that depends on your particular application.

    (Be careful; if your argument goes in the direction of "language A
    is Turing-complete so you can use it simulating language B, which
    makes it effectively the same", then that statement would be of no
    practical value!)

    I want to give you an example code from a little shell tool I wrote:

    function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}

    (What this does is that whenever the environment variable 'LINES'
    changes - e.g. if you pick your mouse and resize the X-window - then
    that function gets triggered and the actions defined executed.)

    I'd be interested how you'd implement or emulate that, say, in Bash.

    Janis

    [...]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 03:15:57 2026
    From Newsgroup: comp.unix.shell

    On 10/26/26 01:04, Janis Papanagnou wrote:
    On 2026-10-26 04:49, c186282 wrote:
    On 10/24/26 05:53, Janis Papanagnou wrote:
    On 2026-10-24 05:59, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    [...]

    -a-a If KSH works for you then stick with it.

    I use Ksh meanwhile for ~35 years, and since I use a lot of
    Ksh features that Bash just doesn't support there's certainly
    no reason to switch. (Also its speed is a criterion, BTW. And
    back then there were no Bash versions on commercial Unixes;
    but commercial Linuxes haven't the prevalence any more today,
    and play no role now in my private systems context.)

    -a-a Note however that MOST distros default to BASH now -

    Yes, Linux often has Bash as its default.

    -a-a so if you plan
    -a-a to 'distribute' your work it'd be better to move your
    -a-a stuff over to BASH.

    Certainly not.

    And this is short-sighted. If _portability_ is an issue you'd
    better stick with the POSIX subset of both, Ksh and Bash.

    (Sadly, as we observe, especially "Linux kiddies" often don't
    know what that POSIX subset actually is; in their scripts they
    are writing #!/bin/sh and using some bash-specific syntax not
    realizing that there's a difference, and that Bash is not the
    [portable] *standard*.)

    -a-a Delay does not necessarily equate with 'ignorance'.

    Not sure why you bring up that statement; nobody said anything
    like that.


    My following exposition explains why.


    My statement about the delayed adoption of Ksh features by Bash
    was just pointing to the fact that Bash users had to wait before
    they could use comfortable features that Ksh had already provided
    for (often many) years.

    Well, good for them.

    I'll stick to my philosophic "Functional Convergence"
    theory here. If shell X does something neat-o then it
    HAS to be incorporated into all others - some way, some
    how, neat or not.

    (It's also a bit unfortunate that Bash implemented some features,
    and some of them IMO unnecessarily, in a slightly different way,
    so that you cannot easily switch between the two shells.)


    -a-a Different developers ... everyone had their own idea
    -a-a of a 'perfect shell' - but then had to adapt and adapt
    -a-a again as the Real Needs became more obvious. Now, most
    -a-a WILL do the same things - just slightly different syntax.

    Where not outright wrong, this is very fuzzy. (I don't think it
    makes sense to comment on that.)

    I think it makes good sense. Everybody just HAS to
    somehow incorporate everyone else's good ideas
    eventually. Otherwise --> TRASH BIN of history.


    -a-a I rather liked the 'c-shell' long back because it, well,
    -a-a 'looked like C'. It was one of the things that attracted
    -a-a me to Unix/Linux in the first place. Now I'm happy (ok,
    -a-a that's not really the word) with BASH. Not much it
    -a-a can't do ... but the fudged-fudged-fudged syntax to add
    -a-a features over time CAN be a pain in the ass.

    If you think it's a good idea to use C-shell for scripting, and
    since for you it seems to be just a syntax-difference, well, do
    what you like in your private working context.

    As said, CSH did initially attract me to -IX. However
    don't really USE it anymore. HAVE tcsh installed though,
    Just In Case. Good idea, but didn't "evolve" enough.

    -a-a If I want 'scripting' now, I do it with Python. BASH
    -a-a or whatever, maybe it just EVOKES the Python scripts,
    -a-a a one or two-liner. Wrote many rather long BASH scripts
    -a-a in the past, and while they worked they were, well, just
    -a-a TOO messy/cryptic.

    Yes, I share your valuation of shells being somewhat cryptic and
    also "messy".

    VERY messy and OFTEN 'cryptic' (unless very short).
    Just no NEED for such shit anymore.

    -a-a Last big BASH script I did was for backing up a bunch
    -a-a of on-network drives. Mount-checking (important), calls
    -a-a to rsync and openSSH and ftp, local AND 'cloud', all
    -a-a with some confirmation checks along the way. SEMI-repeating
    -a-a units but each was a bit 'special'.

    Well, that's what their task mostly is, to "glue" together tools,
    even if that glue is quite powerful (yet still somewhat "messy").


    But NOT 'comprehensible' a year or two LATER. Been
    there, experienced/suffered that. Python is MUCH
    better in that respect. Didn't matter if I wrote
    the thing, the logic/sense of it DECAYS with time
    no matter HOW many comments/doc. I had a 40+ year
    career ... even 'simple' scripts/pgms, the whole
    sense/sensibility decayed over time. It all seems
    SO clear WHEN you're writing it, but ......

    Note a good third of my 'programs' at least
    were COMMENTS - by-line PLUS an informative
    header at the top of each function. Two or three
    years later, revision time - "WHAT The Fuck ???".


    -a-a (ALWAYS pre-encrypt before sending to 'cloud' - I do
    -a-a NOT trust the providers one bit. Mine had an extension
    -a-a that 'suggested' some kind of ZIP, just to help them
    -a-a waste time)

    I suppose you mean here that you encrypt your backups before you
    store them in the cloud. That's sensible. (I don't store my files
    or backups in the cloud in the first place.)

    I very much mean to encrypt the backups BEFORE you
    send them to 'cloud'. Don't put un-encrypted shit
    on their sites for a millisecond. Do NOT trust them !
    AES-xxx is good, though sometimes used Camilla.

    With several langs/FTP you can put a file on 'cloud'
    and then set the datetime/ownership to whatever the
    original had. That's how I did it for a decade+ - works
    very well. Encrypt, upload, then tweak the specifics.
    Pirates get NOTHING.

    -a-a RE-did it in Python. MUCH shorter and more comprehensible
    -a-a and a nice easy CSV config file you could tweak in a text
    -a-a editor or spreadsheet. Python made it all BETTER.

    I'm not too surprised that you say that.

    Do you disagree ???

    -a-a Had a 'C' version of that backup pgm earlier. Worked
    -a-a fine, but there was a lot of string checking/editing
    -a-a involved and 'C' is CLUNKY with string shit.

    Shell has higher abstractions compared to "C".

    Slightly - but also CLUNKY and hard to understand
    a year or two later. Doing serious string stuff in
    BASH and several others ... nasty !

    Look, if you're 20-something it MAY be possible to
    hold all the sense/logic of older shit in your head.
    Believe me - that CHANGES. Too much shit on a
    small drive, so to speak.

    -a-a Python
    -a-a stole the FORTRAN string-slicing stuff, good deal !

    Not sure what you are actually referring here to. (Shell has
    such things as well. Unless you mean something more fancy when
    you talk about Python or FORTRAN? My memories on FORTRAN are
    very faint after 40 years when I had last used it.)

    Um ... check. Almost all the Python string shit
    was 'borrowed' from FORTRAN. This is a GOOD thing.
    SO often you have to slice and dice and squish
    string stuff together in the real world. It'd
    better be EASY and OBVIOUS or you're doomed.

    -a-a Won't ever use BASH or any other 'shell script' for
    -a-a that kind of task again. Those might be "trad -IX"
    -a-a but IMHO they're just OVER. "Solutions" MOVED ON.

    With the POSIX-Shells you have at least a standard language on
    Unixes.

    Python is now 'standard enough' - and totally ubiquitous.

    FIRST place I started seeing a lot of Python wasn't Linux,
    but WINDERS. Had to learn a little P2 just because. Found,
    despite initial prejudice, I didn't hate it ......

    -a-a Most distros, users would have to
    -a-a intentionally install KSH and scripts would need a
    -a-a shebang at the top to specify which shell to use.

    I don't recall to have ever "intentionally installed" Ksh on
    Linux. Earlier Linuxes had just a (sub-optimal!) PD-ksh that
    you could use out of the box. Later they provided also the
    much better "original" [AT&T] Ksh, and meanwhile you find on
    (some?) Linuxes ksh93u+m, Martijn Dekker's improved version.

    -a-a Um ... these days, almost all distros, you do have
    -a-a to "intentionally install" KSH or any rivals. BASH
    -a-a rules by default.

    Mine has even ksh93u+m. Some years ago I've got original ksh. Yet
    more years ago I've seen PD-ksh. All in the standard distribution.
    As said, I've never had to "intentionally install" a Ksh.

    Umm ... what IS this 'ksh'-defaulting distro ???

    There's one exception; back in the days when there was only PD-Ksh
    provided in the distributions and that was the only existing Ksh,
    but AT&T released their ksh93 for free, I got that from the AT&T
    to replace the PD-thing. That *was* an intentional install. But
    all those who didn't want The Original they could just use the one
    that came with the distros.


    Of course you can call shell scripts with the executable-flag
    set and with a she-bang line on top. Personally I run most
    shell scripts with the interpreter explicitly provided, as in
    -a-a ksh my-script flags arguments
    allowing easy debugging by adding '-x' without explicit 'set'
    command in the script. Only if some script gets the status of
    a "standard-command" I regularly use I set the shebang. YMMV.

    -a-a Direct spec of the shell IS useful, however the
    -a-a 'shebang' trick works well too.

    (So you don't "need" a shebang line, but it's useful.)

    -a-a (good practice, always add the shebang)

    Yes, if you are running your scripts executable script (or if
    you want to give your editor a hint for syntax highlighting,
    what shell is actually used, or just for specification purpose;
    but note, as said above, that we see many people have no clear
    idea about what a "/bin/sh" is and where /bin/bash or /bin/ksh
    differ from the standard.

    -a-a I have, I think, FOUR shells on this machine. The
    -a-a shebang IS required/desired.

    -a-a Still kinda like 'tcsh', it's there in case I get
    -a-a a brain-worm and wanna fool around with olde-dayz
    -a-a stuff. Zsh ain't so bad either.

    I don't consider it a good idea to use 'csh' or 'tcsh' for shell *programming*. (Browse the web for the well known paper with the
    thoroughly explained rationales.)


    OFTEN not a 'good idea' ... but sometimes "an IDEA", a
    brain-worm that commands you to "do this it tcsh" ! :-)


    I know some folks use and prefer 'tcsh' as interactive shells.
    (Although the Bash, Zsh, or Ksh, are meanwhile quite comfortable
    to use also interactively.)


    Never got TOO far into ZSH ... but it DOES have a lot
    of potential. Don't count it out of the picture.


    -a-a But, as said, for 'scripting' now, Python is by
    -a-a far my #1 choice unless the script is like a
    -a-a simple little ten-liner. Tend to use those on
    -a-a my PIs.

    -a-a Fooled around a bit with Lua and Ruby for scripting,
    -a-a but, really, Python and the MASSIVE number of libs
    -a-a have them beat. Python will do ANYTHING these days,
    -a-a just not as fast as 'C'. However CPU speed is less
    -a-a of a thing these days - I/O ops drag things down
    -a-a more than the CPU - so Python and 'C' can usually
    -a-a compete pretty well.

    -a-a There are Python compilers too. The main issue there
    -a-a is all the sub-sub-versions of Python, so you always
    -a-a have to include the entire binaries into each compilation
    -a-a to ensure it'll work. But then space is also a minor
    -a-a issue now as well unless you're doing micro-controllers.
    -a-a Did my share of those - DO teach you how to really SQUEEZE
    -a-a shit in - all computer kiddies should learn MCs first.

    (I'm not the appropriate person to discuss Python, Lua, Ruby, and
    similar.)

    Experiences vary. Needs vary.

    As said somewhere, I'm not "religious" in any of
    this stuff - shells/langs/distros. Whatever is
    best for The Job. If "Plan-9" or Solaris seem to
    serve best then USE them.

    NOT much use for Winders these days, not at all.
    A code/method CESSPIT full of spyware and worse.

    Bought five of those "mini-boxes", BMax/BeeLink,
    a couple years back when they were cheap. Kinda
    "lower-end laptop" power. However with -IX the
    performance is very good. Kinda a matter of pride
    to not let Winders run for a single millisecond
    before I install an -IX. Did add SATA SSDs to
    three of them (again cheap before the tariff wars).
    These are my home backbone now, do everything I
    want as fast as I need. Even have one as a de-facto
    NAS box with a bunch of USB drives attached.

    (Oh, DON'T disagree with the tariff wars ... were
    kinda NEEDED in my opinion. BAD idea to let China
    Own All). Alas no USA/EU/Taiwan makers seemed to
    step up to the challenge, at least not yet)

    REALLY simple/dedicated uses - and HAVE several -
    just use PIs. Note had a HORRIBLE/useless experience
    with a SUPPOSED SATA hat. Spent a week trying to
    get it to work - NADA ! Still have several PIs
    pretending to be IP cameras and smart displays
    however. P3s work as IP cams fine, P4s are good
    for smart displays of the images, P5s ... um ...
    they're kinda too weird/expensive right now.
    Have one, don't use it for anything.

    (note there are cheap weather-proof boxes that
    will JUST fit a Pi-3 and a mini-board camera.
    Use "motion" for the cam. Have two of those
    running very well right now. Scripts even compensate
    for varying day/night times. Two cams on one mini-box
    also, again the day/night script. Note the PI3s ...
    kept locking up after about a week. Tried the
    simple solution of forcing a reboot, but that
    tended to hang. Clue - force all Python stuff
    to STOP just before the reboot. Now they run
    for months)

    Have two Pi-0/W2 boards. Might fit an even smaller
    waterproof box. Testing. Less power than a Pi3,
    but still MAYBE just enough if you stick to a
    low frame rate.

    "-IX" is just MUCH better and more efficient and
    less trashy than Winders. Have one with "GhostBSD"
    which is a good FreeBSD alt - easier to install
    and a nice GUI.

    Got into -IX a little back in the 386 days,
    remember SCO ?, but the boss decided against
    using it. Maybe smart back then. The goal was
    to write a database and GIS in it. However
    'cheap'/useful/better' ones came out for Winders
    soon. Old commercial -IX systems were EXPENSIVE
    too.

    'AREV' for the database, multi-value. LOVED it !
    Kinda steep learning curve though, DO check
    the 'advanced' shit at the back of the manuals.
    You can STILL buy it, but no support and DOS
    mem lims.

    STILL kinda interested in Solaris/OpenIndiana.
    Unix-LIKE ... SOME interesting aspects and
    NOT Winders at all. More experiments coming.
    The storage set-up IS weird though ... more
    for 'giant' systems. Don't need that now.

    Oh well, went too long/wide again ...

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 03:38:31 2026
    From Newsgroup: comp.unix.shell

    On 10/26/26 01:20, Janis Papanagnou wrote:
    On 2026-10-26 05:28, c186282 wrote:
    On 10/24/26 12:53, Janis Papanagnou wrote:
    On 2026-10-24 14:10, Kenny McCormack wrote:
    In article <11bhv61$1bjd2$2@dont-email.me>,
    Janis Papanagnou-a <janis_papanagnou+ng@hotmail.com> wrote:
    On 2026-10-24 05:59, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    This is not correct. While Bash has over time adopted quite
    some features from Ksh - but sadly needed often far too many
    years for that - there's still a lot substantial functions
    in Ksh that Bash has not implemented (or substituted by some
    equivalent feature).

    I think you're taking Speedy way too seriously here.-a All of your
    points
    are valid, of course, but it should not be necessary to respond to the >>>> troll.

    Oh, I didn't knew that he's considered a troll. His post looked just
    uninformed, or opinionated, not trollish.

    -a-a Thanks, I think-a :-)

    -a-a I never 'troll' - just relate MY experiences and what
    -a-a I've learned from them. I had my own path, own needs,
    -a-a my own 'environments', starting in the punch-card days.

    (I've still a block of punch-cards in the cellar, so I've got an
    impression where you're coming from.)

    -a-a But what served ME best may not be what served YOU, what
    -a-a I learned may not be what YOU learned.

    My first computer was a PDP-11. Great unit.
    But still remember having to submit my card
    stack (DON'T drop it !) to the IT overlords.
    Helped a bit if you offered them 'gifts'.

    Oh, in my previous reply I said something like that; that it's
    fine if it serves you in your private contexts.

    Most everybody has a 'private context'. Doesn't
    matter what you do in 'IT'. Every life experience
    and need is a bit different, takes you down
    different paths. Since the 70s the field was
    SO wide that nobody could do it ALL, keep it
    ALL in mind.

    DID like that newfangled 'C' language for
    the PDPs though :-)

    A discrepancy might appear when you are working in a larger area
    with rules that are not tailored to your personal likings but to
    experiences from a larger (or another) group of persons.

    Been there.

    -a-a A great purpose of groups like these is to bring in
    -a-a a LOT of experiences and perspectives. You MAY find
    -a-a something compatible/useful in all the diverse advice.
    -a-a I don't pretend to know-it-all, nothing close (though
    -a-a a few, well, SAY they do :-)

    Oh, I'm completely fine with that. - If statements are formulated
    as opinions, what else can we do than agree to those or disagree.
    A problem, though, is, when opinions are stated as facts, and if
    statements are even wrong, then they should be corrected. (Or
    clarified if it was just a communication or expression problem.)

    Still a lot of 'religion' involved ... some present
    THE Way ... holy writ. Rarely works for most.

    Yea, there are maybe a few IQ-200 people who post.
    Well, good for them. we need some IQ-200 people.
    However even they have their prejudices and
    preferences that may not serve all. It's the
    tendency for ATTITUDE that most annoys me. Not
    looking for an Ayatollah.

    Ever see that "Sheldon" character from the TV series ?
    HIS way or you get the "retard" label :-)

    -a-a As said elsewhere, "NEED" eventually supersedes all else.
    -a-a Earlier on, all the shells maybe started with a narrow
    -a-a 'vision' but HAD to include capabilities the other people
    -a-a put in. Sometimes the additions were neat/clear, sometimes
    -a-a not so much, but they're THERE.

    -a-a A sort of 'functional convergence' due to NEEDS.

    -a-a Anyway, I reject 'religions' built around shells or
    -a-a langs and such. For each need, pick the best tools
    -a-a and approaches. "Best" - sometimes that's what most
    -a-a harmonizes with YOUR brand of thinking.

    (Unfortunately language topics are often presented with religious
    fervor.)

    Very much noted.

    But, bigger picture, I think that's *wrong*.

    MANY paths to "your solution". Pick the best
    and most compatible. SO many paths to be had
    these days. Be smart and sensible. Simpler
    TENDS to be better long-term.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 03:50:22 2026
    From Newsgroup: comp.unix.shell

    On 10/26/26 01:41, Janis Papanagnou wrote:
    On 2026-10-26 04:59, c186282 wrote:
    On 10/24/26 07:06, Nuno Silva wrote:
    On 2026-10-24, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    Now that sounds like something Greg Sullivan of Microsoft would say.

    -a-a You "can do" most anything in COBOL or FORTRAN or 'C'
    -a-a in ANY other lang - just as anything in one shell script
    -a-a you can do in any other. The issue is 'how easily' - and
    -a-a that depends on your particular application.

    (Be careful; if your argument goes in the direction of "language A
    is Turing-complete so you can use it simulating language B, which
    makes it effectively the same", then that statement would be of no
    practical value!)

    I know I will offend The Religious.

    Fuck 'em.

    Task, BEST solution for YOU. That is The
    Standard so far as I'm concerned.

    I want to give you an example code from a little shell tool I wrote:

    -a function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}

    (What this does is that whenever the environment variable 'LINES'
    changes - e.g. if you pick your mouse and resize the X-window - then
    that function gets triggered and the actions defined executed.)

    I'd be interested how you'd implement or emulate that, say, in Bash.

    I'd write it in PYTHON now :-)

    Some OS.System() and maybe Subprocess calls.
    Leverage the existing simple/low-level utils
    in Linux to your advantage. Run, parse,
    mutate, USE.

    Done a lot of apps that simply grab output
    from those simple Linux utils - then parse
    and trim and mix. Why re-invent the wheel ?
    You CAN - but WHY ???

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.os.linux.misc,comp.unix.shell on Mon Oct 26 15:16:29 2026
    From Newsgroup: comp.unix.shell

    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
    [...]
    I want to give you an example code from a little shell tool I wrote:

    function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}

    (What this does is that whenever the environment variable 'LINES'
    changes - e.g. if you pick your mouse and resize the X-window - then
    that function gets triggered and the actions defined executed.)

    I'd be interested how you'd implement or emulate that, say, in Bash.

    I do something similar in bash, but using a different mechanism (so this
    isn't a response to your challenge). I trap on SIGWINCH.
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Tue Oct 27 02:26:27 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 23:16, Keith Thompson wrote:
    Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
    [...]
    I want to give you an example code from a little shell tool I wrote:

    function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}

    (What this does is that whenever the environment variable 'LINES'
    changes - e.g. if you pick your mouse and resize the X-window - then
    that function gets triggered and the actions defined executed.)

    I'd be interested how you'd implement or emulate that, say, in Bash.

    I do something similar in bash, but using a different mechanism (so this isn't a response to your challenge).

    (It was not so much a challenge but a motivation to think about it.)

    I trap on SIGWINCH.

    That's a reasonable alternative for that specific task.

    I thought it was an appropriate example because Kornshell's "Discipline Functions" are of course not only applicable to this specific variable
    but to every variable, also user defined.[*] Actually you can associate
    such functions, and not only the predefined 'get', 'set', and 'unset',
    but also user defined, to any shell variables, existing and introduced.
    It was a compact example that stems from a real application not just an academical one, and it was also compact enough to not get distracted.
    It should make it more obvious what simple syntactic features and their differences in the shells are and where there's a more tight embedding
    with the shell mechanisms and features existing. As it was a simple
    example to think about I also not really wanted to see a Bash solution,
    I know a solution[**] which in the light of that feature I can only call
    a workaround, though.

    Above sample line contain also another Kornshell specific feature; use
    of namespaces. Just BTW. (There's still quite a lot unique features in Kornshell.)

    Janis

    [*] It goes further, being able to associate functions to "Types" with
    'typeset -T', making code organizations possible that some call "object oriented".

    [**] Actually, there had been a neat idea in the past; Kaz suggested and developed a shell status line feature for Bash (called "basta"). Since
    it was for Bash it had to handle window resizing by another way. I just
    adopted the idea of the tool and implemented my version for Kornshell
    (called "kosta", to honor the origin of the basic idea) from scratch,
    and of course I could make use of such Kornshell-features to simplify
    the code.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Tue Oct 27 02:44:31 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 08:50, c186282 wrote:
    On 10/26/26 01:41, Janis Papanagnou wrote:
    On 2026-10-26 04:59, c186282 wrote:
    On 10/24/26 07:06, Nuno Silva wrote:
    On 2026-10-24, c186282 wrote:

    -a-a KSH and BASH are "mostly compatible". Minor diffs but
    -a-a nothing hard to get around. Anything you can do in KSH
    -a-a can be done in BASH.

    Now that sounds like something Greg Sullivan of Microsoft would say.

    -a-a You "can do" most anything in COBOL or FORTRAN or 'C'
    -a-a in ANY other lang - just as anything in one shell script
    -a-a you can do in any other. The issue is 'how easily' - and
    -a-a that depends on your particular application.

    (Be careful; if your argument goes in the direction of "language A
    is Turing-complete so you can use it simulating language B, which
    makes it effectively the same", then that statement would be of no
    practical value!)

    -a I know I will offend The Religious.

    -a Fuck 'em.

    -a Task, BEST solution for YOU. That is The
    -a Standard so far as I'm concerned.

    (Hmm.. - are these comments probably what Kenny previously had meant
    when he spoke about trollish behavior. - Beyond that I don't see how
    these statements would contribute anything substantial.)

    (We seem to also have different interpretations of the meaning of the
    word "standard".)


    I want to give you an example code from a little shell tool I wrote:

    -a-a function LINES.set { .kosta.rows=${.sh.value} ; .kosta.update ;}

    (What this does is that whenever the environment variable 'LINES'
    changes - e.g. if you pick your mouse and resize the X-window - then
    that function gets triggered and the actions defined executed.)

    I'd be interested how you'd implement or emulate that, say, in Bash.

    -a I'd write it in PYTHON now-a :-)

    Sure, you said that before that this is (one of) your preference(s).

    (Mind that I was making a comment, backed up with an actual example,
    to explain why I said your generalizing statements are inappropriate
    and even wrong, concerning major features in Ksh vs. Bash.)


    -a Some OS.System() and maybe Subprocess calls.
    -a Leverage the existing simple/low-level utils
    -a in Linux to your advantage. Run, parse,
    -a mutate, USE.

    -a Done a lot of apps that simply grab output
    -a from those simple Linux utils - then parse
    -a and trim and mix. Why re-invent the wheel ?
    -a You CAN - but WHY ???

    Nothing I showed in my sample was "reinventing the wheel". It may not
    have become obvious to you by the sample, despite having deliberately
    kept it terse and focused. The previous discussions was about features,
    simple ones - you basically implied that all features are trivial and
    mapable - and ones that are substantially extending the shell language
    - where I provided an example for better understanding the differences.

    Nevermind.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Tue Oct 27 04:42:56 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 08:15, c186282 wrote:
    On 10/26/26 01:04, Janis Papanagnou wrote:
    On 2026-10-26 04:49, c186282 wrote:
    On 10/24/26 05:53, Janis Papanagnou wrote:
    On 2026-10-24 05:59, c186282 wrote:
    [...]

    Not sure why you bring up that statement; nobody said anything
    like that.

    -a My following exposition explains why.


    My statement about the delayed adoption of Ksh features by Bash
    was just pointing to the fact that Bash users had to wait before
    they could use comfortable features that Ksh had already provided
    for (often many) years.

    -a Well, good for them.

    -a I'll stick to my philosophic "Functional Convergence"
    -a theory here. If shell X does something neat-o then it
    -a HAS to be incorporated into all others - some way, some
    -a how, neat or not.

    I can't see how that would match to what had previously been discussed.

    First, I think, we should acknowledge a few facts for better valuation. Kornshell (ksh88) was the base for the POSIX standard (not "standard").
    Bash (and Zsh) support that standard. All these three shells extended
    their set of features according to the needs and course of evolution.
    Zsh made some fundamental additions in some features to tackle inherent
    issues in Bourne shell. Ksh and Bash kept Bourne shell's basic syntax.
    Ksh extended (and streamlined some) features staying withing Bourne's syntactical paragon (as far as sensible and possible).

    So it came that Ksh featured, for example, things like ${..//../..}, ${..:..:..}, ((...)), <(...), "ksh-patterns", and many more features
    that Bash (and Zsh) adopted.

    Many more features either weren't (yet) adopted, things like 'float'
    arithmetic and more basic math functions in $((...)) and ((...)),
    namespaces, type system, discipline functions, and whatnot.

    I would have hoped that some features would not have been implemented
    in Bash by other names, using other built-in command's options, and
    that the rest would have converged better and faster; mind that many
    of the newer Ksh features have already been available with Ksh in '93.


    (It's also a bit unfortunate that Bash implemented some features,
    and some of them IMO unnecessarily, in a slightly different way,
    so that you cannot easily switch between the two shells.)


    -a-a Different developers ... everyone had their own idea
    -a-a of a 'perfect shell' - but then had to adapt and adapt
    -a-a again as the Real Needs became more obvious. Now, most
    -a-a WILL do the same things - just slightly different syntax.

    Where not outright wrong, this is very fuzzy. (I don't think it
    makes sense to comment on that.)

    -a I think it makes good sense. Everybody just HAS to
    -a somehow incorporate everyone else's good ideas
    -a eventually. Otherwise --> TRASH BIN of history.

    Maybe, maybe not. - But what strikes me more is that (shell-)languages
    might vanish because of other factors; like official maintenance and
    support. I think with the predominance of Bash it will likely persist,
    but I'm not that sure with Ksh; after official support from AT&T was
    dropped we have to rely on those that took over the task today. Since
    the Ksh is less widely used (and the maintainers struggling with the
    code base, at least as it seems to me) I'm not too optimistic here.

    [snip Csh talk]

    -a-a If I want 'scripting' now, I do it with Python. BASH
    -a-a or whatever, maybe it just EVOKES the Python scripts,
    -a-a a one or two-liner. Wrote many rather long BASH scripts
    -a-a in the past, and while they worked they were, well, just
    -a-a TOO messy/cryptic.

    Yes, I share your valuation of shells being somewhat cryptic and
    also "messy".

    -a VERY messy and OFTEN 'cryptic' (unless very short).

    *shrug*

    My experience here is that you can do a lot to address that, so the
    adverbs you use are relative to one's experience and programming
    habits.

    -a Just no NEED for such shit anymore.

    -a-a Last big BASH script I did was for backing up a bunch
    -a-a of on-network drives. Mount-checking (important), calls
    -a-a to rsync and openSSH and ftp, local AND 'cloud', all
    -a-a with some confirmation checks along the way. SEMI-repeating
    -a-a units but each was a bit 'special'.

    Well, that's what their task mostly is, to "glue" together tools,
    even if that glue is quite powerful (yet still somewhat "messy").


    -a But NOT 'comprehensible' a year or two LATER.

    As said, as lot is in the hand of the programmer. (You may be doomed
    if you want to work on third-party code. But if your own code is that
    bad that you can't "decipher" it after a year don't blame the language
    alone.)

    [snip Python talk]

    -a-a (ALWAYS pre-encrypt before sending to 'cloud' - I do
    -a-a NOT trust the providers one bit. Mine had an extension
    -a-a that 'suggested' some kind of ZIP, just to help them
    -a-a waste time)

    I suppose you mean here that you encrypt your backups before you
    store them in the cloud. That's sensible. (I don't store my files
    or backups in the cloud in the first place.)

    -a I very much mean to encrypt the backups BEFORE you
    -a send them to 'cloud'.

    So I understood correctly, fine.

    I maintain my philosophy to not store any of my sensible data in "the
    cloud", neither in plain nor in encrypted form. An encryption that is
    safe today isn't guaranteed to be safe tomorrow. Since if my data is
    accessible by some third party in the cloud _now_ it might get decoded
    later; so that's no option for my.

    Don't put un-encrypted shit
    -a on their sites for a millisecond. Do NOT trust them !
    -a AES-xxx is good, though sometimes used Camilla.

    -a With several langs/FTP you can put a file on 'cloud'
    -a and then set the datetime/ownership to whatever the
    -a original had. That's how I did it for a decade+ - works
    -a very well. Encrypt, upload, then tweak the specifics.
    -a Pirates get NOTHING.

    -a-a RE-did it in Python. MUCH shorter and more comprehensible
    -a-a and a nice easy CSV config file you could tweak in a text
    -a-a editor or spreadsheet. Python made it all BETTER.

    I'm not too surprised that you say that.

    -a Do you disagree ???

    (In my previous post I wrote that I'm not the appropriate person to
    discuss Python.)

    I just said that I understand that because you obviously show some,
    umm.., enthusiasm here, concerning that specific language.

    (I heard and read about Python, I helped debugging a piece of Python
    that my child was trying to run, and I draw the conclusion that it's
    not worth [for me] to learn and use that language.)

    (It certainly appears a lot more "attractive" than the Unix shells.
    But enthusiastic comments often disregard other aspects. Standard
    environments and tools, company policies, etc., so in your private
    system environment you have more options to choose your personally
    preferred tools.)


    -a-a Had a 'C' version of that backup pgm earlier. Worked
    -a-a fine, but there was a lot of string checking/editing
    -a-a involved and 'C' is CLUNKY with string shit.

    Shell has higher abstractions compared to "C".

    -a Slightly - but also CLUNKY and hard to understand
    -a a year or two later.

    (I already commented on that.)

    Doing serious string stuff in
    -a BASH and several others ... nasty !

    I'm curious what specifically you mean; can you give examples?


    -a Look, if you're 20-something it MAY be possible to
    -a hold all the sense/logic of older shit in your head.
    -a Believe me - that CHANGES. Too much shit on a
    -a small drive, so to speak.

    Well, your way of writing programs may differ from mine.

    And (given what you wrote) I'm likely about as old as you are;
    and I'm certainly not "remembering" what an older program does.
    I'm certainly writing my programs in ways that makes it possible
    to resume work at a later stage. This is actually not uncommon;
    I've done it in various languages, and problems arose primarily
    where I ignored (general, or my own) program quality standards.

    I mean I've seen bad code in many languages. And I consider it a
    basic programming skill to structure code, name entities sensibly,
    and comment code, as necessary.

    I understand that the shell with its attributes of being somewhat
    cryptic you may more easily write "messy" code, and that it needs
    experience and more discipline to write maintainable software.[*]

    [*] Back in the 1990's when I gave a couple courses in Kornshell
    I explicitly emphasized to handle the Shell not as a "scripting
    language" but as a _programming language_. (Hope you understand
    what I'm trying to say by that.) To apply all the good practices
    that you also apply with other non-"scripting"-languages.


    -a-a Python
    -a-a stole the FORTRAN string-slicing stuff, good deal !

    Not sure what you are actually referring here to. (Shell has
    such things as well. Unless you mean something more fancy when
    you talk about Python or FORTRAN? My memories on FORTRAN are
    very faint after 40 years when I had last used it.)

    -a Um ... check. Almost all the Python string shit
    -a was 'borrowed' from FORTRAN. This is a GOOD thing.
    -a SO often you have to slice and dice and squish
    -a string stuff together in the real world. It'd
    -a better be EASY and OBVIOUS or you're doomed.

    (I already asked above about any concrete example you have in mind.)

    [snip]

    -a-a Um ... these days, almost all distros, you do have
    -a-a to "intentionally install" KSH or any rivals. BASH
    -a-a rules by default.

    Mine has even ksh93u+m. Some years ago I've got original ksh. Yet
    more years ago I've seen PD-ksh. All in the standard distribution.
    As said, I've never had to "intentionally install" a Ksh.

    -a Umm ... what IS this 'ksh'-defaulting distro ???

    Here we spoke not about "defaulting"[*]; here we spoke about
    explicitly "intentionally installed" shells.

    Over the time I've used several. Around Y2k I had Suse which had a
    PD-ksh. Currently I have Xubuntu which comes with ksh93u+m. But of
    course you can also make another shell your personal default-shell;
    there's really a lot of shells you can choose from (on Linuxes).

    [*] Concerning to your term "'ksh'-defaulting" I refer to another
    post in this thread who already expanded on that. (I don't want to
    engage with you in some terminology-battle, whether that is your
    intention or not.)[**]

    [**] Concerning "default" shell we already exchanged this:
    |
    | 24-10-2026, Janis Papanagnou:
    | > 2026-10-24, c186282:
    | >> Note however that MOST distros default to BASH now -
    | >
    | > Yes, Linux often has Bash as its default.
    |
    and with a seemingly agreed interpretation of "default" we seem to
    have said the same, so I don't think there's more to say.

    [snip]
    [...]

    -a Never got TOO far into ZSH ... but it DOES have a lot
    -a of potential. Don't count it out of the picture.

    (I certainly don't ignore Zsh, I even mentioned it a couple times.)

    [big snip of digressions]
    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Tue Oct 27 05:01:49 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-26 08:38, c186282 wrote:
    [...]
    -a My first computer was a PDP-11. Great unit.
    -a But still remember having to submit my card
    -a stack (DON'T drop it !) to the IT overlords.

    Corrupted data (if you've dropped it)...

    -a Helped a bit if you offered them 'gifts'.

    ...and corrupted people?

    Janis

    PS: The nastiest thing I've encountered with the
    card deck was that a friend exchanged all my cards
    which carried the word 'BEGIN' with cards carrying
    the word 'SADAT' - just as a hilarious play with
    words WRT two international politicians back then.
    Not so funny for me when I noticed all the syntax
    errors and had to wait another hour for the next
    batch run.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Tue Oct 27 12:24:16 2026
    From Newsgroup: comp.unix.shell

    On 10/27/26 00:01, Janis Papanagnou wrote:
    On 2026-10-26 08:38, c186282 wrote:
    [...]
    -a-a My first computer was a PDP-11. Great unit.
    -a-a But still remember having to submit my card
    -a-a stack (DON'T drop it !) to the IT overlords.

    Corrupted data (if you've dropped it)...

    Well, a lot of re-sorting at the very least.

    Punch cards and paper tape WORKED. Clunky and
    low-density but they worked - and were used
    for quite awhile. However putting a COBOL
    corporate accounting system on cards is
    not an attractive prospect.

    I've run into people who remember those
    mag tape towers from old movies and think
    the programs/data was just magically
    uploaded directly to them. Nope, paper
    cards first .....

    Found a PDP-11 emulator for Linux, but it
    just wouldn't be quite the same. MAY be
    some actual working units still out there
    however. Weak unit by today's standards,
    but at the time it was pretty good.

    -a-a Helped a bit if you offered them 'gifts'.

    ...and corrupted people?

    People are mostly pre-corrupted :-)

    The SysLord had a serial terminal, but all
    the rest of us had to do cards.

    Janis

    PS: The nastiest thing I've encountered with the
    card deck was that a friend exchanged all my cards
    which carried the word 'BEGIN' with cards carrying
    the word 'SADAT' - just as a hilarious play with
    words WRT two international politicians back then.
    Not so funny for me when I noticed all the syntax
    errors and had to wait another hour for the next
    batch run.

    Admit it, was a CLEVER joke !

    SADAT ... do, but barely, remember it now.

    The dictator, well, things didn't work out so
    well for him :-)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 01:12:01 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-27 17:24, c186282 wrote:
    On 10/27/26 00:01, Janis Papanagnou wrote:
    [...]

    -a The SysLord had a serial terminal, but all
    -a the rest of us had to do cards.

    I started with punch cards and switched early to a
    terminal.

    (Frankly, the cards had an advantage; the terminal
    made us stay constantly in front of it; write code,
    make some changes/fixes, compile, rinse repeat.
    With the cards we spent time beforehand designing
    the code, seeing and fixing all errors in one turn.
    It turned out to be, WRT net-time, more efficient.
    But, OTOH, fixing a punching mistake was more time
    consuming; needed a lot discipline and attention.)



    PS: The nastiest thing I've encountered with the
    card deck was that a friend exchanged all my cards
    which carried the word 'BEGIN' with cards carrying
    the word 'SADAT' - just as a hilarious play with
    words WRT two international politicians back then.
    Not so funny for me when I noticed all the syntax
    errors and had to wait another hour for the next
    batch run.

    -a Admit it, was a CLEVER joke !

    (I can't tell you how pissed I was at that moment!)

    But, with some distance, it was a marvellous prank.
    (That's why I still remember it after 40+ years.)

    He was all like that. Sadly he died extremely young.


    -a SADAT ... do, but barely, remember it now.

    (I do recall his name only because of that joke.)

    Janis

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 05:26:18 2026
    From Newsgroup: comp.unix.shell

    On 10/27/26 20:12, Janis Papanagnou wrote:
    On 2026-10-27 17:24, c186282 wrote:
    On 10/27/26 00:01, Janis Papanagnou wrote:
    [...]

    -a-a The SysLord had a serial terminal, but all
    -a-a the rest of us had to do cards.

    I started with punch cards and switched early to a
    terminal.

    We got terminals, EVENTUALLY. But at the beginning
    it was all punch cards. FORTRAN, COBOL, even that
    neat-o newfangled PDP-11 lang called 'C'.

    (Frankly, the cards had an advantage; the terminal
    made us stay constantly in front of it; write code,
    make some changes/fixes, compile, rinse repeat.
    With the cards we spent time beforehand designing
    the code, seeing and fixing all errors in one turn.
    It turned out to be, WRT net-time, more efficient.
    But, OTOH, fixing a punching mistake was more time
    consuming; needed a lot discipline and attention.)

    I'll say cards imposed a certain "discipline",
    get it right the first time. But, imho, not really
    a "good" solution.


    PS: The nastiest thing I've encountered with the
    card deck was that a friend exchanged all my cards
    which carried the word 'BEGIN' with cards carrying
    the word 'SADAT' - just as a hilarious play with
    words WRT two international politicians back then.
    Not so funny for me when I noticed all the syntax
    errors and had to wait another hour for the next
    batch run.

    -a-a Admit it, was a CLEVER joke !

    (I can't tell you how pissed I was at that moment!)

    Well, I can imagine ... but it WAS a clever joke !

    But, with some distance, it was a marvellous prank.
    (That's why I still remember it after 40+ years.)

    He was all like that. Sadly he died extremely young.

    Some do alas - the more 'boisterous' personalities
    especially. "Candle burning twice as bright" maybe.

    -a-a SADAT ... do, but barely, remember it now.

    (I do recall his name only because of that joke.)
    Checked a couple hours ago ... barely ANY reference
    to SADAT now ... and then only ABSTRACTS. It was
    a sort of 'structural correctness' tool for FORTRAN.
    Not really 'smart' at all, but it'd find gross
    errors. DID use it ... but it was SO SO long ago.

    Something like "PyCharm" can, sometimes, find
    mis-indented/incomplete bits in Python code.
    But even that IDE isn't as smart as desired.

    None of them can fully grasp What You Intended.
    Haven't even seen AI 'solutions' that are great
    for that. More than once I've put some bit of
    code one indent too far in or out for the
    intended purpose. The debugging CAN be rather
    difficult sometimes. Needs a human mind to
    grasp Where It Went Wrong.

    I miss the old Gen-3 programming IDEs. Not
    too many of them left. Very helpful and
    easy to navigate. Quick debugging and fixes.
    The successors - FAR too complicated and/or
    overly-abstract. Can't even figure out what
    they're saying - much less the problems with
    your code.

    Kinda back to the Olde Days ... "get it right
    the first time".

    Lazarus/FPC and a few others still carry on the
    old Gen-3 tradition. Love 'em. Shortest path
    to success.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Josef_M=C3=B6llers?=@josef@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 17:01:44 2026
    From Newsgroup: comp.unix.shell

    On 28.10.26 01:12, Janis Papanagnou wrote:
    On 2026-10-27 17:24, c186282 wrote:
    On 10/27/26 00:01, Janis Papanagnou wrote:
    [...]

    -a-a The SysLord had a serial terminal, but all
    -a-a the rest of us had to do cards.

    I started with punch cards and switched early to a
    terminal.

    Ah ... yes ... The Olde Times ;-)
    I started studying CS in 1977 (after two years trying my luck at EE).
    Indeed, we too had to use punched cards in the beginning.

    (Frankly, the cards had an advantage; the terminal
    made us stay constantly in front of it; write code,
    make some changes/fixes, compile, rinse repeat.
    With the cards we spent time beforehand designing
    the code, seeing and fixing all errors in one turn.
    It turned out to be, WRT net-time, more efficient.
    But, OTOH, fixing a punching mistake was more time
    consuming; needed a lot discipline and attention.)

    100% +1! Think twice before punching.

    I had been told once that IBM developers did not have a compiler or such
    at their disposal but only a text editor, so they, too, had to think
    twice before committing their code.




    PS: The nastiest thing I've encountered with the
    card deck was that a friend exchanged all my cards
    which carried the word 'BEGIN' with cards carrying
    the word 'SADAT' - just as a hilarious play with
    words WRT two international politicians back then.
    Not so funny for me when I noticed all the syntax
    errors and had to wait another hour for the next
    batch run.

    -a-a Admit it, was a CLEVER joke !

    (I can't tell you how pissed I was at that moment!)

    But, with some distance, it was a marvellous prank.
    (That's why I still remember it after 40+ years.)

    He was all like that. Sadly he died extremely young.


    -a-a SADAT ... do, but barely, remember it now.

    (I do recall his name only because of that joke.)

    This is SOOO funny! At that time I myself had put a note on the wall
    stating that with the developments then the keyword BEGIN should be
    replaced by SADAT.

    I'm 70 now, retired 4 years ago.

    Josef
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 17:50:39 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-28 17:01, Josef M||llers wrote:
    [...]

    I had been told once that IBM developers did not have a compiler or such
    at their disposal but only a text editor, so they, too, had to think
    twice before committing their code.

    This almost sounds like the joke where the editor was actually just
    the 'cat' command. :-)

    PS: The nastiest thing I've encountered with the
    card deck was that a friend exchanged all my cards
    which carried the word 'BEGIN' with cards carrying
    the word 'SADAT' - just as a hilarious play with
    words WRT two international politicians back then.
    Not so funny for me when I noticed all the syntax
    errors and had to wait another hour for the next
    batch run.

    -a-a Admit it, was a CLEVER joke !

    (I can't tell you how pissed I was at that moment!)

    But, with some distance, it was a marvellous prank.
    (That's why I still remember it after 40+ years.)

    He was all like that. Sadly he died extremely young.


    -a-a SADAT ... do, but barely, remember it now.

    (I do recall his name only because of that joke.)

    This is SOOO funny! At that time I myself had put a note on the wall
    stating that with the developments then the keyword BEGIN should be
    replaced by SADAT.

    Wow, what coincidence! :-)


    I'm 70 now, retired 4 years ago.

    Josef

    Janis, retired (hopefully only physically) as well

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 18:18:24 2026
    From Newsgroup: comp.unix.shell

    On Wed, 28 Oct 2026 17:01:44 +0100, Josef M||llers wrote:

    Ah ... yes ... The Olde Times ;-)
    I started studying CS in 1977 (after two years trying my luck at EE).
    Indeed, we too had to use punched cards in the beginning.

    The IBM 2260 terminal came out in 1964 but I didn't see one until I interviewed with IBM/Owego in 1968. If there were any in the college they
    were buried in a cave.

    I didn't get the job. IBM found my programming aptitude questionable.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 19:33:23 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-28, c186282 <c186282@nnada.net> wrote:

    I miss the old Gen-3 programming IDEs. Not
    too many of them left. Very helpful and
    easy to navigate. Quick debugging and fixes.

    The closest I ever came to using an IDE was the
    symbolic debugger that came with Lattice C for
    MS-DOS. Simple, effective... and gone.

    The successors - FAR too complicated and/or
    overly-abstract. Can't even figure out what
    they're saying - much less the problems with
    your code.

    My wife often says to me - on many topics other
    than computers - "Why does everything have to
    be such a huge project?" But with an IDE that's
    exactly what it is. Want to write "Hello, world"?
    You have to create a project. On the few times
    I was desperate enough to try an IDE so I could
    use its debugger, I got so bogged down in project
    politics that I went back to sprinkling printf()s
    through my code - which was faster in the end. It's
    text editors and makefiles for me, thankyouverymuch.

    Most people don't know the difference between
    complexity and sophistication, and are usually
    more impressed by complexity. From incomprehensible
    (but pretty!) web sites to security holes you can
    drive a truck through, those chickens are now coming
    home to roost. Big time.

    Perfection is achieved, not when there
    is nothing more to add, but when there
    is nothing left to take away.
    -- Antoine de Saint-Exup|-ry

    The KISS principle would really hurt sales, though,
    so it had to go.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David LaRue@huey.dll@tampabay.rr.com to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 23:28:12 2026
    From Newsgroup: comp.unix.shell

    rbowman <bowman@montana.com> wrote in news:nkesjgF6rc9U1
    @mid.individual.net:

    On Wed, 28 Oct 2026 17:01:44 +0100, Josef M||llers wrote:

    Ah ... yes ... The Olde Times ;-)
    I started studying CS in 1977 (after two years trying my luck at EE).
    Indeed, we too had to use punched cards in the beginning.

    The IBM 2260 terminal came out in 1964 but I didn't see one until I interviewed with IBM/Owego in 1968. If there were any in the college they were buried in a cave.

    I didn't get the job. IBM found my programming aptitude questionable.

    I too grew up accessing computers (the big iron) first with cards and later with terminals as they became available around campus. I agree that cards
    or anything low tech makes the developer first think about what they want
    to build and then do so.

    I had a slight advantage by the time my parents let me take college level computing with a friend at high school. I started on paper with imaginary simple computers via a Saturday morning show on PBS or more likely WGN Chicago. That was much earlier in my life, perhaps Junior High when I was also in an elective class to earn my Amateur Radio Novice Licence. Upon earning that and quickly moving to Technician, I became a member of the
    local ARRL Club. There I met all kinds of electricians, radio and antenna experts, and one Advanced class leader with his own antenna farm on his
    farm. He was doing moon bounce and slow scan TV. He showed me his latest project -- a home built Z80 Computer that booted by flipping switches to
    input the very tiny OS or a simple program. Now that really helped me form
    my programming and diagnostic capabilities.

    Thankfully all the Hams and teachers I met over the years were eager to
    share their knowledge. I loved teachers from any class that would go
    outside the curriculum and teach students outside class too. I hated
    students that would interupt a teacher with a question like "Is that going
    to be on the test?".

    I loved great teachers and quickly exited the few classes with poor
    teachers.

    Starting early classes on any subject with "low tech" helps form the
    student's mind.

    Ah the memories of a life well lived.

    Thank you to all the teachers who helped us form our minds!

    P.S. During those first years on cards for FORTRAN and COBOL a friend and
    I "competed" for solving programs with the least lines, comments excluded.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 00:11:49 2026
    From Newsgroup: comp.unix.shell

    On Wed, 28 Oct 2026 23:28:12 -0000 (UTC), David LaRue wrote:

    That was much earlier in my life, perhaps Junior High when I was
    also in an elective class to earn my Amateur Radio Novice Licence. Upon earning that and quickly moving to Technician, I became a member of the
    local ARRL Club. There I met all kinds of electricians, radio and
    antenna experts, and one Advanced class leader with his own antenna farm
    on his farm. He was doing moon bounce and slow scan TV. He showed me
    his latest project -- a home built Z80 Computer that booted by flipping switches to input the very tiny OS or a simple program. Now that really helped me form my programming and diagnostic capabilities.

    The Sputnik launch awakened interest in STEM subjects but computers were exotic critters when I was in high school. The IBM System 360/30 was
    released in 1964. RPI had close ties with IBM and iirc had one by 1965.
    That's what I learned FORTRAN IV on. The Z80 was way in the future.

    I did eventually get a Amateur Radio license. I'm stubborn enough to keep
    my Advanced license. They ain't making them anymore but if you had one
    you could keep it. I wasn't that great with code so I never tried for
    Extra.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 00:19:14 2026
    From Newsgroup: comp.unix.shell

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that
    came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and developed it further. I will say for its era Microsoft C had excellent
    hard copy documentation.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 00:46:50 2026
    From Newsgroup: comp.unix.shell

    On Wed, 28 Oct 2026 23:28:12 -0000 (UTC), David LaRue wrote:

    I too grew up accessing computers (the big iron) first with cards
    and later with terminals as they became available around campus. I
    agree that cards or anything low tech makes the developer first
    think about what they want to build and then do so.

    Imagine if your calculator was like that: you had to think carefully
    what you wanted to do, and write it down on a coding form or
    something, before simply switching the thing on and punching buttons
    ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Wed Oct 28 22:36:37 2026
    From Newsgroup: comp.unix.shell

    On 10/28/26 20:46, Lawrence DrCOOliveiro wrote:
    On Wed, 28 Oct 2026 23:28:12 -0000 (UTC), David LaRue wrote:

    I too grew up accessing computers (the big iron) first with cards
    and later with terminals as they became available around campus. I
    agree that cards or anything low tech makes the developer first
    think about what they want to build and then do so.

    Imagine if your calculator was like that: you had to think carefully
    what you wanted to do, and write it down on a coding form or
    something, before simply switching the thing on and punching buttons
    ...

    Well ... THAT'S HOW IT WAS not ALL so long ago.

    Get it right the FIRST time, or SUFFER.

    That plus minimal memory/storage ensured
    good quality, tight, code.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 09:13:14 2026
    From Newsgroup: comp.unix.shell

    On Wed, 28 Oct 2026 22:36:37 -0400
    c186282 <c186282@nnada.net> wrote:

    Well ... THAT'S HOW IT WAS not ALL so long ago.

    Get it right the FIRST time, or SUFFER.

    That plus minimal memory/storage ensured good quality, tight, code.

    :s/ensured/encouraged/

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Ahlstrom@OFeem1987@teleworm.us to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 12:27:18 2026
    From Newsgroup: comp.unix.shell

    rbowman wrote this screed in ALL-CAPS (fixed):

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that
    came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and developed it further. I will say for its era Microsoft C had excellent
    hard copy documentation.

    I agree with that last sentence. In the 80's the manuals for their
    C and FORTRAN were very good, and obviously inspired by the layout
    of DEC's manuals.
    --
    backups: always in season, never out of style.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 18:13:10 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29, John Ames <commodorejohn@gmail.com> wrote:

    On Wed, 28 Oct 2026 22:36:37 -0400
    c186282 <c186282@nnada.net> wrote:

    Well ... THAT'S HOW IT WAS not ALL so long ago.

    Get it right the FIRST time, or SUFFER.

    That plus minimal memory/storage ensured good quality, tight, code.

    :s/ensured/encouraged/

    It also encouraged efficient, logical, consistent system design.
    There just weren't the resources to implement the kinds of cruft
    that seems to be mandatory these days.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Christian Weisgerber@naddy@mips.inka.de to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 17:37:23 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-28, David LaRue <huey.dll@tampabay.rr.com> wrote:

    I too grew up accessing computers (the big iron) first with cards and later with terminals as they became available around campus.

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".
    --
    Christian "naddy" Weisgerber naddy@mips.inka.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 20:01:28 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29, Christian Weisgerber <naddy@mips.inka.de> wrote:
    On 2026-10-28, David LaRue <huey.dll@tampabay.rr.com> wrote:

    I too grew up accessing computers (the big iron) first with cards and later >> with terminals as they became available around campus.

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    By January 1st, 1979, 87.395% of all university access methods to
    computers were interactive visual terminals rather than TTYs or other.
    (With a 95% confidence interval of +/- 0.003% based on the polled
    sample size.)

    A coordinated mass conversion, to visual terminals, of all remaining
    teletype and other non-visual terminals attached to legacy time sharing systems, at all university campuses around the world, took place on
    September 13, 1983, now remembered as "T day".

    Engineering students in New York celebrated by suspending a chain of
    seven key punch machines from the Brooklyn Bridge.
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 21:18:53 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29 18:37, Christian Weisgerber wrote:
    On 2026-10-28, David LaRue <huey.dll@tampabay.rr.com> wrote:

    I too grew up accessing computers (the big iron) first with cards and later >> with terminals as they became available around campus.

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".


    Depends on the country and the uni. Even depends on the department.

    I think I saw it in 1983, but there were departments that had terminals earlier.

    Maybe what counts is the department that teaches programming to students
    buys the terminals, which is an important investment.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Christian Weisgerber@naddy@mips.inka.de to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 21:40:04 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29, Carlos E.R. <robin_listas@es.invalid> wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    Depends on the country and the uni. Even depends on the department.

    I'm asking for personal recollections. When did it happen for you?
    I've been wondering for some time, and this seems like the perfect
    opportunity to ask, given that people have reminisced about their
    punch card days.

    And yes, I expect computer science got terminals earlier than
    engineering.

    I think I saw it in 1983, but there were departments that had terminals earlier.

    That's one data point, thanks.
    --
    Christian "naddy" Weisgerber naddy@mips.inka.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 23:48:39 2026
    From Newsgroup: comp.unix.shell

    On Thu, 29 Oct 2026 17:37:23 -0000 (UTC), Christian Weisgerber wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    How about rCLthe 1970srCY?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Thu Oct 29 23:58:19 2026
    From Newsgroup: comp.unix.shell

    On 29/10/2026 21:40, Christian Weisgerber wrote:
    On 2026-10-29, Carlos E.R. <robin_listas@es.invalid> wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    Depends on the country and the uni. Even depends on the department.

    I'm asking for personal recollections. When did it happen for you?
    I've been wondering for some time, and this seems like the perfect opportunity to ask, given that people have reminisced about their
    punch card days.

    Well in 1969 it was flexowriters and an Elliot computer and paper tape.

    It was so bad I gave up on computers till around 1980
    At some point a friend with more money than sense started building an
    S100 computer. 6800 based I think.
    Think he had a serial terminal

    But what then happened was PC's and computers with keyboards and
    monitors and no one cared about terminals much. Unless you were running
    UNIX and a multiuser setup.
    I remember 32 Wyse 50s on a sco unix 386 box with a custom serial card.


    That was a popular corporate setup.


    And yes, I expect computer science got terminals earlier than
    engineering.

    I think I saw it in 1983, but there were departments that had terminals
    earlier.

    That's one data point, thanks.

    That vaguely gybes with my memory. I THINK that serial terminals for
    micros existed prior to 1980, but have no idea about mainframes etc.

    VT100 was a 1978 released serial terminal

    It was essentially the benchmark

    Later terminals were cheaper, but the VT100 was the first I can recall

    However...

    "DEC's first video terminal was the VT05 (1970), succeeded by the VT50
    (1974), and soon upgraded to the VT52 (1975). The VT52 featured a text
    display with 80 columns and 24 rows, bidirectional scrolling, and a
    custom control protocol that allowed the cursor to be moved about the
    screen. "

    I think that the Vt52 was about the first time a 'glass teletype'
    actually became more cost effective than a teletype
    --
    "Women actually are capable of being far more than the feminists will
    let them."



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 00:09:50 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29, Christian Weisgerber <naddy@mips.inka.de> wrote:

    On 2026-10-29, Carlos E.R. <robin_listas@es.invalid> wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    Depends on the country and the uni. Even depends on the department.

    I'm asking for personal recollections. When did it happen for you?
    I've been wondering for some time, and this seems like the perfect opportunity to ask, given that people have reminisced about their
    punch card days.

    And yes, I expect computer science got terminals earlier than
    engineering.

    I think I saw it in 1983, but there were departments that had terminals
    earlier.

    That's one data point, thanks.

    I attended university from 1968 to 1971. In the fall of 1968
    they converted from an IBM 7044 to a 360/67. The 360 had a few
    2260s, but I wouldn't call them common and access was fairly
    restricted. There was a number of hard-copy terminals, many
    of them dialup: IBM 2741, Teletype 33, 35, and even a few 37s.
    But billing (in computer centre funny money, issued to students at
    the start of a term) was given a fudge factor of 1.4 for terminal
    access. Most of us contented ourselves with either using the
    RJE terminal (originally staffed with an operator who collected
    a ticket for each run, later self-serve IIRC), or dropping our
    cards into a tray and coming back the next day to pick up the
    results (which incurred only a 0.4 fudge factor, which was great
    for conserving CC$ that were running low by the end of the term).
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 04:33:36 2026
    From Newsgroup: comp.unix.shell

    On Fri, 30 Oct 2026 00:09:50 GMT, Charlie Gibbs wrote:

    I attended university from 1968 to 1971. In the fall of 1968 they
    converted from an IBM 7044 to a 360/67. The 360 had a few 2260s, but I wouldn't call them common and access was fairly restricted.

    The 360/67 was the start of something new for IBM -- timesharing. The
    360/30 maxxed out at 64K and became a satellite processor for some of the later 360 machines. I wasn't too interested but a friend was and spoke of
    the future with awe. He eventually dropped out and moved to Boston where
    there was a lot more happening.

    My girlfriend started at SUNY Albany before transferring out of that zoo.
    I can't remember what they had, CDC maybe, but definitely not IBM and her programming course was in some language that I don't think survived
    either.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 03:40:58 2026
    From Newsgroup: comp.unix.shell

    On 10/29/26 12:27, Chris Ahlstrom wrote:
    rbowman wrote this screed in ALL-CAPS (fixed):

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that
    came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and
    developed it further. I will say for its era Microsoft C had excellent
    hard copy documentation.

    I agree with that last sentence. In the 80's the manuals for their
    C and FORTRAN were very good, and obviously inspired by the layout
    of DEC's manuals.

    You are correct - manuals/docs were EXTREMELY good
    for such stuff "back in the day". Found a manual
    for "Aztec C" (great !) from the old days ... WOW ! ...
    literally bit-level shit in there in case you needed
    to hyper-optimize something. Clearly the people who
    wrote the doc also wrote the compiler.

    More VOLUME of docs these days ... but "As Good" ???

    DO have the Aztec compiler ... MIGHT still work in
    DOSBox or a DOS or CP/M VM ........

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 03:58:03 2026
    From Newsgroup: comp.unix.shell

    On 10/29/26 13:37, Christian Weisgerber wrote:
    On 2026-10-28, David LaRue <huey.dll@tampabay.rr.com> wrote:

    I too grew up accessing computers (the big iron) first with cards and later >> with terminals as they became available around campus.

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    Ummmm ... started seeing them in the latter 70s ...
    at least ones 'regular people' were allowed to use
    for anything. EXACT date - forget it - depends on
    where you were. Surely sooner at Princeton than
    SteerPoke U.

    Original 'regular people' uses often included the
    printed library card catalog. Those authorized
    COULD write programs however. First I saw were
    hooked to SOME model of DEC iron.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 04:00:40 2026
    From Newsgroup: comp.unix.shell

    On 10/29/26 14:13, Charlie Gibbs wrote:
    On 2026-10-29, John Ames <commodorejohn@gmail.com> wrote:

    On Wed, 28 Oct 2026 22:36:37 -0400
    c186282 <c186282@nnada.net> wrote:

    Well ... THAT'S HOW IT WAS not ALL so long ago.

    Get it right the FIRST time, or SUFFER.

    That plus minimal memory/storage ensured good quality, tight, code.

    :s/ensured/encouraged/

    It also encouraged efficient, logical, consistent system design.
    There just weren't the resources to implement the kinds of cruft
    that seems to be mandatory these days.

    WILL still stick to my long-time rec that all
    'computer' students START on micro-controllers.
    Teaches efficiency, exact crafting, some hint
    of the underlying electronics.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 04:27:17 2026
    From Newsgroup: comp.unix.shell

    On 10/29/26 19:48, Lawrence DrCOOliveiro wrote:
    On Thu, 29 Oct 2026 17:37:23 -0000 (UTC), Christian Weisgerber wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    How about rCLthe 1970srCY?

    Fair enough. As said, depends on WHERE.

    Where I was, first saw like a dozen 'public
    access' terminals in 1978.

    But you had to be 'authorized' - and for
    minor users it was just access to a few
    little databases.

    Even the 'big iron' (usually medium-iron) of
    the day couldn't handle TOO much stuff.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 11:10:28 2026
    From Newsgroup: comp.unix.shell

    On 30/10/2026 04:33, rbowman wrote:
    her
    programming course was in some language that I don't think survived
    either.

    Probably ALGOL.

    That was all the rage back then
    --
    Any fool can believe in principles - and most of them do!



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Christian Weisgerber@naddy@mips.inka.de to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 15:14:27 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29, The Natural Philosopher <tnp@invalid.invalid> wrote:

    That vaguely gybes with my memory. I THINK that serial terminals for
    micros existed prior to 1980, but have no idea about mainframes etc.

    VT100 was a 1978 released serial terminal

    Somewhat famously the arrival of some ADM-3A terminals prompted
    Bill Joy to extend his ex(1) editor with a visual mode, i.e., vi(1).
    That was circa 1977.
    --
    Christian "naddy" Weisgerber naddy@mips.inka.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 17:52:11 2026
    From Newsgroup: comp.unix.shell

    On Fri, 30 Oct 2026 11:10:28 +0000, The Natural Philosopher wrote:

    On 30/10/2026 04:33, rbowman wrote:
    her programming course was in some language that I don't think survived
    either.

    Probably ALGOL.

    That was all the rage back then

    I think it was something even stranger, maybe SNOBOL. I'll see if she remembers the next time I talk to her. She may have repressed the entire experience. I wouldn't say SUNY was a diploma mill but it had over 10,000 students even back then and was industrial scale education.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Leroy H@lh@somewhere.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 18:26:06 2026
    From Newsgroup: comp.unix.shell

    On Thu, 29 Oct 2026 21:40:04 -0000 (UTC), Christian Weisgerber wrote:

    On 2026-10-29, Carlos E.R. <robin_listas@es.invalid> wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".


    There were only PCs when I was there, but my school also had access
    to time sharing with the mainframes of the Michigan Terminal System,
    or MTS:

    <https://en.wikipedia.org/wiki/Michigan_Terminal_System>

    On an early morning (about 2 am) job run, I literally brought the
    mainframe to its knees while simultaneously burning up the entire
    annual department time-sharing budget, via an extensive numerical
    simulation involving 500x500 matrix calculations.

    From that experience I learned a valuable computer science lesson
    that is not found in the standard textbooks: the most powerful
    digital computers are DAMNED SLOW AND IMPOTENT.

    I ended up doing the simulation on a desktop PC using almost
    4 WEEKS of runtime.

    My current desktop is probably a lot more powerful than those
    mainframes but most tasks of interest are still largely untouchable.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 19:24:59 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-30, c186282 <c186282@nnada.net> wrote:

    On 10/29/26 12:27, Chris Ahlstrom wrote:

    rbowman wrote this screed in ALL-CAPS (fixed):

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that >>>> came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and
    developed it further. I will say for its era Microsoft C had excellent
    hard copy documentation.

    I agree with that last sentence. In the 80's the manuals for their
    C and FORTRAN were very good, and obviously inspired by the layout
    of DEC's manuals.

    You are correct - manuals/docs were EXTREMELY good
    for such stuff "back in the day". Found a manual
    for "Aztec C" (great !) from the old days ... WOW ! ...
    literally bit-level shit in there in case you needed
    to hyper-optimize something. Clearly the people who
    wrote the doc also wrote the compiler.

    More VOLUME of docs these days ... but "As Good" ???

    Hardly. Most manuals back in the day had a section titled
    "Theory of Operation". I really miss that.

    DO have the Aztec compiler ... MIGHT still work in
    DOSBox or a DOS or CP/M VM ........

    My copy of Lattice C for MS-DOS still runs on the
    XP virtual machine I have running under VirtualBox.
    I still have the hard-copy manuals; they were well done.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 19:25:00 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-30, rbowman <bowman@montana.com> wrote:

    On Fri, 30 Oct 2026 00:09:50 GMT, Charlie Gibbs wrote:

    I attended university from 1968 to 1971. In the fall of 1968 they
    converted from an IBM 7044 to a 360/67. The 360 had a few 2260s, but I
    wouldn't call them common and access was fairly restricted.

    The 360/67 was the start of something new for IBM -- timesharing. The
    360/30 maxxed out at 64K and became a satellite processor for some of the later 360 machines. I wasn't too interested but a friend was and spoke of the future with awe. He eventually dropped out and moved to Boston where there was a lot more happening.

    This machine didn't run an IBM operating system; it ran MTS, the
    Michigan Terminal System. It was far better at timesharing than
    any IBM operating system.

    My girlfriend started at SUNY Albany before transferring out of that zoo.
    I can't remember what they had, CDC maybe, but definitely not IBM and her programming course was in some language that I don't think survived
    either.

    One course when I was there hit you with a different language
    every two weeks: Algol 60, Algol 68, Algol W, pl360 (the
    misbegotten bastard child of Algol and assembly language),
    LISP, UMIST, SNOBOL4... Fortunately I dropped out before
    I had to take that one. I did a term project in assembly
    language - my prof kept getting a pained expression as he
    repeatedly asked me why I would do such a thing.

    I left for a programming job in the Real World, writing
    assembly language and RPG for a card-based system with
    16K of memory.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 19:25:01 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-30, Leroy H <lh@somewhere.net> wrote:

    On an early morning (about 2 am) job run, I literally brought the
    mainframe to its knees while simultaneously burning up the entire
    annual department time-sharing budget, via an extensive numerical
    simulation involving 500x500 matrix calculations.

    From that experience I learned a valuable computer science lesson
    that is not found in the standard textbooks: the most powerful
    digital computers are DAMNED SLOW AND IMPOTENT.

    I wouldn't call that a computer science lesson; many CS weenies
    assume that computers are infinitely powerful, and start whining when confronted with systems in the real world. I had a confrontation
    with a guy like that when trying to determine why a COBOL program
    was running like molasses through a pinhole in January. One reason
    was that this genius had declared all subscripts as COMP-3 (packed
    decimal) rather than binary. Just changing those declarations alone
    knocked 30% off the execution time. I wish I could have had more
    time to work on that program; I bet I could have really sped it up.
    I calculated that the nested PERFORM VARYING loop that cleared a
    3-dimensional array would have taken 25 minutes of the estimated
    50-hour run time, due to a combination of those decimal subscripts
    and subroutine calling overhead. (The CPU did about 130 KIPS.)
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Leroy H@lh@somewhere.net to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 20:12:38 2026
    From Newsgroup: comp.unix.shell

    On Fri, 30 Oct 2026 19:25:01 GMT, Charlie Gibbs wrote:


    From that experience I learned a valuable computer science lesson
    that is not found in the standard textbooks: the most powerful
    digital computers are DAMNED SLOW AND IMPOTENT.

    I wouldn't call that a computer science lesson; many CS weenies
    assume that computers are infinitely powerful, and start whining when confronted with systems in the real world. I had a confrontation
    with a guy like that when trying to determine why a COBOL program
    was running like molasses through a pinhole in January. One reason
    was that this genius had declared all subscripts as COMP-3 (packed
    decimal) rather than binary. Just changing those declarations alone
    knocked 30% off the execution time. I wish I could have had more
    time to work on that program; I bet I could have really sped it up.
    I calculated that the nested PERFORM VARYING loop that cleared a 3-dimensional array would have taken 25 minutes of the estimated
    50-hour run time, due to a combination of those decimal subscripts
    and subroutine calling overhead. (The CPU did about 130 KIPS.)


    Optimization can only go so far. That's why supercomputers are being continually developed.

    But yes, software optimization is quite important and very much can be
    said about it, but most users will not ever need to be aware. Modern
    hardware can handle most routine computing tasks very efficiently.
    It is only fringe activities, such as video encoding or scientific calculations, that require massive hardware power.

    One hardware problem that needs to be fixed above all else is memory
    speed. Currently, all RAM is just another storage layer. The CPU
    does not directly process RAM data, but only data that has been transferred from RAM to cache memory -- and only first order cache at that. This ridiculous situation can seriously degrade performance if the programmer
    is not continually vigilant.

    I would claim that this "cache problem" is the most critical of all.
    The company that could produce cheap RAM memory on par with cache speeds
    would make $trillions overnight.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Fri Oct 30 23:10:47 2026
    From Newsgroup: comp.unix.shell

    On Fri, 30 Oct 2026 19:24:59 GMT, Charlie Gibbs wrote:

    I still have the hard-copy manuals; they were well done.

    ThatrCOs rare nowadays.

    Some think thatrCOs a mis-steak ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 04:14:05 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-30, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Fri, 30 Oct 2026 19:24:59 GMT, Charlie Gibbs wrote:

    I still have the hard-copy manuals; they were well done.

    ThatrCOs rare nowadays.

    Some think thatrCOs a mis-steak ...

    <groan>
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 11:40:12 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-30 20:24, Charlie Gibbs wrote:
    On 2026-10-30, c186282 <c186282@nnada.net> wrote:

    On 10/29/26 12:27, Chris Ahlstrom wrote:

    rbowman wrote this screed in ALL-CAPS (fixed):

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that >>>>> came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and >>>> developed it further. I will say for its era Microsoft C had excellent >>>> hard copy documentation.

    I agree with that last sentence. In the 80's the manuals for their
    C and FORTRAN were very good, and obviously inspired by the layout
    of DEC's manuals.

    You are correct - manuals/docs were EXTREMELY good
    for such stuff "back in the day". Found a manual
    for "Aztec C" (great !) from the old days ... WOW ! ...
    literally bit-level shit in there in case you needed
    to hyper-optimize something. Clearly the people who
    wrote the doc also wrote the compiler.

    More VOLUME of docs these days ... but "As Good" ???

    Hardly. Most manuals back in the day had a section titled
    "Theory of Operation". I really miss that.


    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 11:49:18 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29 22:40, Christian Weisgerber wrote:
    On 2026-10-29, Carlos E.R. <robin_listas@es.invalid> wrote:

    For those of us too young: When exactly did terminals become common
    on university campuses? Please be more specific than "the 1980s".

    Depends on the country and the uni. Even depends on the department.

    I'm asking for personal recollections. When did it happen for you?
    I've been wondering for some time, and this seems like the perfect opportunity to ask, given that people have reminisced about their
    punch card days.

    And yes, I expect computer science got terminals earlier than
    engineering.

    I think I saw it in 1983, but there were departments that had terminals
    earlier.

    That's one data point, thanks.


    I was forced by the system to take first year of engineering at the
    university in my province. All engineering had the same first year. Once
    we (if!) we passed, we could actually choose what college to continue
    in. So, when I arrived to Madrid for my second year (I think that was in
    the 83), a friend told me that the computer building that was shared by
    all in the campus had switched from cards to terminals, and that I had
    just missed it.

    And he described me the nightmare that first/second year students had to suffer to get their stack of cards punched and executed. Could take days.

    (I think that the school in which he did the first year had some
    computer thing in the Maths course, but I don't remember well what he
    told me)
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 10:49:58 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31, Carlos E. R. wrote:

    On 2026-10-30 20:24, Charlie Gibbs wrote:
    On 2026-10-30, c186282 <c186282@nnada.net> wrote:

    On 10/29/26 12:27, Chris Ahlstrom wrote:

    rbowman wrote this screed in ALL-CAPS (fixed):

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that >>>>>> came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and >>>>> developed it further. I will say for its era Microsoft C had excellent >>>>> hard copy documentation.

    I agree with that last sentence. In the 80's the manuals for their
    C and FORTRAN were very good, and obviously inspired by the layout
    of DEC's manuals.

    You are correct - manuals/docs were EXTREMELY good
    for such stuff "back in the day". Found a manual
    for "Aztec C" (great !) from the old days ... WOW ! ...
    literally bit-level shit in there in case you needed
    to hyper-optimize something. Clearly the people who
    wrote the doc also wrote the compiler.

    More VOLUME of docs these days ... but "As Good" ???

    Hardly. Most manuals back in the day had a section titled
    "Theory of Operation". I really miss that.


    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than a
    flaw of the online manual in itself?
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 11:57:23 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-29 22:40, Christian Weisgerber wrote:
    On 2026-10-29, Carlos E.R. <robin_listas@es.invalid> wrote:


    I think I saw it in 1983, but there were departments that had terminals
    earlier.

    That's one data point, thanks.

    I have one recollection of maybe 1983 or 84, visiting the microwave department, which was designing the aerial complex of a new frigate.
    They had a model to scale in an anechoic chamber; they had to scale the frequencies up to match the ship model. And they had an Apple-II (or was
    it I?) doing some long calculations. The display was off, the teacher
    was in the back, and he asked us near the machine to turn the display on
    to see the simulation. None of us knew how to do that. He had to come to
    the front, grumbling about how come we did not know where the switch was.

    Well, none of us had the money to buy an Apple II! And the IBM PC was
    still a year or two away.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?St=C3=A9phane?= CARPENTIER@sc@fiat-linux.fr to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 13:11:18 2026
    From Newsgroup: comp.unix.shell

    Le 31-10-2026, Nuno Silva <nunojsilva@invalid.invalid> a |-crit-a:
    On 2026-10-31, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than a
    flaw of the online manual in itself?

    Maybe. When I wanted to learned about Linux, I hated man pages. I found
    them awful and useless. Now, I'm using them only when I know what I'm
    looking for. I mean, when I don't know something, I know that the man
    page will send me a useless shit load of details without anything
    useful. Or, if anything is useful it's buried and hidden among useless
    stuff. If I'm looking for a fast way to use a command, I'm using tldr.
    If I want to understand a command, I avoid man pages and go look for
    some information on Internet. It's only when I want to know what an
    option is really doing or if an option exists that I'm going to look for
    it in the man pages.
    --
    Si vous avez du temps |a perdre :
    https://scarpet42.gitlab.io
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Leroy H@lh@somewhere.net to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 14:11:52 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 11:40:12 +0100, Carlos E. R. wrote:


    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.


    Try TkMan:

    <https://sourceforge.net/projects/tkman/>


    But a patch is required for recent Tcl:

    <https://sourceforge.net/p/tkman/bugs/6/>


    After patching, just click away.

    Tk/Tcl is perhaps the most underrated graphical toolkit.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From jayjwa@jayjwa@atr2.ath.cx.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 11:07:47 2026
    From Newsgroup: comp.unix.shell

    Leroy H <lh@somewhere.net> writes:

    There were only PCs when I was there, but my school also had access
    to time sharing with the mainframes of the Michigan Terminal System,
    or MTS:

    <https://en.wikipedia.org/wiki/Michigan_Terminal_System>
    You can run this under SDL Hercules. I have a D6 system. Unfortunately,
    there's not much installed in the way of software, it doesn't have any languages I really know, and it couldn't do networking last I checked
    (the SDL Hercules project w/MTS - the real machine could or so I
    heard). Still, it's fun and gives me a reason to dust off the x3270.

    https://try-mts.com/why-try-mts/
    https://sdl-hercules-390.github.io/html/

    It has this thing where, after a day or two, it wants to dump its stats
    to "tape" and you have to do a dance with it, only it does not want to
    take its tape, like a kid does not want to eat lima beans.

    00049 MTS *DWB: MOUNT NEW CMDSTAT TAPE RING IN WITH RACK M002 FOR INITIALIZAT

    This is what it looks like if/when you win:
    00049 MTS SYS.: F (1 9TP) M002 on 9TP, ring IN, 'CMDSTAT' ******************** OK M002 T90A

    The DEC systems are more fun, have better docs, and much more software.

    My current desktop is probably a lot more powerful than those
    mainframes but most tasks of interest are still largely untouchable.
    Absolutely. A smartphone is.
    --
    PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
    "The Internet should always be the Wild West!"
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 16:42:44 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 11:49, Carlos E. R. wrote:
    [...] So, when I arrived to Madrid for my second year (I think that was in the 83), a friend told me that the computer building that was shared by
    all in the campus had switched from cards to terminals, and that I had
    just missed it.

    And he described me the nightmare that first/second year students had to suffer to get their stack of cards punched and executed. Could take days.

    Strong words. And absurd time scales. They certainly don't match my observations. All of us did our punch cards based coding often just
    during the pauses between the lectures; the basic code maybe in an
    hour, the fixes - usually just one or two iterations needed - done
    during the "cum tempore" 10 minutes. But most programming in those
    early beginner courses also wasn't too voluminous, to be fair.

    What certainly was painful was the (for obvious reasons) inherent
    non-existence of a <Del> or <Backspace> key on the punch devices.
    (They had a useful "Copy" key (<Dup>?), though.)[*]

    BTW, a "nightmare" I considered the keyboards that came with the
    VT100 series of terminals! (My fingers still ache if I only think
    back of these days!) Luckily these times passed fast.

    Janis, now back at his Model-M keyboard clone

    [*] IIRC, they looked like (or may even have been) these devices: https://mimmsmuseum.org/wp-content/uploads/2020/07/Punchcard-708x1024.jpg
    (For those who couldn't imagine what we dinosaurs are talking about.) :-)
    Still amazing seeing images of these devices again after all those
    many decades.

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 16:57:26 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Janis, preferring to avoid mouse-devices in the first place

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 18:42:34 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 11:49:18 +0100, Carlos E. R. wrote:

    I was forced by the system to take first year of engineering at the university in my province. All engineering had the same first year. Once
    we (if!) we passed, we could actually choose what college to continue
    in.

    At mine the first two years were the same for everyone. It provided the
    basics needed for specialization.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 18:53:52 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 11:57:23 +0100, Carlos E. R. wrote:

    I have one recollection of maybe 1983 or 84, visiting the microwave department, which was designing the aerial complex of a new frigate.
    They had a model to scale in an anechoic chamber; they had to scale the frequencies up to match the ship model. And they had an Apple-II (or was
    it I?) doing some long calculations. The display was off, the teacher
    was in the back, and he asked us near the machine to turn the display on
    to see the simulation. None of us knew how to do that. He had to come to
    the front, grumbling about how come we did not know where the switch
    was.

    Well, none of us had the money to buy an Apple II! And the IBM PC was
    still a year or two away.

    The company I worked for wasn't big on pending money but for some reason
    they had a firm come it to teach us pair programming. The presenter
    arrived with Macs for the hands on experience. There were probably 60
    people attending, none of whom had ever used a Mac. The programmers from
    my area grabbed the snacks and ghosted.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 19:53:52 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 14:11, St|-phane CARPENTIER wrote:
    Le 31-10-2026, Nuno Silva <nunojsilva@invalid.invalid> a |-crit-a:
    On 2026-10-31, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than a
    flaw of the online manual in itself?

    Maybe. When I wanted to learned about Linux, I hated man pages. I found
    them awful and useless. Now, I'm using them only when I know what I'm
    looking for. I mean, when I don't know something, I know that the man
    page will send me a useless shit load of details without anything
    useful. Or, if anything is useful it's buried and hidden among useless
    stuff. If I'm looking for a fast way to use a command, I'm using tldr.
    If I want to understand a command, I avoid man pages and go look for
    some information on Internet. It's only when I want to know what an
    option is really doing or if an option exists that I'm going to look for
    it in the man pages.

    I ask chatgpt how to use the command.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 19:56:17 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?


    Janis, preferring to avoid mouse-devices in the first place

    Sure, point and click can also work without a mouse. Use the cursor to
    select an entry in the table of contents, then hit enter.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 19:56:32 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 11:49, Nuno Silva wrote:
    On 2026-10-31, Carlos E. R. wrote:

    On 2026-10-30 20:24, Charlie Gibbs wrote:
    On 2026-10-30, c186282 <c186282@nnada.net> wrote:

    On 10/29/26 12:27, Chris Ahlstrom wrote:

    rbowman wrote this screed in ALL-CAPS (fixed):

    On Wed, 28 Oct 2026 19:33:23 GMT, Charlie Gibbs wrote:

    The closest I ever came to using an IDE was the symbolic debugger that >>>>>>> came with Lattice C for MS-DOS. Simple, effective... and gone.

    I missed that one although I did use MS C after they bought Lattice and >>>>>> developed it further. I will say for its era Microsoft C had excellent >>>>>> hard copy documentation.

    I agree with that last sentence. In the 80's the manuals for their
    C and FORTRAN were very good, and obviously inspired by the layout
    of DEC's manuals.

    You are correct - manuals/docs were EXTREMELY good
    for such stuff "back in the day". Found a manual
    for "Aztec C" (great !) from the old days ... WOW ! ...
    literally bit-level shit in there in case you needed
    to hyper-optimize something. Clearly the people who
    wrote the doc also wrote the compiler.

    More VOLUME of docs these days ... but "As Good" ???

    Hardly. Most manuals back in the day had a section titled
    "Theory of Operation". I really miss that.


    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than a
    flaw of the online manual in itself?

    No, man pages do not contain links to section of the document. It is not structured.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 20:08:34 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 16:42, Janis Papanagnou wrote:
    On 2026-10-31 11:49, Carlos E. R. wrote:
    [...] So, when I arrived to Madrid for my second year (I think that
    was in the 83), a friend told me that the computer building that was
    shared by all in the campus had switched from cards to terminals, and
    that I had just missed it.

    And he described me the nightmare that first/second year students had
    to suffer to get their stack of cards punched and executed. Could take
    days.

    Strong words. And absurd time scales. They certainly don't match my observations. All of us did our punch cards based coding often just
    during the pauses between the lectures; the basic code maybe in an
    hour, the fixes - usually just one or two iterations needed - done
    during the "cum tempore" 10 minutes. But most programming in those
    early beginner courses also wasn't too voluminous, to be fair.

    What certainly was painful was the (for obvious reasons) inherent non-existence of a <Del> or <Backspace> key on the punch devices.
    (They had a useful "Copy" key (<Dup>?), though.)[*]

    I don't remember if my friend punched his own code, or had it punched.
    Would depend on how many punch machines they had for lowly students.

    I remember his saying that he had to submit his stack of cards to a
    clerk, then given a paper slip to collect the results another day.

    ...
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 21:20:55 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 20:08, Carlos E. R. wrote:

    I don't remember if my friend punched his own code, or had it punched.
    Would depend on how many punch machines they had for lowly students.

    We had a "row" of such machines available. Don't recall to have
    ever waited for a free place (or the waiting time was negligible).


    I remember his saying that he had to submit his stack of cards to a
    clerk, then given a paper slip to collect the results another day.

    The way it was done in our place was technically similar but did
    not require that much time.

    The batch cards reader was in an accessible are, you could just
    put the cards either directly in the reader device or in a queue
    on a nearby desk where an operator did that job then. The reader
    was constantly fed with cards by the operators since the queue
    was also regularly filled by all the students; hardly more delay
    than, maybe, 15 minutes. The printouts were quickly created with
    the batch processing by super-fast chain printers, so were also
    available in short term. Some delay was due to the fanfold paper
    needed to be physically separated (by the jobs or user IDs) to be
    associated to the different users. The output landed sorted in a
    special shelf where we could fetch them. The whole batch process,
    from the punch cards delivery to getting the printout results in
    (typically less than) an hour.

    A peculiarity of the physical separation of the printouts was the
    application of a nice trick; the printing logic for the front page
    of the job printed some text (X-es?) across the paper-perforation
    so that the individual jobs could quickly be detected visually if
    you looked at the paper stack from the side.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 22:11:24 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 19:56, Carlos E. R. wrote:
    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    But technically we have already "clickable" documents; with HTML for
    example.

    (Although it should still be available in one page, and ideally also
    searchable by regexps in easy ways. (As opposed to click on a search
    icon, move the mouse to a new sub-window, (optionally) click another
    time in that window to "activate" it for input, type in only a fixed
    non-regexp text (often without possibility to distinguish caps, or,
    if you're lucky, only with an extra click in some control-box), and
    hit enter (if you're lucky) or have to again move the mouse to click
    on some Okay button.) - I certainly hate to have no '/search-pattern'
    or '<Ctrl-F>search-pattern' available; with emphasis on "pattern".)

    Personally I typically want (at least) three levels of information.
    Terse usage information, complete interface description, and thorough explanations of all details in case of the more complex tools.

    Mostly we (now) have all that information; if only through the Web.
    (But often inconsistent or even unreliable.)

    Should we have everything just in one (clickable) format like HTML?
    I don't think so. Should we have all the spread existing information
    rewritten in some other format? Well, who would do that job?

    What I (also) criticize is that we don't have a consistent level of
    information with some newer Linux platforms. I wished for the "second
    level" of information that the man page format would have been kept/
    maintained instead of trying to deprive that format in favor of the
    'info' format.



    Janis, preferring to avoid mouse-devices in the first place

    Sure, point and click can also work without a mouse. Use the cursor to select an entry in the table of contents, then hit enter.

    Yes, sure. For long documents ("level three" information) with a lot
    content where a "table of contents" is sensible that makes completely
    sense. (Even pure mouse-control would be fine here [for me] in this
    case.)

    For the information level where I'd see the man-pages I wouldn't even
    need a "table of contents", since that type of information shouldn't
    be that voluminous, IMO.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Oct 31 21:38:19 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 11:07:47 -0400, jayjwa wrote:

    The DEC systems are more fun, have better docs, and much more
    software.

    If you look at all the vintage docs collected at Bitsavers, out of
    (currently) about 660GB in total, over 40% is from DEC. Number 2 is
    IBM, but the DEC collection is bigger by nearly 3:1.

    Number 3 is CDC, at about a quarter of the size of the IBM collection.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Oct 31 21:48:06 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 11:57:23 +0100, Carlos E. R. wrote:

    I have one recollection of maybe 1983 or 84, visiting the microwave department, which was designing the aerial complex of a new frigate.
    They had a model to scale in an anechoic chamber; they had to scale
    the frequencies up to match the ship model. And they had an Apple-II
    (or was it I?) doing some long calculations.

    In about 1987 or so, all the Efc|Efc+ universities were members of the Apple University Consortium. We decided to put together a report on what
    people were doing with their respective Apple Mac gear. To try to get
    a fresh perspective on things, each University sent a person to report
    on another one. I got sent to Auckland.

    At the Architecture department, I found a guy using a Macintosh II to
    collect data on the acoustic characteristics of architectural models.
    As you say, to get the numbers to come out proportionally right, he
    had to scale down the wavelengths to match the scale of the model,
    which meant scaling up the frequencies. And the old IBM PC (AT?) bus
    of the time simply didnrCOt have the bandwidth to cope with those high frequencies; but the 32-bit NuBus inside the Mac II could.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 21:57:58 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 11:40:12 +0100, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index.

    Most man pages are not supposed to be that large. Of course, there
    are some exceptions (like bash). For those I think yourCOll find the
    man page was generated from some other, more navigable form anyway.

    For example, if you look at Perl, you will see its documentation is
    broken up across a whole series of man pages -- over 200 of them.

    (Is that going too far in the other direction, do you think ... ?)

    Tip: if you prefer another form, like PDF, itrCOs quite easy to generate
    that from any man page. I used to use a somewhat convoluted command
    for this, but it turns the usual Linux rCLmanrCY command has an option to directly choose the output format, e.g. view a man page directly in
    typeset form without saving it to a file:

    man -Tpdf 7 unix | okular - &

    (Substitute your choice of favourite PDF reader.)

    Info pages are somewhat better.

    I have tried info pages a few times, but always found them awkward to
    navigate. IrCOve never heard of anybody who liked them.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Leroy H@lh@somewhere.net to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 22:14:52 2026
    From Newsgroup: comp.unix.shell

    On Sat, 31 Oct 2026 21:57:58 -0000 (UTC), Lawrence DrCOOliveiro wrote:


    For example, if you look at Perl, you will see its documentation is
    broken up across a whole series of man pages -- over 200 of them.

    (Is that going too far in the other direction, do you think ... ?)


    The record for the number of man pages has to be openssl.

    Here is the list on my Gentoo system. Don't bother counting.

    /usr/share/man/man1
    /usr/share/man/man1/CA.pl.1ossl.bz2
    /usr/share/man/man1/asn1parse.1ossl.bz2
    /usr/share/man/man1/c_rehash.1ossl.bz2
    /usr/share/man/man1/ca.1ossl.bz2
    /usr/share/man/man1/ciphers.1ossl.bz2
    /usr/share/man/man1/cmp.1ossl.bz2
    /usr/share/man/man1/cms.1ossl.bz2
    /usr/share/man/man1/crl.1ossl.bz2
    /usr/share/man/man1/crl2pkcs7.1ossl.bz2
    /usr/share/man/man1/dgst.1ossl.bz2
    /usr/share/man/man1/dhparam.1ossl.bz2
    /usr/share/man/man1/dsa.1ossl.bz2
    /usr/share/man/man1/dsaparam.1ossl.bz2
    /usr/share/man/man1/ec.1ossl.bz2
    /usr/share/man/man1/ecparam.1ossl.bz2
    /usr/share/man/man1/enc.1ossl.bz2
    /usr/share/man/man1/engine.1ossl.bz2
    /usr/share/man/man1/errstr.1ossl.bz2
    /usr/share/man/man1/gendsa.1ossl.bz2
    /usr/share/man/man1/genpkey.1ossl.bz2
    /usr/share/man/man1/genrsa.1ossl.bz2
    /usr/share/man/man1/info.1ossl.bz2
    /usr/share/man/man1/kdf.1ossl.bz2
    /usr/share/man/man1/mac.1ossl.bz2
    /usr/share/man/man1/nseq.1ossl.bz2
    /usr/share/man/man1/ocsp.1ossl.bz2 /usr/share/man/man1/openssl-asn1parse.1ossl.bz2 /usr/share/man/man1/openssl-ca.1ossl.bz2 /usr/share/man/man1/openssl-ciphers.1ossl.bz2 /usr/share/man/man1/openssl-cmds.1ossl.bz2 /usr/share/man/man1/openssl-cmp.1ossl.bz2 /usr/share/man/man1/openssl-cms.1ossl.bz2 /usr/share/man/man1/openssl-configutl.1ossl.bz2 /usr/share/man/man1/openssl-crl.1ossl.bz2 /usr/share/man/man1/openssl-crl2pkcs7.1ossl.bz2 /usr/share/man/man1/openssl-dgst.1ossl.bz2 /usr/share/man/man1/openssl-dhparam.1ossl.bz2 /usr/share/man/man1/openssl-dsa.1ossl.bz2 /usr/share/man/man1/openssl-dsaparam.1ossl.bz2 /usr/share/man/man1/openssl-ec.1ossl.bz2 /usr/share/man/man1/openssl-ecparam.1ossl.bz2 /usr/share/man/man1/openssl-enc.1ossl.bz2 /usr/share/man/man1/openssl-engine.1ossl.bz2 /usr/share/man/man1/openssl-errstr.1ossl.bz2 /usr/share/man/man1/openssl-fipsinstall.1ossl.bz2 /usr/share/man/man1/openssl-format-options.1ossl.bz2 /usr/share/man/man1/openssl-gendsa.1ossl.bz2 /usr/share/man/man1/openssl-genpkey.1ossl.bz2 /usr/share/man/man1/openssl-genrsa.1ossl.bz2 /usr/share/man/man1/openssl-info.1ossl.bz2 /usr/share/man/man1/openssl-kdf.1ossl.bz2 /usr/share/man/man1/openssl-list.1ossl.bz2 /usr/share/man/man1/openssl-mac.1ossl.bz2 /usr/share/man/man1/openssl-namedisplay-options.1ossl.bz2 /usr/share/man/man1/openssl-nseq.1ossl.bz2 /usr/share/man/man1/openssl-ocsp.1ossl.bz2 /usr/share/man/man1/openssl-passphrase-options.1ossl.bz2 /usr/share/man/man1/openssl-passwd.1ossl.bz2 /usr/share/man/man1/openssl-pkcs12.1ossl.bz2 /usr/share/man/man1/openssl-pkcs7.1ossl.bz2 /usr/share/man/man1/openssl-pkcs8.1ossl.bz2 /usr/share/man/man1/openssl-pkey.1ossl.bz2 /usr/share/man/man1/openssl-pkeyparam.1ossl.bz2 /usr/share/man/man1/openssl-pkeyutl.1ossl.bz2 /usr/share/man/man1/openssl-prime.1ossl.bz2 /usr/share/man/man1/openssl-rand.1ossl.bz2 /usr/share/man/man1/openssl-rehash.1ossl.bz2 /usr/share/man/man1/openssl-req.1ossl.bz2 /usr/share/man/man1/openssl-rsa.1ossl.bz2 /usr/share/man/man1/openssl-rsautl.1ossl.bz2 /usr/share/man/man1/openssl-s_client.1ossl.bz2 /usr/share/man/man1/openssl-s_server.1ossl.bz2 /usr/share/man/man1/openssl-s_time.1ossl.bz2 /usr/share/man/man1/openssl-sess_id.1ossl.bz2 /usr/share/man/man1/openssl-skeyutl.1ossl.bz2 /usr/share/man/man1/openssl-smime.1ossl.bz2 /usr/share/man/man1/openssl-speed.1ossl.bz2 /usr/share/man/man1/openssl-spkac.1ossl.bz2 /usr/share/man/man1/openssl-srp.1ossl.bz2 /usr/share/man/man1/openssl-storeutl.1ossl.bz2 /usr/share/man/man1/openssl-ts.1ossl.bz2 /usr/share/man/man1/openssl-verification-options.1ossl.bz2 /usr/share/man/man1/openssl-verify.1ossl.bz2 /usr/share/man/man1/openssl-version.1ossl.bz2 /usr/share/man/man1/openssl-x509.1ossl.bz2 /usr/share/man/man1/openssl.1ossl.bz2
    /usr/share/man/man1/passwd.1ossl.bz2
    /usr/share/man/man1/pkcs12.1ossl.bz2
    /usr/share/man/man1/pkcs7.1ossl.bz2
    /usr/share/man/man1/pkcs8.1ossl.bz2
    /usr/share/man/man1/pkey.1ossl.bz2
    /usr/share/man/man1/pkeyparam.1ossl.bz2
    /usr/share/man/man1/pkeyutl.1ossl.bz2
    /usr/share/man/man1/prime.1ossl.bz2
    /usr/share/man/man1/rand.1ossl.bz2
    /usr/share/man/man1/rehash.1ossl.bz2
    /usr/share/man/man1/req.1ossl.bz2
    /usr/share/man/man1/rsa.1ossl.bz2
    /usr/share/man/man1/rsautl.1ossl.bz2
    /usr/share/man/man1/s_client.1ossl.bz2
    /usr/share/man/man1/s_server.1ossl.bz2
    /usr/share/man/man1/s_time.1ossl.bz2
    /usr/share/man/man1/sess_id.1ossl.bz2
    /usr/share/man/man1/smime.1ossl.bz2
    /usr/share/man/man1/speed.1ossl.bz2
    /usr/share/man/man1/spkac.1ossl.bz2
    /usr/share/man/man1/srp.1ossl.bz2
    /usr/share/man/man1/storeutl.1ossl.bz2
    /usr/share/man/man1/ts.1ossl.bz2
    /usr/share/man/man1/tsget.1ossl.bz2
    /usr/share/man/man1/verify.1ossl.bz2
    /usr/share/man/man1/version.1ossl.bz2
    /usr/share/man/man1/x509.1ossl.bz2
    /usr/share/man/man3
    /usr/share/man/man3/ACCESS_DESCRIPTION_free.3ossl.bz2 /usr/share/man/man3/ACCESS_DESCRIPTION_new.3ossl.bz2 /usr/share/man/man3/ADMISSIONS.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_free.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_get0_admissionAuthority.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_get0_namingAuthority.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_get0_professionInfos.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_new.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_set0_admissionAuthority.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_set0_namingAuthority.3ossl.bz2 /usr/share/man/man3/ADMISSIONS_set0_professionInfos.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX_get0_admissionAuthority.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX_get0_contentsOfAdmissions.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX_set0_admissionAuthority.3ossl.bz2 /usr/share/man/man3/ADMISSION_SYNTAX_set0_contentsOfAdmissions.3ossl.bz2 /usr/share/man/man3/ASIdOrRange_free.3ossl.bz2 /usr/share/man/man3/ASIdOrRange_new.3ossl.bz2 /usr/share/man/man3/ASIdentifierChoice_free.3ossl.bz2 /usr/share/man/man3/ASIdentifierChoice_new.3ossl.bz2 /usr/share/man/man3/ASIdentifiers_free.3ossl.bz2 /usr/share/man/man3/ASIdentifiers_new.3ossl.bz2 /usr/share/man/man3/ASN1_AUX.3ossl.bz2 /usr/share/man/man3/ASN1_ENUMERATED_get.3ossl.bz2 /usr/share/man/man3/ASN1_ENUMERATED_get_int64.3ossl.bz2 /usr/share/man/man3/ASN1_ENUMERATED_set.3ossl.bz2 /usr/share/man/man3/ASN1_ENUMERATED_set_int64.3ossl.bz2 /usr/share/man/man3/ASN1_ENUMERATED_to_BN.3ossl.bz2 /usr/share/man/man3/ASN1_EXTERN_FUNCS.3ossl.bz2 /usr/share/man/man3/ASN1_GENERALIZEDTIME_adj.3ossl.bz2 /usr/share/man/man3/ASN1_GENERALIZEDTIME_check.3ossl.bz2 /usr/share/man/man3/ASN1_GENERALIZEDTIME_dup.3ossl.bz2 /usr/share/man/man3/ASN1_GENERALIZEDTIME_print.3ossl.bz2 /usr/share/man/man3/ASN1_GENERALIZEDTIME_set.3ossl.bz2 /usr/share/man/man3/ASN1_GENERALIZEDTIME_set_string.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_free.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_get.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_get_int64.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_get_uint64.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_new.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_set.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_set_int64.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_set_uint64.3ossl.bz2 /usr/share/man/man3/ASN1_INTEGER_to_BN.3ossl.bz2 /usr/share/man/man3/ASN1_ITEM.3ossl.bz2 /usr/share/man/man3/ASN1_ITEM_get.3ossl.bz2 /usr/share/man/man3/ASN1_ITEM_lookup.3ossl.bz2 /usr/share/man/man3/ASN1_OBJECT_free.3ossl.bz2 /usr/share/man/man3/ASN1_OBJECT_new.3ossl.bz2 /usr/share/man/man3/ASN1_PRINT_ARG.3ossl.bz2 /usr/share/man/man3/ASN1_STREAM_ARG.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_TABLE.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_TABLE_add.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_TABLE_cleanup.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_TABLE_get.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_cmp.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_data.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_dup.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_free.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_get0_data.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_length.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_new.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_print.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_print_ex.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_print_ex_fp.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_set.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_to_UTF8.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_type.3ossl.bz2 /usr/share/man/man3/ASN1_STRING_type_new.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_adj.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_check.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_cmp_time_t.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_compare.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_diff.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_dup.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_normalize.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_print.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_print_ex.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_set.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_set_string.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_set_string_X509.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_to_generalizedtime.3ossl.bz2 /usr/share/man/man3/ASN1_TIME_to_tm.3ossl.bz2 /usr/share/man/man3/ASN1_TYPE_cmp.3ossl.bz2 /usr/share/man/man3/ASN1_TYPE_get.3ossl.bz2 /usr/share/man/man3/ASN1_TYPE_pack_sequence.3ossl.bz2 /usr/share/man/man3/ASN1_TYPE_set.3ossl.bz2 /usr/share/man/man3/ASN1_TYPE_set1.3ossl.bz2 /usr/share/man/man3/ASN1_TYPE_unpack_sequence.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_adj.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_check.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_cmp_time_t.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_dup.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_print.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_set.3ossl.bz2 /usr/share/man/man3/ASN1_UTCTIME_set_string.3ossl.bz2 /usr/share/man/man3/ASN1_add_oid_module.3ossl.bz2 /usr/share/man/man3/ASN1_aux_cb.3ossl.bz2 /usr/share/man/man3/ASN1_aux_const_cb.3ossl.bz2 /usr/share/man/man3/ASN1_ex_d2i.3ossl.bz2 /usr/share/man/man3/ASN1_ex_d2i_ex.3ossl.bz2 /usr/share/man/man3/ASN1_ex_free_func.3ossl.bz2 /usr/share/man/man3/ASN1_ex_i2d.3ossl.bz2 /usr/share/man/man3/ASN1_ex_new_ex_func.3ossl.bz2 /usr/share/man/man3/ASN1_ex_new_func.3ossl.bz2 /usr/share/man/man3/ASN1_ex_print_func.3ossl.bz2 /usr/share/man/man3/ASN1_generate_nconf.3ossl.bz2 /usr/share/man/man3/ASN1_generate_v3.3ossl.bz2 /usr/share/man/man3/ASN1_item_d2i.3ossl.bz2 /usr/share/man/man3/ASN1_item_d2i_bio.3ossl.bz2 /usr/share/man/man3/ASN1_item_d2i_bio_ex.3ossl.bz2 /usr/share/man/man3/ASN1_item_d2i_ex.3ossl.bz2 /usr/share/man/man3/ASN1_item_d2i_fp.3ossl.bz2 /usr/share/man/man3/ASN1_item_d2i_fp_ex.3ossl.bz2 /usr/share/man/man3/ASN1_item_i2d_mem_bio.3ossl.bz2 /usr/share/man/man3/ASN1_item_new.3ossl.bz2 /usr/share/man/man3/ASN1_item_new_ex.3ossl.bz2 /usr/share/man/man3/ASN1_item_pack.3ossl.bz2 /usr/share/man/man3/ASN1_item_sign.3ossl.bz2 /usr/share/man/man3/ASN1_item_sign_ctx.3ossl.bz2 /usr/share/man/man3/ASN1_item_sign_ex.3ossl.bz2 /usr/share/man/man3/ASN1_item_unpack.3ossl.bz2 /usr/share/man/man3/ASN1_item_unpack_ex.3ossl.bz2 /usr/share/man/man3/ASN1_item_verify.3ossl.bz2 /usr/share/man/man3/ASN1_item_verify_ctx.3ossl.bz2 /usr/share/man/man3/ASN1_item_verify_ex.3ossl.bz2 /usr/share/man/man3/ASN1_tag2str.3ossl.bz2 /usr/share/man/man3/ASRange_free.3ossl.bz2 /usr/share/man/man3/ASRange_new.3ossl.bz2 /usr/share/man/man3/ASYNC_STATUS_EAGAIN.3ossl.bz2 /usr/share/man/man3/ASYNC_STATUS_ERR.3ossl.bz2 /usr/share/man/man3/ASYNC_STATUS_OK.3ossl.bz2 /usr/share/man/man3/ASYNC_STATUS_UNSUPPORTED.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_clear_fd.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_free.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_get_all_fds.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_get_callback.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_get_changed_fds.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_get_fd.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_get_status.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_new.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_set_callback.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_set_status.3ossl.bz2 /usr/share/man/man3/ASYNC_WAIT_CTX_set_wait_fd.3ossl.bz2 /usr/share/man/man3/ASYNC_block_pause.3ossl.bz2 /usr/share/man/man3/ASYNC_callback_fn.3ossl.bz2 /usr/share/man/man3/ASYNC_cleanup_thread.3ossl.bz2 /usr/share/man/man3/ASYNC_get_current_job.3ossl.bz2 /usr/share/man/man3/ASYNC_get_mem_functions.3ossl.bz2 /usr/share/man/man3/ASYNC_get_wait_ctx.3ossl.bz2 /usr/share/man/man3/ASYNC_init_thread.3ossl.bz2 /usr/share/man/man3/ASYNC_is_capable.3ossl.bz2 /usr/share/man/man3/ASYNC_pause_job.3ossl.bz2 /usr/share/man/man3/ASYNC_set_mem_functions.3ossl.bz2 /usr/share/man/man3/ASYNC_stack_alloc_fn.3ossl.bz2 /usr/share/man/man3/ASYNC_stack_free_fn.3ossl.bz2 /usr/share/man/man3/ASYNC_start_job.3ossl.bz2 /usr/share/man/man3/ASYNC_unblock_pause.3ossl.bz2 /usr/share/man/man3/AUTHORITY_INFO_ACCESS_free.3ossl.bz2 /usr/share/man/man3/AUTHORITY_INFO_ACCESS_new.3ossl.bz2 /usr/share/man/man3/AUTHORITY_KEYID_free.3ossl.bz2 /usr/share/man/man3/AUTHORITY_KEYID_new.3ossl.bz2 /usr/share/man/man3/BASIC_CONSTRAINTS_free.3ossl.bz2 /usr/share/man/man3/BASIC_CONSTRAINTS_new.3ossl.bz2 /usr/share/man/man3/BF_cbc_encrypt.3ossl.bz2 /usr/share/man/man3/BF_cfb64_encrypt.3ossl.bz2 /usr/share/man/man3/BF_decrypt.3ossl.bz2 /usr/share/man/man3/BF_ecb_encrypt.3ossl.bz2 /usr/share/man/man3/BF_encrypt.3ossl.bz2 /usr/share/man/man3/BF_ofb64_encrypt.3ossl.bz2 /usr/share/man/man3/BF_options.3ossl.bz2 /usr/share/man/man3/BF_set_key.3ossl.bz2
    /usr/share/man/man3/BIO_ADDR.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO_address.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO_family.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO_free.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO_next.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO_protocol.3ossl.bz2 /usr/share/man/man3/BIO_ADDRINFO_socktype.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_clear.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_copy.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_dup.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_family.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_free.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_hostname_string.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_new.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_path_string.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_rawaddress.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_rawmake.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_rawport.3ossl.bz2 /usr/share/man/man3/BIO_ADDR_service_string.3ossl.bz2 /usr/share/man/man3/BIO_accept_ex.3ossl.bz2 /usr/share/man/man3/BIO_append_filename.3ossl.bz2 /usr/share/man/man3/BIO_bind.3ossl.bz2 /usr/share/man/man3/BIO_callback_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_callback_fn.3ossl.bz2 /usr/share/man/man3/BIO_callback_fn_ex.3ossl.bz2 /usr/share/man/man3/BIO_clear_flags.3ossl.bz2 /usr/share/man/man3/BIO_clear_retry_flags.3ossl.bz2 /usr/share/man/man3/BIO_closesocket.3ossl.bz2 /usr/share/man/man3/BIO_connect.3ossl.bz2 /usr/share/man/man3/BIO_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_dgram_connect.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_get_read_request.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_get_write_guarantee.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_pending.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_reset_read_request.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_set_connected.3ossl.bz2 /usr/share/man/man3/BIO_ctrl_wpending.3ossl.bz2 /usr/share/man/man3/BIO_debug_callback.3ossl.bz2 /usr/share/man/man3/BIO_debug_callback_ex.3ossl.bz2 /usr/share/man/man3/BIO_destroy_bio_pair.3ossl.bz2 /usr/share/man/man3/BIO_dgram_detect_peer_addr.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_caps.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_effective_caps.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_local_addr_cap.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_local_addr_enable.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_mtu.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_mtu_overhead.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_no_trunc.3ossl.bz2 /usr/share/man/man3/BIO_dgram_get_peer.3ossl.bz2 /usr/share/man/man3/BIO_dgram_recv_timedout.3ossl.bz2 /usr/share/man/man3/BIO_dgram_send_timedout.3ossl.bz2 /usr/share/man/man3/BIO_dgram_set0_local_addr.3ossl.bz2 /usr/share/man/man3/BIO_dgram_set_caps.3ossl.bz2 /usr/share/man/man3/BIO_dgram_set_local_addr_enable.3ossl.bz2 /usr/share/man/man3/BIO_dgram_set_mtu.3ossl.bz2 /usr/share/man/man3/BIO_dgram_set_no_trunc.3ossl.bz2 /usr/share/man/man3/BIO_dgram_set_peer.3ossl.bz2 /usr/share/man/man3/BIO_do_accept.3ossl.bz2 /usr/share/man/man3/BIO_do_connect.3ossl.bz2 /usr/share/man/man3/BIO_do_connect_retry.3ossl.bz2 /usr/share/man/man3/BIO_do_handshake.3ossl.bz2 /usr/share/man/man3/BIO_eof.3ossl.bz2 /usr/share/man/man3/BIO_err_is_non_fatal.3ossl.bz2 /usr/share/man/man3/BIO_f_base64.3ossl.bz2 /usr/share/man/man3/BIO_f_brotli.3ossl.bz2 /usr/share/man/man3/BIO_f_buffer.3ossl.bz2 /usr/share/man/man3/BIO_f_cipher.3ossl.bz2 /usr/share/man/man3/BIO_f_md.3ossl.bz2
    /usr/share/man/man3/BIO_f_null.3ossl.bz2 /usr/share/man/man3/BIO_f_prefix.3ossl.bz2 /usr/share/man/man3/BIO_f_readbuffer.3ossl.bz2 /usr/share/man/man3/BIO_f_ssl.3ossl.bz2 /usr/share/man/man3/BIO_f_zlib.3ossl.bz2 /usr/share/man/man3/BIO_f_zstd.3ossl.bz2 /usr/share/man/man3/BIO_find_type.3ossl.bz2 /usr/share/man/man3/BIO_flush.3ossl.bz2
    /usr/share/man/man3/BIO_free.3ossl.bz2 /usr/share/man/man3/BIO_free_all.3ossl.bz2 /usr/share/man/man3/BIO_get0_dgram_bio.3ossl.bz2 /usr/share/man/man3/BIO_get_accept_ip_family.3ossl.bz2 /usr/share/man/man3/BIO_get_accept_name.3ossl.bz2 /usr/share/man/man3/BIO_get_accept_port.3ossl.bz2 /usr/share/man/man3/BIO_get_app_data.3ossl.bz2 /usr/share/man/man3/BIO_get_bind_mode.3ossl.bz2 /usr/share/man/man3/BIO_get_buffer_num_lines.3ossl.bz2 /usr/share/man/man3/BIO_get_callback.3ossl.bz2 /usr/share/man/man3/BIO_get_callback_arg.3ossl.bz2 /usr/share/man/man3/BIO_get_callback_ex.3ossl.bz2 /usr/share/man/man3/BIO_get_cipher_ctx.3ossl.bz2 /usr/share/man/man3/BIO_get_cipher_status.3ossl.bz2 /usr/share/man/man3/BIO_get_close.3ossl.bz2 /usr/share/man/man3/BIO_get_conn_address.3ossl.bz2 /usr/share/man/man3/BIO_get_conn_hostname.3ossl.bz2 /usr/share/man/man3/BIO_get_conn_ip_family.3ossl.bz2 /usr/share/man/man3/BIO_get_conn_mode.3ossl.bz2 /usr/share/man/man3/BIO_get_conn_port.3ossl.bz2 /usr/share/man/man3/BIO_get_data.3ossl.bz2 /usr/share/man/man3/BIO_get_ex_data.3ossl.bz2 /usr/share/man/man3/BIO_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/BIO_get_fd.3ossl.bz2 /usr/share/man/man3/BIO_get_flags.3ossl.bz2 /usr/share/man/man3/BIO_get_fp.3ossl.bz2 /usr/share/man/man3/BIO_get_indent.3ossl.bz2 /usr/share/man/man3/BIO_get_info_callback.3ossl.bz2 /usr/share/man/man3/BIO_get_init.3ossl.bz2 /usr/share/man/man3/BIO_get_ktls_recv.3ossl.bz2 /usr/share/man/man3/BIO_get_ktls_send.3ossl.bz2 /usr/share/man/man3/BIO_get_line.3ossl.bz2 /usr/share/man/man3/BIO_get_md.3ossl.bz2 /usr/share/man/man3/BIO_get_md_ctx.3ossl.bz2 /usr/share/man/man3/BIO_get_mem_data.3ossl.bz2 /usr/share/man/man3/BIO_get_mem_ptr.3ossl.bz2 /usr/share/man/man3/BIO_get_new_index.3ossl.bz2 /usr/share/man/man3/BIO_get_num_renegotiates.3ossl.bz2 /usr/share/man/man3/BIO_get_peer_name.3ossl.bz2 /usr/share/man/man3/BIO_get_peer_port.3ossl.bz2 /usr/share/man/man3/BIO_get_read_request.3ossl.bz2 /usr/share/man/man3/BIO_get_retry_BIO.3ossl.bz2 /usr/share/man/man3/BIO_get_retry_flags.3ossl.bz2 /usr/share/man/man3/BIO_get_retry_reason.3ossl.bz2 /usr/share/man/man3/BIO_get_rpoll_descriptor.3ossl.bz2 /usr/share/man/man3/BIO_get_shutdown.3ossl.bz2 /usr/share/man/man3/BIO_get_sock_type.3ossl.bz2 /usr/share/man/man3/BIO_get_ssl.3ossl.bz2 /usr/share/man/man3/BIO_get_wpoll_descriptor.3ossl.bz2 /usr/share/man/man3/BIO_get_write_buf_size.3ossl.bz2 /usr/share/man/man3/BIO_get_write_guarantee.3ossl.bz2 /usr/share/man/man3/BIO_gets.3ossl.bz2 /usr/share/man/man3/BIO_hostserv_priorities.3ossl.bz2 /usr/share/man/man3/BIO_info_cb.3ossl.bz2 /usr/share/man/man3/BIO_int_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_listen.3ossl.bz2 /usr/share/man/man3/BIO_lookup.3ossl.bz2 /usr/share/man/man3/BIO_lookup_ex.3ossl.bz2 /usr/share/man/man3/BIO_lookup_type.3ossl.bz2 /usr/share/man/man3/BIO_make_bio_pair.3ossl.bz2 /usr/share/man/man3/BIO_meth_free.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_callback_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_create.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_destroy.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_gets.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_puts.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_read.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_read_ex.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_recvmmsg.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_sendmmsg.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_write.3ossl.bz2 /usr/share/man/man3/BIO_meth_get_write_ex.3ossl.bz2 /usr/share/man/man3/BIO_meth_new.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_callback_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_create.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_destroy.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_gets.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_puts.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_read.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_read_ex.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_recvmmsg.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_sendmmsg.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_write.3ossl.bz2 /usr/share/man/man3/BIO_meth_set_write_ex.3ossl.bz2 /usr/share/man/man3/BIO_method_type.3ossl.bz2 /usr/share/man/man3/BIO_new.3ossl.bz2
    /usr/share/man/man3/BIO_new_CMS.3ossl.bz2 /usr/share/man/man3/BIO_new_accept.3ossl.bz2 /usr/share/man/man3/BIO_new_bio_dgram_pair.3ossl.bz2 /usr/share/man/man3/BIO_new_bio_pair.3ossl.bz2 /usr/share/man/man3/BIO_new_buffer_ssl_connect.3ossl.bz2 /usr/share/man/man3/BIO_new_connect.3ossl.bz2 /usr/share/man/man3/BIO_new_dgram.3ossl.bz2 /usr/share/man/man3/BIO_new_ex.3ossl.bz2 /usr/share/man/man3/BIO_new_fd.3ossl.bz2 /usr/share/man/man3/BIO_new_file.3ossl.bz2 /usr/share/man/man3/BIO_new_fp.3ossl.bz2 /usr/share/man/man3/BIO_new_from_core_bio.3ossl.bz2 /usr/share/man/man3/BIO_new_mem_buf.3ossl.bz2 /usr/share/man/man3/BIO_new_socket.3ossl.bz2 /usr/share/man/man3/BIO_new_ssl.3ossl.bz2 /usr/share/man/man3/BIO_new_ssl_connect.3ossl.bz2 /usr/share/man/man3/BIO_next.3ossl.bz2
    /usr/share/man/man3/BIO_nread.3ossl.bz2 /usr/share/man/man3/BIO_nread0.3ossl.bz2 /usr/share/man/man3/BIO_nwrite.3ossl.bz2 /usr/share/man/man3/BIO_nwrite0.3ossl.bz2 /usr/share/man/man3/BIO_parse_hostserv.3ossl.bz2 /usr/share/man/man3/BIO_pending.3ossl.bz2
    /usr/share/man/man3/BIO_pop.3ossl.bz2
    /usr/share/man/man3/BIO_printf.3ossl.bz2 /usr/share/man/man3/BIO_ptr_ctrl.3ossl.bz2 /usr/share/man/man3/BIO_push.3ossl.bz2
    /usr/share/man/man3/BIO_puts.3ossl.bz2
    /usr/share/man/man3/BIO_read.3ossl.bz2 /usr/share/man/man3/BIO_read_ex.3ossl.bz2 /usr/share/man/man3/BIO_read_filename.3ossl.bz2 /usr/share/man/man3/BIO_recvmmsg.3ossl.bz2 /usr/share/man/man3/BIO_reset.3ossl.bz2 /usr/share/man/man3/BIO_retry_type.3ossl.bz2 /usr/share/man/man3/BIO_rw_filename.3ossl.bz2 /usr/share/man/man3/BIO_s_accept.3ossl.bz2 /usr/share/man/man3/BIO_s_bio.3ossl.bz2 /usr/share/man/man3/BIO_s_connect.3ossl.bz2 /usr/share/man/man3/BIO_s_core.3ossl.bz2 /usr/share/man/man3/BIO_s_datagram.3ossl.bz2 /usr/share/man/man3/BIO_s_dgram_mem.3ossl.bz2 /usr/share/man/man3/BIO_s_dgram_pair.3ossl.bz2 /usr/share/man/man3/BIO_s_fd.3ossl.bz2
    /usr/share/man/man3/BIO_s_file.3ossl.bz2 /usr/share/man/man3/BIO_s_mem.3ossl.bz2 /usr/share/man/man3/BIO_s_null.3ossl.bz2 /usr/share/man/man3/BIO_s_secmem.3ossl.bz2 /usr/share/man/man3/BIO_s_socket.3ossl.bz2 /usr/share/man/man3/BIO_seek.3ossl.bz2 /usr/share/man/man3/BIO_sendmmsg.3ossl.bz2 /usr/share/man/man3/BIO_set_accept_bios.3ossl.bz2 /usr/share/man/man3/BIO_set_accept_ip_family.3ossl.bz2 /usr/share/man/man3/BIO_set_accept_name.3ossl.bz2 /usr/share/man/man3/BIO_set_accept_port.3ossl.bz2 /usr/share/man/man3/BIO_set_app_data.3ossl.bz2 /usr/share/man/man3/BIO_set_bind_mode.3ossl.bz2 /usr/share/man/man3/BIO_set_buffer_read_data.3ossl.bz2 /usr/share/man/man3/BIO_set_buffer_size.3ossl.bz2 /usr/share/man/man3/BIO_set_callback.3ossl.bz2 /usr/share/man/man3/BIO_set_callback_arg.3ossl.bz2 /usr/share/man/man3/BIO_set_callback_ex.3ossl.bz2 /usr/share/man/man3/BIO_set_cipher.3ossl.bz2 /usr/share/man/man3/BIO_set_close.3ossl.bz2 /usr/share/man/man3/BIO_set_conn_address.3ossl.bz2 /usr/share/man/man3/BIO_set_conn_hostname.3ossl.bz2 /usr/share/man/man3/BIO_set_conn_ip_family.3ossl.bz2 /usr/share/man/man3/BIO_set_conn_mode.3ossl.bz2 /usr/share/man/man3/BIO_set_conn_port.3ossl.bz2 /usr/share/man/man3/BIO_set_data.3ossl.bz2 /usr/share/man/man3/BIO_set_ex_data.3ossl.bz2 /usr/share/man/man3/BIO_set_fd.3ossl.bz2 /usr/share/man/man3/BIO_set_flags.3ossl.bz2 /usr/share/man/man3/BIO_set_fp.3ossl.bz2 /usr/share/man/man3/BIO_set_indent.3ossl.bz2 /usr/share/man/man3/BIO_set_info_callback.3ossl.bz2 /usr/share/man/man3/BIO_set_init.3ossl.bz2 /usr/share/man/man3/BIO_set_md.3ossl.bz2 /usr/share/man/man3/BIO_set_mem_buf.3ossl.bz2 /usr/share/man/man3/BIO_set_mem_eof_return.3ossl.bz2 /usr/share/man/man3/BIO_set_nbio.3ossl.bz2 /usr/share/man/man3/BIO_set_nbio_accept.3ossl.bz2 /usr/share/man/man3/BIO_set_next.3ossl.bz2 /usr/share/man/man3/BIO_set_prefix.3ossl.bz2 /usr/share/man/man3/BIO_set_read_buffer_size.3ossl.bz2 /usr/share/man/man3/BIO_set_retry_read.3ossl.bz2 /usr/share/man/man3/BIO_set_retry_reason.3ossl.bz2 /usr/share/man/man3/BIO_set_retry_special.3ossl.bz2 /usr/share/man/man3/BIO_set_retry_write.3ossl.bz2 /usr/share/man/man3/BIO_set_shutdown.3ossl.bz2 /usr/share/man/man3/BIO_set_sock_type.3ossl.bz2 /usr/share/man/man3/BIO_set_ssl.3ossl.bz2 /usr/share/man/man3/BIO_set_ssl_mode.3ossl.bz2 /usr/share/man/man3/BIO_set_ssl_renegotiate_bytes.3ossl.bz2 /usr/share/man/man3/BIO_set_ssl_renegotiate_timeout.3ossl.bz2 /usr/share/man/man3/BIO_set_tfo.3ossl.bz2 /usr/share/man/man3/BIO_set_tfo_accept.3ossl.bz2 /usr/share/man/man3/BIO_set_write_buf_size.3ossl.bz2 /usr/share/man/man3/BIO_set_write_buffer_size.3ossl.bz2 /usr/share/man/man3/BIO_should_io_special.3ossl.bz2 /usr/share/man/man3/BIO_should_read.3ossl.bz2 /usr/share/man/man3/BIO_should_retry.3ossl.bz2 /usr/share/man/man3/BIO_should_write.3ossl.bz2 /usr/share/man/man3/BIO_shutdown_wr.3ossl.bz2 /usr/share/man/man3/BIO_snprintf.3ossl.bz2 /usr/share/man/man3/BIO_socket.3ossl.bz2 /usr/share/man/man3/BIO_socket_wait.3ossl.bz2 /usr/share/man/man3/BIO_ssl_copy_session_id.3ossl.bz2 /usr/share/man/man3/BIO_ssl_shutdown.3ossl.bz2 /usr/share/man/man3/BIO_tell.3ossl.bz2 /usr/share/man/man3/BIO_test_flags.3ossl.bz2 /usr/share/man/man3/BIO_up_ref.3ossl.bz2 /usr/share/man/man3/BIO_vfree.3ossl.bz2 /usr/share/man/man3/BIO_vprintf.3ossl.bz2 /usr/share/man/man3/BIO_vsnprintf.3ossl.bz2 /usr/share/man/man3/BIO_wait.3ossl.bz2 /usr/share/man/man3/BIO_wpending.3ossl.bz2 /usr/share/man/man3/BIO_write.3ossl.bz2 /usr/share/man/man3/BIO_write_ex.3ossl.bz2 /usr/share/man/man3/BIO_write_filename.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_convert.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_convert_ex.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_create_param.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_free.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_get_flags.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_invert.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_invert_ex.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_is_current_thread.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_lock.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_new.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_set_current_thread.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_set_flags.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_unlock.3ossl.bz2 /usr/share/man/man3/BN_BLINDING_update.3ossl.bz2 /usr/share/man/man3/BN_CTX_end.3ossl.bz2 /usr/share/man/man3/BN_CTX_free.3ossl.bz2 /usr/share/man/man3/BN_CTX_get.3ossl.bz2 /usr/share/man/man3/BN_CTX_new.3ossl.bz2 /usr/share/man/man3/BN_CTX_new_ex.3ossl.bz2 /usr/share/man/man3/BN_CTX_secure_new.3ossl.bz2 /usr/share/man/man3/BN_CTX_secure_new_ex.3ossl.bz2 /usr/share/man/man3/BN_CTX_start.3ossl.bz2 /usr/share/man/man3/BN_GENCB_call.3ossl.bz2 /usr/share/man/man3/BN_GENCB_free.3ossl.bz2 /usr/share/man/man3/BN_GENCB_get_arg.3ossl.bz2 /usr/share/man/man3/BN_GENCB_new.3ossl.bz2 /usr/share/man/man3/BN_GENCB_set.3ossl.bz2 /usr/share/man/man3/BN_GENCB_set_old.3ossl.bz2 /usr/share/man/man3/BN_MONT_CTX_copy.3ossl.bz2 /usr/share/man/man3/BN_MONT_CTX_free.3ossl.bz2 /usr/share/man/man3/BN_MONT_CTX_new.3ossl.bz2 /usr/share/man/man3/BN_MONT_CTX_set.3ossl.bz2 /usr/share/man/man3/BN_RECP_CTX_free.3ossl.bz2 /usr/share/man/man3/BN_RECP_CTX_new.3ossl.bz2 /usr/share/man/man3/BN_RECP_CTX_set.3ossl.bz2 /usr/share/man/man3/BN_abs_is_word.3ossl.bz2 /usr/share/man/man3/BN_add.3ossl.bz2
    /usr/share/man/man3/BN_add_word.3ossl.bz2 /usr/share/man/man3/BN_are_coprime.3ossl.bz2 /usr/share/man/man3/BN_bin2bn.3ossl.bz2
    /usr/share/man/man3/BN_bn2bin.3ossl.bz2 /usr/share/man/man3/BN_bn2binpad.3ossl.bz2 /usr/share/man/man3/BN_bn2dec.3ossl.bz2
    /usr/share/man/man3/BN_bn2hex.3ossl.bz2 /usr/share/man/man3/BN_bn2lebinpad.3ossl.bz2 /usr/share/man/man3/BN_bn2mpi.3ossl.bz2 /usr/share/man/man3/BN_bn2nativepad.3ossl.bz2 /usr/share/man/man3/BN_check_prime.3ossl.bz2 /usr/share/man/man3/BN_clear.3ossl.bz2 /usr/share/man/man3/BN_clear_bit.3ossl.bz2 /usr/share/man/man3/BN_clear_free.3ossl.bz2 /usr/share/man/man3/BN_cmp.3ossl.bz2
    /usr/share/man/man3/BN_copy.3ossl.bz2
    /usr/share/man/man3/BN_dec2bn.3ossl.bz2
    /usr/share/man/man3/BN_div.3ossl.bz2
    /usr/share/man/man3/BN_div_recp.3ossl.bz2 /usr/share/man/man3/BN_div_word.3ossl.bz2
    /usr/share/man/man3/BN_dup.3ossl.bz2
    /usr/share/man/man3/BN_exp.3ossl.bz2
    /usr/share/man/man3/BN_free.3ossl.bz2 /usr/share/man/man3/BN_from_montgomery.3ossl.bz2 /usr/share/man/man3/BN_gcd.3ossl.bz2 /usr/share/man/man3/BN_generate_prime.3ossl.bz2 /usr/share/man/man3/BN_generate_prime_ex.3ossl.bz2 /usr/share/man/man3/BN_generate_prime_ex2.3ossl.bz2 /usr/share/man/man3/BN_get0_nist_prime_192.3ossl.bz2 /usr/share/man/man3/BN_get0_nist_prime_224.3ossl.bz2 /usr/share/man/man3/BN_get0_nist_prime_256.3ossl.bz2 /usr/share/man/man3/BN_get0_nist_prime_384.3ossl.bz2 /usr/share/man/man3/BN_get0_nist_prime_521.3ossl.bz2 /usr/share/man/man3/BN_get_rfc2409_prime_1024.3ossl.bz2 /usr/share/man/man3/BN_get_rfc2409_prime_768.3ossl.bz2 /usr/share/man/man3/BN_get_rfc3526_prime_1536.3ossl.bz2 /usr/share/man/man3/BN_get_rfc3526_prime_2048.3ossl.bz2 /usr/share/man/man3/BN_get_rfc3526_prime_3072.3ossl.bz2 /usr/share/man/man3/BN_get_rfc3526_prime_4096.3ossl.bz2 /usr/share/man/man3/BN_get_rfc3526_prime_6144.3ossl.bz2 /usr/share/man/man3/BN_get_rfc3526_prime_8192.3ossl.bz2 /usr/share/man/man3/BN_get_word.3ossl.bz2 /usr/share/man/man3/BN_hex2bn.3ossl.bz2 /usr/share/man/man3/BN_is_bit_set.3ossl.bz2 /usr/share/man/man3/BN_is_odd.3ossl.bz2
    /usr/share/man/man3/BN_is_one.3ossl.bz2 /usr/share/man/man3/BN_is_prime.3ossl.bz2 /usr/share/man/man3/BN_is_prime_ex.3ossl.bz2 /usr/share/man/man3/BN_is_prime_fasttest.3ossl.bz2 /usr/share/man/man3/BN_is_prime_fasttest_ex.3ossl.bz2 /usr/share/man/man3/BN_is_word.3ossl.bz2 /usr/share/man/man3/BN_is_zero.3ossl.bz2 /usr/share/man/man3/BN_lebin2bn.3ossl.bz2 /usr/share/man/man3/BN_lshift.3ossl.bz2 /usr/share/man/man3/BN_lshift1.3ossl.bz2 /usr/share/man/man3/BN_mask_bits.3ossl.bz2
    /usr/share/man/man3/BN_mod.3ossl.bz2
    /usr/share/man/man3/BN_mod_add.3ossl.bz2 /usr/share/man/man3/BN_mod_exp.3ossl.bz2 /usr/share/man/man3/BN_mod_exp_mont.3ossl.bz2 /usr/share/man/man3/BN_mod_exp_mont_consttime.3ossl.bz2 /usr/share/man/man3/BN_mod_exp_mont_consttime_x2.3ossl.bz2 /usr/share/man/man3/BN_mod_inverse.3ossl.bz2 /usr/share/man/man3/BN_mod_mul.3ossl.bz2 /usr/share/man/man3/BN_mod_mul_montgomery.3ossl.bz2 /usr/share/man/man3/BN_mod_mul_reciprocal.3ossl.bz2 /usr/share/man/man3/BN_mod_sqr.3ossl.bz2 /usr/share/man/man3/BN_mod_sqrt.3ossl.bz2 /usr/share/man/man3/BN_mod_sub.3ossl.bz2 /usr/share/man/man3/BN_mod_word.3ossl.bz2 /usr/share/man/man3/BN_mpi2bn.3ossl.bz2
    /usr/share/man/man3/BN_mul.3ossl.bz2
    /usr/share/man/man3/BN_mul_word.3ossl.bz2 /usr/share/man/man3/BN_native2bn.3ossl.bz2
    /usr/share/man/man3/BN_new.3ossl.bz2
    /usr/share/man/man3/BN_nnmod.3ossl.bz2 /usr/share/man/man3/BN_num_bits.3ossl.bz2 /usr/share/man/man3/BN_num_bits_word.3ossl.bz2 /usr/share/man/man3/BN_num_bytes.3ossl.bz2
    /usr/share/man/man3/BN_one.3ossl.bz2
    /usr/share/man/man3/BN_print.3ossl.bz2 /usr/share/man/man3/BN_print_fp.3ossl.bz2 /usr/share/man/man3/BN_priv_rand.3ossl.bz2 /usr/share/man/man3/BN_priv_rand_ex.3ossl.bz2 /usr/share/man/man3/BN_priv_rand_range.3ossl.bz2 /usr/share/man/man3/BN_priv_rand_range_ex.3ossl.bz2 /usr/share/man/man3/BN_pseudo_rand.3ossl.bz2 /usr/share/man/man3/BN_pseudo_rand_range.3ossl.bz2 /usr/share/man/man3/BN_rand.3ossl.bz2
    /usr/share/man/man3/BN_rand_ex.3ossl.bz2 /usr/share/man/man3/BN_rand_range.3ossl.bz2 /usr/share/man/man3/BN_rand_range_ex.3ossl.bz2 /usr/share/man/man3/BN_rshift.3ossl.bz2 /usr/share/man/man3/BN_rshift1.3ossl.bz2 /usr/share/man/man3/BN_secure_new.3ossl.bz2 /usr/share/man/man3/BN_security_bits.3ossl.bz2 /usr/share/man/man3/BN_set_bit.3ossl.bz2 /usr/share/man/man3/BN_set_word.3ossl.bz2 /usr/share/man/man3/BN_signed_bin2bn.3ossl.bz2 /usr/share/man/man3/BN_signed_bn2bin.3ossl.bz2 /usr/share/man/man3/BN_signed_bn2lebin.3ossl.bz2 /usr/share/man/man3/BN_signed_bn2native.3ossl.bz2 /usr/share/man/man3/BN_signed_lebin2bn.3ossl.bz2 /usr/share/man/man3/BN_signed_native2bn.3ossl.bz2 /usr/share/man/man3/BN_sqr.3ossl.bz2
    /usr/share/man/man3/BN_sub.3ossl.bz2
    /usr/share/man/man3/BN_sub_word.3ossl.bz2
    /usr/share/man/man3/BN_swap.3ossl.bz2 /usr/share/man/man3/BN_to_ASN1_ENUMERATED.3ossl.bz2 /usr/share/man/man3/BN_to_ASN1_INTEGER.3ossl.bz2 /usr/share/man/man3/BN_to_montgomery.3ossl.bz2 /usr/share/man/man3/BN_ucmp.3ossl.bz2 /usr/share/man/man3/BN_value_one.3ossl.bz2 /usr/share/man/man3/BN_with_flags.3ossl.bz2 /usr/share/man/man3/BN_zero.3ossl.bz2 /usr/share/man/man3/BUF_MEM_free.3ossl.bz2 /usr/share/man/man3/BUF_MEM_grow.3ossl.bz2 /usr/share/man/man3/BUF_MEM_grow_clean.3ossl.bz2 /usr/share/man/man3/BUF_MEM_new.3ossl.bz2 /usr/share/man/man3/BUF_MEM_new_ex.3ossl.bz2 /usr/share/man/man3/BUF_reverse.3ossl.bz2 /usr/share/man/man3/CERTIFICATEPOLICIES_free.3ossl.bz2 /usr/share/man/man3/CERTIFICATEPOLICIES_new.3ossl.bz2 /usr/share/man/man3/CMAC_CTX.3ossl.bz2 /usr/share/man/man3/CMAC_CTX_cleanup.3ossl.bz2 /usr/share/man/man3/CMAC_CTX_copy.3ossl.bz2 /usr/share/man/man3/CMAC_CTX_free.3ossl.bz2 /usr/share/man/man3/CMAC_CTX_get0_cipher_ctx.3ossl.bz2 /usr/share/man/man3/CMAC_CTX_new.3ossl.bz2 /usr/share/man/man3/CMAC_Final.3ossl.bz2 /usr/share/man/man3/CMAC_Init.3ossl.bz2 /usr/share/man/man3/CMAC_Update.3ossl.bz2 /usr/share/man/man3/CMAC_resume.3ossl.bz2 /usr/share/man/man3/CMS_AuthEnvelopedData_create.3ossl.bz2 /usr/share/man/man3/CMS_AuthEnvelopedData_create_ex.3ossl.bz2 /usr/share/man/man3/CMS_ContentInfo_free.3ossl.bz2 /usr/share/man/man3/CMS_ContentInfo_new.3ossl.bz2 /usr/share/man/man3/CMS_ContentInfo_new_ex.3ossl.bz2 /usr/share/man/man3/CMS_ContentInfo_print_ctx.3ossl.bz2 /usr/share/man/man3/CMS_EncryptedData_decrypt.3ossl.bz2 /usr/share/man/man3/CMS_EncryptedData_encrypt.3ossl.bz2 /usr/share/man/man3/CMS_EncryptedData_encrypt_ex.3ossl.bz2 /usr/share/man/man3/CMS_EncryptedData_set1_key.3ossl.bz2 /usr/share/man/man3/CMS_EnvelopedData_create.3ossl.bz2 /usr/share/man/man3/CMS_EnvelopedData_create_ex.3ossl.bz2 /usr/share/man/man3/CMS_EnvelopedData_decrypt.3ossl.bz2 /usr/share/man/man3/CMS_EnvelopedData_dup.3ossl.bz2 /usr/share/man/man3/CMS_EnvelopedData_it.3ossl.bz2 /usr/share/man/man3/CMS_ReceiptRequest_create0.3ossl.bz2 /usr/share/man/man3/CMS_ReceiptRequest_create0_ex.3ossl.bz2 /usr/share/man/man3/CMS_ReceiptRequest_free.3ossl.bz2 /usr/share/man/man3/CMS_ReceiptRequest_get0_values.3ossl.bz2 /usr/share/man/man3/CMS_ReceiptRequest_new.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_decrypt.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_encrypt.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kari_get0_ctx.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kari_set0_pkey.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kari_set0_pkey_and_peer.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kekri_get0_id.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kekri_id_cmp.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kemri_cert_cmp.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kemri_get0_ctx.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kemri_get0_kdf_alg.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kemri_set0_pkey.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_kemri_set_ukm.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_ktri_cert_cmp.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_ktri_get0_signer_id.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_set0_key.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_set0_pkey.3ossl.bz2 /usr/share/man/man3/CMS_RecipientInfo_type.3ossl.bz2 /usr/share/man/man3/CMS_SignedData_free.3ossl.bz2 /usr/share/man/man3/CMS_SignedData_new.3ossl.bz2 /usr/share/man/man3/CMS_SignedData_verify.3ossl.bz2 /usr/share/man/man3/CMS_SignerInfo_cert_cmp.3ossl.bz2 /usr/share/man/man3/CMS_SignerInfo_get0_signature.3ossl.bz2 /usr/share/man/man3/CMS_SignerInfo_get0_signer_id.3ossl.bz2 /usr/share/man/man3/CMS_SignerInfo_set1_signer_cert.3ossl.bz2 /usr/share/man/man3/CMS_SignerInfo_sign.3ossl.bz2 /usr/share/man/man3/CMS_add0_cert.3ossl.bz2 /usr/share/man/man3/CMS_add0_crl.3ossl.bz2 /usr/share/man/man3/CMS_add0_recipient_key.3ossl.bz2 /usr/share/man/man3/CMS_add1_ReceiptRequest.3ossl.bz2 /usr/share/man/man3/CMS_add1_cert.3ossl.bz2 /usr/share/man/man3/CMS_add1_crl.3ossl.bz2 /usr/share/man/man3/CMS_add1_recipient.3ossl.bz2 /usr/share/man/man3/CMS_add1_recipient_cert.3ossl.bz2 /usr/share/man/man3/CMS_add1_signer.3ossl.bz2 /usr/share/man/man3/CMS_compress.3ossl.bz2 /usr/share/man/man3/CMS_data_create.3ossl.bz2 /usr/share/man/man3/CMS_data_create_ex.3ossl.bz2 /usr/share/man/man3/CMS_decrypt.3ossl.bz2 /usr/share/man/man3/CMS_decrypt_set1_password.3ossl.bz2 /usr/share/man/man3/CMS_decrypt_set1_pkey.3ossl.bz2 /usr/share/man/man3/CMS_decrypt_set1_pkey_and_peer.3ossl.bz2 /usr/share/man/man3/CMS_digest_create.3ossl.bz2 /usr/share/man/man3/CMS_digest_create_ex.3ossl.bz2 /usr/share/man/man3/CMS_encrypt.3ossl.bz2 /usr/share/man/man3/CMS_encrypt_ex.3ossl.bz2 /usr/share/man/man3/CMS_final.3ossl.bz2 /usr/share/man/man3/CMS_final_digest.3ossl.bz2 /usr/share/man/man3/CMS_get0_RecipientInfos.3ossl.bz2 /usr/share/man/man3/CMS_get0_SignerInfos.3ossl.bz2 /usr/share/man/man3/CMS_get0_content.3ossl.bz2 /usr/share/man/man3/CMS_get0_eContentType.3ossl.bz2 /usr/share/man/man3/CMS_get0_signers.3ossl.bz2 /usr/share/man/man3/CMS_get0_type.3ossl.bz2 /usr/share/man/man3/CMS_get1_ReceiptRequest.3ossl.bz2 /usr/share/man/man3/CMS_get1_certs.3ossl.bz2 /usr/share/man/man3/CMS_get1_crls.3ossl.bz2 /usr/share/man/man3/CMS_set1_eContentType.3ossl.bz2 /usr/share/man/man3/CMS_sign.3ossl.bz2 /usr/share/man/man3/CMS_sign_ex.3ossl.bz2 /usr/share/man/man3/CMS_sign_receipt.3ossl.bz2 /usr/share/man/man3/CMS_signed_add1_attr.3ossl.bz2 /usr/share/man/man3/CMS_signed_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/CMS_signed_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/CMS_signed_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/CMS_signed_delete_attr.3ossl.bz2 /usr/share/man/man3/CMS_signed_get0_data_by_OBJ.3ossl.bz2 /usr/share/man/man3/CMS_signed_get_attr.3ossl.bz2 /usr/share/man/man3/CMS_signed_get_attr_by_NID.3ossl.bz2 /usr/share/man/man3/CMS_signed_get_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/CMS_signed_get_attr_count.3ossl.bz2 /usr/share/man/man3/CMS_uncompress.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_add1_attr.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_delete_attr.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_get0_data_by_OBJ.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_get_attr.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_get_attr_by_NID.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_get_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/CMS_unsigned_get_attr_count.3ossl.bz2 /usr/share/man/man3/CMS_verify.3ossl.bz2 /usr/share/man/man3/CMS_verify_receipt.3ossl.bz2 /usr/share/man/man3/COMP_CTX_free.3ossl.bz2 /usr/share/man/man3/COMP_CTX_get_method.3ossl.bz2 /usr/share/man/man3/COMP_CTX_get_type.3ossl.bz2 /usr/share/man/man3/COMP_CTX_new.3ossl.bz2 /usr/share/man/man3/COMP_brotli.3ossl.bz2 /usr/share/man/man3/COMP_brotli_oneshot.3ossl.bz2 /usr/share/man/man3/COMP_compress_block.3ossl.bz2 /usr/share/man/man3/COMP_expand_block.3ossl.bz2 /usr/share/man/man3/COMP_get_name.3ossl.bz2 /usr/share/man/man3/COMP_get_type.3ossl.bz2 /usr/share/man/man3/COMP_zlib.3ossl.bz2 /usr/share/man/man3/COMP_zlib_oneshot.3ossl.bz2 /usr/share/man/man3/COMP_zstd.3ossl.bz2 /usr/share/man/man3/COMP_zstd_oneshot.3ossl.bz2 /usr/share/man/man3/CONF_get1_default_config_file.3ossl.bz2 /usr/share/man/man3/CONF_modules_finish.3ossl.bz2 /usr/share/man/man3/CONF_modules_free.3ossl.bz2 /usr/share/man/man3/CONF_modules_load.3ossl.bz2 /usr/share/man/man3/CONF_modules_load_file.3ossl.bz2 /usr/share/man/man3/CONF_modules_load_file_ex.3ossl.bz2 /usr/share/man/man3/CONF_modules_unload.3ossl.bz2 /usr/share/man/man3/CRL_DIST_POINTS_free.3ossl.bz2 /usr/share/man/man3/CRL_DIST_POINTS_new.3ossl.bz2 /usr/share/man/man3/CRYPTO_EX_dup.3ossl.bz2 /usr/share/man/man3/CRYPTO_EX_free.3ossl.bz2 /usr/share/man/man3/CRYPTO_EX_new.3ossl.bz2 /usr/share/man/man3/CRYPTO_THREAD_lock_free.3ossl.bz2 /usr/share/man/man3/CRYPTO_THREAD_lock_new.3ossl.bz2 /usr/share/man/man3/CRYPTO_THREAD_read_lock.3ossl.bz2 /usr/share/man/man3/CRYPTO_THREAD_run_once.3ossl.bz2 /usr/share/man/man3/CRYPTO_THREAD_unlock.3ossl.bz2 /usr/share/man/man3/CRYPTO_THREAD_write_lock.3ossl.bz2 /usr/share/man/man3/CRYPTO_aligned_alloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_aligned_alloc_array.3ossl.bz2 /usr/share/man/man3/CRYPTO_alloc_ex_data.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_add.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_add64.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_and.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_load.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_load_int.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_or.3ossl.bz2 /usr/share/man/man3/CRYPTO_atomic_store.3ossl.bz2 /usr/share/man/man3/CRYPTO_calloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_clear_free.3ossl.bz2 /usr/share/man/man3/CRYPTO_clear_realloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_clear_realloc_array.3ossl.bz2 /usr/share/man/man3/CRYPTO_free.3ossl.bz2 /usr/share/man/man3/CRYPTO_free_ex_data.3ossl.bz2 /usr/share/man/man3/CRYPTO_free_ex_index.3ossl.bz2 /usr/share/man/man3/CRYPTO_free_fn.3ossl.bz2 /usr/share/man/man3/CRYPTO_get_alloc_counts.3ossl.bz2 /usr/share/man/man3/CRYPTO_get_ex_data.3ossl.bz2 /usr/share/man/man3/CRYPTO_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/CRYPTO_get_mem_functions.3ossl.bz2 /usr/share/man/man3/CRYPTO_malloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_malloc_array.3ossl.bz2 /usr/share/man/man3/CRYPTO_malloc_fn.3ossl.bz2 /usr/share/man/man3/CRYPTO_mem_ctrl.3ossl.bz2 /usr/share/man/man3/CRYPTO_mem_debug_pop.3ossl.bz2 /usr/share/man/man3/CRYPTO_mem_debug_push.3ossl.bz2 /usr/share/man/man3/CRYPTO_mem_leaks.3ossl.bz2 /usr/share/man/man3/CRYPTO_mem_leaks_cb.3ossl.bz2 /usr/share/man/man3/CRYPTO_mem_leaks_fp.3ossl.bz2 /usr/share/man/man3/CRYPTO_memcmp.3ossl.bz2 /usr/share/man/man3/CRYPTO_memdup.3ossl.bz2 /usr/share/man/man3/CRYPTO_new_ex_data.3ossl.bz2 /usr/share/man/man3/CRYPTO_realloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_realloc_array.3ossl.bz2 /usr/share/man/man3/CRYPTO_realloc_fn.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_actual_size.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_allocated.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_calloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_clear_free.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_free.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_malloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_malloc_array.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_malloc_done.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_malloc_init.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_malloc_initialized.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_used.3ossl.bz2 /usr/share/man/man3/CRYPTO_secure_zalloc.3ossl.bz2 /usr/share/man/man3/CRYPTO_set_ex_data.3ossl.bz2 /usr/share/man/man3/CRYPTO_set_mem_debug.3ossl.bz2 /usr/share/man/man3/CRYPTO_set_mem_functions.3ossl.bz2 /usr/share/man/man3/CRYPTO_strdup.3ossl.bz2 /usr/share/man/man3/CRYPTO_strndup.3ossl.bz2 /usr/share/man/man3/CRYPTO_zalloc.3ossl.bz2 /usr/share/man/man3/CTLOG_STORE_free.3ossl.bz2 /usr/share/man/man3/CTLOG_STORE_get0_log_by_id.3ossl.bz2 /usr/share/man/man3/CTLOG_STORE_load_default_file.3ossl.bz2 /usr/share/man/man3/CTLOG_STORE_load_file.3ossl.bz2 /usr/share/man/man3/CTLOG_STORE_new.3ossl.bz2 /usr/share/man/man3/CTLOG_STORE_new_ex.3ossl.bz2 /usr/share/man/man3/CTLOG_free.3ossl.bz2 /usr/share/man/man3/CTLOG_get0_log_id.3ossl.bz2 /usr/share/man/man3/CTLOG_get0_name.3ossl.bz2 /usr/share/man/man3/CTLOG_get0_public_key.3ossl.bz2 /usr/share/man/man3/CTLOG_new.3ossl.bz2 /usr/share/man/man3/CTLOG_new_ex.3ossl.bz2 /usr/share/man/man3/CTLOG_new_from_base64.3ossl.bz2 /usr/share/man/man3/CTLOG_new_from_base64_ex.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_free.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_get0_cert.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_get0_issuer.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_get0_log_store.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_get_time.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_new.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_new_ex.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_set1_cert.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_set1_issuer.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_set_shared_CTLOG_STORE.3ossl.bz2 /usr/share/man/man3/CT_POLICY_EVAL_CTX_set_time.3ossl.bz2 /usr/share/man/man3/DECLARE_ASN1_FUNCTIONS.3ossl.bz2 /usr/share/man/man3/DECLARE_PEM_rw.3ossl.bz2 /usr/share/man/man3/DEFINE_LHASH_OF.3ossl.bz2 /usr/share/man/man3/DEFINE_LHASH_OF_EX.3ossl.bz2 /usr/share/man/man3/DEFINE_SPECIAL_STACK_OF.3ossl.bz2 /usr/share/man/man3/DEFINE_SPECIAL_STACK_OF_CONST.3ossl.bz2 /usr/share/man/man3/DEFINE_STACK_OF.3ossl.bz2 /usr/share/man/man3/DEFINE_STACK_OF_CONST.3ossl.bz2 /usr/share/man/man3/DES_cbc_cksum.3ossl.bz2 /usr/share/man/man3/DES_cfb64_encrypt.3ossl.bz2 /usr/share/man/man3/DES_cfb_encrypt.3ossl.bz2 /usr/share/man/man3/DES_crypt.3ossl.bz2 /usr/share/man/man3/DES_ecb2_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ecb3_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ecb_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ede2_cbc_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ede2_cfb64_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ede2_ofb64_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ede3_cbc_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ede3_cfb64_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ede3_ofb64_encrypt.3ossl.bz2 /usr/share/man/man3/DES_fcrypt.3ossl.bz2 /usr/share/man/man3/DES_is_weak_key.3ossl.bz2 /usr/share/man/man3/DES_key_sched.3ossl.bz2 /usr/share/man/man3/DES_ncbc_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ofb64_encrypt.3ossl.bz2 /usr/share/man/man3/DES_ofb_encrypt.3ossl.bz2 /usr/share/man/man3/DES_pcbc_encrypt.3ossl.bz2 /usr/share/man/man3/DES_quad_cksum.3ossl.bz2 /usr/share/man/man3/DES_random_key.3ossl.bz2 /usr/share/man/man3/DES_set_key.3ossl.bz2 /usr/share/man/man3/DES_set_key_checked.3ossl.bz2 /usr/share/man/man3/DES_set_key_unchecked.3ossl.bz2 /usr/share/man/man3/DES_set_odd_parity.3ossl.bz2 /usr/share/man/man3/DES_string_to_2keys.3ossl.bz2 /usr/share/man/man3/DES_string_to_key.3ossl.bz2 /usr/share/man/man3/DES_xcbc_encrypt.3ossl.bz2 /usr/share/man/man3/DH_OpenSSL.3ossl.bz2
    /usr/share/man/man3/DH_bits.3ossl.bz2
    /usr/share/man/man3/DH_check.3ossl.bz2 /usr/share/man/man3/DH_check_ex.3ossl.bz2 /usr/share/man/man3/DH_check_params.3ossl.bz2 /usr/share/man/man3/DH_check_params_ex.3ossl.bz2 /usr/share/man/man3/DH_check_pub_key_ex.3ossl.bz2 /usr/share/man/man3/DH_clear_flags.3ossl.bz2 /usr/share/man/man3/DH_compute_key.3ossl.bz2 /usr/share/man/man3/DH_compute_key_padded.3ossl.bz2 /usr/share/man/man3/DH_free.3ossl.bz2 /usr/share/man/man3/DH_generate_key.3ossl.bz2 /usr/share/man/man3/DH_generate_parameters.3ossl.bz2 /usr/share/man/man3/DH_generate_parameters_ex.3ossl.bz2 /usr/share/man/man3/DH_get0_engine.3ossl.bz2 /usr/share/man/man3/DH_get0_g.3ossl.bz2 /usr/share/man/man3/DH_get0_key.3ossl.bz2 /usr/share/man/man3/DH_get0_p.3ossl.bz2 /usr/share/man/man3/DH_get0_pqg.3ossl.bz2 /usr/share/man/man3/DH_get0_priv_key.3ossl.bz2 /usr/share/man/man3/DH_get0_pub_key.3ossl.bz2 /usr/share/man/man3/DH_get0_q.3ossl.bz2 /usr/share/man/man3/DH_get_1024_160.3ossl.bz2 /usr/share/man/man3/DH_get_2048_224.3ossl.bz2 /usr/share/man/man3/DH_get_2048_256.3ossl.bz2 /usr/share/man/man3/DH_get_default_method.3ossl.bz2 /usr/share/man/man3/DH_get_ex_data.3ossl.bz2 /usr/share/man/man3/DH_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/DH_get_length.3ossl.bz2 /usr/share/man/man3/DH_get_nid.3ossl.bz2 /usr/share/man/man3/DH_meth_dup.3ossl.bz2 /usr/share/man/man3/DH_meth_free.3ossl.bz2 /usr/share/man/man3/DH_meth_get0_app_data.3ossl.bz2 /usr/share/man/man3/DH_meth_get0_name.3ossl.bz2 /usr/share/man/man3/DH_meth_get_bn_mod_exp.3ossl.bz2 /usr/share/man/man3/DH_meth_get_compute_key.3ossl.bz2 /usr/share/man/man3/DH_meth_get_finish.3ossl.bz2 /usr/share/man/man3/DH_meth_get_flags.3ossl.bz2 /usr/share/man/man3/DH_meth_get_generate_key.3ossl.bz2 /usr/share/man/man3/DH_meth_get_generate_params.3ossl.bz2 /usr/share/man/man3/DH_meth_get_init.3ossl.bz2 /usr/share/man/man3/DH_meth_new.3ossl.bz2 /usr/share/man/man3/DH_meth_set0_app_data.3ossl.bz2 /usr/share/man/man3/DH_meth_set1_name.3ossl.bz2 /usr/share/man/man3/DH_meth_set_bn_mod_exp.3ossl.bz2 /usr/share/man/man3/DH_meth_set_compute_key.3ossl.bz2 /usr/share/man/man3/DH_meth_set_finish.3ossl.bz2 /usr/share/man/man3/DH_meth_set_flags.3ossl.bz2 /usr/share/man/man3/DH_meth_set_generate_key.3ossl.bz2 /usr/share/man/man3/DH_meth_set_generate_params.3ossl.bz2 /usr/share/man/man3/DH_meth_set_init.3ossl.bz2 /usr/share/man/man3/DH_new.3ossl.bz2 /usr/share/man/man3/DH_new_by_nid.3ossl.bz2 /usr/share/man/man3/DH_new_method.3ossl.bz2 /usr/share/man/man3/DH_security_bits.3ossl.bz2 /usr/share/man/man3/DH_set0_key.3ossl.bz2 /usr/share/man/man3/DH_set0_pqg.3ossl.bz2 /usr/share/man/man3/DH_set_default_method.3ossl.bz2 /usr/share/man/man3/DH_set_ex_data.3ossl.bz2 /usr/share/man/man3/DH_set_flags.3ossl.bz2 /usr/share/man/man3/DH_set_length.3ossl.bz2 /usr/share/man/man3/DH_set_method.3ossl.bz2 /usr/share/man/man3/DH_size.3ossl.bz2 /usr/share/man/man3/DH_test_flags.3ossl.bz2 /usr/share/man/man3/DHparams_print.3ossl.bz2 /usr/share/man/man3/DHparams_print_fp.3ossl.bz2 /usr/share/man/man3/DIRECTORYSTRING_free.3ossl.bz2 /usr/share/man/man3/DIRECTORYSTRING_new.3ossl.bz2 /usr/share/man/man3/DISPLAYTEXT_free.3ossl.bz2 /usr/share/man/man3/DISPLAYTEXT_new.3ossl.bz2 /usr/share/man/man3/DIST_POINT_NAME_dup.3ossl.bz2 /usr/share/man/man3/DIST_POINT_NAME_free.3ossl.bz2 /usr/share/man/man3/DIST_POINT_NAME_new.3ossl.bz2 /usr/share/man/man3/DIST_POINT_free.3ossl.bz2 /usr/share/man/man3/DIST_POINT_new.3ossl.bz2 /usr/share/man/man3/DSA_OpenSSL.3ossl.bz2 /usr/share/man/man3/DSA_SIG_free.3ossl.bz2 /usr/share/man/man3/DSA_SIG_get0.3ossl.bz2 /usr/share/man/man3/DSA_SIG_new.3ossl.bz2 /usr/share/man/man3/DSA_SIG_set0.3ossl.bz2 /usr/share/man/man3/DSA_bits.3ossl.bz2 /usr/share/man/man3/DSA_clear_flags.3ossl.bz2 /usr/share/man/man3/DSA_do_sign.3ossl.bz2 /usr/share/man/man3/DSA_do_verify.3ossl.bz2 /usr/share/man/man3/DSA_dup_DH.3ossl.bz2
    /usr/share/man/man3/DSA_free.3ossl.bz2 /usr/share/man/man3/DSA_generate_key.3ossl.bz2 /usr/share/man/man3/DSA_generate_parameters.3ossl.bz2 /usr/share/man/man3/DSA_generate_parameters_ex.3ossl.bz2 /usr/share/man/man3/DSA_get0_engine.3ossl.bz2 /usr/share/man/man3/DSA_get0_g.3ossl.bz2 /usr/share/man/man3/DSA_get0_key.3ossl.bz2 /usr/share/man/man3/DSA_get0_p.3ossl.bz2 /usr/share/man/man3/DSA_get0_pqg.3ossl.bz2 /usr/share/man/man3/DSA_get0_priv_key.3ossl.bz2 /usr/share/man/man3/DSA_get0_pub_key.3ossl.bz2 /usr/share/man/man3/DSA_get0_q.3ossl.bz2 /usr/share/man/man3/DSA_get_default_method.3ossl.bz2 /usr/share/man/man3/DSA_get_ex_data.3ossl.bz2 /usr/share/man/man3/DSA_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/DSA_meth_dup.3ossl.bz2 /usr/share/man/man3/DSA_meth_free.3ossl.bz2 /usr/share/man/man3/DSA_meth_get0_app_data.3ossl.bz2 /usr/share/man/man3/DSA_meth_get0_name.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_bn_mod_exp.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_finish.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_flags.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_init.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_keygen.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_mod_exp.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_paramgen.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_sign.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_sign_setup.3ossl.bz2 /usr/share/man/man3/DSA_meth_get_verify.3ossl.bz2 /usr/share/man/man3/DSA_meth_new.3ossl.bz2 /usr/share/man/man3/DSA_meth_set0_app_data.3ossl.bz2 /usr/share/man/man3/DSA_meth_set1_name.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_bn_mod_exp.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_finish.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_flags.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_init.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_keygen.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_mod_exp.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_paramgen.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_sign.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_sign_setup.3ossl.bz2 /usr/share/man/man3/DSA_meth_set_verify.3ossl.bz2 /usr/share/man/man3/DSA_new.3ossl.bz2 /usr/share/man/man3/DSA_new_method.3ossl.bz2 /usr/share/man/man3/DSA_print.3ossl.bz2 /usr/share/man/man3/DSA_print_fp.3ossl.bz2 /usr/share/man/man3/DSA_security_bits.3ossl.bz2 /usr/share/man/man3/DSA_set0_key.3ossl.bz2 /usr/share/man/man3/DSA_set0_pqg.3ossl.bz2 /usr/share/man/man3/DSA_set_default_method.3ossl.bz2 /usr/share/man/man3/DSA_set_ex_data.3ossl.bz2 /usr/share/man/man3/DSA_set_flags.3ossl.bz2 /usr/share/man/man3/DSA_set_method.3ossl.bz2 /usr/share/man/man3/DSA_sign.3ossl.bz2 /usr/share/man/man3/DSA_sign_setup.3ossl.bz2 /usr/share/man/man3/DSA_size.3ossl.bz2 /usr/share/man/man3/DSA_test_flags.3ossl.bz2 /usr/share/man/man3/DSA_verify.3ossl.bz2 /usr/share/man/man3/DSAparams_dup.3ossl.bz2 /usr/share/man/man3/DSAparams_print.3ossl.bz2 /usr/share/man/man3/DSAparams_print_fp.3ossl.bz2 /usr/share/man/man3/DTLS_client_method.3ossl.bz2 /usr/share/man/man3/DTLS_get_data_mtu.3ossl.bz2 /usr/share/man/man3/DTLS_method.3ossl.bz2 /usr/share/man/man3/DTLS_server_method.3ossl.bz2 /usr/share/man/man3/DTLS_set_timer_cb.3ossl.bz2 /usr/share/man/man3/DTLS_timer_cb.3ossl.bz2 /usr/share/man/man3/DTLSv1_2_client_method.3ossl.bz2 /usr/share/man/man3/DTLSv1_2_method.3ossl.bz2 /usr/share/man/man3/DTLSv1_2_server_method.3ossl.bz2 /usr/share/man/man3/DTLSv1_client_method.3ossl.bz2 /usr/share/man/man3/DTLSv1_get_timeout.3ossl.bz2 /usr/share/man/man3/DTLSv1_handle_timeout.3ossl.bz2 /usr/share/man/man3/DTLSv1_listen.3ossl.bz2 /usr/share/man/man3/DTLSv1_method.3ossl.bz2 /usr/share/man/man3/DTLSv1_server_method.3ossl.bz2 /usr/share/man/man3/ECDSA_SIG_free.3ossl.bz2 /usr/share/man/man3/ECDSA_SIG_get0.3ossl.bz2 /usr/share/man/man3/ECDSA_SIG_get0_r.3ossl.bz2 /usr/share/man/man3/ECDSA_SIG_get0_s.3ossl.bz2 /usr/share/man/man3/ECDSA_SIG_new.3ossl.bz2 /usr/share/man/man3/ECDSA_SIG_set0.3ossl.bz2 /usr/share/man/man3/ECDSA_do_sign.3ossl.bz2 /usr/share/man/man3/ECDSA_do_sign_ex.3ossl.bz2 /usr/share/man/man3/ECDSA_do_verify.3ossl.bz2 /usr/share/man/man3/ECDSA_sign.3ossl.bz2 /usr/share/man/man3/ECDSA_sign_ex.3ossl.bz2 /usr/share/man/man3/ECDSA_sign_setup.3ossl.bz2 /usr/share/man/man3/ECDSA_size.3ossl.bz2 /usr/share/man/man3/ECDSA_verify.3ossl.bz2 /usr/share/man/man3/ECPARAMETERS_free.3ossl.bz2 /usr/share/man/man3/ECPARAMETERS_new.3ossl.bz2 /usr/share/man/man3/ECPKPARAMETERS_free.3ossl.bz2 /usr/share/man/man3/ECPKPARAMETERS_new.3ossl.bz2 /usr/share/man/man3/ECPKParameters_print.3ossl.bz2 /usr/share/man/man3/ECPKParameters_print_fp.3ossl.bz2 /usr/share/man/man3/EC_GF2m_simple_method.3ossl.bz2 /usr/share/man/man3/EC_GFp_mont_method.3ossl.bz2 /usr/share/man/man3/EC_GFp_nist_method.3ossl.bz2 /usr/share/man/man3/EC_GFp_nistp224_method.3ossl.bz2 /usr/share/man/man3/EC_GFp_nistp256_method.3ossl.bz2 /usr/share/man/man3/EC_GFp_nistp521_method.3ossl.bz2 /usr/share/man/man3/EC_GFp_simple_method.3ossl.bz2 /usr/share/man/man3/EC_GROUP_check.3ossl.bz2 /usr/share/man/man3/EC_GROUP_check_discriminant.3ossl.bz2 /usr/share/man/man3/EC_GROUP_check_named_curve.3ossl.bz2 /usr/share/man/man3/EC_GROUP_clear_free.3ossl.bz2 /usr/share/man/man3/EC_GROUP_cmp.3ossl.bz2 /usr/share/man/man3/EC_GROUP_copy.3ossl.bz2 /usr/share/man/man3/EC_GROUP_dup.3ossl.bz2 /usr/share/man/man3/EC_GROUP_free.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get0_cofactor.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get0_field.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get0_generator.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get0_order.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get0_seed.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_asn1_flag.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_basis_type.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_cofactor.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_curve.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_curve_GF2m.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_curve_GFp.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_curve_name.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_degree.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_ecparameters.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_ecpkparameters.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_field_type.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_order.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_pentanomial_basis.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_point_conversion_form.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_seed_len.3ossl.bz2 /usr/share/man/man3/EC_GROUP_get_trinomial_basis.3ossl.bz2 /usr/share/man/man3/EC_GROUP_have_precompute_mult.3ossl.bz2 /usr/share/man/man3/EC_GROUP_method_of.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_by_curve_name.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_by_curve_name_ex.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_curve_GF2m.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_curve_GFp.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_from_ecparameters.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_from_ecpkparameters.3ossl.bz2 /usr/share/man/man3/EC_GROUP_new_from_params.3ossl.bz2 /usr/share/man/man3/EC_GROUP_order_bits.3ossl.bz2 /usr/share/man/man3/EC_GROUP_precompute_mult.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_asn1_flag.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_curve.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_curve_GF2m.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_curve_GFp.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_curve_name.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_generator.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_point_conversion_form.3ossl.bz2 /usr/share/man/man3/EC_GROUP_set_seed.3ossl.bz2 /usr/share/man/man3/EC_GROUP_to_params.3ossl.bz2 /usr/share/man/man3/EC_KEY_check_key.3ossl.bz2 /usr/share/man/man3/EC_KEY_clear_flags.3ossl.bz2 /usr/share/man/man3/EC_KEY_copy.3ossl.bz2 /usr/share/man/man3/EC_KEY_decoded_from_explicit_params.3ossl.bz2 /usr/share/man/man3/EC_KEY_dup.3ossl.bz2 /usr/share/man/man3/EC_KEY_free.3ossl.bz2 /usr/share/man/man3/EC_KEY_generate_key.3ossl.bz2 /usr/share/man/man3/EC_KEY_get0_engine.3ossl.bz2 /usr/share/man/man3/EC_KEY_get0_group.3ossl.bz2 /usr/share/man/man3/EC_KEY_get0_private_key.3ossl.bz2 /usr/share/man/man3/EC_KEY_get0_public_key.3ossl.bz2 /usr/share/man/man3/EC_KEY_get_conv_form.3ossl.bz2 /usr/share/man/man3/EC_KEY_get_enc_flags.3ossl.bz2 /usr/share/man/man3/EC_KEY_get_ex_data.3ossl.bz2 /usr/share/man/man3/EC_KEY_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/EC_KEY_get_flags.3ossl.bz2 /usr/share/man/man3/EC_KEY_get_method.3ossl.bz2 /usr/share/man/man3/EC_KEY_key2buf.3ossl.bz2 /usr/share/man/man3/EC_KEY_new.3ossl.bz2 /usr/share/man/man3/EC_KEY_new_by_curve_name.3ossl.bz2 /usr/share/man/man3/EC_KEY_new_by_curve_name_ex.3ossl.bz2 /usr/share/man/man3/EC_KEY_new_ex.3ossl.bz2 /usr/share/man/man3/EC_KEY_oct2key.3ossl.bz2 /usr/share/man/man3/EC_KEY_oct2priv.3ossl.bz2 /usr/share/man/man3/EC_KEY_precompute_mult.3ossl.bz2 /usr/share/man/man3/EC_KEY_priv2buf.3ossl.bz2 /usr/share/man/man3/EC_KEY_priv2oct.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_asn1_flag.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_conv_form.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_enc_flags.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_ex_data.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_flags.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_group.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_method.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_private_key.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_public_key.3ossl.bz2 /usr/share/man/man3/EC_KEY_set_public_key_affine_coordinates.3ossl.bz2 /usr/share/man/man3/EC_KEY_up_ref.3ossl.bz2 /usr/share/man/man3/EC_METHOD_get_field_type.3ossl.bz2 /usr/share/man/man3/EC_POINT_add.3ossl.bz2 /usr/share/man/man3/EC_POINT_bn2point.3ossl.bz2 /usr/share/man/man3/EC_POINT_clear_free.3ossl.bz2 /usr/share/man/man3/EC_POINT_cmp.3ossl.bz2 /usr/share/man/man3/EC_POINT_copy.3ossl.bz2 /usr/share/man/man3/EC_POINT_dbl.3ossl.bz2 /usr/share/man/man3/EC_POINT_dup.3ossl.bz2 /usr/share/man/man3/EC_POINT_free.3ossl.bz2 /usr/share/man/man3/EC_POINT_get_Jprojective_coordinates_GFp.3ossl.bz2 /usr/share/man/man3/EC_POINT_get_affine_coordinates.3ossl.bz2 /usr/share/man/man3/EC_POINT_get_affine_coordinates_GF2m.3ossl.bz2 /usr/share/man/man3/EC_POINT_get_affine_coordinates_GFp.3ossl.bz2 /usr/share/man/man3/EC_POINT_hex2point.3ossl.bz2 /usr/share/man/man3/EC_POINT_invert.3ossl.bz2 /usr/share/man/man3/EC_POINT_is_at_infinity.3ossl.bz2 /usr/share/man/man3/EC_POINT_is_on_curve.3ossl.bz2 /usr/share/man/man3/EC_POINT_make_affine.3ossl.bz2 /usr/share/man/man3/EC_POINT_method_of.3ossl.bz2 /usr/share/man/man3/EC_POINT_mul.3ossl.bz2 /usr/share/man/man3/EC_POINT_new.3ossl.bz2 /usr/share/man/man3/EC_POINT_oct2point.3ossl.bz2 /usr/share/man/man3/EC_POINT_point2bn.3ossl.bz2 /usr/share/man/man3/EC_POINT_point2buf.3ossl.bz2 /usr/share/man/man3/EC_POINT_point2hex.3ossl.bz2 /usr/share/man/man3/EC_POINT_point2oct.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_Jprojective_coordinates_GFp.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_affine_coordinates.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_affine_coordinates_GF2m.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_affine_coordinates_GFp.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_compressed_coordinates.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_compressed_coordinates_GF2m.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_compressed_coordinates_GFp.3ossl.bz2 /usr/share/man/man3/EC_POINT_set_to_infinity.3ossl.bz2 /usr/share/man/man3/EC_POINTs_make_affine.3ossl.bz2 /usr/share/man/man3/EC_POINTs_mul.3ossl.bz2 /usr/share/man/man3/EC_get_builtin_curves.3ossl.bz2 /usr/share/man/man3/EDIPARTYNAME_free.3ossl.bz2 /usr/share/man/man3/EDIPARTYNAME_new.3ossl.bz2 /usr/share/man/man3/ENGINE_add.3ossl.bz2 /usr/share/man/man3/ENGINE_add_conf_module.3ossl.bz2 /usr/share/man/man3/ENGINE_by_id.3ossl.bz2 /usr/share/man/man3/ENGINE_cleanup.3ossl.bz2 /usr/share/man/man3/ENGINE_cmd_is_executable.3ossl.bz2 /usr/share/man/man3/ENGINE_ctrl.3ossl.bz2 /usr/share/man/man3/ENGINE_ctrl_cmd.3ossl.bz2 /usr/share/man/man3/ENGINE_ctrl_cmd_string.3ossl.bz2 /usr/share/man/man3/ENGINE_finish.3ossl.bz2 /usr/share/man/man3/ENGINE_free.3ossl.bz2 /usr/share/man/man3/ENGINE_get_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_get_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_get_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_get_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_get_cipher.3ossl.bz2 /usr/share/man/man3/ENGINE_get_cipher_engine.3ossl.bz2 /usr/share/man/man3/ENGINE_get_ciphers.3ossl.bz2 /usr/share/man/man3/ENGINE_get_cmd_defns.3ossl.bz2 /usr/share/man/man3/ENGINE_get_ctrl_function.3ossl.bz2 /usr/share/man/man3/ENGINE_get_default_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_get_default_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_get_default_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_get_default_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_get_destroy_function.3ossl.bz2 /usr/share/man/man3/ENGINE_get_digest.3ossl.bz2 /usr/share/man/man3/ENGINE_get_digest_engine.3ossl.bz2 /usr/share/man/man3/ENGINE_get_digests.3ossl.bz2 /usr/share/man/man3/ENGINE_get_ex_data.3ossl.bz2 /usr/share/man/man3/ENGINE_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/ENGINE_get_finish_function.3ossl.bz2 /usr/share/man/man3/ENGINE_get_first.3ossl.bz2 /usr/share/man/man3/ENGINE_get_flags.3ossl.bz2 /usr/share/man/man3/ENGINE_get_id.3ossl.bz2 /usr/share/man/man3/ENGINE_get_init_function.3ossl.bz2 /usr/share/man/man3/ENGINE_get_last.3ossl.bz2 /usr/share/man/man3/ENGINE_get_load_privkey_function.3ossl.bz2 /usr/share/man/man3/ENGINE_get_load_pubkey_function.3ossl.bz2 /usr/share/man/man3/ENGINE_get_name.3ossl.bz2 /usr/share/man/man3/ENGINE_get_next.3ossl.bz2 /usr/share/man/man3/ENGINE_get_prev.3ossl.bz2 /usr/share/man/man3/ENGINE_get_table_flags.3ossl.bz2 /usr/share/man/man3/ENGINE_init.3ossl.bz2 /usr/share/man/man3/ENGINE_load_builtin_engines.3ossl.bz2 /usr/share/man/man3/ENGINE_load_private_key.3ossl.bz2 /usr/share/man/man3/ENGINE_load_public_key.3ossl.bz2 /usr/share/man/man3/ENGINE_new.3ossl.bz2 /usr/share/man/man3/ENGINE_register_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_register_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_register_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_register_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_ciphers.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_complete.3ossl.bz2 /usr/share/man/man3/ENGINE_register_all_digests.3ossl.bz2 /usr/share/man/man3/ENGINE_register_ciphers.3ossl.bz2 /usr/share/man/man3/ENGINE_register_complete.3ossl.bz2 /usr/share/man/man3/ENGINE_register_digests.3ossl.bz2 /usr/share/man/man3/ENGINE_remove.3ossl.bz2 /usr/share/man/man3/ENGINE_set_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_set_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_set_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_set_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_set_ciphers.3ossl.bz2 /usr/share/man/man3/ENGINE_set_cmd_defns.3ossl.bz2 /usr/share/man/man3/ENGINE_set_ctrl_function.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_ciphers.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_digests.3ossl.bz2 /usr/share/man/man3/ENGINE_set_default_string.3ossl.bz2 /usr/share/man/man3/ENGINE_set_destroy_function.3ossl.bz2 /usr/share/man/man3/ENGINE_set_digests.3ossl.bz2 /usr/share/man/man3/ENGINE_set_ex_data.3ossl.bz2 /usr/share/man/man3/ENGINE_set_finish_function.3ossl.bz2 /usr/share/man/man3/ENGINE_set_flags.3ossl.bz2 /usr/share/man/man3/ENGINE_set_id.3ossl.bz2 /usr/share/man/man3/ENGINE_set_init_function.3ossl.bz2 /usr/share/man/man3/ENGINE_set_load_privkey_function.3ossl.bz2 /usr/share/man/man3/ENGINE_set_load_pubkey_function.3ossl.bz2 /usr/share/man/man3/ENGINE_set_name.3ossl.bz2 /usr/share/man/man3/ENGINE_set_table_flags.3ossl.bz2 /usr/share/man/man3/ENGINE_unregister_DH.3ossl.bz2 /usr/share/man/man3/ENGINE_unregister_DSA.3ossl.bz2 /usr/share/man/man3/ENGINE_unregister_RAND.3ossl.bz2 /usr/share/man/man3/ENGINE_unregister_RSA.3ossl.bz2 /usr/share/man/man3/ENGINE_unregister_ciphers.3ossl.bz2 /usr/share/man/man3/ENGINE_unregister_digests.3ossl.bz2 /usr/share/man/man3/ENGINE_up_ref.3ossl.bz2 /usr/share/man/man3/ERR_FATAL_ERROR.3ossl.bz2 /usr/share/man/man3/ERR_GET_LIB.3ossl.bz2 /usr/share/man/man3/ERR_GET_REASON.3ossl.bz2 /usr/share/man/man3/ERR_PACK.3ossl.bz2 /usr/share/man/man3/ERR_add_error_data.3ossl.bz2 /usr/share/man/man3/ERR_add_error_mem_bio.3ossl.bz2 /usr/share/man/man3/ERR_add_error_txt.3ossl.bz2 /usr/share/man/man3/ERR_add_error_vdata.3ossl.bz2 /usr/share/man/man3/ERR_clear_error.3ossl.bz2 /usr/share/man/man3/ERR_clear_last_mark.3ossl.bz2 /usr/share/man/man3/ERR_count_to_mark.3ossl.bz2 /usr/share/man/man3/ERR_error_string.3ossl.bz2 /usr/share/man/man3/ERR_error_string_n.3ossl.bz2 /usr/share/man/man3/ERR_free_strings.3ossl.bz2 /usr/share/man/man3/ERR_func_error_string.3ossl.bz2 /usr/share/man/man3/ERR_get_error.3ossl.bz2 /usr/share/man/man3/ERR_get_error_all.3ossl.bz2 /usr/share/man/man3/ERR_get_error_line.3ossl.bz2 /usr/share/man/man3/ERR_get_error_line_data.3ossl.bz2 /usr/share/man/man3/ERR_get_next_error_library.3ossl.bz2 /usr/share/man/man3/ERR_lib_error_string.3ossl.bz2 /usr/share/man/man3/ERR_load_crypto_strings.3ossl.bz2 /usr/share/man/man3/ERR_load_strings.3ossl.bz2 /usr/share/man/man3/ERR_new.3ossl.bz2 /usr/share/man/man3/ERR_peek_error.3ossl.bz2 /usr/share/man/man3/ERR_peek_error_all.3ossl.bz2 /usr/share/man/man3/ERR_peek_error_data.3ossl.bz2 /usr/share/man/man3/ERR_peek_error_func.3ossl.bz2 /usr/share/man/man3/ERR_peek_error_line.3ossl.bz2 /usr/share/man/man3/ERR_peek_error_line_data.3ossl.bz2 /usr/share/man/man3/ERR_peek_last_error.3ossl.bz2 /usr/share/man/man3/ERR_peek_last_error_all.3ossl.bz2 /usr/share/man/man3/ERR_peek_last_error_data.3ossl.bz2 /usr/share/man/man3/ERR_peek_last_error_func.3ossl.bz2 /usr/share/man/man3/ERR_peek_last_error_line.3ossl.bz2 /usr/share/man/man3/ERR_peek_last_error_line_data.3ossl.bz2 /usr/share/man/man3/ERR_pop.3ossl.bz2 /usr/share/man/man3/ERR_pop_to_mark.3ossl.bz2 /usr/share/man/man3/ERR_print_errors.3ossl.bz2 /usr/share/man/man3/ERR_print_errors_cb.3ossl.bz2 /usr/share/man/man3/ERR_print_errors_fp.3ossl.bz2 /usr/share/man/man3/ERR_put_error.3ossl.bz2 /usr/share/man/man3/ERR_raise.3ossl.bz2 /usr/share/man/man3/ERR_raise_data.3ossl.bz2 /usr/share/man/man3/ERR_reason_error_string.3ossl.bz2 /usr/share/man/man3/ERR_remove_state.3ossl.bz2 /usr/share/man/man3/ERR_remove_thread_state.3ossl.bz2 /usr/share/man/man3/ERR_set_debug.3ossl.bz2 /usr/share/man/man3/ERR_set_error.3ossl.bz2 /usr/share/man/man3/ERR_set_mark.3ossl.bz2 /usr/share/man/man3/ERR_vset_error.3ossl.bz2 /usr/share/man/man3/ESS_CERT_ID_V2_dup.3ossl.bz2 /usr/share/man/man3/ESS_CERT_ID_V2_free.3ossl.bz2 /usr/share/man/man3/ESS_CERT_ID_V2_new.3ossl.bz2 /usr/share/man/man3/ESS_CERT_ID_dup.3ossl.bz2 /usr/share/man/man3/ESS_CERT_ID_free.3ossl.bz2 /usr/share/man/man3/ESS_CERT_ID_new.3ossl.bz2 /usr/share/man/man3/ESS_ISSUER_SERIAL_dup.3ossl.bz2 /usr/share/man/man3/ESS_ISSUER_SERIAL_free.3ossl.bz2 /usr/share/man/man3/ESS_ISSUER_SERIAL_new.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_V2_dup.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_V2_free.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_V2_it.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_V2_new.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_dup.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_free.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_it.3ossl.bz2 /usr/share/man/man3/ESS_SIGNING_CERT_new.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_fetch.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_free.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_is_a.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_ASYM_CIPHER_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_BytesToKey.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_block_size.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_cipher.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_clear_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_copy.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_dup.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_encrypting.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get0_cipher.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get1_cipher.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_algor.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_algor_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_app_data.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_block_size.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_cipher_data.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_iv_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_key_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_mode.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_nid.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_num.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_original_iv.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_tag_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_type.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_get_updated_iv.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_is_encrypting.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_iv.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_iv_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_iv_noconst.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_key_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_mode.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_nid.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_num.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_original_iv.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_reset.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_algor_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_app_data.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_cipher_data.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_key_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_num.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_padding.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_set_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_tag_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_test_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_CTX_type.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_asn1_to_param.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_block_size.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_can_pipeline.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_fetch.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_free.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_block_size.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_iv_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_key_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_mode.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_nid.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_get_type.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_is_a.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_iv_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_key_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_dup.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_free.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_get_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_get_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_get_do_cipher.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_get_get_asn1_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_get_init.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_get_set_asn1_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_new.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_do_cipher.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_flags.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_get_asn1_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_impl_ctx_size.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_init.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_iv_length.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_meth_set_set_asn1_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_mode.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_name.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_nid.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_param_to_asn1.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_type.3ossl.bz2 /usr/share/man/man3/EVP_CIPHER_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_Cipher.3ossl.bz2 /usr/share/man/man3/EVP_CipherFinal.3ossl.bz2 /usr/share/man/man3/EVP_CipherFinal_ex.3ossl.bz2 /usr/share/man/man3/EVP_CipherInit.3ossl.bz2 /usr/share/man/man3/EVP_CipherInit_SKEY.3ossl.bz2 /usr/share/man/man3/EVP_CipherInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_CipherInit_ex2.3ossl.bz2 /usr/share/man/man3/EVP_CipherPipelineDecryptInit.3ossl.bz2 /usr/share/man/man3/EVP_CipherPipelineEncryptInit.3ossl.bz2 /usr/share/man/man3/EVP_CipherPipelineFinal.3ossl.bz2 /usr/share/man/man3/EVP_CipherPipelineUpdate.3ossl.bz2 /usr/share/man/man3/EVP_CipherUpdate.3ossl.bz2 /usr/share/man/man3/EVP_DecodeBlock.3ossl.bz2 /usr/share/man/man3/EVP_DecodeFinal.3ossl.bz2 /usr/share/man/man3/EVP_DecodeInit.3ossl.bz2 /usr/share/man/man3/EVP_DecodeUpdate.3ossl.bz2 /usr/share/man/man3/EVP_DecryptFinal.3ossl.bz2 /usr/share/man/man3/EVP_DecryptFinal_ex.3ossl.bz2 /usr/share/man/man3/EVP_DecryptInit.3ossl.bz2 /usr/share/man/man3/EVP_DecryptInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_DecryptInit_ex2.3ossl.bz2 /usr/share/man/man3/EVP_DecryptUpdate.3ossl.bz2 /usr/share/man/man3/EVP_Digest.3ossl.bz2 /usr/share/man/man3/EVP_DigestFinal.3ossl.bz2 /usr/share/man/man3/EVP_DigestFinalXOF.3ossl.bz2 /usr/share/man/man3/EVP_DigestFinal_ex.3ossl.bz2 /usr/share/man/man3/EVP_DigestInit.3ossl.bz2 /usr/share/man/man3/EVP_DigestInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_DigestInit_ex2.3ossl.bz2 /usr/share/man/man3/EVP_DigestSign.3ossl.bz2 /usr/share/man/man3/EVP_DigestSignFinal.3ossl.bz2 /usr/share/man/man3/EVP_DigestSignInit.3ossl.bz2 /usr/share/man/man3/EVP_DigestSignInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_DigestSignUpdate.3ossl.bz2 /usr/share/man/man3/EVP_DigestSqueeze.3ossl.bz2 /usr/share/man/man3/EVP_DigestUpdate.3ossl.bz2 /usr/share/man/man3/EVP_DigestVerify.3ossl.bz2 /usr/share/man/man3/EVP_DigestVerifyFinal.3ossl.bz2 /usr/share/man/man3/EVP_DigestVerifyInit.3ossl.bz2 /usr/share/man/man3/EVP_DigestVerifyInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_DigestVerifyUpdate.3ossl.bz2 /usr/share/man/man3/EVP_EC_gen.3ossl.bz2 /usr/share/man/man3/EVP_ENCODE_CTX_copy.3ossl.bz2 /usr/share/man/man3/EVP_ENCODE_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_ENCODE_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_ENCODE_CTX_num.3ossl.bz2 /usr/share/man/man3/EVP_EncodeBlock.3ossl.bz2 /usr/share/man/man3/EVP_EncodeFinal.3ossl.bz2 /usr/share/man/man3/EVP_EncodeInit.3ossl.bz2 /usr/share/man/man3/EVP_EncodeUpdate.3ossl.bz2 /usr/share/man/man3/EVP_EncryptFinal.3ossl.bz2 /usr/share/man/man3/EVP_EncryptFinal_ex.3ossl.bz2 /usr/share/man/man3/EVP_EncryptInit.3ossl.bz2 /usr/share/man/man3/EVP_EncryptInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_EncryptInit_ex2.3ossl.bz2 /usr/share/man/man3/EVP_EncryptUpdate.3ossl.bz2 /usr/share/man/man3/EVP_KDF.3ossl.bz2
    /usr/share/man/man3/EVP_KDF_CTX.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_dup.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_get_kdf_size.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_get_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_kdf.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_reset.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_set_SKEY.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_set_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_CTX_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_derive.3ossl.bz2 /usr/share/man/man3/EVP_KDF_derive_SKEY.3ossl.bz2 /usr/share/man/man3/EVP_KDF_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_KDF_fetch.3ossl.bz2 /usr/share/man/man3/EVP_KDF_free.3ossl.bz2 /usr/share/man/man3/EVP_KDF_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_KDF_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_KDF_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_KDF_get_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_is_a.3ossl.bz2 /usr/share/man/man3/EVP_KDF_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_KDF_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_KDF_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_KEM_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_KEM_fetch.3ossl.bz2 /usr/share/man/man3/EVP_KEM_free.3ossl.bz2 /usr/share/man/man3/EVP_KEM_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_KEM_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_KEM_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_KEM_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_KEM_is_a.3ossl.bz2 /usr/share/man/man3/EVP_KEM_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_KEM_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_KEM_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_fetch.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_free.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_is_a.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_KEYEXCH_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_fetch.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_free.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_gen_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_gen_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_is_a.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_KEYMGMT_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_MAC.3ossl.bz2
    /usr/share/man/man3/EVP_MAC_CTX.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_dup.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_get0_mac.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_get_block_size.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_get_mac_size.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_get_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_set_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_CTX_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_MAC_fetch.3ossl.bz2 /usr/share/man/man3/EVP_MAC_final.3ossl.bz2 /usr/share/man/man3/EVP_MAC_finalXOF.3ossl.bz2 /usr/share/man/man3/EVP_MAC_free.3ossl.bz2 /usr/share/man/man3/EVP_MAC_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_MAC_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_MAC_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_MAC_get_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_init.3ossl.bz2 /usr/share/man/man3/EVP_MAC_init_SKEY.3ossl.bz2 /usr/share/man/man3/EVP_MAC_is_a.3ossl.bz2 /usr/share/man/man3/EVP_MAC_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_MAC_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_MAC_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_MAC_update.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_block_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_clear_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_copy.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_copy_ex.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_dup.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get0_md.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get0_md_data.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get1_md.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get_block_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get_pkey_ctx.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get_size_ex.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_get_type.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_md.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_md_data.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_pkey_ctx.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_reset.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_set_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_set_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_set_pkey_ctx.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_set_update_fn.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_test_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_type.3ossl.bz2 /usr/share/man/man3/EVP_MD_CTX_update_fn.3ossl.bz2 /usr/share/man/man3/EVP_MD_block_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_MD_fetch.3ossl.bz2 /usr/share/man/man3/EVP_MD_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_free.3ossl.bz2 /usr/share/man/man3/EVP_MD_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_MD_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_MD_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_MD_get_block_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_get_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_get_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_get_pkey_type.3ossl.bz2 /usr/share/man/man3/EVP_MD_get_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_get_type.3ossl.bz2 /usr/share/man/man3/EVP_MD_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_is_a.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_dup.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_free.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_app_datasize.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_copy.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_final.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_init.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_input_blocksize.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_result_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_get_update.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_new.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_app_datasize.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_copy.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_final.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_flags.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_init.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_input_blocksize.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_result_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_meth_set_update.3ossl.bz2 /usr/share/man/man3/EVP_MD_name.3ossl.bz2 /usr/share/man/man3/EVP_MD_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_MD_nid.3ossl.bz2 /usr/share/man/man3/EVP_MD_pkey_type.3ossl.bz2 /usr/share/man/man3/EVP_MD_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_MD_size.3ossl.bz2 /usr/share/man/man3/EVP_MD_type.3ossl.bz2 /usr/share/man/man3/EVP_MD_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_MD_xof.3ossl.bz2 /usr/share/man/man3/EVP_OpenFinal.3ossl.bz2 /usr/share/man/man3/EVP_OpenInit.3ossl.bz2 /usr/share/man/man3/EVP_OpenUpdate.3ossl.bz2 /usr/share/man/man3/EVP_PBE_CipherInit.3ossl.bz2 /usr/share/man/man3/EVP_PBE_CipherInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_PBE_alg_add.3ossl.bz2 /usr/share/man/man3/EVP_PBE_alg_add_type.3ossl.bz2 /usr/share/man/man3/EVP_PBE_find.3ossl.bz2 /usr/share/man/man3/EVP_PBE_find_ex.3ossl.bz2 /usr/share/man/man3/EVP_PBE_scrypt.3ossl.bz2 /usr/share/man/man3/EVP_PBE_scrypt_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKCS82PKEY.3ossl.bz2 /usr/share/man/man3/EVP_PKCS82PKEY_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY.3ossl.bz2 /usr/share/man/man3/EVP_PKEY2PKCS8.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_ASN1_METHOD.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_add1_hkdf_info.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_add1_tls1_prf_seed.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_ctrl_str.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_ctrl_uint64.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_dup.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_dh_kdf_oid.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_dh_kdf_ukm.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_ecdh_kdf_ukm.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_libctx.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_peerkey.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_pkey.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_propq.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get0_rsa_oaep_label.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get1_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get1_id_len.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_algor.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_algor_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_app_data.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_cb.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_dh_kdf_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_dh_kdf_outlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_dh_kdf_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_ecdh_cofactor_mode.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_ecdh_kdf_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_ecdh_kdf_outlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_ecdh_kdf_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_group_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_keygen_info.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_rsa_mgf1_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_rsa_mgf1_md_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_rsa_oaep_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_rsa_oaep_md_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_rsa_padding.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_rsa_pss_saltlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_get_signature_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_is_a.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_new_from_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_new_from_pkey.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_new_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set0_dh_kdf_oid.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set0_dh_kdf_ukm.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set0_ecdh_kdf_ukm.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set0_rsa_oaep_label.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_hkdf_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_hkdf_salt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_pbe_pass.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_rsa_keygen_pubexp.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_scrypt_salt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set1_tls1_prf_secret.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_algor_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_app_data.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_cb.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_kdf_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_kdf_outlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_kdf_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_nid.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_pad.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_paramgen_generator.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_paramgen_gindex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_paramgen_prime_len.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_paramgen_seed.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_paramgen_subprime_len.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_paramgen_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dh_rfc5114.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dhx_rfc5114.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_gindex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_md_props.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_q_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_seed.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_dsa_paramgen_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_ec_param_enc.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_ec_paramgen_curve_nid.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_ecdh_cofactor_mode.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_ecdh_kdf_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_ecdh_kdf_outlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_ecdh_kdf_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_group_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_hkdf_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_hkdf_mode.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_kem_op.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_mac_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_keygen_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_keygen_primes.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_keygen_pubexp.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_mgf1_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_mgf1_md_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_oaep_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_oaep_md_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_padding.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_pss_keygen_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_pss_keygen_md_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_md_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_pss_keygen_saltlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_rsa_pss_saltlen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_scrypt_N.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_scrypt_maxmem_bytes.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_scrypt_p.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_scrypt_r.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_signature.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_signature_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_set_tls1_prf_md.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_CTX_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_METHOD.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_Q_keygen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_add1_attr.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_add0.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_add_alias.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_copy.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_find.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_find_str.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_free.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_get0.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_get0_info.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_get_count.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_new.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_free.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_get_priv_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_get_pub_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_item.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_param_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_private.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_public.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_public_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_security_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_set_priv_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_set_pub_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_asn1_set_siginf.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_assign_DH.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_assign_DSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_assign_EC_KEY.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_assign_POLY1305.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_assign_RSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_assign_SIPHASH.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_auth_decapsulate_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_auth_encapsulate_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_base_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_can_sign.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_cmp.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_cmp_parameters.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_copy_parameters.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_decapsulate.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_decapsulate_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_decrypt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_decrypt_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_decrypt_init_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_delete_attr.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_derive.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_derive_SKEY.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_derive_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_derive_init_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_derive_set_peer.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_derive_set_peer_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_digestsign_supports_digest.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_dup.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_encapsulate.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_encapsulate_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_encrypt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_encrypt_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_encrypt_init_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_eq.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_export.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_free.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_fromdata.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_fromdata_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_fromdata_settable.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_gen_cb.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_generate.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_DH.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_DSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_EC_KEY.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_RSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_asn1.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_engine.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_hmac.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_poly1305.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_siphash.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get0_type_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get1_DH.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get1_DSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get1_EC_KEY.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get1_RSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get1_encoded_public_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get1_tls_encodedpoint.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_attr.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_attr_by_NID.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_attr_count.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_base_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_bn_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_default_digest_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_default_digest_nid.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_ec_point_conv_form.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_ex_data.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_field_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_group_name.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_int_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_octet_string_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_raw_private_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_raw_public_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_security_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_security_category.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_size.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_size_t_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_get_utf8_string_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_id.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_is_a.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_keygen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_keygen_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_add0.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_copy.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_find.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_free.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get0.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get0_info.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_copy.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_count.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_decrypt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_derive.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_digest_custom.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_digestsign.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_digestverify.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_encrypt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_keygen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_param_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_paramgen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_public_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_sign.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_signctx.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_verify.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_verify_recover.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_get_verifyctx.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_new.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_remove.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_copy.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_ctrl.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_decrypt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_derive.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_digest_custom.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_digestsign.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_digestverify.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_encrypt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_keygen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_param_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_paramgen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_public_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_sign.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_signctx.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_verify.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_verify_recover.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_meth_set_verifyctx.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_missing_parameters.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new_CMAC_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new_mac_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new_raw_private_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new_raw_private_key_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new_raw_public_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_new_raw_public_key_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_pairwise_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_param_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_param_check_quick.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_parameters_eq.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_paramgen.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_paramgen_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_print_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_print_params_fp.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_print_private.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_print_private_fp.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_print_public.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_print_public_fp.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_private_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_public_check.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_public_check_quick.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_security_bits.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_DH.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_DSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_EC_KEY.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_RSA.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_encoded_public_key.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_engine.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set1_tls_encodedpoint.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_bn_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_ex_data.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_int_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_octet_string_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_size_t_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_type_by_keymgmt.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_type_str.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_set_utf8_string_param.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign_init_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign_init_ex2.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign_message_final.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign_message_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_sign_message_update.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_size.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_todata.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_type.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_type_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_init_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_init_ex2.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_message_final.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_message_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_message_update.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_recover.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_recover_init.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_recover_init_ex.3ossl.bz2 /usr/share/man/man3/EVP_PKEY_verify_recover_init_ex2.3ossl.bz2 /usr/share/man/man3/EVP_Q_digest.3ossl.bz2 /usr/share/man/man3/EVP_Q_mac.3ossl.bz2
    /usr/share/man/man3/EVP_RAND.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_free.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_get0_rand.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_get_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_new.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_set_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_CTX_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_RAND_STATE_ERROR.3ossl.bz2 /usr/share/man/man3/EVP_RAND_STATE_READY.3ossl.bz2 /usr/share/man/man3/EVP_RAND_STATE_UNINITIALISED.3ossl.bz2 /usr/share/man/man3/EVP_RAND_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_RAND_enable_locking.3ossl.bz2 /usr/share/man/man3/EVP_RAND_fetch.3ossl.bz2 /usr/share/man/man3/EVP_RAND_free.3ossl.bz2 /usr/share/man/man3/EVP_RAND_generate.3ossl.bz2 /usr/share/man/man3/EVP_RAND_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_RAND_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_RAND_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_RAND_get_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_get_state.3ossl.bz2 /usr/share/man/man3/EVP_RAND_get_strength.3ossl.bz2 /usr/share/man/man3/EVP_RAND_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_gettable_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_instantiate.3ossl.bz2 /usr/share/man/man3/EVP_RAND_is_a.3ossl.bz2 /usr/share/man/man3/EVP_RAND_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_RAND_nonce.3ossl.bz2 /usr/share/man/man3/EVP_RAND_reseed.3ossl.bz2 /usr/share/man/man3/EVP_RAND_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_RAND_uninstantiate.3ossl.bz2 /usr/share/man/man3/EVP_RAND_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_RAND_verify_zeroization.3ossl.bz2 /usr/share/man/man3/EVP_RSA_gen.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_fetch.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_free.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_gettable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_is_a.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/EVP_SIGNATURE_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_SKEY.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_do_all_provided.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_fetch.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_free.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_get0_description.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_get0_gen_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_get0_imp_settable_params.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_get0_name.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_get0_provider.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_is_a.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_names_do_all.3ossl.bz2 /usr/share/man/man3/EVP_SKEYMGMT_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_export.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_free.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_generate.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_get0_key_id.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_get0_provider_name.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_get0_raw_key.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_get0_skeymgmt_name.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_import.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_import_SKEYMGMT.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_import_raw_key.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_is_a.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_to_provider.3ossl.bz2 /usr/share/man/man3/EVP_SKEY_up_ref.3ossl.bz2 /usr/share/man/man3/EVP_SealFinal.3ossl.bz2 /usr/share/man/man3/EVP_SealInit.3ossl.bz2 /usr/share/man/man3/EVP_SealUpdate.3ossl.bz2 /usr/share/man/man3/EVP_SignFinal.3ossl.bz2 /usr/share/man/man3/EVP_SignFinal_ex.3ossl.bz2 /usr/share/man/man3/EVP_SignInit.3ossl.bz2 /usr/share/man/man3/EVP_SignInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_SignUpdate.3ossl.bz2 /usr/share/man/man3/EVP_VerifyFinal.3ossl.bz2 /usr/share/man/man3/EVP_VerifyFinal_ex.3ossl.bz2 /usr/share/man/man3/EVP_VerifyInit.3ossl.bz2 /usr/share/man/man3/EVP_VerifyInit_ex.3ossl.bz2 /usr/share/man/man3/EVP_VerifyUpdate.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cbc.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cbc_hmac_sha1.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cbc_hmac_sha256.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_ccm.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cfb.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_ctr.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_ecb.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_gcm.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_ocb.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_ofb.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_wrap.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_wrap_pad.3ossl.bz2 /usr/share/man/man3/EVP_aes_128_xts.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_cbc.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_ccm.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_cfb.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_ctr.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_ecb.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_gcm.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_ocb.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_ofb.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_wrap.3ossl.bz2 /usr/share/man/man3/EVP_aes_192_wrap_pad.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cbc.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cbc_hmac_sha1.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cbc_hmac_sha256.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_ccm.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cfb.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_ctr.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_ecb.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_gcm.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_ocb.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_ofb.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_wrap.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_wrap_pad.3ossl.bz2 /usr/share/man/man3/EVP_aes_256_xts.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_cbc.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_ccm.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_cfb.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_ctr.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_ecb.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_gcm.3ossl.bz2 /usr/share/man/man3/EVP_aria_128_ofb.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_cbc.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_ccm.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_cfb.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_ctr.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_ecb.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_gcm.3ossl.bz2 /usr/share/man/man3/EVP_aria_192_ofb.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_cbc.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_ccm.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_cfb.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_ctr.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_ecb.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_gcm.3ossl.bz2 /usr/share/man/man3/EVP_aria_256_ofb.3ossl.bz2 /usr/share/man/man3/EVP_bf_cbc.3ossl.bz2 /usr/share/man/man3/EVP_bf_cfb.3ossl.bz2 /usr/share/man/man3/EVP_bf_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_bf_ecb.3ossl.bz2 /usr/share/man/man3/EVP_bf_ofb.3ossl.bz2 /usr/share/man/man3/EVP_blake2b512.3ossl.bz2 /usr/share/man/man3/EVP_blake2s256.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_cbc.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_cfb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_ctr.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_ecb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_128_ofb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_cbc.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_cfb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_ctr.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_ecb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_192_ofb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_cbc.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_cfb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_ctr.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_ecb.3ossl.bz2 /usr/share/man/man3/EVP_camellia_256_ofb.3ossl.bz2 /usr/share/man/man3/EVP_cast5_cbc.3ossl.bz2 /usr/share/man/man3/EVP_cast5_cfb.3ossl.bz2 /usr/share/man/man3/EVP_cast5_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_cast5_ecb.3ossl.bz2 /usr/share/man/man3/EVP_cast5_ofb.3ossl.bz2 /usr/share/man/man3/EVP_chacha20.3ossl.bz2 /usr/share/man/man3/EVP_chacha20_poly1305.3ossl.bz2 /usr/share/man/man3/EVP_cleanup.3ossl.bz2 /usr/share/man/man3/EVP_default_properties_enable_fips.3ossl.bz2 /usr/share/man/man3/EVP_default_properties_is_fips_enabled.3ossl.bz2 /usr/share/man/man3/EVP_des_cbc.3ossl.bz2 /usr/share/man/man3/EVP_des_cfb.3ossl.bz2 /usr/share/man/man3/EVP_des_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_des_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_des_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_des_ecb.3ossl.bz2 /usr/share/man/man3/EVP_des_ede.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_cbc.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_cfb.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_cfb1.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_cfb8.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_ecb.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_ofb.3ossl.bz2 /usr/share/man/man3/EVP_des_ede3_wrap.3ossl.bz2 /usr/share/man/man3/EVP_des_ede_cbc.3ossl.bz2 /usr/share/man/man3/EVP_des_ede_cfb.3ossl.bz2 /usr/share/man/man3/EVP_des_ede_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_des_ede_ecb.3ossl.bz2 /usr/share/man/man3/EVP_des_ede_ofb.3ossl.bz2 /usr/share/man/man3/EVP_des_ofb.3ossl.bz2 /usr/share/man/man3/EVP_desx_cbc.3ossl.bz2 /usr/share/man/man3/EVP_enc_null.3ossl.bz2 /usr/share/man/man3/EVP_get1_default_properties.3ossl.bz2 /usr/share/man/man3/EVP_get_cipherbyname.3ossl.bz2 /usr/share/man/man3/EVP_get_cipherbynid.3ossl.bz2 /usr/share/man/man3/EVP_get_cipherbyobj.3ossl.bz2 /usr/share/man/man3/EVP_get_digestbyname.3ossl.bz2 /usr/share/man/man3/EVP_get_digestbynid.3ossl.bz2 /usr/share/man/man3/EVP_get_digestbyobj.3ossl.bz2 /usr/share/man/man3/EVP_idea_cbc.3ossl.bz2 /usr/share/man/man3/EVP_idea_cfb.3ossl.bz2 /usr/share/man/man3/EVP_idea_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_idea_ecb.3ossl.bz2 /usr/share/man/man3/EVP_idea_ofb.3ossl.bz2 /usr/share/man/man3/EVP_md2.3ossl.bz2
    /usr/share/man/man3/EVP_md4.3ossl.bz2
    /usr/share/man/man3/EVP_md5.3ossl.bz2 /usr/share/man/man3/EVP_md5_sha1.3ossl.bz2 /usr/share/man/man3/EVP_md_null.3ossl.bz2 /usr/share/man/man3/EVP_mdc2.3ossl.bz2 /usr/share/man/man3/EVP_rc2_40_cbc.3ossl.bz2 /usr/share/man/man3/EVP_rc2_64_cbc.3ossl.bz2 /usr/share/man/man3/EVP_rc2_cbc.3ossl.bz2 /usr/share/man/man3/EVP_rc2_cfb.3ossl.bz2 /usr/share/man/man3/EVP_rc2_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_rc2_ecb.3ossl.bz2 /usr/share/man/man3/EVP_rc2_ofb.3ossl.bz2
    /usr/share/man/man3/EVP_rc4.3ossl.bz2
    /usr/share/man/man3/EVP_rc4_40.3ossl.bz2 /usr/share/man/man3/EVP_rc4_hmac_md5.3ossl.bz2 /usr/share/man/man3/EVP_rc5_32_12_16_cbc.3ossl.bz2 /usr/share/man/man3/EVP_rc5_32_12_16_cfb.3ossl.bz2 /usr/share/man/man3/EVP_rc5_32_12_16_cfb64.3ossl.bz2 /usr/share/man/man3/EVP_rc5_32_12_16_ecb.3ossl.bz2 /usr/share/man/man3/EVP_rc5_32_12_16_ofb.3ossl.bz2 /usr/share/man/man3/EVP_ripemd160.3ossl.bz2 /usr/share/man/man3/EVP_seed_cbc.3ossl.bz2 /usr/share/man/man3/EVP_seed_cfb.3ossl.bz2 /usr/share/man/man3/EVP_seed_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_seed_ecb.3ossl.bz2 /usr/share/man/man3/EVP_seed_ofb.3ossl.bz2 /usr/share/man/man3/EVP_set_default_properties.3ossl.bz2 /usr/share/man/man3/EVP_sha1.3ossl.bz2
    /usr/share/man/man3/EVP_sha224.3ossl.bz2 /usr/share/man/man3/EVP_sha256.3ossl.bz2 /usr/share/man/man3/EVP_sha384.3ossl.bz2 /usr/share/man/man3/EVP_sha3_224.3ossl.bz2 /usr/share/man/man3/EVP_sha3_256.3ossl.bz2 /usr/share/man/man3/EVP_sha3_384.3ossl.bz2 /usr/share/man/man3/EVP_sha3_512.3ossl.bz2 /usr/share/man/man3/EVP_sha512.3ossl.bz2 /usr/share/man/man3/EVP_sha512_224.3ossl.bz2 /usr/share/man/man3/EVP_sha512_256.3ossl.bz2 /usr/share/man/man3/EVP_shake128.3ossl.bz2 /usr/share/man/man3/EVP_shake256.3ossl.bz2 /usr/share/man/man3/EVP_sm3.3ossl.bz2
    /usr/share/man/man3/EVP_sm4_cbc.3ossl.bz2 /usr/share/man/man3/EVP_sm4_cfb.3ossl.bz2 /usr/share/man/man3/EVP_sm4_cfb128.3ossl.bz2 /usr/share/man/man3/EVP_sm4_ctr.3ossl.bz2 /usr/share/man/man3/EVP_sm4_ecb.3ossl.bz2 /usr/share/man/man3/EVP_sm4_ofb.3ossl.bz2 /usr/share/man/man3/EVP_whirlpool.3ossl.bz2 /usr/share/man/man3/EXTENDED_KEY_USAGE_free.3ossl.bz2 /usr/share/man/man3/EXTENDED_KEY_USAGE_new.3ossl.bz2 /usr/share/man/man3/EXT_UTF8STRING.3ossl.bz2 /usr/share/man/man3/GENERAL_NAME.3ossl.bz2 /usr/share/man/man3/GENERAL_NAMES_free.3ossl.bz2 /usr/share/man/man3/GENERAL_NAMES_new.3ossl.bz2 /usr/share/man/man3/GENERAL_NAME_dup.3ossl.bz2 /usr/share/man/man3/GENERAL_NAME_free.3ossl.bz2 /usr/share/man/man3/GENERAL_NAME_new.3ossl.bz2 /usr/share/man/man3/GENERAL_NAME_set1_X509_NAME.3ossl.bz2 /usr/share/man/man3/GENERAL_SUBTREE_free.3ossl.bz2 /usr/share/man/man3/GENERAL_SUBTREE_new.3ossl.bz2 /usr/share/man/man3/GEN_SESSION_CB.3ossl.bz2
    /usr/share/man/man3/HMAC.3ossl.bz2
    /usr/share/man/man3/HMAC_CTX_copy.3ossl.bz2 /usr/share/man/man3/HMAC_CTX_free.3ossl.bz2 /usr/share/man/man3/HMAC_CTX_get_md.3ossl.bz2 /usr/share/man/man3/HMAC_CTX_new.3ossl.bz2 /usr/share/man/man3/HMAC_CTX_reset.3ossl.bz2 /usr/share/man/man3/HMAC_CTX_set_flags.3ossl.bz2 /usr/share/man/man3/HMAC_Final.3ossl.bz2 /usr/share/man/man3/HMAC_Init.3ossl.bz2 /usr/share/man/man3/HMAC_Init_ex.3ossl.bz2 /usr/share/man/man3/HMAC_Update.3ossl.bz2 /usr/share/man/man3/HMAC_size.3ossl.bz2 /usr/share/man/man3/IMPLEMENT_ASN1_FUNCTIONS.3ossl.bz2 /usr/share/man/man3/IMPLEMENT_EXTERN_ASN1.3ossl.bz2 /usr/share/man/man3/IMPLEMENT_LHASH_COMP_FN.3ossl.bz2 /usr/share/man/man3/IMPLEMENT_LHASH_HASH_FN.3ossl.bz2 /usr/share/man/man3/IPAddressChoice_free.3ossl.bz2 /usr/share/man/man3/IPAddressChoice_new.3ossl.bz2 /usr/share/man/man3/IPAddressFamily_free.3ossl.bz2 /usr/share/man/man3/IPAddressFamily_new.3ossl.bz2 /usr/share/man/man3/IPAddressOrRange_free.3ossl.bz2 /usr/share/man/man3/IPAddressOrRange_new.3ossl.bz2 /usr/share/man/man3/IPAddressRange_free.3ossl.bz2 /usr/share/man/man3/IPAddressRange_new.3ossl.bz2 /usr/share/man/man3/ISSUER_SIGN_TOOL_free.3ossl.bz2 /usr/share/man/man3/ISSUER_SIGN_TOOL_it.3ossl.bz2 /usr/share/man/man3/ISSUER_SIGN_TOOL_new.3ossl.bz2 /usr/share/man/man3/ISSUING_DIST_POINT_free.3ossl.bz2 /usr/share/man/man3/ISSUING_DIST_POINT_it.3ossl.bz2 /usr/share/man/man3/ISSUING_DIST_POINT_new.3ossl.bz2 /usr/share/man/man3/LHASH.3ossl.bz2 /usr/share/man/man3/LHASH_DOALL_ARG_FN_TYPE.3ossl.bz2 /usr/share/man/man3/LHASH_OF.3ossl.bz2
    /usr/share/man/man3/MD2.3ossl.bz2
    /usr/share/man/man3/MD2_Final.3ossl.bz2
    /usr/share/man/man3/MD2_Init.3ossl.bz2
    /usr/share/man/man3/MD2_Update.3ossl.bz2
    /usr/share/man/man3/MD4.3ossl.bz2
    /usr/share/man/man3/MD4_Final.3ossl.bz2
    /usr/share/man/man3/MD4_Init.3ossl.bz2
    /usr/share/man/man3/MD4_Update.3ossl.bz2
    /usr/share/man/man3/MD5.3ossl.bz2
    /usr/share/man/man3/MD5_Final.3ossl.bz2
    /usr/share/man/man3/MD5_Init.3ossl.bz2
    /usr/share/man/man3/MD5_Update.3ossl.bz2
    /usr/share/man/man3/MDC2.3ossl.bz2
    /usr/share/man/man3/MDC2_Final.3ossl.bz2 /usr/share/man/man3/MDC2_Init.3ossl.bz2 /usr/share/man/man3/MDC2_Update.3ossl.bz2 /usr/share/man/man3/NAME_CONSTRAINTS_check.3ossl.bz2 /usr/share/man/man3/NAME_CONSTRAINTS_check_CN.3ossl.bz2 /usr/share/man/man3/NAME_CONSTRAINTS_free.3ossl.bz2 /usr/share/man/man3/NAME_CONSTRAINTS_new.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_free.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_get0_authorityId.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_get0_authorityText.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_get0_authorityURL.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_new.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_set0_authorityId.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_set0_authorityText.3ossl.bz2 /usr/share/man/man3/NAMING_AUTHORITY_set0_authorityURL.3ossl.bz2 /usr/share/man/man3/NCONF_default.3ossl.bz2 /usr/share/man/man3/NCONF_free.3ossl.bz2 /usr/share/man/man3/NCONF_get0_libctx.3ossl.bz2 /usr/share/man/man3/NCONF_get_section.3ossl.bz2 /usr/share/man/man3/NCONF_get_section_names.3ossl.bz2 /usr/share/man/man3/NCONF_load.3ossl.bz2 /usr/share/man/man3/NCONF_new.3ossl.bz2 /usr/share/man/man3/NCONF_new_ex.3ossl.bz2 /usr/share/man/man3/NETSCAPE_CERT_SEQUENCE_free.3ossl.bz2 /usr/share/man/man3/NETSCAPE_CERT_SEQUENCE_new.3ossl.bz2 /usr/share/man/man3/NETSCAPE_SPKAC_free.3ossl.bz2 /usr/share/man/man3/NETSCAPE_SPKAC_new.3ossl.bz2 /usr/share/man/man3/NETSCAPE_SPKI_free.3ossl.bz2 /usr/share/man/man3/NETSCAPE_SPKI_new.3ossl.bz2 /usr/share/man/man3/NOTICEREF_free.3ossl.bz2 /usr/share/man/man3/NOTICEREF_new.3ossl.bz2 /usr/share/man/man3/OBJ_add_sigid.3ossl.bz2 /usr/share/man/man3/OBJ_cleanup.3ossl.bz2
    /usr/share/man/man3/OBJ_cmp.3ossl.bz2
    /usr/share/man/man3/OBJ_create.3ossl.bz2
    /usr/share/man/man3/OBJ_dup.3ossl.bz2 /usr/share/man/man3/OBJ_get0_data.3ossl.bz2 /usr/share/man/man3/OBJ_length.3ossl.bz2 /usr/share/man/man3/OBJ_ln2nid.3ossl.bz2 /usr/share/man/man3/OBJ_nid2ln.3ossl.bz2 /usr/share/man/man3/OBJ_nid2obj.3ossl.bz2 /usr/share/man/man3/OBJ_nid2sn.3ossl.bz2 /usr/share/man/man3/OBJ_obj2nid.3ossl.bz2 /usr/share/man/man3/OBJ_obj2txt.3ossl.bz2 /usr/share/man/man3/OBJ_sn2nid.3ossl.bz2 /usr/share/man/man3/OBJ_txt2nid.3ossl.bz2 /usr/share/man/man3/OBJ_txt2obj.3ossl.bz2 /usr/share/man/man3/OCSP_BASICRESP_free.3ossl.bz2 /usr/share/man/man3/OCSP_BASICRESP_new.3ossl.bz2 /usr/share/man/man3/OCSP_CERTID_dup.3ossl.bz2 /usr/share/man/man3/OCSP_CERTID_free.3ossl.bz2 /usr/share/man/man3/OCSP_CERTID_new.3ossl.bz2 /usr/share/man/man3/OCSP_CERTSTATUS_free.3ossl.bz2 /usr/share/man/man3/OCSP_CERTSTATUS_new.3ossl.bz2 /usr/share/man/man3/OCSP_CRLID_free.3ossl.bz2 /usr/share/man/man3/OCSP_CRLID_new.3ossl.bz2 /usr/share/man/man3/OCSP_ONEREQ_free.3ossl.bz2 /usr/share/man/man3/OCSP_ONEREQ_new.3ossl.bz2 /usr/share/man/man3/OCSP_REQINFO_free.3ossl.bz2 /usr/share/man/man3/OCSP_REQINFO_new.3ossl.bz2 /usr/share/man/man3/OCSP_REQUEST_free.3ossl.bz2 /usr/share/man/man3/OCSP_REQUEST_new.3ossl.bz2 /usr/share/man/man3/OCSP_REQ_CTX.3ossl.bz2 /usr/share/man/man3/OCSP_REQ_CTX_add1_header.3ossl.bz2 /usr/share/man/man3/OCSP_REQ_CTX_free.3ossl.bz2 /usr/share/man/man3/OCSP_REQ_CTX_i2d.3ossl.bz2 /usr/share/man/man3/OCSP_REQ_CTX_set1_req.3ossl.bz2 /usr/share/man/man3/OCSP_RESPBYTES_free.3ossl.bz2 /usr/share/man/man3/OCSP_RESPBYTES_new.3ossl.bz2 /usr/share/man/man3/OCSP_RESPDATA_free.3ossl.bz2 /usr/share/man/man3/OCSP_RESPDATA_new.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_free.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_match.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_match_ex.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_new.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_set_by_key.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_set_by_key_ex.3ossl.bz2 /usr/share/man/man3/OCSP_RESPID_set_by_name.3ossl.bz2 /usr/share/man/man3/OCSP_RESPONSE_free.3ossl.bz2 /usr/share/man/man3/OCSP_RESPONSE_new.3ossl.bz2 /usr/share/man/man3/OCSP_REVOKEDINFO_free.3ossl.bz2 /usr/share/man/man3/OCSP_REVOKEDINFO_new.3ossl.bz2 /usr/share/man/man3/OCSP_SERVICELOC_free.3ossl.bz2 /usr/share/man/man3/OCSP_SERVICELOC_new.3ossl.bz2 /usr/share/man/man3/OCSP_SIGNATURE_free.3ossl.bz2 /usr/share/man/man3/OCSP_SIGNATURE_new.3ossl.bz2 /usr/share/man/man3/OCSP_SINGLERESP_free.3ossl.bz2 /usr/share/man/man3/OCSP_SINGLERESP_new.3ossl.bz2 /usr/share/man/man3/OCSP_basic_add1_nonce.3ossl.bz2 /usr/share/man/man3/OCSP_basic_sign.3ossl.bz2 /usr/share/man/man3/OCSP_basic_sign_ctx.3ossl.bz2 /usr/share/man/man3/OCSP_basic_verify.3ossl.bz2 /usr/share/man/man3/OCSP_cert_id_new.3ossl.bz2 /usr/share/man/man3/OCSP_cert_to_id.3ossl.bz2 /usr/share/man/man3/OCSP_check_nonce.3ossl.bz2 /usr/share/man/man3/OCSP_check_validity.3ossl.bz2 /usr/share/man/man3/OCSP_copy_nonce.3ossl.bz2 /usr/share/man/man3/OCSP_id_cmp.3ossl.bz2 /usr/share/man/man3/OCSP_id_get0_info.3ossl.bz2 /usr/share/man/man3/OCSP_id_issuer_cmp.3ossl.bz2 /usr/share/man/man3/OCSP_parse_url.3ossl.bz2 /usr/share/man/man3/OCSP_request_add0_id.3ossl.bz2 /usr/share/man/man3/OCSP_request_add1_cert.3ossl.bz2 /usr/share/man/man3/OCSP_request_add1_nonce.3ossl.bz2 /usr/share/man/man3/OCSP_request_onereq_count.3ossl.bz2 /usr/share/man/man3/OCSP_request_onereq_get0.3ossl.bz2 /usr/share/man/man3/OCSP_request_sign.3ossl.bz2 /usr/share/man/man3/OCSP_resp_count.3ossl.bz2 /usr/share/man/man3/OCSP_resp_find.3ossl.bz2 /usr/share/man/man3/OCSP_resp_find_status.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_certs.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_id.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_produced_at.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_respdata.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_signature.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_signer.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get0_tbs_sigalg.3ossl.bz2 /usr/share/man/man3/OCSP_resp_get1_id.3ossl.bz2 /usr/share/man/man3/OCSP_response_create.3ossl.bz2 /usr/share/man/man3/OCSP_response_get1_basic.3ossl.bz2 /usr/share/man/man3/OCSP_response_status.3ossl.bz2 /usr/share/man/man3/OCSP_sendreq_bio.3ossl.bz2 /usr/share/man/man3/OCSP_sendreq_nbio.3ossl.bz2 /usr/share/man/man3/OCSP_sendreq_new.3ossl.bz2 /usr/share/man/man3/OCSP_set_max_response_length.3ossl.bz2 /usr/share/man/man3/OCSP_single_get0_status.3ossl.bz2 /usr/share/man/man3/OPENSSL_Applink.3ossl.bz2 /usr/share/man/man3/OPENSSL_FILE.3ossl.bz2 /usr/share/man/man3/OPENSSL_FUNC.3ossl.bz2 /usr/share/man/man3/OPENSSL_INIT_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_INIT_new.3ossl.bz2 /usr/share/man/man3/OPENSSL_INIT_set_config_appname.3ossl.bz2 /usr/share/man/man3/OPENSSL_INIT_set_config_file_flags.3ossl.bz2 /usr/share/man/man3/OPENSSL_INIT_set_config_filename.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_COMPFUNC.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_DOALL_FUNC.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_HASHFUNC.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_delete.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_doall.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_doall_arg.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_doall_arg_thunk.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_error.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_flush.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_get_down_load.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_insert.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_new.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_node_stats.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_node_stats_bio.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_node_usage_stats.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_node_usage_stats_bio.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_num_items.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_retrieve.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_set_down_load.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_set_thunks.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_stats.3ossl.bz2 /usr/share/man/man3/OPENSSL_LH_stats_bio.3ossl.bz2 /usr/share/man/man3/OPENSSL_LINE.3ossl.bz2 /usr/share/man/man3/OPENSSL_MALLOC_FAILURES.3ossl.bz2 /usr/share/man/man3/OPENSSL_MALLOC_FD.3ossl.bz2 /usr/share/man/man3/OPENSSL_MALLOC_SEED.3ossl.bz2 /usr/share/man/man3/OPENSSL_MSTR.3ossl.bz2 /usr/share/man/man3/OPENSSL_MSTR_HELPER.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_BUILD_METADATA.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_MAJOR.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_MINOR.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_NUMBER.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_PATCH.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_PREREQ.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_PRE_RELEASE.3ossl.bz2 /usr/share/man/man3/OPENSSL_VERSION_TEXT.3ossl.bz2 /usr/share/man/man3/OPENSSL_aligned_alloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_aligned_alloc_array.3ossl.bz2 /usr/share/man/man3/OPENSSL_armcap.3ossl.bz2 /usr/share/man/man3/OPENSSL_atexit.3ossl.bz2 /usr/share/man/man3/OPENSSL_buf2hexstr.3ossl.bz2 /usr/share/man/man3/OPENSSL_buf2hexstr_ex.3ossl.bz2 /usr/share/man/man3/OPENSSL_calloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_cipher_name.3ossl.bz2 /usr/share/man/man3/OPENSSL_cleanse.3ossl.bz2 /usr/share/man/man3/OPENSSL_cleanup.3ossl.bz2 /usr/share/man/man3/OPENSSL_clear_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_clear_realloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_clear_realloc_array.3ossl.bz2 /usr/share/man/man3/OPENSSL_config.3ossl.bz2 /usr/share/man/man3/OPENSSL_fork_child.3ossl.bz2 /usr/share/man/man3/OPENSSL_fork_parent.3ossl.bz2 /usr/share/man/man3/OPENSSL_fork_prepare.3ossl.bz2 /usr/share/man/man3/OPENSSL_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_gmtime.3ossl.bz2 /usr/share/man/man3/OPENSSL_gmtime_adj.3ossl.bz2 /usr/share/man/man3/OPENSSL_gmtime_diff.3ossl.bz2 /usr/share/man/man3/OPENSSL_hexchar2int.3ossl.bz2 /usr/share/man/man3/OPENSSL_hexstr2buf.3ossl.bz2 /usr/share/man/man3/OPENSSL_hexstr2buf_ex.3ossl.bz2 /usr/share/man/man3/OPENSSL_ia32cap.3ossl.bz2 /usr/share/man/man3/OPENSSL_info.3ossl.bz2 /usr/share/man/man3/OPENSSL_init_crypto.3ossl.bz2 /usr/share/man/man3/OPENSSL_init_ssl.3ossl.bz2 /usr/share/man/man3/OPENSSL_instrument_bus.3ossl.bz2 /usr/share/man/man3/OPENSSL_instrument_bus2.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_builtin_modules.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_u16_be.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_u16_le.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_u32_be.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_u32_le.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_u64_be.3ossl.bz2 /usr/share/man/man3/OPENSSL_load_u64_le.3ossl.bz2 /usr/share/man/man3/OPENSSL_malloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_malloc_array.3ossl.bz2 /usr/share/man/man3/OPENSSL_malloc_init.3ossl.bz2 /usr/share/man/man3/OPENSSL_mem_debug_pop.3ossl.bz2 /usr/share/man/man3/OPENSSL_mem_debug_push.3ossl.bz2 /usr/share/man/man3/OPENSSL_memdup.3ossl.bz2 /usr/share/man/man3/OPENSSL_no_config.3ossl.bz2 /usr/share/man/man3/OPENSSL_ppccap.3ossl.bz2 /usr/share/man/man3/OPENSSL_realloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_realloc_array.3ossl.bz2 /usr/share/man/man3/OPENSSL_riscvcap.3ossl.bz2 /usr/share/man/man3/OPENSSL_s390xcap.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_actual_size.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_calloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_clear_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_malloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_malloc_array.3ossl.bz2 /usr/share/man/man3/OPENSSL_secure_zalloc.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_deep_copy.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_delete.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_delete_ptr.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_dup.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_find.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_find_all.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_find_ex.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_insert.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_is_sorted.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_new.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_new_null.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_new_reserve.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_num.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_pop.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_pop_free.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_push.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_reserve.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_set.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_set_cmp_func.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_set_thunks.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_shift.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_sort.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_unshift.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_value.3ossl.bz2 /usr/share/man/man3/OPENSSL_sk_zero.3ossl.bz2 /usr/share/man/man3/OPENSSL_store_u16_be.3ossl.bz2 /usr/share/man/man3/OPENSSL_store_u16_le.3ossl.bz2 /usr/share/man/man3/OPENSSL_store_u32_be.3ossl.bz2 /usr/share/man/man3/OPENSSL_store_u32_le.3ossl.bz2 /usr/share/man/man3/OPENSSL_store_u64_be.3ossl.bz2 /usr/share/man/man3/OPENSSL_store_u64_le.3ossl.bz2 /usr/share/man/man3/OPENSSL_strcasecmp.3ossl.bz2 /usr/share/man/man3/OPENSSL_strdup.3ossl.bz2 /usr/share/man/man3/OPENSSL_strlcat.3ossl.bz2 /usr/share/man/man3/OPENSSL_strlcpy.3ossl.bz2 /usr/share/man/man3/OPENSSL_strncasecmp.3ossl.bz2 /usr/share/man/man3/OPENSSL_strndup.3ossl.bz2 /usr/share/man/man3/OPENSSL_strtoul.3ossl.bz2 /usr/share/man/man3/OPENSSL_thread_stop.3ossl.bz2 /usr/share/man/man3/OPENSSL_thread_stop_ex.3ossl.bz2 /usr/share/man/man3/OPENSSL_version_build_metadata.3ossl.bz2 /usr/share/man/man3/OPENSSL_version_major.3ossl.bz2 /usr/share/man/man3/OPENSSL_version_minor.3ossl.bz2 /usr/share/man/man3/OPENSSL_version_patch.3ossl.bz2 /usr/share/man/man3/OPENSSL_version_pre_release.3ossl.bz2 /usr/share/man/man3/OPENSSL_zalloc.3ossl.bz2 /usr/share/man/man3/OSSL_AA_DIST_POINT_free.3ossl.bz2 /usr/share/man/man3/OSSL_AA_DIST_POINT_it.3ossl.bz2 /usr/share/man/man3/OSSL_AA_DIST_POINT_new.3ossl.bz2 /usr/share/man/man3/OSSL_ALGORITHM.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_CHOICE_free.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_CHOICE_it.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_CHOICE_new.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_ITEM_free.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_ITEM_it.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_ITEM_new.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_ALLOWED_ATTRIBUTES_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATAV_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATAV_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATAV_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTES_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTES_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTES_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_DESCRIPTOR_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_DESCRIPTOR_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_DESCRIPTOR_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_MAPPINGS_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_MAPPINGS_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_MAPPINGS_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_MAPPING_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_MAPPING_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_MAPPING_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_TYPE_MAPPING_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_TYPE_MAPPING_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_TYPE_MAPPING_new.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_VALUE_MAPPING_free.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_VALUE_MAPPING_it.3ossl.bz2 /usr/share/man/man3/OSSL_ATTRIBUTE_VALUE_MAPPING_new.3ossl.bz2 /usr/share/man/man3/OSSL_AUTHORITY_ATTRIBUTE_ID_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_AUTHORITY_ATTRIBUTE_ID_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_AUTHORITY_ATTRIBUTE_ID_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_BASIC_ATTR_CONSTRAINTS_free.3ossl.bz2 /usr/share/man/man3/OSSL_BASIC_ATTR_CONSTRAINTS_it.3ossl.bz2 /usr/share/man/man3/OSSL_BASIC_ATTR_CONSTRAINTS_new.3ossl.bz2 /usr/share/man/man3/OSSL_CALLBACK.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAVS.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAVS_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAVS_it.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAVS_new.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_create.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_get0_algId.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_get0_type.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_get0_value.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_get_rsaKeyLen.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_new_algId.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_new_rsaKeyLen.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_push1.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ATAV_set0.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CR.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CRLSTATUS_create.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CRLSTATUS_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CRLSTATUS_get0.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CRLSTATUS_new1.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_build_cert_chain.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_geninfo_ITAVs.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_libctx.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_newCert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_newPkey.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_propq.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_statusString.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_trusted.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_trustedStore.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_untrusted.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get0_validatedSrvCert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get1_caPubs.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get1_extraCertsIn.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get1_newChain.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get_certConf_cb_arg.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get_failInfoCode.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get_http_cb_arg.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get_option.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get_status.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_get_transfer_cb_arg.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_print_errors.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_push0_geninfo_ITAV.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_push0_genm_ITAV.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_push0_policy.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_push1_subjectAltName.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_reinit.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_reqExtensions_have_SAN.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_reset_geninfo_ITAVs.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_server_perform.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set0_newPkey.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set0_reqExtensions.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set0_trusted.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set0_trustedStore.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_cert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_expected_sender.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_extraCertsOut.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_issuer.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_no_proxy.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_oldCert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_p10CSR.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_pkey.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_proxy.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_recipient.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_referenceValue.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_secretValue.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_senderNonce.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_serialNumber.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_server.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_serverPath.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_srvCert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_subjectName.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_transactionID.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set1_untrusted.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_certConf_cb.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_certConf_cb_arg.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_http_cb.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_http_cb_arg.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_log_cb.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_log_verbosity.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_option.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_serverPort.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_transfer_cb.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_set_transfer_cb_arg.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_setup_CRM.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_CTX_snprint_PKIStatus.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_HDR_get0_geninfo_ITAVs.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_HDR_get0_recipNonce.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_HDR_get0_transactionID.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_IR.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_create.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_caCerts.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_certProfile.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_crlStatusList.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_crls.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_rootCaCert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_rootCaKeyUpdate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_type.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get0_value.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_get1_certReqTemplate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new0_certProfile.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new0_certReqTemplate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new0_crlStatusList.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new_caCerts.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new_crls.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new_rootCaCert.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_new_rootCaKeyUpdate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_push0_stack_item.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_ITAV_set0.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_KUR.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_ALERT.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_CRIT.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_DEBUG.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_EMERG.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_ERR.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_INFO.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_NOTICE.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_TRACE.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_LOG_WARNING.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_get0_certreq_publickey.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_get0_header.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_get_bodytype.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_http_perform.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_it.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_read.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_update_recipNonce.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_update_transactionID.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_MSG_write.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_P10CR.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKIHEADER_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKIHEADER_it.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKIHEADER_new.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKISI_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKISI_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKISI_it.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKISI_new.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_PKISTATUS_it.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_get0_cmp_ctx.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_get0_custom_ctx.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_init.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_init_trans.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_set_accept_raverified.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_set_accept_unprotected.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_set_grant_implicit_confirm.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_CTX_set_send_unprotected_errors.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_certConf_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_cert_request_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_clean_transaction_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_delayed_delivery_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_error_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_genm_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_pollReq_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_process_request.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_SRV_rr_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_STATUSINFO_new.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_certConf_cb.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_certConf_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_CR_ses.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_GENM_ses.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_IR_ses.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_KUR_ses.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_P10CR_ses.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_RR_ses.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_exec_certreq.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_get1_caCerts.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_get1_certReqTemplate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_get1_crlUpdate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_get1_rootCaKeyUpdate.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_log_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_log_close.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_log_open.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_print_errors_cb.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_print_to_bio.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_severity.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_snprint_PKIStatusInfo.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_transfer_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_try_certreq.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_validate_cert_path.3ossl.bz2 /usr/share/man/man3/OSSL_CMP_validate_msg.3ossl.bz2 /usr/share/man/man3/OSSL_CORE_MAKE_FUNC.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ATTRIBUTETYPEANDVALUE_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ATTRIBUTETYPEANDVALUE_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_gen.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_get0_issuer.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_get0_serialNumber.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTID_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_fill.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_get0_extensions.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_get0_issuer.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_get0_publicKey.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_get0_serialNumber.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_get0_subject.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_CERTTEMPLATE_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDKEY_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDKEY_get1_encCert.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDKEY_get1_pkey.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDKEY_init_envdata.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDKEY_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDKEY_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDVALUE_decrypt.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDVALUE_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDVALUE_get1_encCert.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDVALUE_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_ENCRYPTEDVALUE_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSGS_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSGS_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSGS_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSGS_verify_popo.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_PKIPublicationInfo_push0_SinglePubInfo.3ossl.bz2
    /usr/share/man/man3/OSSL_CRMF_MSG_centralkeygen_requested.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_create_popo.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_dup.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regCtrl_authenticator.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regCtrl_oldCertID.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regCtrl_pkiPublicationInfo.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regCtrl_protocolEncrKey.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regCtrl_regToken.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regInfo_certReq.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_regInfo_utf8Pairs.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get0_tmpl.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_get_certReqId.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_push0_extension.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set0_SinglePubInfo.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set0_extensions.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set0_validity.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regCtrl_authenticator.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regCtrl_oldCertID.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regCtrl_pkiPublicationInfo.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regCtrl_protocolEncrKey.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regCtrl_regToken.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regInfo_certReq.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set1_regInfo_utf8Pairs.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set_PKIPublicationInfo_action.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_MSG_set_certReqId.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_PBMPARAMETER_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_PBMPARAMETER_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_PBMPARAMETER_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_PKIPUBLICATIONINFO_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_PKIPUBLICATIONINFO_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_PKIPUBLICATIONINFO_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_SINGLEPUBINFO_free.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_SINGLEPUBINFO_it.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_SINGLEPUBINFO_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_pbm_new.3ossl.bz2 /usr/share/man/man3/OSSL_CRMF_pbmp_new.3ossl.bz2 /usr/share/man/man3/OSSL_DAY_TIME_BAND_free.3ossl.bz2 /usr/share/man/man3/OSSL_DAY_TIME_BAND_it.3ossl.bz2 /usr/share/man/man3/OSSL_DAY_TIME_BAND_new.3ossl.bz2 /usr/share/man/man3/OSSL_DAY_TIME_free.3ossl.bz2 /usr/share/man/man3/OSSL_DAY_TIME_it.3ossl.bz2 /usr/share/man/man3/OSSL_DAY_TIME_new.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CLEANUP.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CONSTRUCT.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_add_decoder.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_add_extra.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_get_cleanup.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_get_construct.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_get_construct_data.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_get_num_decoders.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_new_for_pkey.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_cleanup.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_construct.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_construct_data.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_input_structure.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_input_type.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_params.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_passphrase.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_passphrase_cb.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_passphrase_ui.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_pem_password_cb.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_CTX_set_selection.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_INSTANCE.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_INSTANCE_get_decoder.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_INSTANCE_get_decoder_ctx.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_INSTANCE_get_input_structure.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_INSTANCE_get_input_type.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_do_all_provided.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_export.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_fetch.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_free.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_from_bio.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_from_data.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_from_fp.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_get0_description.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_get0_name.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_get0_properties.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_get0_provider.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_get_params.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_gettable_params.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_is_a.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_names_do_all.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/OSSL_DECODER_up_ref.3ossl.bz2 /usr/share/man/man3/OSSL_DISPATCH.3ossl.bz2 /usr/share/man/man3/OSSL_DISPATCH_END.3ossl.bz2 /usr/share/man/man3/OSSL_EC_curve_nid2name.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CLEANUP.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CONSTRUCT.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_add_encoder.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_add_extra.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_get_num_encoders.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_new_for_pkey.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_cipher.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_cleanup.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_construct.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_construct_data.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_output_structure.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_output_type.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_params.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_passphrase.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_passphrase_cb.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_passphrase_ui.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_pem_password_cb.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_CTX_set_selection.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_INSTANCE.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_INSTANCE_get_encoder.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_INSTANCE_get_encoder_ctx.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_INSTANCE_get_output_structure.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_INSTANCE_get_output_type.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_do_all_provided.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_fetch.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_free.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_get0_description.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_get0_name.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_get0_properties.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_get0_provider.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_get_params.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_gettable_params.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_is_a.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_names_do_all.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_to_bio.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_to_data.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_to_fp.3ossl.bz2 /usr/share/man/man3/OSSL_ENCODER_up_ref.3ossl.bz2 /usr/share/man/man3/OSSL_ERR_STATE_free.3ossl.bz2 /usr/share/man/man3/OSSL_ERR_STATE_new.3ossl.bz2 /usr/share/man/man3/OSSL_ERR_STATE_restore.3ossl.bz2 /usr/share/man/man3/OSSL_ERR_STATE_save.3ossl.bz2 /usr/share/man/man3/OSSL_ERR_STATE_save_to_mark.3ossl.bz2 /usr/share/man/man3/OSSL_ESS_check_signing_certs.3ossl.bz2 /usr/share/man/man3/OSSL_ESS_signing_cert_new_init.3ossl.bz2 /usr/share/man/man3/OSSL_ESS_signing_cert_v2_new_init.3ossl.bz2 /usr/share/man/man3/OSSL_FUNC_SSL_QUIC_TLS_alert_fn.3ossl.bz2 /usr/share/man/man3/OSSL_FUNC_SSL_QUIC_TLS_crypto_recv_rcd_fn.3ossl.bz2 /usr/share/man/man3/OSSL_FUNC_SSL_QUIC_TLS_crypto_release_rcd_fn.3ossl.bz2 /usr/share/man/man3/OSSL_FUNC_SSL_QUIC_TLS_crypto_send_fn.3ossl.bz2 /usr/share/man/man3/OSSL_FUNC_SSL_QUIC_TLS_got_transport_params_fn.3ossl.bz2 /usr/share/man/man3/OSSL_FUNC_SSL_QUIC_TLS_yield_secret_fn.3ossl.bz2 /usr/share/man/man3/OSSL_GENERAL_NAMES_print.3ossl.bz2 /usr/share/man/man3/OSSL_HASH_free.3ossl.bz2 /usr/share/man/man3/OSSL_HASH_it.3ossl.bz2 /usr/share/man/man3/OSSL_HASH_new.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_get_seq.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_set1_authpriv.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_set1_authpub.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_set1_ikme.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_set1_psk.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_CTX_set_seq.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_decap.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_encap.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_export.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_get_ciphertext_size.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_get_grease_value.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_get_public_encap_size.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_get_recommended_ikmelen.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_keygen.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_open.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_seal.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_str2suite.3ossl.bz2 /usr/share/man/man3/OSSL_HPKE_suite_check.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_add1_header.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_exchange.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_get0_mem_bio.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_get_resp_len.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_nbio.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_nbio_d2i.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_set1_req.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_set_expected.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_set_max_response_hdr_lines.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_set_max_response_length.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_REQ_CTX_set_request_line.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_adapt_proxy.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_bio_cb_t.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_close.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_exchange.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_get.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_is_alive.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_open.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_parse_url.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_proxy_connect.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_set1_request.3ossl.bz2 /usr/share/man/man3/OSSL_HTTP_transfer.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_VALUE_free.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_VALUE_it.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_VALUE_new.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_add1_value.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_get0_policyAuthority.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_get0_value.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_get_value_num.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_print.3ossl.bz2 /usr/share/man/man3/OSSL_IETF_ATTR_SYNTAX_set0_policyAuthority.3ossl.bz2 /usr/share/man/man3/OSSL_INDICATOR_get_callback.3ossl.bz2 /usr/share/man/man3/OSSL_INDICATOR_set_callback.3ossl.bz2 /usr/share/man/man3/OSSL_INFO_SYNTAX_POINTER_free.3ossl.bz2 /usr/share/man/man3/OSSL_INFO_SYNTAX_POINTER_it.3ossl.bz2 /usr/share/man/man3/OSSL_INFO_SYNTAX_POINTER_new.3ossl.bz2 /usr/share/man/man3/OSSL_INFO_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_INFO_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_INFO_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_free.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_get0_issuer.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_get0_issuerUID.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_get0_serial.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_new.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_set1_issuer.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_set1_issuerUID.3ossl.bz2 /usr/share/man/man3/OSSL_ISSUER_SERIAL_set1_serial.3ossl.bz2 /usr/share/man/man3/OSSL_ITEM.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_free.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_get0_global_default.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_get_conf_diagnostics.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_get_data.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_load_config.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_new.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_new_child.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_new_from_dispatch.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_set0_default.3ossl.bz2 /usr/share/man/man3/OSSL_LIB_CTX_set_conf_diagnostics.3ossl.bz2 /usr/share/man/man3/OSSL_NAMED_DAY_free.3ossl.bz2 /usr/share/man/man3/OSSL_NAMED_DAY_it.3ossl.bz2 /usr/share/man/man3/OSSL_NAMED_DAY_new.3ossl.bz2 /usr/share/man/man3/OSSL_OBJECT_DIGEST_INFO_free.3ossl.bz2 /usr/share/man/man3/OSSL_OBJECT_DIGEST_INFO_get0_digest.3ossl.bz2 /usr/share/man/man3/OSSL_OBJECT_DIGEST_INFO_new.3ossl.bz2 /usr/share/man/man3/OSSL_OBJECT_DIGEST_INFO_set1_digest.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_free.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_new.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_BN.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_BN_pad.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_double.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_int.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_int32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_int64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_long.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_octet_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_octet_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_size_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_time_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_uint.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_uint32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_uint64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_ulong.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_utf8_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_push_utf8_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BLD_to_param.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_BN.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_DEFN.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_END.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_UNMODIFIED.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_allocate_from_text.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_BN.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_double.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_end.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_int.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_int32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_int64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_long.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_octet_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_octet_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_size_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_time_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_uint.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_uint32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_uint64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_ulong.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_utf8_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_construct_utf8_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_double.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_dup.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_free.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_BN.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_double.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_int.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_int32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_int64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_long.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_octet_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_octet_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_octet_string_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_size_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_time_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_uint.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_uint32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_uint64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_ulong.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_utf8_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_utf8_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_get_utf8_string_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_int.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_int32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_int64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_locate.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_locate_const.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_long.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_merge.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_modified.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_octet_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_octet_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_print_to_bio.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_BN.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_all_unmodified.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_double.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_int.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_int32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_int64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_long.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_octet_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_octet_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_octet_string_or_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_size_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_time_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_uint.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_uint32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_uint64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_ulong.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_utf8_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_set_utf8_string.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_size_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_time_t.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_uint.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_uint32.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_uint64.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_ulong.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_utf8_ptr.3ossl.bz2 /usr/share/man/man3/OSSL_PARAM_utf8_string.3ossl.bz2 /usr/share/man/man3/OSSL_PASSPHRASE_CALLBACK.3ossl.bz2 /usr/share/man/man3/OSSL_PRIVILEGE_POLICY_ID_free.3ossl.bz2 /usr/share/man/man3/OSSL_PRIVILEGE_POLICY_ID_it.3ossl.bz2 /usr/share/man/man3/OSSL_PRIVILEGE_POLICY_ID_new.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_add_builtin.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_add_conf_parameter.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_available.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_conf_get_bool.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_do_all.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get0_default_search_path.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get0_dispatch.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get0_name.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get0_provider_ctx.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get_capabilities.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get_conf_parameters.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_get_params.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_gettable_params.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_load.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_load_ex.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_query_operation.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_self_test.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_set_default_search_path.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_try_load.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_try_load_ex.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_unload.3ossl.bz2 /usr/share/man/man3/OSSL_PROVIDER_unquery_operation.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_AEAD_LIMIT_REACHED.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_APPLICATION_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_CONNECTION_ID_LIMIT_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_CONNECTION_REFUSED.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_CRYPTO_BUFFER_EXCEEDED.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_CRYPTO_ERR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_CRYPTO_ERR_BEGIN.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_CRYPTO_ERR_END.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_FINAL_SIZE_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_FLOW_CONTROL_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_FRAME_ENCODING_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_INTERNAL_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_INVALID_TOKEN.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_KEY_UPDATE_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_NO_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_NO_VIABLE_PATH.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_PROTOCOL_VIOLATION.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_STREAM_LIMIT_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_STREAM_STATE_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_ERR_TRANSPORT_PARAMETER_ERROR.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_LOCAL_ERR_IDLE_TIMEOUT.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_client_method.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_client_thread_method.3ossl.bz2 /usr/share/man/man3/OSSL_QUIC_server_method.3ossl.bz2 /usr/share/man/man3/OSSL_ROLE_SPEC_CERT_ID_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_ROLE_SPEC_CERT_ID_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_ROLE_SPEC_CERT_ID_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_ROLE_SPEC_CERT_ID_free.3ossl.bz2 /usr/share/man/man3/OSSL_ROLE_SPEC_CERT_ID_it.3ossl.bz2 /usr/share/man/man3/OSSL_ROLE_SPEC_CERT_ID_new.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_free.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_get_callback.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_new.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_onbegin.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_oncorrupt_byte.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_onend.3ossl.bz2 /usr/share/man/man3/OSSL_SELF_TEST_set_callback.3ossl.bz2 /usr/share/man/man3/OSSL_STACK_OF_X509_free.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_CTX.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_free.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_CERT.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_CRL.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_NAME.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_NAME_description.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_PARAMS.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_PKEY.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_PUBKEY.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get0_data.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_CERT.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_CRL.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_NAME.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_NAME_description.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_PARAMS.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_PKEY.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get1_PUBKEY.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_get_type.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new_CERT.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new_CRL.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new_NAME.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new_PARAMS.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new_PKEY.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_new_PUBKEY.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_set0_NAME_description.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_INFO_type_string.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_CTX.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_do_all_provided.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_fetch.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_free.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_get0_description.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_get0_engine.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_get0_properties.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_get0_provider.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_get0_scheme.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_is_a.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_names_do_all.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_new.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_attach.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_close.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_ctrl.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_eof.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_error.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_expect.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_find.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_load.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_open.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_set_open_ex.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_settable_ctx_params.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_LOADER_up_ref.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_by_alias.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_by_issuer_serial.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_by_key_fingerprint.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_by_name.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_free.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_get0_bytes.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_get0_digest.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_get0_name.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_get0_serial.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_get0_string.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_SEARCH_get_type.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_attach.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_attach_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_close.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_close_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_ctrl.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_ctrl_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_delete.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_eof.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_eof_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_error.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_error_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_expect.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_expect_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_find.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_find_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_load.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_load_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_open.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_open_ex.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_open_ex_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_open_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_post_process_info_fn.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_register_loader.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_supports_search.3ossl.bz2 /usr/share/man/man3/OSSL_STORE_unregister_loader.3ossl.bz2 /usr/share/man/man3/OSSL_TARGETING_INFORMATION_free.3ossl.bz2 /usr/share/man/man3/OSSL_TARGETING_INFORMATION_it.3ossl.bz2 /usr/share/man/man3/OSSL_TARGETING_INFORMATION_new.3ossl.bz2 /usr/share/man/man3/OSSL_TARGETS_free.3ossl.bz2 /usr/share/man/man3/OSSL_TARGETS_it.3ossl.bz2 /usr/share/man/man3/OSSL_TARGETS_new.3ossl.bz2 /usr/share/man/man3/OSSL_TARGET_CERT_free.3ossl.bz2 /usr/share/man/man3/OSSL_TARGET_CERT_it.3ossl.bz2 /usr/share/man/man3/OSSL_TARGET_CERT_new.3ossl.bz2 /usr/share/man/man3/OSSL_TARGET_free.3ossl.bz2 /usr/share/man/man3/OSSL_TARGET_it.3ossl.bz2 /usr/share/man/man3/OSSL_TARGET_new.3ossl.bz2 /usr/share/man/man3/OSSL_THREAD_SUPPORT_FLAG_DEFAULT_SPAWN.3ossl.bz2 /usr/share/man/man3/OSSL_THREAD_SUPPORT_FLAG_THREAD_POOL.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_PERIOD_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_PERIOD_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_PERIOD_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_ABSOLUTE_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_ABSOLUTE_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_ABSOLUTE_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_DAY_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_DAY_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_DAY_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_MONTH_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_MONTH_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_MONTH_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_TIME_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_TIME_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_TIME_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_WEEKS_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_WEEKS_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_WEEKS_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_X_DAY_OF_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_X_DAY_OF_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_X_DAY_OF_new.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_free.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_it.3ossl.bz2 /usr/share/man/man3/OSSL_TIME_SPEC_new.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE1.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE2.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE3.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE4.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE5.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE6.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE7.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE8.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE9.3ossl.bz2 /usr/share/man/man3/OSSL_TRACEV.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE_BEGIN.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE_CANCEL.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE_ENABLED.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE_END.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE_STRING.3ossl.bz2 /usr/share/man/man3/OSSL_TRACE_STRING_MAX.3ossl.bz2 /usr/share/man/man3/OSSL_USER_NOTICE_SYNTAX_free.3ossl.bz2 /usr/share/man/man3/OSSL_USER_NOTICE_SYNTAX_it.3ossl.bz2 /usr/share/man/man3/OSSL_USER_NOTICE_SYNTAX_new.3ossl.bz2 /usr/share/man/man3/OSSL_default_cipher_list.3ossl.bz2 /usr/share/man/man3/OSSL_default_ciphersuites.3ossl.bz2 /usr/share/man/man3/OSSL_get_max_threads.3ossl.bz2 /usr/share/man/man3/OSSL_get_thread_support_flags.3ossl.bz2 /usr/share/man/man3/OSSL_parse_url.3ossl.bz2 /usr/share/man/man3/OSSL_set_max_threads.3ossl.bz2 /usr/share/man/man3/OSSL_sleep.3ossl.bz2 /usr/share/man/man3/OSSL_trace_begin.3ossl.bz2 /usr/share/man/man3/OSSL_trace_cb.3ossl.bz2 /usr/share/man/man3/OSSL_trace_enabled.3ossl.bz2 /usr/share/man/man3/OSSL_trace_end.3ossl.bz2 /usr/share/man/man3/OSSL_trace_get_category_name.3ossl.bz2 /usr/share/man/man3/OSSL_trace_get_category_num.3ossl.bz2 /usr/share/man/man3/OSSL_trace_set_callback.3ossl.bz2 /usr/share/man/man3/OSSL_trace_set_channel.3ossl.bz2 /usr/share/man/man3/OSSL_trace_set_prefix.3ossl.bz2 /usr/share/man/man3/OSSL_trace_set_suffix.3ossl.bz2 /usr/share/man/man3/OSSL_trace_string.3ossl.bz2 /usr/share/man/man3/OTHERNAME_free.3ossl.bz2 /usr/share/man/man3/OTHERNAME_new.3ossl.bz2 /usr/share/man/man3/OpenSSL_add_all_algorithms.3ossl.bz2 /usr/share/man/man3/OpenSSL_add_all_ciphers.3ossl.bz2 /usr/share/man/man3/OpenSSL_add_all_digests.3ossl.bz2 /usr/share/man/man3/OpenSSL_add_ssl_algorithms.3ossl.bz2 /usr/share/man/man3/OpenSSL_version.3ossl.bz2 /usr/share/man/man3/OpenSSL_version_num.3ossl.bz2 /usr/share/man/man3/PBE2PARAM_free.3ossl.bz2 /usr/share/man/man3/PBE2PARAM_new.3ossl.bz2 /usr/share/man/man3/PBEPARAM_free.3ossl.bz2 /usr/share/man/man3/PBEPARAM_new.3ossl.bz2 /usr/share/man/man3/PBKDF2PARAM_free.3ossl.bz2 /usr/share/man/man3/PBKDF2PARAM_new.3ossl.bz2 /usr/share/man/man3/PBMAC1PARAM_free.3ossl.bz2 /usr/share/man/man3/PBMAC1PARAM_it.3ossl.bz2 /usr/share/man/man3/PBMAC1PARAM_new.3ossl.bz2 /usr/share/man/man3/PBMAC1_get1_pbkdf2_param.3ossl.bz2 /usr/share/man/man3/PEM_ASN1_write.3ossl.bz2 /usr/share/man/man3/PEM_ASN1_write_bio.3ossl.bz2 /usr/share/man/man3/PEM_ASN1_write_bio_ctx.3ossl.bz2 /usr/share/man/man3/PEM_FLAG_EAY_COMPATIBLE.3ossl.bz2 /usr/share/man/man3/PEM_FLAG_ONLY_B64.3ossl.bz2 /usr/share/man/man3/PEM_FLAG_SECURE.3ossl.bz2 /usr/share/man/man3/PEM_X509_INFO_read.3ossl.bz2 /usr/share/man/man3/PEM_X509_INFO_read_bio.3ossl.bz2 /usr/share/man/man3/PEM_X509_INFO_read_bio_ex.3ossl.bz2 /usr/share/man/man3/PEM_X509_INFO_read_ex.3ossl.bz2 /usr/share/man/man3/PEM_bytes_read_bio.3ossl.bz2 /usr/share/man/man3/PEM_bytes_read_bio_secmem.3ossl.bz2 /usr/share/man/man3/PEM_do_header.3ossl.bz2 /usr/share/man/man3/PEM_get_EVP_CIPHER_INFO.3ossl.bz2 /usr/share/man/man3/PEM_read.3ossl.bz2 /usr/share/man/man3/PEM_read_CMS.3ossl.bz2 /usr/share/man/man3/PEM_read_DHparams.3ossl.bz2 /usr/share/man/man3/PEM_read_DSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_DSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_DSAparams.3ossl.bz2 /usr/share/man/man3/PEM_read_ECPKParameters.3ossl.bz2 /usr/share/man/man3/PEM_read_ECPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_EC_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_NETSCAPE_CERT_SEQUENCE.3ossl.bz2 /usr/share/man/man3/PEM_read_PKCS7.3ossl.bz2 /usr/share/man/man3/PEM_read_PKCS8.3ossl.bz2 /usr/share/man/man3/PEM_read_PKCS8_PRIV_KEY_INFO.3ossl.bz2 /usr/share/man/man3/PEM_read_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_PUBKEY_ex.3ossl.bz2 /usr/share/man/man3/PEM_read_PrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_PrivateKey_ex.3ossl.bz2 /usr/share/man/man3/PEM_read_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_RSAPublicKey.3ossl.bz2 /usr/share/man/man3/PEM_read_RSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_SSL_SESSION.3ossl.bz2 /usr/share/man/man3/PEM_read_X509.3ossl.bz2 /usr/share/man/man3/PEM_read_X509_ACERT.3ossl.bz2 /usr/share/man/man3/PEM_read_X509_AUX.3ossl.bz2 /usr/share/man/man3/PEM_read_X509_CRL.3ossl.bz2 /usr/share/man/man3/PEM_read_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_X509_REQ.3ossl.bz2 /usr/share/man/man3/PEM_read_bio.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_CMS.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_DHparams.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_DSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_DSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_DSAparams.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_ECPKParameters.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_EC_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_NETSCAPE_CERT_SEQUENCE.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PKCS7.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PKCS8.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PKCS8_PRIV_KEY_INFO.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PUBKEY_ex.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_Parameters.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_Parameters_ex.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_PrivateKey_ex.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_RSAPublicKey.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_RSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_SSL_SESSION.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_X509.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_X509_ACERT.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_X509_AUX.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_X509_CRL.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_X509_REQ.3ossl.bz2 /usr/share/man/man3/PEM_read_bio_ex.3ossl.bz2 /usr/share/man/man3/PEM_write.3ossl.bz2 /usr/share/man/man3/PEM_write_CMS.3ossl.bz2 /usr/share/man/man3/PEM_write_DHparams.3ossl.bz2 /usr/share/man/man3/PEM_write_DHxparams.3ossl.bz2 /usr/share/man/man3/PEM_write_DSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_DSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_DSAparams.3ossl.bz2 /usr/share/man/man3/PEM_write_ECPKParameters.3ossl.bz2 /usr/share/man/man3/PEM_write_ECPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_EC_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_NETSCAPE_CERT_SEQUENCE.3ossl.bz2 /usr/share/man/man3/PEM_write_PKCS7.3ossl.bz2 /usr/share/man/man3/PEM_write_PKCS8.3ossl.bz2 /usr/share/man/man3/PEM_write_PKCS8PrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_PKCS8PrivateKey_nid.3ossl.bz2 /usr/share/man/man3/PEM_write_PKCS8_PRIV_KEY_INFO.3ossl.bz2 /usr/share/man/man3/PEM_write_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_PUBKEY_ex.3ossl.bz2 /usr/share/man/man3/PEM_write_PrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_PrivateKey_ex.3ossl.bz2 /usr/share/man/man3/PEM_write_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_RSAPublicKey.3ossl.bz2 /usr/share/man/man3/PEM_write_RSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_SSL_SESSION.3ossl.bz2 /usr/share/man/man3/PEM_write_X509.3ossl.bz2 /usr/share/man/man3/PEM_write_X509_ACERT.3ossl.bz2 /usr/share/man/man3/PEM_write_X509_AUX.3ossl.bz2 /usr/share/man/man3/PEM_write_X509_CRL.3ossl.bz2 /usr/share/man/man3/PEM_write_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_X509_REQ.3ossl.bz2 /usr/share/man/man3/PEM_write_X509_REQ_NEW.3ossl.bz2 /usr/share/man/man3/PEM_write_bio.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_CMS.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_CMS_stream.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_DHparams.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_DHxparams.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_DSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_DSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_DSAparams.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_ECPKParameters.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_ECPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_EC_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_NETSCAPE_CERT_SEQUENCE.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PKCS7.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PKCS7_stream.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PKCS8.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PKCS8PrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PKCS8PrivateKey_nid.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PKCS8_PRIV_KEY_INFO.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PUBKEY_ex.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_Parameters.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PrivateKey_ex.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_PrivateKey_traditional.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_RSAPublicKey.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_RSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_SSL_SESSION.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509_ACERT.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509_AUX.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509_CRL.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509_REQ.3ossl.bz2 /usr/share/man/man3/PEM_write_bio_X509_REQ_NEW.3ossl.bz2 /usr/share/man/man3/PKCS12_BAGS_free.3ossl.bz2 /usr/share/man/man3/PKCS12_BAGS_new.3ossl.bz2 /usr/share/man/man3/PKCS12_MAC_DATA_free.3ossl.bz2 /usr/share/man/man3/PKCS12_MAC_DATA_new.3ossl.bz2 /usr/share/man/man3/PKCS12_PBE_keyivgen.3ossl.bz2 /usr/share/man/man3/PKCS12_PBE_keyivgen_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create0_p8inf.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create0_pkcs8.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create_cert.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create_crl.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create_pkcs8_encrypt.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create_pkcs8_encrypt_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_create_secret.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_free.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_attr.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_attrs.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_bag_obj.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_bag_type.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_p8inf.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_pkcs8.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_safes.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get0_type.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get1_cert.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get1_cert_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get1_crl.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get1_crl_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get_bag_nid.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_get_nid.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_new.3ossl.bz2 /usr/share/man/man3/PKCS12_SAFEBAG_set0_attrs.3ossl.bz2 /usr/share/man/man3/PKCS12_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/PKCS12_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/PKCS12_add_CSPName_asc.3ossl.bz2 /usr/share/man/man3/PKCS12_add_cert.3ossl.bz2 /usr/share/man/man3/PKCS12_add_friendlyname_asc.3ossl.bz2 /usr/share/man/man3/PKCS12_add_friendlyname_uni.3ossl.bz2 /usr/share/man/man3/PKCS12_add_friendlyname_utf8.3ossl.bz2 /usr/share/man/man3/PKCS12_add_key.3ossl.bz2 /usr/share/man/man3/PKCS12_add_key_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_add_localkeyid.3ossl.bz2 /usr/share/man/man3/PKCS12_add_safe.3ossl.bz2 /usr/share/man/man3/PKCS12_add_safe_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_add_safes.3ossl.bz2 /usr/share/man/man3/PKCS12_add_safes_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_add_secret.3ossl.bz2 /usr/share/man/man3/PKCS12_create.3ossl.bz2 /usr/share/man/man3/PKCS12_create_cb.3ossl.bz2 /usr/share/man/man3/PKCS12_create_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_create_ex2.3ossl.bz2 /usr/share/man/man3/PKCS12_decrypt_skey.3ossl.bz2 /usr/share/man/man3/PKCS12_decrypt_skey_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_free.3ossl.bz2 /usr/share/man/man3/PKCS12_gen_mac.3ossl.bz2 /usr/share/man/man3/PKCS12_get0_mac.3ossl.bz2 /usr/share/man/man3/PKCS12_get_attr_gen.3ossl.bz2 /usr/share/man/man3/PKCS12_get_friendlyname.3ossl.bz2 /usr/share/man/man3/PKCS12_init.3ossl.bz2 /usr/share/man/man3/PKCS12_init_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_item_decrypt_d2i.3ossl.bz2 /usr/share/man/man3/PKCS12_item_decrypt_d2i_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_item_i2d_encrypt.3ossl.bz2 /usr/share/man/man3/PKCS12_item_i2d_encrypt_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_key_gen_asc.3ossl.bz2 /usr/share/man/man3/PKCS12_key_gen_asc_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_key_gen_uni.3ossl.bz2 /usr/share/man/man3/PKCS12_key_gen_uni_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_key_gen_utf8.3ossl.bz2 /usr/share/man/man3/PKCS12_key_gen_utf8_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_new.3ossl.bz2 /usr/share/man/man3/PKCS12_newpass.3ossl.bz2 /usr/share/man/man3/PKCS12_pack_p7encdata.3ossl.bz2 /usr/share/man/man3/PKCS12_pack_p7encdata_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_parse.3ossl.bz2 /usr/share/man/man3/PKCS12_pbe_crypt.3ossl.bz2 /usr/share/man/man3/PKCS12_pbe_crypt_ex.3ossl.bz2 /usr/share/man/man3/PKCS12_set_mac.3ossl.bz2 /usr/share/man/man3/PKCS12_set_pbmac1_pbkdf2.3ossl.bz2 /usr/share/man/man3/PKCS12_setup_mac.3ossl.bz2 /usr/share/man/man3/PKCS12_verify_mac.3ossl.bz2 /usr/share/man/man3/PKCS5_PBE_keyivgen.3ossl.bz2 /usr/share/man/man3/PKCS5_PBE_keyivgen_ex.3ossl.bz2 /usr/share/man/man3/PKCS5_PBKDF2_HMAC.3ossl.bz2 /usr/share/man/man3/PKCS5_PBKDF2_HMAC_SHA1.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe2_set.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe2_set_iv.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe2_set_iv_ex.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe2_set_scrypt.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe_set.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe_set0_algor.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe_set0_algor_ex.3ossl.bz2 /usr/share/man/man3/PKCS5_pbe_set_ex.3ossl.bz2 /usr/share/man/man3/PKCS5_pbkdf2_set.3ossl.bz2 /usr/share/man/man3/PKCS5_pbkdf2_set_ex.3ossl.bz2 /usr/share/man/man3/PKCS5_v2_PBE_keyivgen.3ossl.bz2 /usr/share/man/man3/PKCS5_v2_PBE_keyivgen_ex.3ossl.bz2 /usr/share/man/man3/PKCS5_v2_scrypt_keyivgen.3ossl.bz2 /usr/share/man/man3/PKCS5_v2_scrypt_keyivgen_ex.3ossl.bz2 /usr/share/man/man3/PKCS7_DIGEST_free.3ossl.bz2 /usr/share/man/man3/PKCS7_DIGEST_new.3ossl.bz2 /usr/share/man/man3/PKCS7_ENCRYPT_free.3ossl.bz2 /usr/share/man/man3/PKCS7_ENCRYPT_new.3ossl.bz2 /usr/share/man/man3/PKCS7_ENC_CONTENT_free.3ossl.bz2 /usr/share/man/man3/PKCS7_ENC_CONTENT_new.3ossl.bz2 /usr/share/man/man3/PKCS7_ENVELOPE_free.3ossl.bz2 /usr/share/man/man3/PKCS7_ENVELOPE_new.3ossl.bz2 /usr/share/man/man3/PKCS7_ISSUER_AND_SERIAL_digest.3ossl.bz2 /usr/share/man/man3/PKCS7_ISSUER_AND_SERIAL_free.3ossl.bz2 /usr/share/man/man3/PKCS7_ISSUER_AND_SERIAL_new.3ossl.bz2 /usr/share/man/man3/PKCS7_RECIP_INFO_free.3ossl.bz2 /usr/share/man/man3/PKCS7_RECIP_INFO_new.3ossl.bz2 /usr/share/man/man3/PKCS7_SIGNED_free.3ossl.bz2 /usr/share/man/man3/PKCS7_SIGNED_new.3ossl.bz2 /usr/share/man/man3/PKCS7_SIGNER_INFO_free.3ossl.bz2 /usr/share/man/man3/PKCS7_SIGNER_INFO_new.3ossl.bz2 /usr/share/man/man3/PKCS7_SIGN_ENVELOPE_free.3ossl.bz2 /usr/share/man/man3/PKCS7_SIGN_ENVELOPE_new.3ossl.bz2 /usr/share/man/man3/PKCS7_add_certificate.3ossl.bz2 /usr/share/man/man3/PKCS7_add_crl.3ossl.bz2 /usr/share/man/man3/PKCS7_decrypt.3ossl.bz2 /usr/share/man/man3/PKCS7_dup.3ossl.bz2 /usr/share/man/man3/PKCS7_encrypt.3ossl.bz2 /usr/share/man/man3/PKCS7_encrypt_ex.3ossl.bz2 /usr/share/man/man3/PKCS7_free.3ossl.bz2 /usr/share/man/man3/PKCS7_get0_signers.3ossl.bz2 /usr/share/man/man3/PKCS7_get_octet_string.3ossl.bz2 /usr/share/man/man3/PKCS7_new.3ossl.bz2 /usr/share/man/man3/PKCS7_new_ex.3ossl.bz2 /usr/share/man/man3/PKCS7_print_ctx.3ossl.bz2 /usr/share/man/man3/PKCS7_sign.3ossl.bz2 /usr/share/man/man3/PKCS7_sign_add_signer.3ossl.bz2 /usr/share/man/man3/PKCS7_sign_ex.3ossl.bz2 /usr/share/man/man3/PKCS7_type_is_other.3ossl.bz2 /usr/share/man/man3/PKCS7_verify.3ossl.bz2 /usr/share/man/man3/PKCS8_PRIV_KEY_INFO_free.3ossl.bz2 /usr/share/man/man3/PKCS8_PRIV_KEY_INFO_new.3ossl.bz2 /usr/share/man/man3/PKCS8_decrypt.3ossl.bz2 /usr/share/man/man3/PKCS8_decrypt_ex.3ossl.bz2 /usr/share/man/man3/PKCS8_encrypt.3ossl.bz2 /usr/share/man/man3/PKCS8_encrypt_ex.3ossl.bz2 /usr/share/man/man3/PKCS8_pkey_add1_attr.3ossl.bz2 /usr/share/man/man3/PKCS8_pkey_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/PKCS8_pkey_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/PKCS8_pkey_get0_attrs.3ossl.bz2 /usr/share/man/man3/PKCS8_set0_pbe.3ossl.bz2 /usr/share/man/man3/PKCS8_set0_pbe_ex.3ossl.bz2 /usr/share/man/man3/PKEY_USAGE_PERIOD_free.3ossl.bz2 /usr/share/man/man3/PKEY_USAGE_PERIOD_new.3ossl.bz2 /usr/share/man/man3/POLICYINFO_free.3ossl.bz2 /usr/share/man/man3/POLICYINFO_new.3ossl.bz2 /usr/share/man/man3/POLICYQUALINFO_free.3ossl.bz2 /usr/share/man/man3/POLICYQUALINFO_new.3ossl.bz2 /usr/share/man/man3/POLICY_CONSTRAINTS_free.3ossl.bz2 /usr/share/man/man3/POLICY_CONSTRAINTS_new.3ossl.bz2 /usr/share/man/man3/POLICY_MAPPING_free.3ossl.bz2 /usr/share/man/man3/POLICY_MAPPING_new.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFOS.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFOS_free.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFOS_new.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_free.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_get0_addProfessionInfo.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_get0_namingAuthority.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_get0_professionItems.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_get0_professionOIDs.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_get0_registrationNumber.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_new.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_set0_addProfessionInfo.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_set0_namingAuthority.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_set0_professionItems.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_set0_professionOIDs.3ossl.bz2 /usr/share/man/man3/PROFESSION_INFO_set0_registrationNumber.3ossl.bz2 /usr/share/man/man3/PROXY_CERT_INFO_EXTENSION_free.3ossl.bz2 /usr/share/man/man3/PROXY_CERT_INFO_EXTENSION_new.3ossl.bz2 /usr/share/man/man3/PROXY_POLICY_free.3ossl.bz2 /usr/share/man/man3/PROXY_POLICY_new.3ossl.bz2 /usr/share/man/man3/RAND_OpenSSL.3ossl.bz2 /usr/share/man/man3/RAND_add.3ossl.bz2
    /usr/share/man/man3/RAND_bytes.3ossl.bz2 /usr/share/man/man3/RAND_bytes_ex.3ossl.bz2 /usr/share/man/man3/RAND_cleanup.3ossl.bz2 /usr/share/man/man3/RAND_egd.3ossl.bz2 /usr/share/man/man3/RAND_egd_bytes.3ossl.bz2 /usr/share/man/man3/RAND_event.3ossl.bz2 /usr/share/man/man3/RAND_file_name.3ossl.bz2 /usr/share/man/man3/RAND_get0_primary.3ossl.bz2 /usr/share/man/man3/RAND_get0_private.3ossl.bz2 /usr/share/man/man3/RAND_get0_public.3ossl.bz2 /usr/share/man/man3/RAND_get_rand_method.3ossl.bz2 /usr/share/man/man3/RAND_keep_random_devices_open.3ossl.bz2 /usr/share/man/man3/RAND_load_file.3ossl.bz2 /usr/share/man/man3/RAND_poll.3ossl.bz2 /usr/share/man/man3/RAND_priv_bytes.3ossl.bz2 /usr/share/man/man3/RAND_priv_bytes_ex.3ossl.bz2 /usr/share/man/man3/RAND_pseudo_bytes.3ossl.bz2 /usr/share/man/man3/RAND_query_egd_bytes.3ossl.bz2 /usr/share/man/man3/RAND_screen.3ossl.bz2 /usr/share/man/man3/RAND_seed.3ossl.bz2 /usr/share/man/man3/RAND_set0_private.3ossl.bz2 /usr/share/man/man3/RAND_set0_public.3ossl.bz2 /usr/share/man/man3/RAND_set1_random_provider.3ossl.bz2 /usr/share/man/man3/RAND_set_DRBG_type.3ossl.bz2 /usr/share/man/man3/RAND_set_rand_method.3ossl.bz2 /usr/share/man/man3/RAND_set_seed_source_type.3ossl.bz2 /usr/share/man/man3/RAND_status.3ossl.bz2 /usr/share/man/man3/RAND_write_file.3ossl.bz2
    /usr/share/man/man3/RC4.3ossl.bz2
    /usr/share/man/man3/RC4_set_key.3ossl.bz2 /usr/share/man/man3/RIPEMD160.3ossl.bz2 /usr/share/man/man3/RIPEMD160_Final.3ossl.bz2 /usr/share/man/man3/RIPEMD160_Init.3ossl.bz2 /usr/share/man/man3/RIPEMD160_Update.3ossl.bz2 /usr/share/man/man3/RSAPrivateKey_dup.3ossl.bz2 /usr/share/man/man3/RSAPublicKey_dup.3ossl.bz2 /usr/share/man/man3/RSA_OAEP_PARAMS_free.3ossl.bz2 /usr/share/man/man3/RSA_OAEP_PARAMS_new.3ossl.bz2 /usr/share/man/man3/RSA_PKCS1_OpenSSL.3ossl.bz2 /usr/share/man/man3/RSA_PSS_PARAMS_dup.3ossl.bz2 /usr/share/man/man3/RSA_PSS_PARAMS_free.3ossl.bz2 /usr/share/man/man3/RSA_PSS_PARAMS_new.3ossl.bz2 /usr/share/man/man3/RSA_bits.3ossl.bz2 /usr/share/man/man3/RSA_blinding_off.3ossl.bz2 /usr/share/man/man3/RSA_blinding_on.3ossl.bz2 /usr/share/man/man3/RSA_check_key.3ossl.bz2 /usr/share/man/man3/RSA_check_key_ex.3ossl.bz2 /usr/share/man/man3/RSA_clear_flags.3ossl.bz2 /usr/share/man/man3/RSA_flags.3ossl.bz2
    /usr/share/man/man3/RSA_free.3ossl.bz2 /usr/share/man/man3/RSA_generate_key.3ossl.bz2 /usr/share/man/man3/RSA_generate_key_ex.3ossl.bz2 /usr/share/man/man3/RSA_generate_multi_prime_key.3ossl.bz2 /usr/share/man/man3/RSA_get0_crt_params.3ossl.bz2 /usr/share/man/man3/RSA_get0_d.3ossl.bz2 /usr/share/man/man3/RSA_get0_dmp1.3ossl.bz2 /usr/share/man/man3/RSA_get0_dmq1.3ossl.bz2 /usr/share/man/man3/RSA_get0_e.3ossl.bz2 /usr/share/man/man3/RSA_get0_engine.3ossl.bz2 /usr/share/man/man3/RSA_get0_factors.3ossl.bz2 /usr/share/man/man3/RSA_get0_iqmp.3ossl.bz2 /usr/share/man/man3/RSA_get0_key.3ossl.bz2 /usr/share/man/man3/RSA_get0_multi_prime_crt_params.3ossl.bz2 /usr/share/man/man3/RSA_get0_multi_prime_factors.3ossl.bz2 /usr/share/man/man3/RSA_get0_n.3ossl.bz2 /usr/share/man/man3/RSA_get0_p.3ossl.bz2 /usr/share/man/man3/RSA_get0_pss_params.3ossl.bz2 /usr/share/man/man3/RSA_get0_q.3ossl.bz2 /usr/share/man/man3/RSA_get_app_data.3ossl.bz2 /usr/share/man/man3/RSA_get_default_method.3ossl.bz2 /usr/share/man/man3/RSA_get_ex_data.3ossl.bz2 /usr/share/man/man3/RSA_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/RSA_get_method.3ossl.bz2 /usr/share/man/man3/RSA_get_multi_prime_extra_count.3ossl.bz2 /usr/share/man/man3/RSA_get_version.3ossl.bz2 /usr/share/man/man3/RSA_meth_dup.3ossl.bz2 /usr/share/man/man3/RSA_meth_free.3ossl.bz2 /usr/share/man/man3/RSA_meth_get0_app_data.3ossl.bz2 /usr/share/man/man3/RSA_meth_get0_name.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_bn_mod_exp.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_finish.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_flags.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_init.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_keygen.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_mod_exp.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_multi_prime_keygen.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_priv_dec.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_priv_enc.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_pub_dec.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_pub_enc.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_sign.3ossl.bz2 /usr/share/man/man3/RSA_meth_get_verify.3ossl.bz2 /usr/share/man/man3/RSA_meth_new.3ossl.bz2 /usr/share/man/man3/RSA_meth_set0_app_data.3ossl.bz2 /usr/share/man/man3/RSA_meth_set1_name.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_bn_mod_exp.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_finish.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_flags.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_init.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_keygen.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_mod_exp.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_multi_prime_keygen.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_priv_dec.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_priv_enc.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_pub_dec.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_pub_enc.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_sign.3ossl.bz2 /usr/share/man/man3/RSA_meth_set_verify.3ossl.bz2 /usr/share/man/man3/RSA_new.3ossl.bz2 /usr/share/man/man3/RSA_new_method.3ossl.bz2 /usr/share/man/man3/RSA_padding_add_PKCS1_OAEP.3ossl.bz2 /usr/share/man/man3/RSA_padding_add_PKCS1_OAEP_mgf1.3ossl.bz2 /usr/share/man/man3/RSA_padding_add_PKCS1_type_1.3ossl.bz2 /usr/share/man/man3/RSA_padding_add_PKCS1_type_2.3ossl.bz2 /usr/share/man/man3/RSA_padding_add_none.3ossl.bz2 /usr/share/man/man3/RSA_padding_check_PKCS1_OAEP.3ossl.bz2 /usr/share/man/man3/RSA_padding_check_PKCS1_OAEP_mgf1.3ossl.bz2 /usr/share/man/man3/RSA_padding_check_PKCS1_type_1.3ossl.bz2 /usr/share/man/man3/RSA_padding_check_PKCS1_type_2.3ossl.bz2 /usr/share/man/man3/RSA_padding_check_none.3ossl.bz2 /usr/share/man/man3/RSA_print.3ossl.bz2 /usr/share/man/man3/RSA_print_fp.3ossl.bz2 /usr/share/man/man3/RSA_private_decrypt.3ossl.bz2 /usr/share/man/man3/RSA_private_encrypt.3ossl.bz2 /usr/share/man/man3/RSA_public_decrypt.3ossl.bz2 /usr/share/man/man3/RSA_public_encrypt.3ossl.bz2 /usr/share/man/man3/RSA_security_bits.3ossl.bz2 /usr/share/man/man3/RSA_set0_crt_params.3ossl.bz2 /usr/share/man/man3/RSA_set0_factors.3ossl.bz2 /usr/share/man/man3/RSA_set0_key.3ossl.bz2 /usr/share/man/man3/RSA_set0_multi_prime_params.3ossl.bz2 /usr/share/man/man3/RSA_set_app_data.3ossl.bz2 /usr/share/man/man3/RSA_set_default_method.3ossl.bz2 /usr/share/man/man3/RSA_set_ex_data.3ossl.bz2 /usr/share/man/man3/RSA_set_flags.3ossl.bz2 /usr/share/man/man3/RSA_set_method.3ossl.bz2 /usr/share/man/man3/RSA_sign.3ossl.bz2 /usr/share/man/man3/RSA_sign_ASN1_OCTET_STRING.3ossl.bz2 /usr/share/man/man3/RSA_size.3ossl.bz2 /usr/share/man/man3/RSA_test_flags.3ossl.bz2 /usr/share/man/man3/RSA_verify.3ossl.bz2 /usr/share/man/man3/RSA_verify_ASN1_OCTET_STRING.3ossl.bz2 /usr/share/man/man3/SCRYPT_PARAMS_free.3ossl.bz2 /usr/share/man/man3/SCRYPT_PARAMS_new.3ossl.bz2 /usr/share/man/man3/SCT_LIST_free.3ossl.bz2 /usr/share/man/man3/SCT_LIST_print.3ossl.bz2 /usr/share/man/man3/SCT_LIST_validate.3ossl.bz2 /usr/share/man/man3/SCT_free.3ossl.bz2 /usr/share/man/man3/SCT_get0_extensions.3ossl.bz2 /usr/share/man/man3/SCT_get0_log_id.3ossl.bz2 /usr/share/man/man3/SCT_get0_signature.3ossl.bz2 /usr/share/man/man3/SCT_get_log_entry_type.3ossl.bz2 /usr/share/man/man3/SCT_get_signature_nid.3ossl.bz2 /usr/share/man/man3/SCT_get_source.3ossl.bz2 /usr/share/man/man3/SCT_get_timestamp.3ossl.bz2 /usr/share/man/man3/SCT_get_validation_status.3ossl.bz2 /usr/share/man/man3/SCT_get_version.3ossl.bz2 /usr/share/man/man3/SCT_new.3ossl.bz2 /usr/share/man/man3/SCT_new_from_base64.3ossl.bz2 /usr/share/man/man3/SCT_print.3ossl.bz2 /usr/share/man/man3/SCT_set0_extensions.3ossl.bz2 /usr/share/man/man3/SCT_set0_log_id.3ossl.bz2 /usr/share/man/man3/SCT_set0_signature.3ossl.bz2 /usr/share/man/man3/SCT_set1_extensions.3ossl.bz2 /usr/share/man/man3/SCT_set1_log_id.3ossl.bz2 /usr/share/man/man3/SCT_set1_signature.3ossl.bz2 /usr/share/man/man3/SCT_set_log_entry_type.3ossl.bz2 /usr/share/man/man3/SCT_set_signature_nid.3ossl.bz2 /usr/share/man/man3/SCT_set_source.3ossl.bz2 /usr/share/man/man3/SCT_set_timestamp.3ossl.bz2 /usr/share/man/man3/SCT_set_version.3ossl.bz2 /usr/share/man/man3/SCT_validate.3ossl.bz2 /usr/share/man/man3/SCT_validation_status_string.3ossl.bz2 /usr/share/man/man3/SHA1.3ossl.bz2
    /usr/share/man/man3/SHA1_Final.3ossl.bz2 /usr/share/man/man3/SHA1_Init.3ossl.bz2 /usr/share/man/man3/SHA1_Update.3ossl.bz2
    /usr/share/man/man3/SHA224.3ossl.bz2
    /usr/share/man/man3/SHA224_Final.3ossl.bz2 /usr/share/man/man3/SHA224_Init.3ossl.bz2 /usr/share/man/man3/SHA224_Update.3ossl.bz2 /usr/share/man/man3/SHA256.3ossl.bz2
    /usr/share/man/man3/SHA256_Final.3ossl.bz2 /usr/share/man/man3/SHA256_Init.3ossl.bz2 /usr/share/man/man3/SHA256_Update.3ossl.bz2 /usr/share/man/man3/SHA384.3ossl.bz2
    /usr/share/man/man3/SHA384_Final.3ossl.bz2 /usr/share/man/man3/SHA384_Init.3ossl.bz2 /usr/share/man/man3/SHA384_Update.3ossl.bz2 /usr/share/man/man3/SHA512.3ossl.bz2
    /usr/share/man/man3/SHA512_Final.3ossl.bz2 /usr/share/man/man3/SHA512_Init.3ossl.bz2 /usr/share/man/man3/SHA512_Update.3ossl.bz2 /usr/share/man/man3/SMIME_read_ASN1.3ossl.bz2 /usr/share/man/man3/SMIME_read_ASN1_ex.3ossl.bz2 /usr/share/man/man3/SMIME_read_CMS.3ossl.bz2 /usr/share/man/man3/SMIME_read_CMS_ex.3ossl.bz2 /usr/share/man/man3/SMIME_read_PKCS7.3ossl.bz2 /usr/share/man/man3/SMIME_read_PKCS7_ex.3ossl.bz2 /usr/share/man/man3/SMIME_write_ASN1.3ossl.bz2 /usr/share/man/man3/SMIME_write_ASN1_ex.3ossl.bz2 /usr/share/man/man3/SMIME_write_CMS.3ossl.bz2 /usr/share/man/man3/SMIME_write_PKCS7.3ossl.bz2 /usr/share/man/man3/SRP_Calc_A.3ossl.bz2 /usr/share/man/man3/SRP_Calc_B.3ossl.bz2 /usr/share/man/man3/SRP_Calc_B_ex.3ossl.bz2 /usr/share/man/man3/SRP_Calc_client_key.3ossl.bz2 /usr/share/man/man3/SRP_Calc_client_key_ex.3ossl.bz2 /usr/share/man/man3/SRP_Calc_server_key.3ossl.bz2 /usr/share/man/man3/SRP_Calc_u.3ossl.bz2 /usr/share/man/man3/SRP_Calc_u_ex.3ossl.bz2 /usr/share/man/man3/SRP_Calc_x.3ossl.bz2 /usr/share/man/man3/SRP_Calc_x_ex.3ossl.bz2 /usr/share/man/man3/SRP_VBASE_add0_user.3ossl.bz2 /usr/share/man/man3/SRP_VBASE_free.3ossl.bz2 /usr/share/man/man3/SRP_VBASE_get1_by_user.3ossl.bz2 /usr/share/man/man3/SRP_VBASE_get_by_user.3ossl.bz2 /usr/share/man/man3/SRP_VBASE_init.3ossl.bz2 /usr/share/man/man3/SRP_VBASE_new.3ossl.bz2 /usr/share/man/man3/SRP_check_known_gN_param.3ossl.bz2 /usr/share/man/man3/SRP_create_verifier.3ossl.bz2 /usr/share/man/man3/SRP_create_verifier_BN.3ossl.bz2 /usr/share/man/man3/SRP_create_verifier_BN_ex.3ossl.bz2 /usr/share/man/man3/SRP_create_verifier_ex.3ossl.bz2 /usr/share/man/man3/SRP_get_default_gN.3ossl.bz2 /usr/share/man/man3/SRP_user_pwd_free.3ossl.bz2 /usr/share/man/man3/SRP_user_pwd_new.3ossl.bz2 /usr/share/man/man3/SRP_user_pwd_set0_sv.3ossl.bz2 /usr/share/man/man3/SRP_user_pwd_set1_ids.3ossl.bz2 /usr/share/man/man3/SRP_user_pwd_set_gN.3ossl.bz2 /usr/share/man/man3/SSL_ACCEPT_CONNECTION_NO_BLOCK.3ossl.bz2 /usr/share/man/man3/SSL_ACCEPT_STREAM_BIDI.3ossl.bz2 /usr/share/man/man3/SSL_ACCEPT_STREAM_NO_BLOCK.3ossl.bz2 /usr/share/man/man3/SSL_ACCEPT_STREAM_UNI.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_description.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_find.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_auth_nid.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_bits.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_cipher_nid.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_digest_nid.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_handshake_digest.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_id.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_kx_nid.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_name.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_protocol_id.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_get_version.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_is_aead.3ossl.bz2 /usr/share/man/man3/SSL_CIPHER_standard_name.3ossl.bz2 /usr/share/man/man3/SSL_COMP_add_compression_method.3ossl.bz2 /usr/share/man/man3/SSL_COMP_free_compression_methods.3ossl.bz2 /usr/share/man/man3/SSL_COMP_get0_name.3ossl.bz2 /usr/share/man/man3/SSL_COMP_get_compression_methods.3ossl.bz2 /usr/share/man/man3/SSL_COMP_get_id.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_clear_flags.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_finish.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_free.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_new.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_set1_prefix.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_set_flags.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_set_ssl.3ossl.bz2 /usr/share/man/man3/SSL_CONF_CTX_set_ssl_ctx.3ossl.bz2 /usr/share/man/man3/SSL_CONF_cmd.3ossl.bz2 /usr/share/man/man3/SSL_CONF_cmd_argv.3ossl.bz2 /usr/share/man/man3/SSL_CONF_cmd_value_type.3ossl.bz2 /usr/share/man/man3/SSL_CONN_CLOSE_FLAG_LOCAL.3ossl.bz2 /usr/share/man/man3/SSL_CONN_CLOSE_FLAG_TRANSPORT.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add0_chain_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add1_chain_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add1_to_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add_client_CA.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add_client_custom_ext.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add_custom_ext.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add_extra_chain_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add_server_custom_ext.3ossl.bz2 /usr/share/man/man3/SSL_CTX_add_session.3ossl.bz2 /usr/share/man/man3/SSL_CTX_build_cert_chain.3ossl.bz2 /usr/share/man/man3/SSL_CTX_callback_ctrl.3ossl.bz2 /usr/share/man/man3/SSL_CTX_check_private_key.3ossl.bz2 /usr/share/man/man3/SSL_CTX_clear_chain_certs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_clear_extra_chain_certs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_clear_mode.3ossl.bz2 /usr/share/man/man3/SSL_CTX_clear_options.3ossl.bz2 /usr/share/man/man3/SSL_CTX_compress_certs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_config.3ossl.bz2 /usr/share/man/man3/SSL_CTX_ct_is_enabled.3ossl.bz2 /usr/share/man/man3/SSL_CTX_ctrl.3ossl.bz2 /usr/share/man/man3/SSL_CTX_dane_clear_flags.3ossl.bz2 /usr/share/man/man3/SSL_CTX_dane_enable.3ossl.bz2 /usr/share/man/man3/SSL_CTX_dane_mtype_set.3ossl.bz2 /usr/share/man/man3/SSL_CTX_dane_set_flags.3ossl.bz2 /usr/share/man/man3/SSL_CTX_decrypt_session_ticket_fn.3ossl.bz2 /usr/share/man/man3/SSL_CTX_disable_ct.3ossl.bz2 /usr/share/man/man3/SSL_CTX_enable_ct.3ossl.bz2 /usr/share/man/man3/SSL_CTX_flush_sessions.3ossl.bz2 /usr/share/man/man3/SSL_CTX_flush_sessions_ex.3ossl.bz2 /usr/share/man/man3/SSL_CTX_free.3ossl.bz2 /usr/share/man/man3/SSL_CTX_generate_session_ticket_fn.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_chain_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_chain_certs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_client_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_implemented_groups.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_param.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_security_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_server_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get0_verify_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get1_compressed_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_app_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_ciphers.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_client_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_client_cert_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_default_passwd_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_default_passwd_cb_userdata.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_default_read_ahead.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_domain_flags.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_extra_chain_certs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_extra_chain_certs_only.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_info_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_keylog_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_max_cert_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_max_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_min_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_mode.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_num_tickets.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_options.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_quiet_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_read_ahead.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_record_padding_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_recv_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_security_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_security_level.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_session_cache_mode.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_ssl_method.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_timeout.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_tlsext_status_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_tlsext_status_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_tlsext_status_type.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_verify_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_verify_depth.3ossl.bz2 /usr/share/man/man3/SSL_CTX_get_verify_mode.3ossl.bz2 /usr/share/man/man3/SSL_CTX_has_client_custom_ext.3ossl.bz2 /usr/share/man/man3/SSL_CTX_keylog_cb_func.3ossl.bz2 /usr/share/man/man3/SSL_CTX_load_verify_dir.3ossl.bz2 /usr/share/man/man3/SSL_CTX_load_verify_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_load_verify_locations.3ossl.bz2 /usr/share/man/man3/SSL_CTX_load_verify_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_new.3ossl.bz2 /usr/share/man/man3/SSL_CTX_new_ex.3ossl.bz2 /usr/share/man/man3/SSL_CTX_remove_session.3ossl.bz2 /usr/share/man/man3/SSL_CTX_select_current_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_accept.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_accept_good.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_accept_renegotiate.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_cache_full.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_cb_hits.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_connect.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_connect_good.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_connect_renegotiate.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_get_cache_size.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_get_get_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_get_new_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_get_remove_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_hits.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_misses.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_number.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_set_cache_size.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_set_get_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_set_new_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_set_remove_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sess_timeouts.3ossl.bz2 /usr/share/man/man3/SSL_CTX_sessions.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set0_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set0_chain.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set0_chain_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set0_security_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set0_tmp_dh_pkey.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set0_verify_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_cert_comp_preference.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_chain.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_chain_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_client_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_client_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_client_sigalgs_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_compressed_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_curves.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_curves_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_groups.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_groups_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_param.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_server_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_sigalgs_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set1_verify_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_allow_early_data_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_alpn_protos.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_alpn_select_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_app_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_async_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_async_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_block_padding.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_block_padding_ex.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_cert_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_cert_verify_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_cipher_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_ciphersuites.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_client_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_client_cert_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_client_hello_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_cookie_generate_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_cookie_verify_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_ct_validation_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_ctlog_list_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_current_cert.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_ctlog_list_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_passwd_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_passwd_cb_userdata.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_read_buffer_len.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_verify_dir.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_verify_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_verify_paths.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_default_verify_store.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_dh_auto.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_domain_flags.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_ecdh_auto.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_generate_session_id.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_info_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_keylog_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_max_cert_list.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_max_pipelines.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_max_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_max_send_fragment.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_min_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_mode.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_msg_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_msg_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_new_pending_conn_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_next_proto_select_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_next_protos_advertised_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_num_tickets.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_options.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_post_handshake_auth.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_psk_client_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_psk_find_session_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_psk_server_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_psk_use_session_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_purpose.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_quiet_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_read_ahead.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_record_padding_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_record_padding_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_recv_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_security_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_security_level.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_session_cache_mode.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_session_id_context.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_session_ticket_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_split_send_fragment.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_cb_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_client_pwd_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_password.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_strength.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_username.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_username_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_srp_verify_param_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_ssl_version.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_stateless_cookie_generate_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_stateless_cookie_verify_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_timeout.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_max_fragment_length.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_servername_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_servername_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_status_arg.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_status_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_status_type.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_ticket_key_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_ticket_key_evp_cb.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tlsext_use_srtp.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tmp_dh.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tmp_dh_callback.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_tmp_ecdh.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_trust.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_verify.3ossl.bz2 /usr/share/man/man3/SSL_CTX_set_verify_depth.3ossl.bz2 /usr/share/man/man3/SSL_CTX_up_ref.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_PrivateKey.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_PrivateKey_ASN1.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_PrivateKey_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_RSAPrivateKey_ASN1.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_RSAPrivateKey_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_cert_and_key.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_certificate.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_certificate_ASN1.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_certificate_chain_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_certificate_file.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_psk_identity_hint.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_serverinfo.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_serverinfo_ex.3ossl.bz2 /usr/share/man/man3/SSL_CTX_use_serverinfo_file.3ossl.bz2 /usr/share/man/man3/SSL_DEFAULT_STREAM_MODE_AUTO_BIDI.3ossl.bz2 /usr/share/man/man3/SSL_DEFAULT_STREAM_MODE_AUTO_UNI.3ossl.bz2 /usr/share/man/man3/SSL_DEFAULT_STREAM_MODE_NONE.3ossl.bz2 /usr/share/man/man3/SSL_DOMAIN_FLAG_BLOCKING.3ossl.bz2 /usr/share/man/man3/SSL_DOMAIN_FLAG_LEGACY_BLOCKING.3ossl.bz2 /usr/share/man/man3/SSL_DOMAIN_FLAG_MULTI_THREAD.3ossl.bz2 /usr/share/man/man3/SSL_DOMAIN_FLAG_SINGLE_THREAD.3ossl.bz2 /usr/share/man/man3/SSL_DOMAIN_FLAG_THREAD_ASSISTED.3ossl.bz2 /usr/share/man/man3/SSL_INCOMING_STREAM_POLICY_ACCEPT.3ossl.bz2 /usr/share/man/man3/SSL_INCOMING_STREAM_POLICY_AUTO.3ossl.bz2 /usr/share/man/man3/SSL_INCOMING_STREAM_POLICY_REJECT.3ossl.bz2 /usr/share/man/man3/SSL_OP_BIT.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_E.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_EC.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_ECD.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_EL.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_ER.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_EW.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_F.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_I.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_IC.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_IS.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_ISB.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_ISE.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_ISU.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_NONE.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_OS.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_OSB.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_OSE.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_OSU.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_R.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_RE.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_RW.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_RWE.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_W.3ossl.bz2 /usr/share/man/man3/SSL_POLL_EVENT_WE.3ossl.bz2 /usr/share/man/man3/SSL_POLL_FLAG_NO_HANDLE_EVENTS.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_dup.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_free.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_alpn_selected.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_cipher.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_hostname.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_id_context.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_peer.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_peer_rpk.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_ticket.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get0_ticket_appdata.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_app_data.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_compress_id.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_id.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_master_key.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_max_fragment_length.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_protocol_version.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_ticket_lifetime_hint.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_time.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_time_ex.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_get_timeout.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_has_ticket.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_is_resumable.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_new.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_print.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_print_fp.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_print_keylog.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set1_alpn_selected.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set1_hostname.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set1_id.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set1_id_context.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set1_master_key.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set1_ticket_appdata.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_app_data.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_cipher.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_protocol_version.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_time.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_time_ex.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_set_timeout.3ossl.bz2 /usr/share/man/man3/SSL_SESSION_up_ref.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_FLAG_ADVANCE.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_FLAG_NO_BLOCK.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_FLAG_UNI.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_CONN_CLOSED.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_FINISHED.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_NONE.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_OK.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_RESET_LOCAL.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_RESET_REMOTE.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_STATE_WRONG_DIR.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_TYPE_BIDI.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_TYPE_NONE.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_TYPE_READ.3ossl.bz2 /usr/share/man/man3/SSL_STREAM_TYPE_WRITE.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_CLASS_FEATURE_NEGOTIATED.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_CLASS_FEATURE_PEER_REQUEST.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_CLASS_FEATURE_REQUEST.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_CLASS_GENERIC.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_EVENT_HANDLING_MODE.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_EVENT_HANDLING_MODE_EXPLICIT.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_EVENT_HANDLING_MODE_IMPLICIT.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_EVENT_HANDLING_MODE_INHERIT.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_QUIC_IDLE_TIMEOUT.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_QUIC_MAX_PENDING_CONNS.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_QUIC_STREAM_BIDI_LOCAL_AVAIL.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_QUIC_STREAM_BIDI_REMOTE_AVAIL.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_QUIC_STREAM_UNI_LOCAL_AVAIL.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_QUIC_STREAM_UNI_REMOTE_AVAIL.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_STREAM_WRITE_BUF_AVAIL.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_STREAM_WRITE_BUF_SIZE.3ossl.bz2 /usr/share/man/man3/SSL_VALUE_STREAM_WRITE_BUF_USED.3ossl.bz2 /usr/share/man/man3/SSL_WRITE_FLAG_CONCLUDE.3ossl.bz2 /usr/share/man/man3/SSL_accept.3ossl.bz2 /usr/share/man/man3/SSL_accept_connection.3ossl.bz2 /usr/share/man/man3/SSL_accept_stream.3ossl.bz2 /usr/share/man/man3/SSL_add0_chain_cert.3ossl.bz2 /usr/share/man/man3/SSL_add1_chain_cert.3ossl.bz2 /usr/share/man/man3/SSL_add1_host.3ossl.bz2 /usr/share/man/man3/SSL_add1_to_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_add_client_CA.3ossl.bz2 /usr/share/man/man3/SSL_add_dir_cert_subjects_to_stack.3ossl.bz2 /usr/share/man/man3/SSL_add_expected_rpk.3ossl.bz2 /usr/share/man/man3/SSL_add_file_cert_subjects_to_stack.3ossl.bz2 /usr/share/man/man3/SSL_add_store_cert_subjects_to_stack.3ossl.bz2 /usr/share/man/man3/SSL_alert_desc_string.3ossl.bz2 /usr/share/man/man3/SSL_alert_desc_string_long.3ossl.bz2 /usr/share/man/man3/SSL_alert_type_string.3ossl.bz2 /usr/share/man/man3/SSL_alert_type_string_long.3ossl.bz2 /usr/share/man/man3/SSL_alloc_buffers.3ossl.bz2 /usr/share/man/man3/SSL_allow_early_data_cb_fn.3ossl.bz2 /usr/share/man/man3/SSL_async_callback_fn.3ossl.bz2 /usr/share/man/man3/SSL_build_cert_chain.3ossl.bz2 /usr/share/man/man3/SSL_bytes_to_cipher_list.3ossl.bz2 /usr/share/man/man3/SSL_callback_ctrl.3ossl.bz2 /usr/share/man/man3/SSL_check_chain.3ossl.bz2 /usr/share/man/man3/SSL_check_private_key.3ossl.bz2 /usr/share/man/man3/SSL_clear.3ossl.bz2 /usr/share/man/man3/SSL_clear_chain_certs.3ossl.bz2 /usr/share/man/man3/SSL_clear_mode.3ossl.bz2 /usr/share/man/man3/SSL_clear_options.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_cb_fn.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get0_ciphers.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get0_compression_methods.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get0_ext.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get0_legacy_version.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get0_random.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get0_session_id.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get1_extensions_present.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_get_extension_order.3ossl.bz2 /usr/share/man/man3/SSL_client_hello_isv2.3ossl.bz2 /usr/share/man/man3/SSL_client_version.3ossl.bz2 /usr/share/man/man3/SSL_compress_certs.3ossl.bz2 /usr/share/man/man3/SSL_config.3ossl.bz2 /usr/share/man/man3/SSL_connect.3ossl.bz2 /usr/share/man/man3/SSL_ct_is_enabled.3ossl.bz2 /usr/share/man/man3/SSL_ctrl.3ossl.bz2 /usr/share/man/man3/SSL_custom_ext_add_cb_ex.3ossl.bz2 /usr/share/man/man3/SSL_custom_ext_free_cb_ex.3ossl.bz2 /usr/share/man/man3/SSL_custom_ext_parse_cb_ex.3ossl.bz2 /usr/share/man/man3/SSL_dane_clear_flags.3ossl.bz2 /usr/share/man/man3/SSL_dane_enable.3ossl.bz2 /usr/share/man/man3/SSL_dane_set_flags.3ossl.bz2 /usr/share/man/man3/SSL_dane_tlsa_add.3ossl.bz2 /usr/share/man/man3/SSL_disable_ct.3ossl.bz2 /usr/share/man/man3/SSL_do_handshake.3ossl.bz2 /usr/share/man/man3/SSL_dup.3ossl.bz2 /usr/share/man/man3/SSL_enable_ct.3ossl.bz2 /usr/share/man/man3/SSL_export_keying_material.3ossl.bz2 /usr/share/man/man3/SSL_export_keying_material_early.3ossl.bz2 /usr/share/man/man3/SSL_extension_supported.3ossl.bz2 /usr/share/man/man3/SSL_free.3ossl.bz2 /usr/share/man/man3/SSL_free_buffers.3ossl.bz2 /usr/share/man/man3/SSL_get0_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_get0_alpn_selected.3ossl.bz2 /usr/share/man/man3/SSL_get0_chain_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_get0_chain_certs.3ossl.bz2 /usr/share/man/man3/SSL_get0_client_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_get0_connection.3ossl.bz2 /usr/share/man/man3/SSL_get0_dane_authority.3ossl.bz2 /usr/share/man/man3/SSL_get0_dane_tlsa.3ossl.bz2 /usr/share/man/man3/SSL_get0_domain.3ossl.bz2 /usr/share/man/man3/SSL_get0_group_name.3ossl.bz2 /usr/share/man/man3/SSL_get0_iana_groups.3ossl.bz2 /usr/share/man/man3/SSL_get0_listener.3ossl.bz2 /usr/share/man/man3/SSL_get0_next_proto_negotiated.3ossl.bz2 /usr/share/man/man3/SSL_get0_param.3ossl.bz2 /usr/share/man/man3/SSL_get0_peer_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_get0_peer_certificate.3ossl.bz2 /usr/share/man/man3/SSL_get0_peer_rpk.3ossl.bz2 /usr/share/man/man3/SSL_get0_peer_scts.3ossl.bz2 /usr/share/man/man3/SSL_get0_peer_signature_name.3ossl.bz2 /usr/share/man/man3/SSL_get0_peername.3ossl.bz2 /usr/share/man/man3/SSL_get0_security_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_get0_server_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_get0_session.3ossl.bz2 /usr/share/man/man3/SSL_get0_signature_name.3ossl.bz2 /usr/share/man/man3/SSL_get0_tlsext_status_ocsp_resp_ex.3ossl.bz2 /usr/share/man/man3/SSL_get0_verified_chain.3ossl.bz2 /usr/share/man/man3/SSL_get0_verify_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_get1_builtin_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_get1_compressed_cert.3ossl.bz2 /usr/share/man/man3/SSL_get1_curves.3ossl.bz2 /usr/share/man/man3/SSL_get1_groups.3ossl.bz2 /usr/share/man/man3/SSL_get1_peer_certificate.3ossl.bz2 /usr/share/man/man3/SSL_get1_session.3ossl.bz2 /usr/share/man/man3/SSL_get1_supported_ciphers.3ossl.bz2 /usr/share/man/man3/SSL_get_SSL_CTX.3ossl.bz2 /usr/share/man/man3/SSL_get_accept_connection_queue_len.3ossl.bz2 /usr/share/man/man3/SSL_get_accept_stream_queue_len.3ossl.bz2 /usr/share/man/man3/SSL_get_all_async_fds.3ossl.bz2 /usr/share/man/man3/SSL_get_app_data.3ossl.bz2 /usr/share/man/man3/SSL_get_async_status.3ossl.bz2 /usr/share/man/man3/SSL_get_blocking_mode.3ossl.bz2 /usr/share/man/man3/SSL_get_certificate.3ossl.bz2 /usr/share/man/man3/SSL_get_changed_async_fds.3ossl.bz2 /usr/share/man/man3/SSL_get_cipher.3ossl.bz2 /usr/share/man/man3/SSL_get_cipher_bits.3ossl.bz2 /usr/share/man/man3/SSL_get_cipher_list.3ossl.bz2 /usr/share/man/man3/SSL_get_cipher_name.3ossl.bz2 /usr/share/man/man3/SSL_get_cipher_version.3ossl.bz2 /usr/share/man/man3/SSL_get_ciphers.3ossl.bz2 /usr/share/man/man3/SSL_get_client_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_get_client_ciphers.3ossl.bz2 /usr/share/man/man3/SSL_get_client_random.3ossl.bz2 /usr/share/man/man3/SSL_get_conn_close_info.3ossl.bz2 /usr/share/man/man3/SSL_get_current_cipher.3ossl.bz2 /usr/share/man/man3/SSL_get_default_passwd_cb.3ossl.bz2 /usr/share/man/man3/SSL_get_default_passwd_cb_userdata.3ossl.bz2 /usr/share/man/man3/SSL_get_default_timeout.3ossl.bz2 /usr/share/man/man3/SSL_get_domain_flags.3ossl.bz2 /usr/share/man/man3/SSL_get_early_data_status.3ossl.bz2 /usr/share/man/man3/SSL_get_error.3ossl.bz2 /usr/share/man/man3/SSL_get_event_handling_mode.3ossl.bz2 /usr/share/man/man3/SSL_get_event_timeout.3ossl.bz2 /usr/share/man/man3/SSL_get_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_get_ex_data_X509_STORE_CTX_idx.3ossl.bz2 /usr/share/man/man3/SSL_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/SSL_get_extms_support.3ossl.bz2 /usr/share/man/man3/SSL_get_fd.3ossl.bz2 /usr/share/man/man3/SSL_get_feature_negotiated_uint.3ossl.bz2 /usr/share/man/man3/SSL_get_feature_peer_request_uint.3ossl.bz2 /usr/share/man/man3/SSL_get_feature_request_uint.3ossl.bz2 /usr/share/man/man3/SSL_get_generic_value_uint.3ossl.bz2 /usr/share/man/man3/SSL_get_handshake_rtt.3ossl.bz2 /usr/share/man/man3/SSL_get_info_callback.3ossl.bz2 /usr/share/man/man3/SSL_get_key_update_type.3ossl.bz2 /usr/share/man/man3/SSL_get_max_cert_list.3ossl.bz2 /usr/share/man/man3/SSL_get_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_get_max_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_get_min_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_get_mode.3ossl.bz2 /usr/share/man/man3/SSL_get_negotiated_client_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_get_negotiated_group.3ossl.bz2 /usr/share/man/man3/SSL_get_negotiated_server_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_get_num_tickets.3ossl.bz2 /usr/share/man/man3/SSL_get_options.3ossl.bz2 /usr/share/man/man3/SSL_get_peer_cert_chain.3ossl.bz2 /usr/share/man/man3/SSL_get_peer_certificate.3ossl.bz2 /usr/share/man/man3/SSL_get_peer_signature_nid.3ossl.bz2 /usr/share/man/man3/SSL_get_peer_signature_type_nid.3ossl.bz2 /usr/share/man/man3/SSL_get_peer_tmp_key.3ossl.bz2 /usr/share/man/man3/SSL_get_pending_cipher.3ossl.bz2 /usr/share/man/man3/SSL_get_privatekey.3ossl.bz2 /usr/share/man/man3/SSL_get_psk_identity.3ossl.bz2 /usr/share/man/man3/SSL_get_psk_identity_hint.3ossl.bz2 /usr/share/man/man3/SSL_get_quic_stream_bidi_local_avail.3ossl.bz2 /usr/share/man/man3/SSL_get_quic_stream_bidi_remote_avail.3ossl.bz2 /usr/share/man/man3/SSL_get_quic_stream_uni_local_avail.3ossl.bz2 /usr/share/man/man3/SSL_get_quic_stream_uni_remote_avail.3ossl.bz2 /usr/share/man/man3/SSL_get_quiet_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_get_rbio.3ossl.bz2 /usr/share/man/man3/SSL_get_read_ahead.3ossl.bz2 /usr/share/man/man3/SSL_get_record_padding_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_get_recv_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_get_rfd.3ossl.bz2 /usr/share/man/man3/SSL_get_rpoll_descriptor.3ossl.bz2 /usr/share/man/man3/SSL_get_secure_renegotiation_support.3ossl.bz2 /usr/share/man/man3/SSL_get_security_callback.3ossl.bz2 /usr/share/man/man3/SSL_get_security_level.3ossl.bz2 /usr/share/man/man3/SSL_get_selected_srtp_profile.3ossl.bz2 /usr/share/man/man3/SSL_get_server_random.3ossl.bz2 /usr/share/man/man3/SSL_get_server_tmp_key.3ossl.bz2 /usr/share/man/man3/SSL_get_servername.3ossl.bz2 /usr/share/man/man3/SSL_get_servername_type.3ossl.bz2 /usr/share/man/man3/SSL_get_session.3ossl.bz2 /usr/share/man/man3/SSL_get_shared_ciphers.3ossl.bz2 /usr/share/man/man3/SSL_get_shared_curve.3ossl.bz2 /usr/share/man/man3/SSL_get_shared_group.3ossl.bz2 /usr/share/man/man3/SSL_get_shared_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_get_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_get_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_get_signature_nid.3ossl.bz2 /usr/share/man/man3/SSL_get_signature_type_nid.3ossl.bz2 /usr/share/man/man3/SSL_get_srp_N.3ossl.bz2 /usr/share/man/man3/SSL_get_srp_g.3ossl.bz2 /usr/share/man/man3/SSL_get_srp_userinfo.3ossl.bz2 /usr/share/man/man3/SSL_get_srp_username.3ossl.bz2 /usr/share/man/man3/SSL_get_srtp_profiles.3ossl.bz2 /usr/share/man/man3/SSL_get_ssl_method.3ossl.bz2 /usr/share/man/man3/SSL_get_state.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_id.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_read_error_code.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_read_state.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_type.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_write_buf_avail.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_write_buf_size.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_write_buf_used.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_write_error_code.3ossl.bz2 /usr/share/man/man3/SSL_get_stream_write_state.3ossl.bz2 /usr/share/man/man3/SSL_get_time.3ossl.bz2 /usr/share/man/man3/SSL_get_timeout.3ossl.bz2 /usr/share/man/man3/SSL_get_tlsext_status_ocsp_resp.3ossl.bz2 /usr/share/man/man3/SSL_get_tlsext_status_type.3ossl.bz2 /usr/share/man/man3/SSL_get_tmp_key.3ossl.bz2 /usr/share/man/man3/SSL_get_value_uint.3ossl.bz2 /usr/share/man/man3/SSL_get_verify_callback.3ossl.bz2 /usr/share/man/man3/SSL_get_verify_depth.3ossl.bz2 /usr/share/man/man3/SSL_get_verify_mode.3ossl.bz2 /usr/share/man/man3/SSL_get_verify_result.3ossl.bz2 /usr/share/man/man3/SSL_get_version.3ossl.bz2 /usr/share/man/man3/SSL_get_wbio.3ossl.bz2 /usr/share/man/man3/SSL_get_wfd.3ossl.bz2 /usr/share/man/man3/SSL_get_wpoll_descriptor.3ossl.bz2 /usr/share/man/man3/SSL_group_to_name.3ossl.bz2 /usr/share/man/man3/SSL_handle_events.3ossl.bz2 /usr/share/man/man3/SSL_has_matching_session_id.3ossl.bz2 /usr/share/man/man3/SSL_has_pending.3ossl.bz2 /usr/share/man/man3/SSL_in_accept_init.3ossl.bz2 /usr/share/man/man3/SSL_in_before.3ossl.bz2 /usr/share/man/man3/SSL_in_connect_init.3ossl.bz2 /usr/share/man/man3/SSL_in_init.3ossl.bz2 /usr/share/man/man3/SSL_inject_net_dgram.3ossl.bz2 /usr/share/man/man3/SSL_is_connection.3ossl.bz2 /usr/share/man/man3/SSL_is_domain.3ossl.bz2 /usr/share/man/man3/SSL_is_dtls.3ossl.bz2 /usr/share/man/man3/SSL_is_init_finished.3ossl.bz2 /usr/share/man/man3/SSL_is_listener.3ossl.bz2 /usr/share/man/man3/SSL_is_quic.3ossl.bz2 /usr/share/man/man3/SSL_is_server.3ossl.bz2 /usr/share/man/man3/SSL_is_stream_local.3ossl.bz2 /usr/share/man/man3/SSL_is_tls.3ossl.bz2 /usr/share/man/man3/SSL_key_update.3ossl.bz2 /usr/share/man/man3/SSL_library_init.3ossl.bz2 /usr/share/man/man3/SSL_listen.3ossl.bz2 /usr/share/man/man3/SSL_load_client_CA_file.3ossl.bz2 /usr/share/man/man3/SSL_load_client_CA_file_ex.3ossl.bz2 /usr/share/man/man3/SSL_load_error_strings.3ossl.bz2 /usr/share/man/man3/SSL_net_read_desired.3ossl.bz2 /usr/share/man/man3/SSL_net_write_desired.3ossl.bz2 /usr/share/man/man3/SSL_new.3ossl.bz2 /usr/share/man/man3/SSL_new_domain.3ossl.bz2 /usr/share/man/man3/SSL_new_from_listener.3ossl.bz2 /usr/share/man/man3/SSL_new_listener.3ossl.bz2 /usr/share/man/man3/SSL_new_listener_from.3ossl.bz2 /usr/share/man/man3/SSL_new_session_ticket.3ossl.bz2 /usr/share/man/man3/SSL_new_stream.3ossl.bz2 /usr/share/man/man3/SSL_peek.3ossl.bz2 /usr/share/man/man3/SSL_peek_ex.3ossl.bz2 /usr/share/man/man3/SSL_pending.3ossl.bz2 /usr/share/man/man3/SSL_poll.3ossl.bz2 /usr/share/man/man3/SSL_psk_client_cb_func.3ossl.bz2 /usr/share/man/man3/SSL_psk_find_session_cb_func.3ossl.bz2 /usr/share/man/man3/SSL_psk_server_cb_func.3ossl.bz2 /usr/share/man/man3/SSL_psk_use_session_cb_func.3ossl.bz2 /usr/share/man/man3/SSL_read.3ossl.bz2 /usr/share/man/man3/SSL_read_early_data.3ossl.bz2 /usr/share/man/man3/SSL_read_ex.3ossl.bz2 /usr/share/man/man3/SSL_renegotiate.3ossl.bz2 /usr/share/man/man3/SSL_renegotiate_abbreviated.3ossl.bz2 /usr/share/man/man3/SSL_renegotiate_pending.3ossl.bz2 /usr/share/man/man3/SSL_rstate_string.3ossl.bz2 /usr/share/man/man3/SSL_rstate_string_long.3ossl.bz2 /usr/share/man/man3/SSL_select_current_cert.3ossl.bz2 /usr/share/man/man3/SSL_select_next_proto.3ossl.bz2 /usr/share/man/man3/SSL_sendfile.3ossl.bz2 /usr/share/man/man3/SSL_session_reused.3ossl.bz2 /usr/share/man/man3/SSL_set0_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_set0_chain.3ossl.bz2 /usr/share/man/man3/SSL_set0_chain_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_set0_rbio.3ossl.bz2 /usr/share/man/man3/SSL_set0_security_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_set0_tlsext_status_ocsp_resp_ex.3ossl.bz2 /usr/share/man/man3/SSL_set0_tmp_dh_pkey.3ossl.bz2 /usr/share/man/man3/SSL_set0_verify_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_set0_wbio.3ossl.bz2 /usr/share/man/man3/SSL_set1_cert_comp_preference.3ossl.bz2 /usr/share/man/man3/SSL_set1_chain.3ossl.bz2 /usr/share/man/man3/SSL_set1_chain_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_set1_client_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_set1_client_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_set1_client_sigalgs_list.3ossl.bz2 /usr/share/man/man3/SSL_set1_compressed_cert.3ossl.bz2 /usr/share/man/man3/SSL_set1_curves.3ossl.bz2 /usr/share/man/man3/SSL_set1_curves_list.3ossl.bz2 /usr/share/man/man3/SSL_set1_groups.3ossl.bz2 /usr/share/man/man3/SSL_set1_groups_list.3ossl.bz2 /usr/share/man/man3/SSL_set1_host.3ossl.bz2 /usr/share/man/man3/SSL_set1_initial_peer_addr.3ossl.bz2 /usr/share/man/man3/SSL_set1_param.3ossl.bz2 /usr/share/man/man3/SSL_set1_server_cert_type.3ossl.bz2 /usr/share/man/man3/SSL_set1_sigalgs.3ossl.bz2 /usr/share/man/man3/SSL_set1_sigalgs_list.3ossl.bz2 /usr/share/man/man3/SSL_set1_verify_cert_store.3ossl.bz2 /usr/share/man/man3/SSL_set_accept_state.3ossl.bz2 /usr/share/man/man3/SSL_set_allow_early_data_cb.3ossl.bz2 /usr/share/man/man3/SSL_set_alpn_protos.3ossl.bz2 /usr/share/man/man3/SSL_set_app_data.3ossl.bz2 /usr/share/man/man3/SSL_set_async_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_async_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_set_bio.3ossl.bz2 /usr/share/man/man3/SSL_set_block_padding.3ossl.bz2 /usr/share/man/man3/SSL_set_block_padding_ex.3ossl.bz2 /usr/share/man/man3/SSL_set_blocking_mode.3ossl.bz2 /usr/share/man/man3/SSL_set_cert_cb.3ossl.bz2 /usr/share/man/man3/SSL_set_cipher_list.3ossl.bz2 /usr/share/man/man3/SSL_set_ciphersuites.3ossl.bz2 /usr/share/man/man3/SSL_set_client_CA_list.3ossl.bz2 /usr/share/man/man3/SSL_set_connect_state.3ossl.bz2 /usr/share/man/man3/SSL_set_ct_validation_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_current_cert.3ossl.bz2 /usr/share/man/man3/SSL_set_default_passwd_cb.3ossl.bz2 /usr/share/man/man3/SSL_set_default_passwd_cb_userdata.3ossl.bz2 /usr/share/man/man3/SSL_set_default_read_buffer_len.3ossl.bz2 /usr/share/man/man3/SSL_set_default_stream_mode.3ossl.bz2 /usr/share/man/man3/SSL_set_dh_auto.3ossl.bz2 /usr/share/man/man3/SSL_set_ecdh_auto.3ossl.bz2 /usr/share/man/man3/SSL_set_event_handling_mode.3ossl.bz2 /usr/share/man/man3/SSL_set_ex_data.3ossl.bz2 /usr/share/man/man3/SSL_set_fd.3ossl.bz2 /usr/share/man/man3/SSL_set_feature_request_uint.3ossl.bz2 /usr/share/man/man3/SSL_set_generate_session_id.3ossl.bz2 /usr/share/man/man3/SSL_set_generic_value_uint.3ossl.bz2 /usr/share/man/man3/SSL_set_hostflags.3ossl.bz2 /usr/share/man/man3/SSL_set_incoming_stream_policy.3ossl.bz2 /usr/share/man/man3/SSL_set_info_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_max_cert_list.3ossl.bz2 /usr/share/man/man3/SSL_set_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_set_max_pipelines.3ossl.bz2 /usr/share/man/man3/SSL_set_max_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_set_max_send_fragment.3ossl.bz2 /usr/share/man/man3/SSL_set_min_proto_version.3ossl.bz2 /usr/share/man/man3/SSL_set_mode.3ossl.bz2 /usr/share/man/man3/SSL_set_msg_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_msg_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_set_new_pending_conn_cb_fn.3ossl.bz2 /usr/share/man/man3/SSL_set_num_tickets.3ossl.bz2 /usr/share/man/man3/SSL_set_options.3ossl.bz2 /usr/share/man/man3/SSL_set_post_handshake_auth.3ossl.bz2 /usr/share/man/man3/SSL_set_psk_client_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_psk_find_session_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_psk_server_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_psk_use_session_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_purpose.3ossl.bz2 /usr/share/man/man3/SSL_set_quic_tls_cbs.3ossl.bz2 /usr/share/man/man3/SSL_set_quic_tls_early_data_enabled.3ossl.bz2 /usr/share/man/man3/SSL_set_quic_tls_transport_params.3ossl.bz2 /usr/share/man/man3/SSL_set_quiet_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_set_read_ahead.3ossl.bz2 /usr/share/man/man3/SSL_set_record_padding_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_record_padding_callback_arg.3ossl.bz2 /usr/share/man/man3/SSL_set_recv_max_early_data.3ossl.bz2 /usr/share/man/man3/SSL_set_retry_verify.3ossl.bz2 /usr/share/man/man3/SSL_set_rfd.3ossl.bz2 /usr/share/man/man3/SSL_set_security_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_security_level.3ossl.bz2 /usr/share/man/man3/SSL_set_session.3ossl.bz2 /usr/share/man/man3/SSL_set_session_id_context.3ossl.bz2 /usr/share/man/man3/SSL_set_session_secret_cb.3ossl.bz2 /usr/share/man/man3/SSL_set_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_set_split_send_fragment.3ossl.bz2 /usr/share/man/man3/SSL_set_srp_server_param.3ossl.bz2 /usr/share/man/man3/SSL_set_srp_server_param_pw.3ossl.bz2 /usr/share/man/man3/SSL_set_ssl_method.3ossl.bz2 /usr/share/man/man3/SSL_set_time.3ossl.bz2 /usr/share/man/man3/SSL_set_timeout.3ossl.bz2 /usr/share/man/man3/SSL_set_tlsext_host_name.3ossl.bz2 /usr/share/man/man3/SSL_set_tlsext_max_fragment_length.3ossl.bz2 /usr/share/man/man3/SSL_set_tlsext_status_ocsp_resp.3ossl.bz2 /usr/share/man/man3/SSL_set_tlsext_status_type.3ossl.bz2 /usr/share/man/man3/SSL_set_tlsext_use_srtp.3ossl.bz2 /usr/share/man/man3/SSL_set_tmp_dh.3ossl.bz2 /usr/share/man/man3/SSL_set_tmp_dh_callback.3ossl.bz2 /usr/share/man/man3/SSL_set_tmp_ecdh.3ossl.bz2 /usr/share/man/man3/SSL_set_trust.3ossl.bz2 /usr/share/man/man3/SSL_set_value_uint.3ossl.bz2 /usr/share/man/man3/SSL_set_verify.3ossl.bz2 /usr/share/man/man3/SSL_set_verify_depth.3ossl.bz2 /usr/share/man/man3/SSL_set_verify_result.3ossl.bz2 /usr/share/man/man3/SSL_set_wfd.3ossl.bz2 /usr/share/man/man3/SSL_shutdown.3ossl.bz2 /usr/share/man/man3/SSL_shutdown_ex.3ossl.bz2 /usr/share/man/man3/SSL_state_string.3ossl.bz2 /usr/share/man/man3/SSL_state_string_long.3ossl.bz2 /usr/share/man/man3/SSL_stateless.3ossl.bz2 /usr/share/man/man3/SSL_stream_conclude.3ossl.bz2 /usr/share/man/man3/SSL_stream_reset.3ossl.bz2 /usr/share/man/man3/SSL_trace.3ossl.bz2 /usr/share/man/man3/SSL_up_ref.3ossl.bz2 /usr/share/man/man3/SSL_use_PrivateKey.3ossl.bz2 /usr/share/man/man3/SSL_use_PrivateKey_ASN1.3ossl.bz2 /usr/share/man/man3/SSL_use_PrivateKey_file.3ossl.bz2 /usr/share/man/man3/SSL_use_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/SSL_use_RSAPrivateKey_ASN1.3ossl.bz2 /usr/share/man/man3/SSL_use_RSAPrivateKey_file.3ossl.bz2 /usr/share/man/man3/SSL_use_cert_and_key.3ossl.bz2 /usr/share/man/man3/SSL_use_certificate.3ossl.bz2 /usr/share/man/man3/SSL_use_certificate_ASN1.3ossl.bz2 /usr/share/man/man3/SSL_use_certificate_chain_file.3ossl.bz2 /usr/share/man/man3/SSL_use_certificate_file.3ossl.bz2 /usr/share/man/man3/SSL_use_psk_identity_hint.3ossl.bz2 /usr/share/man/man3/SSL_verify_cb.3ossl.bz2 /usr/share/man/man3/SSL_verify_client_post_handshake.3ossl.bz2 /usr/share/man/man3/SSL_version.3ossl.bz2 /usr/share/man/man3/SSL_waiting_for_async.3ossl.bz2 /usr/share/man/man3/SSL_want.3ossl.bz2 /usr/share/man/man3/SSL_want_async.3ossl.bz2 /usr/share/man/man3/SSL_want_async_job.3ossl.bz2 /usr/share/man/man3/SSL_want_client_hello_cb.3ossl.bz2 /usr/share/man/man3/SSL_want_nothing.3ossl.bz2 /usr/share/man/man3/SSL_want_read.3ossl.bz2 /usr/share/man/man3/SSL_want_retry_verify.3ossl.bz2 /usr/share/man/man3/SSL_want_write.3ossl.bz2 /usr/share/man/man3/SSL_want_x509_lookup.3ossl.bz2 /usr/share/man/man3/SSL_write.3ossl.bz2 /usr/share/man/man3/SSL_write_early_data.3ossl.bz2 /usr/share/man/man3/SSL_write_ex.3ossl.bz2 /usr/share/man/man3/SSL_write_ex2.3ossl.bz2 /usr/share/man/man3/SSLv23_client_method.3ossl.bz2 /usr/share/man/man3/SSLv23_method.3ossl.bz2 /usr/share/man/man3/SSLv23_server_method.3ossl.bz2 /usr/share/man/man3/SSLv3_client_method.3ossl.bz2 /usr/share/man/man3/SSLv3_method.3ossl.bz2 /usr/share/man/man3/SSLv3_server_method.3ossl.bz2 /usr/share/man/man3/SXNETID_free.3ossl.bz2 /usr/share/man/man3/SXNETID_new.3ossl.bz2 /usr/share/man/man3/SXNET_free.3ossl.bz2 /usr/share/man/man3/SXNET_new.3ossl.bz2 /usr/share/man/man3/TLS_FEATURE_free.3ossl.bz2 /usr/share/man/man3/TLS_FEATURE_new.3ossl.bz2 /usr/share/man/man3/TLS_client_method.3ossl.bz2 /usr/share/man/man3/TLS_method.3ossl.bz2 /usr/share/man/man3/TLS_server_method.3ossl.bz2 /usr/share/man/man3/TLSv1_1_client_method.3ossl.bz2 /usr/share/man/man3/TLSv1_1_method.3ossl.bz2 /usr/share/man/man3/TLSv1_1_server_method.3ossl.bz2 /usr/share/man/man3/TLSv1_2_client_method.3ossl.bz2 /usr/share/man/man3/TLSv1_2_method.3ossl.bz2 /usr/share/man/man3/TLSv1_2_server_method.3ossl.bz2 /usr/share/man/man3/TLSv1_client_method.3ossl.bz2 /usr/share/man/man3/TLSv1_method.3ossl.bz2 /usr/share/man/man3/TLSv1_server_method.3ossl.bz2 /usr/share/man/man3/TS_ACCURACY_dup.3ossl.bz2 /usr/share/man/man3/TS_ACCURACY_free.3ossl.bz2 /usr/share/man/man3/TS_ACCURACY_new.3ossl.bz2 /usr/share/man/man3/TS_MSG_IMPRINT_dup.3ossl.bz2 /usr/share/man/man3/TS_MSG_IMPRINT_free.3ossl.bz2 /usr/share/man/man3/TS_MSG_IMPRINT_new.3ossl.bz2 /usr/share/man/man3/TS_REQ_dup.3ossl.bz2 /usr/share/man/man3/TS_REQ_free.3ossl.bz2 /usr/share/man/man3/TS_REQ_new.3ossl.bz2 /usr/share/man/man3/TS_RESP_CTX_free.3ossl.bz2 /usr/share/man/man3/TS_RESP_CTX_new.3ossl.bz2 /usr/share/man/man3/TS_RESP_CTX_new_ex.3ossl.bz2 /usr/share/man/man3/TS_RESP_dup.3ossl.bz2 /usr/share/man/man3/TS_RESP_free.3ossl.bz2 /usr/share/man/man3/TS_RESP_new.3ossl.bz2 /usr/share/man/man3/TS_STATUS_INFO_dup.3ossl.bz2 /usr/share/man/man3/TS_STATUS_INFO_free.3ossl.bz2 /usr/share/man/man3/TS_STATUS_INFO_new.3ossl.bz2 /usr/share/man/man3/TS_TST_INFO_dup.3ossl.bz2 /usr/share/man/man3/TS_TST_INFO_free.3ossl.bz2 /usr/share/man/man3/TS_TST_INFO_new.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTS_set_certs.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_add_flags.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_cleanup.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_free.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_init.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_new.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set0_certs.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set0_data.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set0_imprint.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set0_store.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set_certs.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set_data.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set_flags.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set_imprint.3ossl.bz2 /usr/share/man/man3/TS_VERIFY_CTX_set_store.3ossl.bz2 /usr/share/man/man3/UI.3ossl.bz2
    /usr/share/man/man3/UI_METHOD.3ossl.bz2 /usr/share/man/man3/UI_OpenSSL.3ossl.bz2 /usr/share/man/man3/UI_STRING.3ossl.bz2 /usr/share/man/man3/UI_UTIL_read_pw.3ossl.bz2 /usr/share/man/man3/UI_UTIL_read_pw_string.3ossl.bz2 /usr/share/man/man3/UI_UTIL_wrap_read_pem_callback.3ossl.bz2 /usr/share/man/man3/UI_add_error_string.3ossl.bz2 /usr/share/man/man3/UI_add_info_string.3ossl.bz2 /usr/share/man/man3/UI_add_input_boolean.3ossl.bz2 /usr/share/man/man3/UI_add_input_string.3ossl.bz2 /usr/share/man/man3/UI_add_user_data.3ossl.bz2 /usr/share/man/man3/UI_add_verify_string.3ossl.bz2 /usr/share/man/man3/UI_construct_prompt.3ossl.bz2 /usr/share/man/man3/UI_create_method.3ossl.bz2 /usr/share/man/man3/UI_ctrl.3ossl.bz2 /usr/share/man/man3/UI_destroy_method.3ossl.bz2 /usr/share/man/man3/UI_dup_error_string.3ossl.bz2 /usr/share/man/man3/UI_dup_info_string.3ossl.bz2 /usr/share/man/man3/UI_dup_input_boolean.3ossl.bz2 /usr/share/man/man3/UI_dup_input_string.3ossl.bz2 /usr/share/man/man3/UI_dup_user_data.3ossl.bz2 /usr/share/man/man3/UI_dup_verify_string.3ossl.bz2 /usr/share/man/man3/UI_free.3ossl.bz2 /usr/share/man/man3/UI_get0_action_string.3ossl.bz2 /usr/share/man/man3/UI_get0_output_string.3ossl.bz2 /usr/share/man/man3/UI_get0_result.3ossl.bz2 /usr/share/man/man3/UI_get0_result_string.3ossl.bz2 /usr/share/man/man3/UI_get0_test_string.3ossl.bz2 /usr/share/man/man3/UI_get0_user_data.3ossl.bz2 /usr/share/man/man3/UI_get_app_data.3ossl.bz2 /usr/share/man/man3/UI_get_default_method.3ossl.bz2 /usr/share/man/man3/UI_get_ex_data.3ossl.bz2 /usr/share/man/man3/UI_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/UI_get_input_flags.3ossl.bz2 /usr/share/man/man3/UI_get_method.3ossl.bz2 /usr/share/man/man3/UI_get_result_length.3ossl.bz2 /usr/share/man/man3/UI_get_result_maxsize.3ossl.bz2 /usr/share/man/man3/UI_get_result_minsize.3ossl.bz2 /usr/share/man/man3/UI_get_result_string_length.3ossl.bz2 /usr/share/man/man3/UI_get_string_type.3ossl.bz2 /usr/share/man/man3/UI_method_get_closer.3ossl.bz2 /usr/share/man/man3/UI_method_get_data_destructor.3ossl.bz2 /usr/share/man/man3/UI_method_get_data_duplicator.3ossl.bz2 /usr/share/man/man3/UI_method_get_ex_data.3ossl.bz2 /usr/share/man/man3/UI_method_get_flusher.3ossl.bz2 /usr/share/man/man3/UI_method_get_opener.3ossl.bz2 /usr/share/man/man3/UI_method_get_prompt_constructor.3ossl.bz2 /usr/share/man/man3/UI_method_get_reader.3ossl.bz2 /usr/share/man/man3/UI_method_get_writer.3ossl.bz2 /usr/share/man/man3/UI_method_set_closer.3ossl.bz2 /usr/share/man/man3/UI_method_set_data_duplicator.3ossl.bz2 /usr/share/man/man3/UI_method_set_ex_data.3ossl.bz2 /usr/share/man/man3/UI_method_set_flusher.3ossl.bz2 /usr/share/man/man3/UI_method_set_opener.3ossl.bz2 /usr/share/man/man3/UI_method_set_prompt_constructor.3ossl.bz2 /usr/share/man/man3/UI_method_set_reader.3ossl.bz2 /usr/share/man/man3/UI_method_set_writer.3ossl.bz2 /usr/share/man/man3/UI_new.3ossl.bz2 /usr/share/man/man3/UI_new_method.3ossl.bz2 /usr/share/man/man3/UI_null.3ossl.bz2
    /usr/share/man/man3/UI_process.3ossl.bz2 /usr/share/man/man3/UI_set_app_data.3ossl.bz2 /usr/share/man/man3/UI_set_default_method.3ossl.bz2 /usr/share/man/man3/UI_set_ex_data.3ossl.bz2 /usr/share/man/man3/UI_set_method.3ossl.bz2 /usr/share/man/man3/UI_set_result.3ossl.bz2 /usr/share/man/man3/UI_set_result_ex.3ossl.bz2 /usr/share/man/man3/UI_string_types.3ossl.bz2 /usr/share/man/man3/USERNOTICE_free.3ossl.bz2 /usr/share/man/man3/USERNOTICE_new.3ossl.bz2 /usr/share/man/man3/X509V3_EXT_d2i.3ossl.bz2 /usr/share/man/man3/X509V3_EXT_i2d.3ossl.bz2 /usr/share/man/man3/X509V3_EXT_nconf.3ossl.bz2 /usr/share/man/man3/X509V3_EXT_nconf_nid.3ossl.bz2 /usr/share/man/man3/X509V3_EXT_print.3ossl.bz2 /usr/share/man/man3/X509V3_EXT_print_fp.3ossl.bz2 /usr/share/man/man3/X509V3_add1_i2d.3ossl.bz2 /usr/share/man/man3/X509V3_get_d2i.3ossl.bz2 /usr/share/man/man3/X509V3_set_ctx.3ossl.bz2 /usr/share/man/man3/X509V3_set_issuer_pkey.3ossl.bz2 /usr/share/man/man3/X509_ACERT_INFO_free.3ossl.bz2 /usr/share/man/man3/X509_ACERT_INFO_it.3ossl.bz2 /usr/share/man/man3/X509_ACERT_INFO_new.3ossl.bz2 /usr/share/man/man3/X509_ACERT_ISSUER_V2FORM_free.3ossl.bz2 /usr/share/man/man3/X509_ACERT_ISSUER_V2FORM_new.3ossl.bz2 /usr/share/man/man3/X509_ACERT_add1_attr.3ossl.bz2 /usr/share/man/man3/X509_ACERT_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/X509_ACERT_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_ACERT_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/X509_ACERT_add1_ext_i2d.3ossl.bz2 /usr/share/man/man3/X509_ACERT_add_attr_nconf.3ossl.bz2 /usr/share/man/man3/X509_ACERT_delete_attr.3ossl.bz2 /usr/share/man/man3/X509_ACERT_dup.3ossl.bz2 /usr/share/man/man3/X509_ACERT_free.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_extensions.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_holder_baseCertId.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_holder_digest.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_holder_entityName.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_info_sigalg.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_issuerName.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_issuerUID.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_notAfter.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_notBefore.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get0_signature.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_attr.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_attr_by_NID.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_attr_count.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_ext_d2i.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_signature_nid.3ossl.bz2 /usr/share/man/man3/X509_ACERT_get_version.3ossl.bz2 /usr/share/man/man3/X509_ACERT_it.3ossl.bz2 /usr/share/man/man3/X509_ACERT_new.3ossl.bz2 /usr/share/man/man3/X509_ACERT_print.3ossl.bz2 /usr/share/man/man3/X509_ACERT_print_ex.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set0_holder_baseCertId.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set0_holder_digest.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set0_holder_entityName.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set1_issuerName.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set1_notAfter.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set1_notBefore.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set1_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_ACERT_set_version.3ossl.bz2 /usr/share/man/man3/X509_ACERT_sign.3ossl.bz2 /usr/share/man/man3/X509_ACERT_sign_ctx.3ossl.bz2 /usr/share/man/man3/X509_ACERT_verify.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_cmp.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_copy.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_dup.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_free.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_get0.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_it.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_new.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_set0.3ossl.bz2 /usr/share/man/man3/X509_ALGOR_set_md.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_count.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_create.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_create_by_NID.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_create_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_create_by_txt.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_dup.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_free.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_get0_data.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_get0_object.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_get0_type.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_new.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_set1_data.3ossl.bz2 /usr/share/man/man3/X509_ATTRIBUTE_set1_object.3ossl.bz2 /usr/share/man/man3/X509_CERT_AUX_free.3ossl.bz2 /usr/share/man/man3/X509_CERT_AUX_new.3ossl.bz2 /usr/share/man/man3/X509_CINF_free.3ossl.bz2 /usr/share/man/man3/X509_CINF_new.3ossl.bz2 /usr/share/man/man3/X509_CRL_INFO_free.3ossl.bz2 /usr/share/man/man3/X509_CRL_INFO_new.3ossl.bz2 /usr/share/man/man3/X509_CRL_add0_revoked.3ossl.bz2 /usr/share/man/man3/X509_CRL_add1_ext_i2d.3ossl.bz2 /usr/share/man/man3/X509_CRL_add_ext.3ossl.bz2 /usr/share/man/man3/X509_CRL_cmp.3ossl.bz2 /usr/share/man/man3/X509_CRL_delete_ext.3ossl.bz2 /usr/share/man/man3/X509_CRL_digest.3ossl.bz2 /usr/share/man/man3/X509_CRL_dup.3ossl.bz2 /usr/share/man/man3/X509_CRL_free.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_by_cert.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_by_serial.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_extensions.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_lastUpdate.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_nextUpdate.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_signature.3ossl.bz2 /usr/share/man/man3/X509_CRL_get0_tbs_sigalg.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_REVOKED.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_ext.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_ext_by_NID.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_ext_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_ext_by_critical.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_ext_count.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_ext_d2i.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_issuer.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_signature_nid.3ossl.bz2 /usr/share/man/man3/X509_CRL_get_version.3ossl.bz2 /usr/share/man/man3/X509_CRL_http_nbio.3ossl.bz2 /usr/share/man/man3/X509_CRL_load_http.3ossl.bz2 /usr/share/man/man3/X509_CRL_match.3ossl.bz2 /usr/share/man/man3/X509_CRL_new.3ossl.bz2 /usr/share/man/man3/X509_CRL_new_ex.3ossl.bz2 /usr/share/man/man3/X509_CRL_set1_lastUpdate.3ossl.bz2 /usr/share/man/man3/X509_CRL_set1_nextUpdate.3ossl.bz2 /usr/share/man/man3/X509_CRL_set_issuer_name.3ossl.bz2 /usr/share/man/man3/X509_CRL_set_version.3ossl.bz2 /usr/share/man/man3/X509_CRL_sign.3ossl.bz2 /usr/share/man/man3/X509_CRL_sign_ctx.3ossl.bz2 /usr/share/man/man3/X509_CRL_sort.3ossl.bz2 /usr/share/man/man3/X509_CRL_verify.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_create_by_NID.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_create_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_dup.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_free.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_get_critical.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_get_data.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_get_object.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_new.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_set_critical.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_set_data.3ossl.bz2 /usr/share/man/man3/X509_EXTENSION_set_object.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_METHOD.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_TYPE.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_add_dir.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_add_store.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_add_store_ex.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_by_alias.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_by_fingerprint.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_by_issuer_serial.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_by_subject.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_by_subject_ex.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_ctrl.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_ctrl_ex.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_ctrl_fn.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_file.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_free.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_get_by_alias_fn.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_get_by_fingerprint_fn.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_get_by_issuer_serial_fn.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_get_by_subject_fn.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_get_method_data.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_get_store.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_hash_dir.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_init.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_load_file.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_load_file_ex.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_load_store.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_load_store_ex.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_free.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_ctrl.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_free.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_get_by_alias.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_get_by_fingerprint.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_get_by_issuer_serial.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_get_by_subject.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_init.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_new_item.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_get_shutdown.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_new.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_ctrl.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_free.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_get_by_alias.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_get_by_fingerprint.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_get_by_issuer_serial.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_get_by_subject.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_init.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_new_item.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_meth_set_shutdown.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_new.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_set_method_data.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_shutdown.3ossl.bz2 /usr/share/man/man3/X509_LOOKUP_store.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_create_by_NID.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_create_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_create_by_txt.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_dup.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_free.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_get_data.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_get_object.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_new.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_set_data.3ossl.bz2 /usr/share/man/man3/X509_NAME_ENTRY_set_object.3ossl.bz2 /usr/share/man/man3/X509_NAME_add_entry.3ossl.bz2 /usr/share/man/man3/X509_NAME_add_entry_by_NID.3ossl.bz2 /usr/share/man/man3/X509_NAME_add_entry_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_NAME_add_entry_by_txt.3ossl.bz2 /usr/share/man/man3/X509_NAME_cmp.3ossl.bz2 /usr/share/man/man3/X509_NAME_delete_entry.3ossl.bz2 /usr/share/man/man3/X509_NAME_digest.3ossl.bz2 /usr/share/man/man3/X509_NAME_dup.3ossl.bz2 /usr/share/man/man3/X509_NAME_entry_count.3ossl.bz2 /usr/share/man/man3/X509_NAME_free.3ossl.bz2 /usr/share/man/man3/X509_NAME_get0_der.3ossl.bz2 /usr/share/man/man3/X509_NAME_get_entry.3ossl.bz2 /usr/share/man/man3/X509_NAME_get_index_by_NID.3ossl.bz2 /usr/share/man/man3/X509_NAME_get_index_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_NAME_get_text_by_NID.3ossl.bz2 /usr/share/man/man3/X509_NAME_get_text_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_NAME_hash.3ossl.bz2 /usr/share/man/man3/X509_NAME_hash_ex.3ossl.bz2 /usr/share/man/man3/X509_NAME_new.3ossl.bz2 /usr/share/man/man3/X509_NAME_oneline.3ossl.bz2 /usr/share/man/man3/X509_NAME_print.3ossl.bz2 /usr/share/man/man3/X509_NAME_print_ex.3ossl.bz2 /usr/share/man/man3/X509_NAME_print_ex_fp.3ossl.bz2 /usr/share/man/man3/X509_OBJECT_set1_X509.3ossl.bz2 /usr/share/man/man3/X509_OBJECT_set1_X509_CRL.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_dup.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_eq.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_free.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_get.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_get0.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_get0_param.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_new.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_new_ex.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_set.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_set0_param.3ossl.bz2 /usr/share/man/man3/X509_PUBKEY_set0_public_key.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_add.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_cleanup.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get0.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get0_name.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get0_sname.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get_by_id.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get_by_sname.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get_count.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get_id.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get_trust.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_get_unused_id.3ossl.bz2 /usr/share/man/man3/X509_PURPOSE_set.3ossl.bz2 /usr/share/man/man3/X509_REQ_INFO_free.3ossl.bz2 /usr/share/man/man3/X509_REQ_INFO_new.3ossl.bz2 /usr/share/man/man3/X509_REQ_add1_attr.3ossl.bz2 /usr/share/man/man3/X509_REQ_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/X509_REQ_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_REQ_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/X509_REQ_add_extensions.3ossl.bz2 /usr/share/man/man3/X509_REQ_add_extensions_nid.3ossl.bz2 /usr/share/man/man3/X509_REQ_check_private_key.3ossl.bz2 /usr/share/man/man3/X509_REQ_delete_attr.3ossl.bz2 /usr/share/man/man3/X509_REQ_digest.3ossl.bz2 /usr/share/man/man3/X509_REQ_dup.3ossl.bz2 /usr/share/man/man3/X509_REQ_free.3ossl.bz2 /usr/share/man/man3/X509_REQ_get0_distinguishing_id.3ossl.bz2 /usr/share/man/man3/X509_REQ_get0_pubkey.3ossl.bz2 /usr/share/man/man3/X509_REQ_get0_signature.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_attr.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_attr_by_NID.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_attr_count.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_extensions.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_pubkey.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_signature_nid.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_subject_name.3ossl.bz2 /usr/share/man/man3/X509_REQ_get_version.3ossl.bz2 /usr/share/man/man3/X509_REQ_new.3ossl.bz2 /usr/share/man/man3/X509_REQ_new_ex.3ossl.bz2 /usr/share/man/man3/X509_REQ_set0_distinguishing_id.3ossl.bz2 /usr/share/man/man3/X509_REQ_set0_signature.3ossl.bz2 /usr/share/man/man3/X509_REQ_set1_signature_algo.3ossl.bz2 /usr/share/man/man3/X509_REQ_set_pubkey.3ossl.bz2 /usr/share/man/man3/X509_REQ_set_subject_name.3ossl.bz2 /usr/share/man/man3/X509_REQ_set_version.3ossl.bz2 /usr/share/man/man3/X509_REQ_sign.3ossl.bz2 /usr/share/man/man3/X509_REQ_sign_ctx.3ossl.bz2 /usr/share/man/man3/X509_REQ_verify.3ossl.bz2 /usr/share/man/man3/X509_REQ_verify_ex.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_add1_ext_i2d.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_add_ext.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_delete_ext.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_dup.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_free.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get0_extensions.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get0_revocationDate.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get0_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get_ext.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get_ext_by_NID.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get_ext_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get_ext_by_critical.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get_ext_count.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_get_ext_d2i.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_new.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_set_revocationDate.3ossl.bz2 /usr/share/man/man3/X509_REVOKED_set_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_SIG_INFO_get.3ossl.bz2 /usr/share/man/man3/X509_SIG_INFO_set.3ossl.bz2 /usr/share/man/man3/X509_SIG_free.3ossl.bz2 /usr/share/man/man3/X509_SIG_get0.3ossl.bz2 /usr/share/man/man3/X509_SIG_getm.3ossl.bz2 /usr/share/man/man3/X509_SIG_new.3ossl.bz2 /usr/share/man/man3/X509_STORE.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_cert_crl_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_check_crl_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_check_issued_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_check_policy_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_check_revocation_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_cleanup.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_cleanup_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_free.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get0_cert.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get0_chain.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get0_param.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get0_rpk.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get0_untrusted.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get1_chain.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get1_issuer.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_app_data.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_by_subject.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_cert_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_check_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_check_issued.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_check_policy.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_check_revocation.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_cleanup.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_crl_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_current_cert.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_error.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_error_depth.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_ex_data.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_get_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_get_issuer.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_issuer_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_lookup_certs.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_lookup_crls.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_num_untrusted.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_obj_by_subject.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_verify.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_get_verify_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_init.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_init_rpk.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_lookup_certs_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_lookup_crls_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_new.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_new_ex.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_print_verify_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_purpose_inherit.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set0_crls.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set0_param.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set0_rpk.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set0_trusted_stack.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set0_untrusted.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set0_verified_chain.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_app_data.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_cert.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_current_cert.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_current_reasons.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_default.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_error.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_error_depth.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_ex_data.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_get_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_ocsp_resp.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_purpose.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_trust.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_verify.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_set_verify_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_verify.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_verify_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_CTX_verify_fn.3ossl.bz2 /usr/share/man/man3/X509_STORE_add_cert.3ossl.bz2 /usr/share/man/man3/X509_STORE_add_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_add_lookup.3ossl.bz2 /usr/share/man/man3/X509_STORE_free.3ossl.bz2 /usr/share/man/man3/X509_STORE_get0_objects.3ossl.bz2 /usr/share/man/man3/X509_STORE_get0_param.3ossl.bz2 /usr/share/man/man3/X509_STORE_get1_all_certs.3ossl.bz2 /usr/share/man/man3/X509_STORE_get1_objects.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_cert_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_check_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_check_issued.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_check_policy.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_check_revocation.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_cleanup.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_ex_data.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_get_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_get_issuer.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_lookup_certs.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_lookup_crls.3ossl.bz2 /usr/share/man/man3/X509_STORE_get_verify_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_file.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_file_ex.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_locations.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_locations_ex.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_path.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_store.3ossl.bz2 /usr/share/man/man3/X509_STORE_load_store_ex.3ossl.bz2 /usr/share/man/man3/X509_STORE_lock.3ossl.bz2 /usr/share/man/man3/X509_STORE_new.3ossl.bz2 /usr/share/man/man3/X509_STORE_set1_param.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_cert_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_check_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_check_issued.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_check_policy.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_check_revocation.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_cleanup.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_default_paths.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_default_paths_ex.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_depth.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_ex_data.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_flags.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_get_crl.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_get_issuer.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_lookup_certs.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_lookup_crls.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_lookup_crls_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_purpose.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_trust.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_verify.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_verify_cb.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_verify_cb_func.3ossl.bz2 /usr/share/man/man3/X509_STORE_set_verify_func.3ossl.bz2 /usr/share/man/man3/X509_STORE_unlock.3ossl.bz2 /usr/share/man/man3/X509_STORE_up_ref.3ossl.bz2 /usr/share/man/man3/X509_VAL_free.3ossl.bz2 /usr/share/man/man3/X509_VAL_new.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_add0_policy.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_add1_host.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_clear_flags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get0_email.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get0_host.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get0_peername.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get1_ip_asc.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_auth_level.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_depth.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_flags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_hostflags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_inh_flags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_purpose.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_get_time.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set1_email.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set1_host.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set1_ip.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set1_ip_asc.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set1_policies.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_auth_level.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_depth.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_flags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_hostflags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_inh_flags.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_purpose.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_time.3ossl.bz2 /usr/share/man/man3/X509_VERIFY_PARAM_set_trust.3ossl.bz2 /usr/share/man/man3/X509_add1_ext_i2d.3ossl.bz2 /usr/share/man/man3/X509_add_cert.3ossl.bz2 /usr/share/man/man3/X509_add_certs.3ossl.bz2 /usr/share/man/man3/X509_add_ext.3ossl.bz2 /usr/share/man/man3/X509_build_chain.3ossl.bz2 /usr/share/man/man3/X509_chain_up_ref.3ossl.bz2 /usr/share/man/man3/X509_check_ca.3ossl.bz2 /usr/share/man/man3/X509_check_email.3ossl.bz2 /usr/share/man/man3/X509_check_host.3ossl.bz2 /usr/share/man/man3/X509_check_ip.3ossl.bz2 /usr/share/man/man3/X509_check_ip_asc.3ossl.bz2 /usr/share/man/man3/X509_check_issued.3ossl.bz2 /usr/share/man/man3/X509_check_private_key.3ossl.bz2 /usr/share/man/man3/X509_check_purpose.3ossl.bz2 /usr/share/man/man3/X509_cmp.3ossl.bz2 /usr/share/man/man3/X509_cmp_current_time.3ossl.bz2 /usr/share/man/man3/X509_cmp_time.3ossl.bz2 /usr/share/man/man3/X509_cmp_timeframe.3ossl.bz2 /usr/share/man/man3/X509_delete_ext.3ossl.bz2 /usr/share/man/man3/X509_digest.3ossl.bz2 /usr/share/man/man3/X509_digest_sig.3ossl.bz2 /usr/share/man/man3/X509_dup.3ossl.bz2
    /usr/share/man/man3/X509_free.3ossl.bz2 /usr/share/man/man3/X509_get0_authority_issuer.3ossl.bz2 /usr/share/man/man3/X509_get0_authority_key_id.3ossl.bz2 /usr/share/man/man3/X509_get0_authority_serial.3ossl.bz2 /usr/share/man/man3/X509_get0_distinguishing_id.3ossl.bz2 /usr/share/man/man3/X509_get0_extensions.3ossl.bz2 /usr/share/man/man3/X509_get0_notAfter.3ossl.bz2 /usr/share/man/man3/X509_get0_notBefore.3ossl.bz2 /usr/share/man/man3/X509_get0_pubkey.3ossl.bz2 /usr/share/man/man3/X509_get0_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_get0_signature.3ossl.bz2 /usr/share/man/man3/X509_get0_subject_key_id.3ossl.bz2 /usr/share/man/man3/X509_get0_tbs_sigalg.3ossl.bz2 /usr/share/man/man3/X509_get0_uids.3ossl.bz2 /usr/share/man/man3/X509_get_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/X509_get_default_cert_dir.3ossl.bz2 /usr/share/man/man3/X509_get_default_cert_dir_env.3ossl.bz2 /usr/share/man/man3/X509_get_default_cert_file.3ossl.bz2 /usr/share/man/man3/X509_get_default_cert_file_env.3ossl.bz2 /usr/share/man/man3/X509_get_ex_data.3ossl.bz2 /usr/share/man/man3/X509_get_ex_new_index.3ossl.bz2 /usr/share/man/man3/X509_get_ext.3ossl.bz2 /usr/share/man/man3/X509_get_ext_by_NID.3ossl.bz2 /usr/share/man/man3/X509_get_ext_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509_get_ext_by_critical.3ossl.bz2 /usr/share/man/man3/X509_get_ext_count.3ossl.bz2 /usr/share/man/man3/X509_get_ext_d2i.3ossl.bz2 /usr/share/man/man3/X509_get_extended_key_usage.3ossl.bz2 /usr/share/man/man3/X509_get_extension_flags.3ossl.bz2 /usr/share/man/man3/X509_get_issuer_name.3ossl.bz2 /usr/share/man/man3/X509_get_key_usage.3ossl.bz2 /usr/share/man/man3/X509_get_pathlen.3ossl.bz2 /usr/share/man/man3/X509_get_proxy_pathlen.3ossl.bz2 /usr/share/man/man3/X509_get_pubkey.3ossl.bz2 /usr/share/man/man3/X509_get_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_get_signature_info.3ossl.bz2 /usr/share/man/man3/X509_get_signature_nid.3ossl.bz2 /usr/share/man/man3/X509_get_subject_name.3ossl.bz2 /usr/share/man/man3/X509_get_version.3ossl.bz2 /usr/share/man/man3/X509_getm_notAfter.3ossl.bz2 /usr/share/man/man3/X509_getm_notBefore.3ossl.bz2 /usr/share/man/man3/X509_gmtime_adj.3ossl.bz2 /usr/share/man/man3/X509_http_nbio.3ossl.bz2 /usr/share/man/man3/X509_issuer_and_serial_cmp.3ossl.bz2 /usr/share/man/man3/X509_issuer_name_cmp.3ossl.bz2 /usr/share/man/man3/X509_issuer_name_hash.3ossl.bz2 /usr/share/man/man3/X509_load_cert_crl_file.3ossl.bz2 /usr/share/man/man3/X509_load_cert_crl_file_ex.3ossl.bz2 /usr/share/man/man3/X509_load_cert_file.3ossl.bz2 /usr/share/man/man3/X509_load_cert_file_ex.3ossl.bz2 /usr/share/man/man3/X509_load_crl_file.3ossl.bz2 /usr/share/man/man3/X509_load_http.3ossl.bz2 /usr/share/man/man3/X509_new.3ossl.bz2 /usr/share/man/man3/X509_new_ex.3ossl.bz2 /usr/share/man/man3/X509_pubkey_digest.3ossl.bz2 /usr/share/man/man3/X509_self_signed.3ossl.bz2 /usr/share/man/man3/X509_set0_distinguishing_id.3ossl.bz2 /usr/share/man/man3/X509_set1_notAfter.3ossl.bz2 /usr/share/man/man3/X509_set1_notBefore.3ossl.bz2 /usr/share/man/man3/X509_set_ex_data.3ossl.bz2 /usr/share/man/man3/X509_set_issuer_name.3ossl.bz2 /usr/share/man/man3/X509_set_proxy_flag.3ossl.bz2 /usr/share/man/man3/X509_set_proxy_pathlen.3ossl.bz2 /usr/share/man/man3/X509_set_pubkey.3ossl.bz2 /usr/share/man/man3/X509_set_serialNumber.3ossl.bz2 /usr/share/man/man3/X509_set_subject_name.3ossl.bz2 /usr/share/man/man3/X509_set_version.3ossl.bz2 /usr/share/man/man3/X509_sign.3ossl.bz2 /usr/share/man/man3/X509_sign_ctx.3ossl.bz2 /usr/share/man/man3/X509_subject_name_cmp.3ossl.bz2 /usr/share/man/man3/X509_subject_name_hash.3ossl.bz2 /usr/share/man/man3/X509_time_adj.3ossl.bz2 /usr/share/man/man3/X509_time_adj_ex.3ossl.bz2 /usr/share/man/man3/X509_up_ref.3ossl.bz2 /usr/share/man/man3/X509_verify.3ossl.bz2 /usr/share/man/man3/X509_verify_cert.3ossl.bz2 /usr/share/man/man3/X509_verify_cert_error_string.3ossl.bz2 /usr/share/man/man3/X509at_add1_attr.3ossl.bz2 /usr/share/man/man3/X509at_add1_attr_by_NID.3ossl.bz2 /usr/share/man/man3/X509at_add1_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509at_add1_attr_by_txt.3ossl.bz2 /usr/share/man/man3/X509at_delete_attr.3ossl.bz2 /usr/share/man/man3/X509at_get0_data_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509at_get_attr.3ossl.bz2 /usr/share/man/man3/X509at_get_attr_by_NID.3ossl.bz2 /usr/share/man/man3/X509at_get_attr_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509at_get_attr_count.3ossl.bz2 /usr/share/man/man3/X509v3_add_ext.3ossl.bz2 /usr/share/man/man3/X509v3_add_extensions.3ossl.bz2 /usr/share/man/man3/X509v3_delete_ext.3ossl.bz2 /usr/share/man/man3/X509v3_get_ext.3ossl.bz2 /usr/share/man/man3/X509v3_get_ext_by_NID.3ossl.bz2 /usr/share/man/man3/X509v3_get_ext_by_OBJ.3ossl.bz2 /usr/share/man/man3/X509v3_get_ext_by_critical.3ossl.bz2 /usr/share/man/man3/X509v3_get_ext_count.3ossl.bz2 /usr/share/man/man3/b2i_PVK_bio.3ossl.bz2 /usr/share/man/man3/b2i_PVK_bio_ex.3ossl.bz2 /usr/share/man/man3/custom_ext_add_cb.3ossl.bz2 /usr/share/man/man3/custom_ext_free_cb.3ossl.bz2 /usr/share/man/man3/custom_ext_parse_cb.3ossl.bz2 /usr/share/man/man3/d2i_ACCESS_DESCRIPTION.3ossl.bz2 /usr/share/man/man3/d2i_ADMISSIONS.3ossl.bz2 /usr/share/man/man3/d2i_ADMISSION_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_ASIdOrRange.3ossl.bz2 /usr/share/man/man3/d2i_ASIdentifierChoice.3ossl.bz2 /usr/share/man/man3/d2i_ASIdentifiers.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_BIT_STRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_BMPSTRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_ENUMERATED.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_GENERALIZEDTIME.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_GENERALSTRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_IA5STRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_INTEGER.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_NULL.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_OBJECT.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_OCTET_STRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_PRINTABLE.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_PRINTABLESTRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_SEQUENCE_ANY.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_SET_ANY.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_T61STRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_TIME.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_TYPE.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_UINTEGER.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_UNIVERSALSTRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_UTCTIME.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_UTF8STRING.3ossl.bz2 /usr/share/man/man3/d2i_ASN1_VISIBLESTRING.3ossl.bz2 /usr/share/man/man3/d2i_ASRange.3ossl.bz2 /usr/share/man/man3/d2i_AUTHORITY_INFO_ACCESS.3ossl.bz2 /usr/share/man/man3/d2i_AUTHORITY_KEYID.3ossl.bz2 /usr/share/man/man3/d2i_AutoPrivateKey.3ossl.bz2 /usr/share/man/man3/d2i_AutoPrivateKey_ex.3ossl.bz2 /usr/share/man/man3/d2i_BASIC_CONSTRAINTS.3ossl.bz2 /usr/share/man/man3/d2i_CERTIFICATEPOLICIES.3ossl.bz2 /usr/share/man/man3/d2i_CMS_ContentInfo.3ossl.bz2 /usr/share/man/man3/d2i_CMS_ReceiptRequest.3ossl.bz2 /usr/share/man/man3/d2i_CMS_bio.3ossl.bz2 /usr/share/man/man3/d2i_CRL_DIST_POINTS.3ossl.bz2 /usr/share/man/man3/d2i_DHparams.3ossl.bz2 /usr/share/man/man3/d2i_DHparams_bio.3ossl.bz2 /usr/share/man/man3/d2i_DHparams_fp.3ossl.bz2 /usr/share/man/man3/d2i_DHxparams.3ossl.bz2 /usr/share/man/man3/d2i_DIRECTORYSTRING.3ossl.bz2 /usr/share/man/man3/d2i_DISPLAYTEXT.3ossl.bz2 /usr/share/man/man3/d2i_DIST_POINT.3ossl.bz2 /usr/share/man/man3/d2i_DIST_POINT_NAME.3ossl.bz2 /usr/share/man/man3/d2i_DSAPrivateKey.3ossl.bz2 /usr/share/man/man3/d2i_DSAPrivateKey_bio.3ossl.bz2 /usr/share/man/man3/d2i_DSAPrivateKey_fp.3ossl.bz2 /usr/share/man/man3/d2i_DSAPublicKey.3ossl.bz2 /usr/share/man/man3/d2i_DSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/d2i_DSA_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/d2i_DSA_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/d2i_DSA_SIG.3ossl.bz2 /usr/share/man/man3/d2i_DSAparams.3ossl.bz2 /usr/share/man/man3/d2i_ECDSA_SIG.3ossl.bz2 /usr/share/man/man3/d2i_ECPKParameters.3ossl.bz2 /usr/share/man/man3/d2i_ECParameters.3ossl.bz2 /usr/share/man/man3/d2i_ECPrivateKey.3ossl.bz2 /usr/share/man/man3/d2i_ECPrivateKey_bio.3ossl.bz2 /usr/share/man/man3/d2i_ECPrivateKey_fp.3ossl.bz2 /usr/share/man/man3/d2i_EC_PUBKEY.3ossl.bz2 /usr/share/man/man3/d2i_EC_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/d2i_EC_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/d2i_EDIPARTYNAME.3ossl.bz2 /usr/share/man/man3/d2i_ESS_CERT_ID.3ossl.bz2 /usr/share/man/man3/d2i_ESS_CERT_ID_V2.3ossl.bz2 /usr/share/man/man3/d2i_ESS_ISSUER_SERIAL.3ossl.bz2 /usr/share/man/man3/d2i_ESS_SIGNING_CERT.3ossl.bz2 /usr/share/man/man3/d2i_ESS_SIGNING_CERT_V2.3ossl.bz2 /usr/share/man/man3/d2i_EXTENDED_KEY_USAGE.3ossl.bz2 /usr/share/man/man3/d2i_GENERAL_NAME.3ossl.bz2 /usr/share/man/man3/d2i_GENERAL_NAMES.3ossl.bz2 /usr/share/man/man3/d2i_IPAddressChoice.3ossl.bz2 /usr/share/man/man3/d2i_IPAddressFamily.3ossl.bz2 /usr/share/man/man3/d2i_IPAddressOrRange.3ossl.bz2 /usr/share/man/man3/d2i_IPAddressRange.3ossl.bz2 /usr/share/man/man3/d2i_ISSUER_SIGN_TOOL.3ossl.bz2 /usr/share/man/man3/d2i_ISSUING_DIST_POINT.3ossl.bz2 /usr/share/man/man3/d2i_KeyParams.3ossl.bz2 /usr/share/man/man3/d2i_KeyParams_bio.3ossl.bz2 /usr/share/man/man3/d2i_NAMING_AUTHORITY.3ossl.bz2 /usr/share/man/man3/d2i_NETSCAPE_CERT_SEQUENCE.3ossl.bz2 /usr/share/man/man3/d2i_NETSCAPE_SPKAC.3ossl.bz2 /usr/share/man/man3/d2i_NETSCAPE_SPKI.3ossl.bz2 /usr/share/man/man3/d2i_NOTICEREF.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_BASICRESP.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_CERTID.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_CERTSTATUS.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_CRLID.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_ONEREQ.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_REQINFO.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_REQUEST.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_RESPBYTES.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_RESPDATA.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_RESPID.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_RESPONSE.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_REVOKEDINFO.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_SERVICELOC.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_SIGNATURE.3ossl.bz2 /usr/share/man/man3/d2i_OCSP_SINGLERESP.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_AA_DIST_POINT.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ALLOWED_ATTRIBUTES_CHOICE.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ALLOWED_ATTRIBUTES_ITEM.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ALLOWED_ATTRIBUTES_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATAV.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATTRIBUTES_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATTRIBUTE_DESCRIPTOR.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATTRIBUTE_MAPPING.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATTRIBUTE_MAPPINGS.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATTRIBUTE_TYPE_MAPPING.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ATTRIBUTE_VALUE_MAPPING.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_AUTHORITY_ATTRIBUTE_ID_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_BASIC_ATTR_CONSTRAINTS.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CMP_ATAVS.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CMP_MSG.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CMP_MSG_bio.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CMP_PKIHEADER.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CMP_PKISI.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_CERTID.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_CERTTEMPLATE.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_ENCRYPTEDKEY.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_ENCRYPTEDVALUE.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_MSG.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_MSGS.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_PBMPARAMETER.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_PKIPUBLICATIONINFO.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_CRMF_SINGLEPUBINFO.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_DAY_TIME.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_DAY_TIME_BAND.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_HASH.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_IETF_ATTR_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_INFO_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_INFO_SYNTAX_POINTER.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ISSUER_SERIAL.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_NAMED_DAY.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_OBJECT_DIGEST_INFO.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_PRIVILEGE_POLICY_ID.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ROLE_SPEC_CERT_ID.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_ROLE_SPEC_CERT_ID_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TARGET.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TARGETING_INFORMATION.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TARGETS.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TARGET_CERT.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_PERIOD.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC_ABSOLUTE.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC_DAY.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC_MONTH.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC_TIME.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC_WEEKS.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_TIME_SPEC_X_DAY_OF.3ossl.bz2 /usr/share/man/man3/d2i_OSSL_USER_NOTICE_SYNTAX.3ossl.bz2 /usr/share/man/man3/d2i_OTHERNAME.3ossl.bz2 /usr/share/man/man3/d2i_PBE2PARAM.3ossl.bz2 /usr/share/man/man3/d2i_PBEPARAM.3ossl.bz2 /usr/share/man/man3/d2i_PBKDF2PARAM.3ossl.bz2 /usr/share/man/man3/d2i_PBMAC1PARAM.3ossl.bz2 /usr/share/man/man3/d2i_PKCS12.3ossl.bz2 /usr/share/man/man3/d2i_PKCS12_BAGS.3ossl.bz2 /usr/share/man/man3/d2i_PKCS12_MAC_DATA.3ossl.bz2 /usr/share/man/man3/d2i_PKCS12_SAFEBAG.3ossl.bz2 /usr/share/man/man3/d2i_PKCS12_bio.3ossl.bz2 /usr/share/man/man3/d2i_PKCS12_fp.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_DIGEST.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_ENCRYPT.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_ENC_CONTENT.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_ENVELOPE.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_ISSUER_AND_SERIAL.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_RECIP_INFO.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_SIGNED.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_SIGNER_INFO.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_SIGN_ENVELOPE.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_bio.3ossl.bz2 /usr/share/man/man3/d2i_PKCS7_fp.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8PrivateKey_bio.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8PrivateKey_fp.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8_PRIV_KEY_INFO.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8_PRIV_KEY_INFO_bio.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8_PRIV_KEY_INFO_fp.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8_bio.3ossl.bz2 /usr/share/man/man3/d2i_PKCS8_fp.3ossl.bz2 /usr/share/man/man3/d2i_PKEY_USAGE_PERIOD.3ossl.bz2 /usr/share/man/man3/d2i_POLICYINFO.3ossl.bz2 /usr/share/man/man3/d2i_POLICYQUALINFO.3ossl.bz2 /usr/share/man/man3/d2i_PROFESSION_INFO.3ossl.bz2 /usr/share/man/man3/d2i_PROXY_CERT_INFO_EXTENSION.3ossl.bz2 /usr/share/man/man3/d2i_PROXY_POLICY.3ossl.bz2 /usr/share/man/man3/d2i_PUBKEY.3ossl.bz2 /usr/share/man/man3/d2i_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/d2i_PUBKEY_ex.3ossl.bz2 /usr/share/man/man3/d2i_PUBKEY_ex_bio.3ossl.bz2 /usr/share/man/man3/d2i_PUBKEY_ex_fp.3ossl.bz2 /usr/share/man/man3/d2i_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/d2i_PrivateKey.3ossl.bz2 /usr/share/man/man3/d2i_PrivateKey_bio.3ossl.bz2 /usr/share/man/man3/d2i_PrivateKey_ex.3ossl.bz2 /usr/share/man/man3/d2i_PrivateKey_ex_bio.3ossl.bz2 /usr/share/man/man3/d2i_PrivateKey_ex_fp.3ossl.bz2 /usr/share/man/man3/d2i_PrivateKey_fp.3ossl.bz2 /usr/share/man/man3/d2i_PublicKey.3ossl.bz2 /usr/share/man/man3/d2i_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/d2i_RSAPrivateKey_bio.3ossl.bz2 /usr/share/man/man3/d2i_RSAPrivateKey_fp.3ossl.bz2 /usr/share/man/man3/d2i_RSAPublicKey.3ossl.bz2 /usr/share/man/man3/d2i_RSAPublicKey_bio.3ossl.bz2 /usr/share/man/man3/d2i_RSAPublicKey_fp.3ossl.bz2 /usr/share/man/man3/d2i_RSA_OAEP_PARAMS.3ossl.bz2 /usr/share/man/man3/d2i_RSA_PSS_PARAMS.3ossl.bz2 /usr/share/man/man3/d2i_RSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/d2i_RSA_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/d2i_RSA_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/d2i_SCRYPT_PARAMS.3ossl.bz2 /usr/share/man/man3/d2i_SCT_LIST.3ossl.bz2 /usr/share/man/man3/d2i_SSL_SESSION.3ossl.bz2 /usr/share/man/man3/d2i_SSL_SESSION_ex.3ossl.bz2 /usr/share/man/man3/d2i_SXNET.3ossl.bz2 /usr/share/man/man3/d2i_SXNETID.3ossl.bz2 /usr/share/man/man3/d2i_TS_ACCURACY.3ossl.bz2 /usr/share/man/man3/d2i_TS_MSG_IMPRINT.3ossl.bz2 /usr/share/man/man3/d2i_TS_MSG_IMPRINT_bio.3ossl.bz2 /usr/share/man/man3/d2i_TS_MSG_IMPRINT_fp.3ossl.bz2 /usr/share/man/man3/d2i_TS_REQ.3ossl.bz2 /usr/share/man/man3/d2i_TS_REQ_bio.3ossl.bz2 /usr/share/man/man3/d2i_TS_REQ_fp.3ossl.bz2 /usr/share/man/man3/d2i_TS_RESP.3ossl.bz2 /usr/share/man/man3/d2i_TS_RESP_bio.3ossl.bz2 /usr/share/man/man3/d2i_TS_RESP_fp.3ossl.bz2 /usr/share/man/man3/d2i_TS_STATUS_INFO.3ossl.bz2 /usr/share/man/man3/d2i_TS_TST_INFO.3ossl.bz2 /usr/share/man/man3/d2i_TS_TST_INFO_bio.3ossl.bz2 /usr/share/man/man3/d2i_TS_TST_INFO_fp.3ossl.bz2 /usr/share/man/man3/d2i_USERNOTICE.3ossl.bz2 /usr/share/man/man3/d2i_X509.3ossl.bz2 /usr/share/man/man3/d2i_X509_ACERT.3ossl.bz2 /usr/share/man/man3/d2i_X509_ACERT_bio.3ossl.bz2 /usr/share/man/man3/d2i_X509_ACERT_fp.3ossl.bz2 /usr/share/man/man3/d2i_X509_ALGOR.3ossl.bz2 /usr/share/man/man3/d2i_X509_ALGORS.3ossl.bz2 /usr/share/man/man3/d2i_X509_ATTRIBUTE.3ossl.bz2 /usr/share/man/man3/d2i_X509_AUX.3ossl.bz2 /usr/share/man/man3/d2i_X509_CERT_AUX.3ossl.bz2 /usr/share/man/man3/d2i_X509_CINF.3ossl.bz2 /usr/share/man/man3/d2i_X509_CRL.3ossl.bz2 /usr/share/man/man3/d2i_X509_CRL_INFO.3ossl.bz2 /usr/share/man/man3/d2i_X509_CRL_bio.3ossl.bz2 /usr/share/man/man3/d2i_X509_CRL_fp.3ossl.bz2 /usr/share/man/man3/d2i_X509_EXTENSION.3ossl.bz2 /usr/share/man/man3/d2i_X509_EXTENSIONS.3ossl.bz2 /usr/share/man/man3/d2i_X509_NAME.3ossl.bz2 /usr/share/man/man3/d2i_X509_NAME_ENTRY.3ossl.bz2 /usr/share/man/man3/d2i_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/d2i_X509_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/d2i_X509_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/d2i_X509_REQ.3ossl.bz2 /usr/share/man/man3/d2i_X509_REQ_INFO.3ossl.bz2 /usr/share/man/man3/d2i_X509_REQ_bio.3ossl.bz2 /usr/share/man/man3/d2i_X509_REQ_fp.3ossl.bz2 /usr/share/man/man3/d2i_X509_REVOKED.3ossl.bz2 /usr/share/man/man3/d2i_X509_SIG.3ossl.bz2 /usr/share/man/man3/d2i_X509_VAL.3ossl.bz2 /usr/share/man/man3/d2i_X509_bio.3ossl.bz2 /usr/share/man/man3/d2i_X509_fp.3ossl.bz2 /usr/share/man/man3/i2b_PVK_bio.3ossl.bz2 /usr/share/man/man3/i2b_PVK_bio_ex.3ossl.bz2 /usr/share/man/man3/i2d_ACCESS_DESCRIPTION.3ossl.bz2 /usr/share/man/man3/i2d_ADMISSIONS.3ossl.bz2 /usr/share/man/man3/i2d_ADMISSION_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_ASIdOrRange.3ossl.bz2 /usr/share/man/man3/i2d_ASIdentifierChoice.3ossl.bz2 /usr/share/man/man3/i2d_ASIdentifiers.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_BIT_STRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_BMPSTRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_ENUMERATED.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_GENERALIZEDTIME.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_GENERALSTRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_IA5STRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_INTEGER.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_NULL.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_OBJECT.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_OCTET_STRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_PRINTABLE.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_PRINTABLESTRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_SEQUENCE_ANY.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_SET_ANY.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_T61STRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_TIME.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_TYPE.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_UNIVERSALSTRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_UTCTIME.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_UTF8STRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_VISIBLESTRING.3ossl.bz2 /usr/share/man/man3/i2d_ASN1_bio_stream.3ossl.bz2 /usr/share/man/man3/i2d_ASRange.3ossl.bz2 /usr/share/man/man3/i2d_AUTHORITY_INFO_ACCESS.3ossl.bz2 /usr/share/man/man3/i2d_AUTHORITY_KEYID.3ossl.bz2 /usr/share/man/man3/i2d_BASIC_CONSTRAINTS.3ossl.bz2 /usr/share/man/man3/i2d_CERTIFICATEPOLICIES.3ossl.bz2 /usr/share/man/man3/i2d_CMS_ContentInfo.3ossl.bz2 /usr/share/man/man3/i2d_CMS_ReceiptRequest.3ossl.bz2 /usr/share/man/man3/i2d_CMS_bio.3ossl.bz2 /usr/share/man/man3/i2d_CMS_bio_stream.3ossl.bz2 /usr/share/man/man3/i2d_CRL_DIST_POINTS.3ossl.bz2 /usr/share/man/man3/i2d_DHparams.3ossl.bz2 /usr/share/man/man3/i2d_DHparams_bio.3ossl.bz2 /usr/share/man/man3/i2d_DHparams_fp.3ossl.bz2 /usr/share/man/man3/i2d_DHxparams.3ossl.bz2 /usr/share/man/man3/i2d_DIRECTORYSTRING.3ossl.bz2 /usr/share/man/man3/i2d_DISPLAYTEXT.3ossl.bz2 /usr/share/man/man3/i2d_DIST_POINT.3ossl.bz2 /usr/share/man/man3/i2d_DIST_POINT_NAME.3ossl.bz2 /usr/share/man/man3/i2d_DSAPrivateKey.3ossl.bz2 /usr/share/man/man3/i2d_DSAPrivateKey_bio.3ossl.bz2 /usr/share/man/man3/i2d_DSAPrivateKey_fp.3ossl.bz2 /usr/share/man/man3/i2d_DSAPublicKey.3ossl.bz2 /usr/share/man/man3/i2d_DSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/i2d_DSA_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/i2d_DSA_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/i2d_DSA_SIG.3ossl.bz2 /usr/share/man/man3/i2d_DSAparams.3ossl.bz2 /usr/share/man/man3/i2d_ECDSA_SIG.3ossl.bz2 /usr/share/man/man3/i2d_ECPKParameters.3ossl.bz2 /usr/share/man/man3/i2d_ECParameters.3ossl.bz2 /usr/share/man/man3/i2d_ECPrivateKey.3ossl.bz2 /usr/share/man/man3/i2d_ECPrivateKey_bio.3ossl.bz2 /usr/share/man/man3/i2d_ECPrivateKey_fp.3ossl.bz2 /usr/share/man/man3/i2d_EC_PUBKEY.3ossl.bz2 /usr/share/man/man3/i2d_EC_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/i2d_EC_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/i2d_EDIPARTYNAME.3ossl.bz2 /usr/share/man/man3/i2d_ESS_CERT_ID.3ossl.bz2 /usr/share/man/man3/i2d_ESS_CERT_ID_V2.3ossl.bz2 /usr/share/man/man3/i2d_ESS_ISSUER_SERIAL.3ossl.bz2 /usr/share/man/man3/i2d_ESS_SIGNING_CERT.3ossl.bz2 /usr/share/man/man3/i2d_ESS_SIGNING_CERT_V2.3ossl.bz2 /usr/share/man/man3/i2d_EXTENDED_KEY_USAGE.3ossl.bz2 /usr/share/man/man3/i2d_GENERAL_NAME.3ossl.bz2 /usr/share/man/man3/i2d_GENERAL_NAMES.3ossl.bz2 /usr/share/man/man3/i2d_IPAddressChoice.3ossl.bz2 /usr/share/man/man3/i2d_IPAddressFamily.3ossl.bz2 /usr/share/man/man3/i2d_IPAddressOrRange.3ossl.bz2 /usr/share/man/man3/i2d_IPAddressRange.3ossl.bz2 /usr/share/man/man3/i2d_ISSUER_SIGN_TOOL.3ossl.bz2 /usr/share/man/man3/i2d_ISSUING_DIST_POINT.3ossl.bz2 /usr/share/man/man3/i2d_KeyParams.3ossl.bz2 /usr/share/man/man3/i2d_KeyParams_bio.3ossl.bz2 /usr/share/man/man3/i2d_NAMING_AUTHORITY.3ossl.bz2 /usr/share/man/man3/i2d_NETSCAPE_CERT_SEQUENCE.3ossl.bz2 /usr/share/man/man3/i2d_NETSCAPE_SPKAC.3ossl.bz2 /usr/share/man/man3/i2d_NETSCAPE_SPKI.3ossl.bz2 /usr/share/man/man3/i2d_NOTICEREF.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_BASICRESP.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_CERTID.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_CERTSTATUS.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_CRLID.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_ONEREQ.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_REQINFO.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_REQUEST.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_RESPBYTES.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_RESPDATA.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_RESPID.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_RESPONSE.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_REVOKEDINFO.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_SERVICELOC.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_SIGNATURE.3ossl.bz2 /usr/share/man/man3/i2d_OCSP_SINGLERESP.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_AA_DIST_POINT.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ALLOWED_ATTRIBUTES_CHOICE.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ALLOWED_ATTRIBUTES_ITEM.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ALLOWED_ATTRIBUTES_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATAV.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATTRIBUTES_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATTRIBUTE_DESCRIPTOR.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATTRIBUTE_MAPPING.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATTRIBUTE_MAPPINGS.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATTRIBUTE_TYPE_MAPPING.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ATTRIBUTE_VALUE_MAPPING.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_AUTHORITY_ATTRIBUTE_ID_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_BASIC_ATTR_CONSTRAINTS.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CMP_ATAVS.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CMP_MSG.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CMP_MSG_bio.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CMP_PKIHEADER.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CMP_PKISI.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_CERTID.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_CERTTEMPLATE.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_ENCRYPTEDKEY.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_ENCRYPTEDVALUE.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_MSG.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_MSGS.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_PBMPARAMETER.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_PKIPUBLICATIONINFO.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_CRMF_SINGLEPUBINFO.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_DAY_TIME.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_DAY_TIME_BAND.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_HASH.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_IETF_ATTR_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_INFO_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_INFO_SYNTAX_POINTER.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ISSUER_SERIAL.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_NAMED_DAY.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_OBJECT_DIGEST_INFO.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_PRIVILEGE_POLICY_ID.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ROLE_SPEC_CERT_ID.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_ROLE_SPEC_CERT_ID_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TARGET.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TARGETING_INFORMATION.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TARGETS.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TARGET_CERT.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_PERIOD.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC_ABSOLUTE.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC_DAY.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC_MONTH.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC_TIME.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC_WEEKS.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_TIME_SPEC_X_DAY_OF.3ossl.bz2 /usr/share/man/man3/i2d_OSSL_USER_NOTICE_SYNTAX.3ossl.bz2 /usr/share/man/man3/i2d_OTHERNAME.3ossl.bz2 /usr/share/man/man3/i2d_PBE2PARAM.3ossl.bz2 /usr/share/man/man3/i2d_PBEPARAM.3ossl.bz2 /usr/share/man/man3/i2d_PBKDF2PARAM.3ossl.bz2 /usr/share/man/man3/i2d_PBMAC1PARAM.3ossl.bz2 /usr/share/man/man3/i2d_PKCS12.3ossl.bz2 /usr/share/man/man3/i2d_PKCS12_BAGS.3ossl.bz2 /usr/share/man/man3/i2d_PKCS12_MAC_DATA.3ossl.bz2 /usr/share/man/man3/i2d_PKCS12_SAFEBAG.3ossl.bz2 /usr/share/man/man3/i2d_PKCS12_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS12_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_DIGEST.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_ENCRYPT.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_ENC_CONTENT.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_ENVELOPE.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_ISSUER_AND_SERIAL.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_NDEF.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_RECIP_INFO.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_SIGNED.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_SIGNER_INFO.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_SIGN_ENVELOPE.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_bio_stream.3ossl.bz2 /usr/share/man/man3/i2d_PKCS7_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKey.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKeyInfo_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKeyInfo_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKey_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKey_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKey_nid_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8PrivateKey_nid_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8_PRIV_KEY_INFO.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8_PRIV_KEY_INFO_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8_PRIV_KEY_INFO_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8_bio.3ossl.bz2 /usr/share/man/man3/i2d_PKCS8_fp.3ossl.bz2 /usr/share/man/man3/i2d_PKEY_USAGE_PERIOD.3ossl.bz2 /usr/share/man/man3/i2d_POLICYINFO.3ossl.bz2 /usr/share/man/man3/i2d_POLICYQUALINFO.3ossl.bz2 /usr/share/man/man3/i2d_PROFESSION_INFO.3ossl.bz2 /usr/share/man/man3/i2d_PROXY_CERT_INFO_EXTENSION.3ossl.bz2 /usr/share/man/man3/i2d_PROXY_POLICY.3ossl.bz2 /usr/share/man/man3/i2d_PUBKEY.3ossl.bz2 /usr/share/man/man3/i2d_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/i2d_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/i2d_PrivateKey.3ossl.bz2 /usr/share/man/man3/i2d_PrivateKey_bio.3ossl.bz2 /usr/share/man/man3/i2d_PrivateKey_fp.3ossl.bz2 /usr/share/man/man3/i2d_PublicKey.3ossl.bz2 /usr/share/man/man3/i2d_RSAPrivateKey.3ossl.bz2 /usr/share/man/man3/i2d_RSAPrivateKey_bio.3ossl.bz2 /usr/share/man/man3/i2d_RSAPrivateKey_fp.3ossl.bz2 /usr/share/man/man3/i2d_RSAPublicKey.3ossl.bz2 /usr/share/man/man3/i2d_RSAPublicKey_bio.3ossl.bz2 /usr/share/man/man3/i2d_RSAPublicKey_fp.3ossl.bz2 /usr/share/man/man3/i2d_RSA_OAEP_PARAMS.3ossl.bz2 /usr/share/man/man3/i2d_RSA_PSS_PARAMS.3ossl.bz2 /usr/share/man/man3/i2d_RSA_PUBKEY.3ossl.bz2 /usr/share/man/man3/i2d_RSA_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/i2d_RSA_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/i2d_SCRYPT_PARAMS.3ossl.bz2 /usr/share/man/man3/i2d_SCT_LIST.3ossl.bz2 /usr/share/man/man3/i2d_SSL_SESSION.3ossl.bz2 /usr/share/man/man3/i2d_SXNET.3ossl.bz2 /usr/share/man/man3/i2d_SXNETID.3ossl.bz2 /usr/share/man/man3/i2d_TS_ACCURACY.3ossl.bz2 /usr/share/man/man3/i2d_TS_MSG_IMPRINT.3ossl.bz2 /usr/share/man/man3/i2d_TS_MSG_IMPRINT_bio.3ossl.bz2 /usr/share/man/man3/i2d_TS_MSG_IMPRINT_fp.3ossl.bz2 /usr/share/man/man3/i2d_TS_REQ.3ossl.bz2 /usr/share/man/man3/i2d_TS_REQ_bio.3ossl.bz2 /usr/share/man/man3/i2d_TS_REQ_fp.3ossl.bz2 /usr/share/man/man3/i2d_TS_RESP.3ossl.bz2 /usr/share/man/man3/i2d_TS_RESP_bio.3ossl.bz2 /usr/share/man/man3/i2d_TS_RESP_fp.3ossl.bz2 /usr/share/man/man3/i2d_TS_STATUS_INFO.3ossl.bz2 /usr/share/man/man3/i2d_TS_TST_INFO.3ossl.bz2 /usr/share/man/man3/i2d_TS_TST_INFO_bio.3ossl.bz2 /usr/share/man/man3/i2d_TS_TST_INFO_fp.3ossl.bz2 /usr/share/man/man3/i2d_USERNOTICE.3ossl.bz2 /usr/share/man/man3/i2d_X509.3ossl.bz2 /usr/share/man/man3/i2d_X509_ACERT.3ossl.bz2 /usr/share/man/man3/i2d_X509_ACERT_bio.3ossl.bz2 /usr/share/man/man3/i2d_X509_ACERT_fp.3ossl.bz2 /usr/share/man/man3/i2d_X509_ALGOR.3ossl.bz2 /usr/share/man/man3/i2d_X509_ALGORS.3ossl.bz2 /usr/share/man/man3/i2d_X509_ATTRIBUTE.3ossl.bz2 /usr/share/man/man3/i2d_X509_AUX.3ossl.bz2 /usr/share/man/man3/i2d_X509_CERT_AUX.3ossl.bz2 /usr/share/man/man3/i2d_X509_CINF.3ossl.bz2 /usr/share/man/man3/i2d_X509_CRL.3ossl.bz2 /usr/share/man/man3/i2d_X509_CRL_INFO.3ossl.bz2 /usr/share/man/man3/i2d_X509_CRL_bio.3ossl.bz2 /usr/share/man/man3/i2d_X509_CRL_fp.3ossl.bz2 /usr/share/man/man3/i2d_X509_EXTENSION.3ossl.bz2 /usr/share/man/man3/i2d_X509_EXTENSIONS.3ossl.bz2 /usr/share/man/man3/i2d_X509_NAME.3ossl.bz2 /usr/share/man/man3/i2d_X509_NAME_ENTRY.3ossl.bz2 /usr/share/man/man3/i2d_X509_PUBKEY.3ossl.bz2 /usr/share/man/man3/i2d_X509_PUBKEY_bio.3ossl.bz2 /usr/share/man/man3/i2d_X509_PUBKEY_fp.3ossl.bz2 /usr/share/man/man3/i2d_X509_REQ.3ossl.bz2 /usr/share/man/man3/i2d_X509_REQ_INFO.3ossl.bz2 /usr/share/man/man3/i2d_X509_REQ_bio.3ossl.bz2 /usr/share/man/man3/i2d_X509_REQ_fp.3ossl.bz2 /usr/share/man/man3/i2d_X509_REVOKED.3ossl.bz2 /usr/share/man/man3/i2d_X509_SIG.3ossl.bz2 /usr/share/man/man3/i2d_X509_VAL.3ossl.bz2 /usr/share/man/man3/i2d_X509_bio.3ossl.bz2 /usr/share/man/man3/i2d_X509_fp.3ossl.bz2 /usr/share/man/man3/i2d_re_X509_CRL_tbs.3ossl.bz2 /usr/share/man/man3/i2d_re_X509_REQ_tbs.3ossl.bz2 /usr/share/man/man3/i2d_re_X509_tbs.3ossl.bz2 /usr/share/man/man3/i2o_SCT.3ossl.bz2 /usr/share/man/man3/i2o_SCT_LIST.3ossl.bz2 /usr/share/man/man3/i2s_ASN1_ENUMERATED.3ossl.bz2 /usr/share/man/man3/i2s_ASN1_ENUMERATED_TABLE.3ossl.bz2 /usr/share/man/man3/i2s_ASN1_IA5STRING.3ossl.bz2 /usr/share/man/man3/i2s_ASN1_INTEGER.3ossl.bz2 /usr/share/man/man3/i2s_ASN1_OCTET_STRING.3ossl.bz2 /usr/share/man/man3/i2s_ASN1_UTF8STRING.3ossl.bz2 /usr/share/man/man3/i2t_ASN1_OBJECT.3ossl.bz2 /usr/share/man/man3/lh_TYPE_delete.3ossl.bz2 /usr/share/man/man3/lh_TYPE_doall.3ossl.bz2 /usr/share/man/man3/lh_TYPE_doall_arg.3ossl.bz2 /usr/share/man/man3/lh_TYPE_error.3ossl.bz2 /usr/share/man/man3/lh_TYPE_flush.3ossl.bz2 /usr/share/man/man3/lh_TYPE_free.3ossl.bz2 /usr/share/man/man3/lh_TYPE_get_down_load.3ossl.bz2 /usr/share/man/man3/lh_TYPE_insert.3ossl.bz2 /usr/share/man/man3/lh_TYPE_new.3ossl.bz2 /usr/share/man/man3/lh_TYPE_num_items.3ossl.bz2 /usr/share/man/man3/lh_TYPE_retrieve.3ossl.bz2 /usr/share/man/man3/lh_TYPE_set_down_load.3ossl.bz2 /usr/share/man/man3/o2i_SCT.3ossl.bz2 /usr/share/man/man3/o2i_SCT_LIST.3ossl.bz2 /usr/share/man/man3/pem_password_cb.3ossl.bz2 /usr/share/man/man3/s2i_ASN1_IA5STRING.3ossl.bz2 /usr/share/man/man3/s2i_ASN1_INTEGER.3ossl.bz2 /usr/share/man/man3/s2i_ASN1_OCTET_STRING.3ossl.bz2 /usr/share/man/man3/s2i_ASN1_UTF8STRING.3ossl.bz2 /usr/share/man/man3/sk_TYPE_deep_copy.3ossl.bz2 /usr/share/man/man3/sk_TYPE_delete.3ossl.bz2 /usr/share/man/man3/sk_TYPE_delete_ptr.3ossl.bz2 /usr/share/man/man3/sk_TYPE_dup.3ossl.bz2 /usr/share/man/man3/sk_TYPE_find.3ossl.bz2 /usr/share/man/man3/sk_TYPE_find_all.3ossl.bz2 /usr/share/man/man3/sk_TYPE_find_ex.3ossl.bz2 /usr/share/man/man3/sk_TYPE_free.3ossl.bz2 /usr/share/man/man3/sk_TYPE_insert.3ossl.bz2 /usr/share/man/man3/sk_TYPE_is_sorted.3ossl.bz2 /usr/share/man/man3/sk_TYPE_new.3ossl.bz2 /usr/share/man/man3/sk_TYPE_new_null.3ossl.bz2 /usr/share/man/man3/sk_TYPE_new_reserve.3ossl.bz2 /usr/share/man/man3/sk_TYPE_num.3ossl.bz2 /usr/share/man/man3/sk_TYPE_pop.3ossl.bz2 /usr/share/man/man3/sk_TYPE_pop_free.3ossl.bz2 /usr/share/man/man3/sk_TYPE_push.3ossl.bz2 /usr/share/man/man3/sk_TYPE_reserve.3ossl.bz2 /usr/share/man/man3/sk_TYPE_set.3ossl.bz2 /usr/share/man/man3/sk_TYPE_set_cmp_func.3ossl.bz2 /usr/share/man/man3/sk_TYPE_shift.3ossl.bz2 /usr/share/man/man3/sk_TYPE_sort.3ossl.bz2 /usr/share/man/man3/sk_TYPE_unshift.3ossl.bz2 /usr/share/man/man3/sk_TYPE_value.3ossl.bz2 /usr/share/man/man3/sk_TYPE_zero.3ossl.bz2 /usr/share/man/man3/ssl_ct_validation_cb.3ossl.bz2 /usr/share/man/man3/tls_session_secret_cb_fn.3ossl.bz2
    /usr/share/man/man5
    /usr/share/man/man5/config.5ossl.bz2
    /usr/share/man/man5/fips_config.5ossl.bz2 /usr/share/man/man5/x509v3_config.5ossl.bz2
    /usr/share/man/man7
    /usr/share/man/man7/EVP_ASYM_CIPHER-RSA.7ossl.bz2 /usr/share/man/man7/EVP_ASYM_CIPHER-SM2.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-AES.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-ARIA.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-BLOWFISH.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-CAMELLIA.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-CAST.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-CHACHA.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-DES.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-IDEA.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-NULL.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-RC2.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-RC4.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-RC5.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-SEED.7ossl.bz2 /usr/share/man/man7/EVP_CIPHER-SM4.7ossl.bz2 /usr/share/man/man7/EVP_KDF-ARGON2.7ossl.bz2 /usr/share/man/man7/EVP_KDF-HKDF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-HMAC-DRBG.7ossl.bz2 /usr/share/man/man7/EVP_KDF-KB.7ossl.bz2 /usr/share/man/man7/EVP_KDF-KRB5KDF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-PBKDF1.7ossl.bz2 /usr/share/man/man7/EVP_KDF-PBKDF2.7ossl.bz2 /usr/share/man/man7/EVP_KDF-PKCS12KDF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-PVKKDF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-SCRYPT.7ossl.bz2 /usr/share/man/man7/EVP_KDF-SS.7ossl.bz2 /usr/share/man/man7/EVP_KDF-SSHKDF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-TLS13_KDF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-TLS1_PRF.7ossl.bz2 /usr/share/man/man7/EVP_KDF-X942-ASN1.7ossl.bz2 /usr/share/man/man7/EVP_KDF-X942-CONCAT.7ossl.bz2 /usr/share/man/man7/EVP_KDF-X963.7ossl.bz2 /usr/share/man/man7/EVP_KEM-EC.7ossl.bz2 /usr/share/man/man7/EVP_KEM-ML-KEM-1024.7ossl.bz2 /usr/share/man/man7/EVP_KEM-ML-KEM-512.7ossl.bz2 /usr/share/man/man7/EVP_KEM-ML-KEM-768.7ossl.bz2 /usr/share/man/man7/EVP_KEM-ML-KEM.7ossl.bz2 /usr/share/man/man7/EVP_KEM-RSA.7ossl.bz2 /usr/share/man/man7/EVP_KEM-X25519.7ossl.bz2 /usr/share/man/man7/EVP_KEM-X448.7ossl.bz2 /usr/share/man/man7/EVP_KEYEXCH-DH.7ossl.bz2 /usr/share/man/man7/EVP_KEYEXCH-ECDH.7ossl.bz2 /usr/share/man/man7/EVP_KEYEXCH-X25519.7ossl.bz2 /usr/share/man/man7/EVP_KEYEXCH-X448.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-CMAC.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-DH.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-DHX.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-DSA.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-EC.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ED25519.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ED448.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-HMAC.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-LMS.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ML-DSA.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ML-KEM-1024.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ML-KEM-512.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ML-KEM-768.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-ML-KEM.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-Poly1305.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-RSA.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-SLH-DSA.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-SM2.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-Siphash.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-X25519.7ossl.bz2 /usr/share/man/man7/EVP_KEYMGMT-X448.7ossl.bz2 /usr/share/man/man7/EVP_MAC-BLAKE2.7ossl.bz2 /usr/share/man/man7/EVP_MAC-BLAKE2BMAC.7ossl.bz2 /usr/share/man/man7/EVP_MAC-BLAKE2SMAC.7ossl.bz2 /usr/share/man/man7/EVP_MAC-CMAC.7ossl.bz2 /usr/share/man/man7/EVP_MAC-GMAC.7ossl.bz2 /usr/share/man/man7/EVP_MAC-HMAC.7ossl.bz2 /usr/share/man/man7/EVP_MAC-KMAC.7ossl.bz2 /usr/share/man/man7/EVP_MAC-KMAC128.7ossl.bz2 /usr/share/man/man7/EVP_MAC-KMAC256.7ossl.bz2 /usr/share/man/man7/EVP_MAC-Poly1305.7ossl.bz2 /usr/share/man/man7/EVP_MAC-Siphash.7ossl.bz2 /usr/share/man/man7/EVP_MD-BLAKE2.7ossl.bz2 /usr/share/man/man7/EVP_MD-KECCAK-KMAC.7ossl.bz2 /usr/share/man/man7/EVP_MD-KECCAK.7ossl.bz2 /usr/share/man/man7/EVP_MD-MD2.7ossl.bz2 /usr/share/man/man7/EVP_MD-MD4.7ossl.bz2 /usr/share/man/man7/EVP_MD-MD5-SHA1.7ossl.bz2 /usr/share/man/man7/EVP_MD-MD5.7ossl.bz2 /usr/share/man/man7/EVP_MD-MDC2.7ossl.bz2 /usr/share/man/man7/EVP_MD-NULL.7ossl.bz2 /usr/share/man/man7/EVP_MD-RIPEMD160.7ossl.bz2 /usr/share/man/man7/EVP_MD-SHA1.7ossl.bz2 /usr/share/man/man7/EVP_MD-SHA2.7ossl.bz2 /usr/share/man/man7/EVP_MD-SHA3.7ossl.bz2 /usr/share/man/man7/EVP_MD-SHAKE.7ossl.bz2 /usr/share/man/man7/EVP_MD-SM3.7ossl.bz2 /usr/share/man/man7/EVP_MD-WHIRLPOOL.7ossl.bz2 /usr/share/man/man7/EVP_MD-common.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-CMAC.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-DH.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-DHX.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-DSA.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-EC.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ED25519.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ED448.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-FFC.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-HMAC.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-LMS.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-DSA-44.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-DSA-65.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-DSA-87.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-DSA.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-KEM-1024.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-KEM-512.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-KEM-768.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-ML-KEM.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-Poly1305.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-RSA.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHA2-128f.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHA2-128s.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHA2-192f.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHA2-192s.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHA2-256f.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHA2-256s.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHAKE-128f.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHAKE-128s.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHAKE-192f.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHAKE-192s.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHAKE-256f.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA-SHAKE-256s.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SLH-DSA.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-SM2.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-Siphash.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-X25519.7ossl.bz2 /usr/share/man/man7/EVP_PKEY-X448.7ossl.bz2 /usr/share/man/man7/EVP_RAND-CRNG-TEST.7ossl.bz2 /usr/share/man/man7/EVP_RAND-CTR-DRBG.7ossl.bz2 /usr/share/man/man7/EVP_RAND-HASH-DRBG.7ossl.bz2 /usr/share/man/man7/EVP_RAND-HMAC-DRBG.7ossl.bz2 /usr/share/man/man7/EVP_RAND-JITTER.7ossl.bz2 /usr/share/man/man7/EVP_RAND-SEED-SRC.7ossl.bz2 /usr/share/man/man7/EVP_RAND-TEST-RAND.7ossl.bz2 /usr/share/man/man7/EVP_RAND.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-CMAC.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-DSA.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ECDSA.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ED25519.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ED448.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-HMAC.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-LMS.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ML-DSA-44.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ML-DSA-65.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ML-DSA-87.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-ML-DSA.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-Poly1305.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-RSA.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHA2-128f.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHA2-128s.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHA2-192f.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHA2-192s.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHA2-256f.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHA2-256s.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHAKE-128f.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHAKE-128s.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHAKE-192f.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHAKE-192s.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHAKE-256f.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA-SHAKE-256s.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-SLH-DSA.7ossl.bz2 /usr/share/man/man7/EVP_SIGNATURE-Siphash.7ossl.bz2 /usr/share/man/man7/Ed25519.7ossl.bz2
    /usr/share/man/man7/Ed448.7ossl.bz2
    /usr/share/man/man7/LMS.7ossl.bz2 /usr/share/man/man7/OPENSSL_API_COMPAT.7ossl.bz2 /usr/share/man/man7/OPENSSL_NO_DEPRECATED.7ossl.bz2 /usr/share/man/man7/OSSL_PROVIDER-FIPS.7ossl.bz2 /usr/share/man/man7/OSSL_PROVIDER-base.7ossl.bz2 /usr/share/man/man7/OSSL_PROVIDER-default.7ossl.bz2 /usr/share/man/man7/OSSL_PROVIDER-legacy.7ossl.bz2 /usr/share/man/man7/OSSL_PROVIDER-null.7ossl.bz2 /usr/share/man/man7/OSSL_STORE-winstore.7ossl.bz2 /usr/share/man/man7/RAND.7ossl.bz2
    /usr/share/man/man7/RSA-PSS.7ossl.bz2
    /usr/share/man/man7/RSA.7ossl.bz2
    /usr/share/man/man7/SM2.7ossl.bz2
    /usr/share/man/man7/X25519.7ossl.bz2
    /usr/share/man/man7/X448.7ossl.bz2
    /usr/share/man/man7/bio.7ossl.bz2
    /usr/share/man/man7/crypto.7ossl.bz2
    /usr/share/man/man7/ct.7ossl.bz2
    /usr/share/man/man7/des_modes.7ossl.bz2
    /usr/share/man/man7/evp.7ossl.bz2
    /usr/share/man/man7/fips_module.7ossl.bz2 /usr/share/man/man7/life_cycle-cipher.7ossl.bz2 /usr/share/man/man7/life_cycle-digest.7ossl.bz2 /usr/share/man/man7/life_cycle-kdf.7ossl.bz2 /usr/share/man/man7/life_cycle-mac.7ossl.bz2 /usr/share/man/man7/life_cycle-pkey.7ossl.bz2 /usr/share/man/man7/life_cycle-rand.7ossl.bz2 /usr/share/man/man7/migration_guide.7ossl.bz2 /usr/share/man/man7/openssl-core.h.7ossl.bz2 /usr/share/man/man7/openssl-core_dispatch.h.7ossl.bz2 /usr/share/man/man7/openssl-core_names.h.7ossl.bz2 /usr/share/man/man7/openssl-env.7ossl.bz2 /usr/share/man/man7/openssl-glossary.7ossl.bz2 /usr/share/man/man7/openssl-qlog.7ossl.bz2 /usr/share/man/man7/openssl-quic-concurrency.7ossl.bz2 /usr/share/man/man7/openssl-quic.7ossl.bz2 /usr/share/man/man7/openssl-threads.7ossl.bz2 /usr/share/man/man7/openssl_user_macros.7ossl.bz2 /usr/share/man/man7/ossl-guide-introduction.7ossl.bz2 /usr/share/man/man7/ossl-guide-libcrypto-introduction.7ossl.bz2 /usr/share/man/man7/ossl-guide-libraries-introduction.7ossl.bz2 /usr/share/man/man7/ossl-guide-libssl-introduction.7ossl.bz2 /usr/share/man/man7/ossl-guide-migration.7ossl.bz2 /usr/share/man/man7/ossl-guide-quic-client-block.7ossl.bz2 /usr/share/man/man7/ossl-guide-quic-client-non-block.7ossl.bz2 /usr/share/man/man7/ossl-guide-quic-introduction.7ossl.bz2 /usr/share/man/man7/ossl-guide-quic-multi-stream.7ossl.bz2 /usr/share/man/man7/ossl-guide-quic-server-block.7ossl.bz2 /usr/share/man/man7/ossl-guide-quic-server-non-block.7ossl.bz2 /usr/share/man/man7/ossl-guide-tls-client-block.7ossl.bz2 /usr/share/man/man7/ossl-guide-tls-client-non-block.7ossl.bz2 /usr/share/man/man7/ossl-guide-tls-introduction.7ossl.bz2 /usr/share/man/man7/ossl-guide-tls-server-block.7ossl.bz2 /usr/share/man/man7/ossl_store-file.7ossl.bz2 /usr/share/man/man7/ossl_store.7ossl.bz2 /usr/share/man/man7/passphrase-encoding.7ossl.bz2 /usr/share/man/man7/property.7ossl.bz2 /usr/share/man/man7/provider-asym_cipher.7ossl.bz2 /usr/share/man/man7/provider-base.7ossl.bz2 /usr/share/man/man7/provider-cipher.7ossl.bz2 /usr/share/man/man7/provider-decoder.7ossl.bz2 /usr/share/man/man7/provider-digest.7ossl.bz2 /usr/share/man/man7/provider-encoder.7ossl.bz2 /usr/share/man/man7/provider-kdf.7ossl.bz2 /usr/share/man/man7/provider-kem.7ossl.bz2 /usr/share/man/man7/provider-keyexch.7ossl.bz2 /usr/share/man/man7/provider-keymgmt.7ossl.bz2 /usr/share/man/man7/provider-mac.7ossl.bz2 /usr/share/man/man7/provider-object.7ossl.bz2 /usr/share/man/man7/provider-rand.7ossl.bz2 /usr/share/man/man7/provider-signature.7ossl.bz2 /usr/share/man/man7/provider-skeymgmt.7ossl.bz2 /usr/share/man/man7/provider-storemgmt.7ossl.bz2 /usr/share/man/man7/provider.7ossl.bz2 /usr/share/man/man7/proxy-certificates.7ossl.bz2 /usr/share/man/man7/ssl.7ossl.bz2
    /usr/share/man/man7/x509.7ossl.bz2

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Richard Kettlewell@invalid@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Sat Oct 31 22:41:58 2026
    From Newsgroup: comp.unix.shell

    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-10-31 11:49, Nuno Silva wrote:
    On 2026-10-31, Carlos E. R. wrote:
    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than
    a flaw of the online manual in itself?

    No, man pages do not contain links to section of the document. It is
    not structured.

    Nuno is right; a viewer can include links. For an example see man7.org.
    --
    https://www.greenend.org.uk/rjk/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 01:08:48 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31, Carlos E. R. wrote:

    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    A question is how much of that is already possible using the current
    format.

    And another question is whether the current format, which could easily
    be printed besides being installed as an online manual, does make for
    better documentation to read than something focused on having more
    internal references.

    Janis, preferring to avoid mouse-devices in the first place

    Sure, point and click can also work without a mouse. Use the cursor to
    select an entry in the table of contents, then hit enter.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 04:18:11 2026
    From Newsgroup: comp.unix.shell

    On 10/31/26 17:11, Janis Papanagnou wrote:
    On 2026-10-31 19:56, Carlos E. R. wrote:
    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    But technically we have already "clickable" documents; with HTML for
    example.

    "Hyper-Text" - it goes WAY back. Had a *little*
    input on at least the concept. Also suggested
    an 'any machine' lang ... eventually we got Java.

    Pref 'C' :-)

    (Although it should still be available in one page, and ideally also searchable by regexps in easy ways. (As opposed to click on a search
    icon, move the mouse to a new sub-window, (optionally) click another
    time in that window to "activate" it for input, type in only a fixed non-regexp text (often without possibility to distinguish caps, or,
    if you're lucky, only with an extra click in some control-box), and
    hit enter (if you're lucky) or have to again move the mouse to click
    on some Okay button.) - I certainly hate to have no '/search-pattern'
    or '<Ctrl-F>search-pattern' available; with emphasis on "pattern".)

    Personally I typically want (at least) three levels of information.
    Terse usage information, complete interface description, and thorough explanations of all details in case of the more complex tools.

    Mostly we (now) have all that information; if only through the Web.
    (But often inconsistent or even unreliable.)

    Should we have everything just in one (clickable) format like HTML?
    I don't think so. Should we have all the spread existing information rewritten in some other format? Well, who would do that job?

    What I (also) criticize is that we don't have a consistent level of information with some newer Linux platforms. I wished for the "second
    level" of information that the man page format would have been kept/ maintained instead of trying to deprive that format in favor of the
    'info' format.



    Janis, preferring to avoid mouse-devices in the first place

    Sure, point and click can also work without a mouse. Use the cursor to
    select an entry in the table of contents, then hit enter.

    Yes, sure. For long documents ("level three" information) with a lot
    content where a "table of contents" is sensible that makes completely
    sense. (Even pure mouse-control would be fine here [for me] in this
    case.)

    'Mice' are still a GREAT/useful idea. Thank Xerox !
    Finer control than poking yer finger at a screen too.

    For the information level where I'd see the man-pages I wouldn't even
    need a "table of contents", since that type of information shouldn't
    be that voluminous, IMO.

    But what if it BECAME so ?

    Shit turns into a lot MORE shit.

    My input to hypertext in the ancient days was the
    idea of a sort of 'infinitely-indexed database'
    where everything of importance somehow linked to
    a huge tree of related info, which linked to a
    huge tree of related info .....

    Weren't as many 'computer geeks' back then.

    They solved the index-space issue by using html
    page links. The giant 'tree' wasn't in one place
    any more. Not really possible before the early-80s
    alas until DARPA-Net firmly became the Internet.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 1 04:30:28 2026
    From Newsgroup: comp.unix.shell

    On 10/31/26 17:38, Lawrence DrCOOliveiro wrote:
    On Sat, 31 Oct 2026 11:07:47 -0400, jayjwa wrote:

    The DEC systems are more fun, have better docs, and much more
    software.

    If you look at all the vintage docs collected at Bitsavers, out of (currently) about 660GB in total, over 40% is from DEC. Number 2 is
    IBM, but the DEC collection is bigger by nearly 3:1.

    Number 3 is CDC, at about a quarter of the size of the IBM collection.

    The DEC boxes were GREAT !

    Not entirely sure why they went out of biz - likely
    idiot management. Daddy builds it, Junior TRASHES it.

    Still wish someone would modernize VMS - it was a
    fantastic/powerful system with a ton of prescient
    modern features - could do international internet
    before there WAS an internet.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Andreas Eder@a_eder_muc@web.de to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 10:58:56 2026
    From Newsgroup: comp.unix.shell

    On Sa 31 Okt 2026 at 19:56, Carlos E. R. wrote:

    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use, specially >>> when you need something specific. No clickable table of content, no
    clickable index. Info pages are somewhat better.
    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)
    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    Well, Info in Emacs isn't too bad.
    Have a look at the Symbolics Lisp Machine Documentation System
    Concordia. That was pretty good.

    'Andreas
    --
    ceterum censeo redmondinem esse delendam
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 1 10:16:14 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> schrieb:
    On 10/31/26 17:38, Lawrence DrCOOliveiro wrote:
    On Sat, 31 Oct 2026 11:07:47 -0400, jayjwa wrote:

    The DEC systems are more fun, have better docs, and much more
    software.

    If you look at all the vintage docs collected at Bitsavers, out of
    (currently) about 660GB in total, over 40% is from DEC. Number 2 is
    IBM, but the DEC collection is bigger by nearly 3:1.

    Number 3 is CDC, at about a quarter of the size of the IBM collection.

    The DEC boxes were GREAT !

    Not entirely sure why they went out of biz - likely
    idiot management. Daddy builds it, Junior TRASHES it.

    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    If you are interested, you could look up "DEC is Dead, Long Live
    DEC", an excellent book.

    Still wish someone would modernize VMS - it was a
    fantastic/powerful system with a ton of prescient
    modern features - could do international internet
    before there WAS an internet.

    Somebody is trying to do so (see https://vmssoftware.com/) but
    that particular train has left the station a long time ago.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 12:19:18 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 21:20, Janis Papanagnou wrote:
    On 2026-10-31 20:08, Carlos E. R. wrote:

    I don't remember if my friend punched his own code, or had it punched.
    Would depend on how many punch machines they had for lowly students.

    We had a "row" of such machines available. Don't recall to have
    ever waited for a free place (or the waiting time was negligible).


    I remember his saying that he had to submit his stack of cards to a
    clerk, then given a paper slip to collect the results another day.

    The way it was done in our place was technically similar but did
    not require that much time.

    The batch cards reader was in an accessible are, you could just
    put the cards either directly in the reader device or in a queue
    on a nearby desk where an operator did that job then. The reader
    was constantly fed with cards by the operators since the queue
    was also regularly filled by all the students; hardly more delay
    than, maybe, 15 minutes. The printouts were quickly created with
    the batch processing by super-fast chain printers, so were also
    available in short term. Some delay was due to the fanfold paper
    needed to be physically separated (by the jobs or user IDs) to be
    associated to the different users. The output landed sorted in a
    special shelf where we could fetch them. The whole batch process,
    from the punch cards delivery to getting the printout results in
    (typically less than) an hour.

    A peculiarity of the physical separation of the printouts was the
    application of a nice trick; the printing logic for the front page
    of the job printed some text (X-es?) across the paper-perforation
    so that the individual jobs could quickly be detected visually if
    you looked at the paper stack from the side.

    Ah! This part I knew nothing about, but makes sense.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 12:31:21 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 23:41, Richard Kettlewell wrote:
    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-10-31 11:49, Nuno Silva wrote:
    On 2026-10-31, Carlos E. R. wrote:
    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than
    a flaw of the online manual in itself?

    No, man pages do not contain links to section of the document. It is
    not structured.

    Nuno is right; a viewer can include links. For an example see man7.org.

    Maybe the viewer can, but the man files don't.


    There is the tool "pinfo", it can highlight somethings like the name of another man page, and jump to it.

    Still, no table of content. No jumping from one section while browsing
    the man page.

    See man man page, for example.

    SYNOPSIS
    man [man options] [[section] page ...] ...
    man -k [apropos options] regexp ...
    man -K [man options] [section] term ...
    man -f [whatis options] page ...
    man -l [man options] file ...
    man -w|-W [man options] page ...

    I can not click or tap on the third line to explain to me about "man -K"
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 12:59:54 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 22:11, Janis Papanagnou wrote:
    On 2026-10-31 19:56, Carlos E. R. wrote:
    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    But technically we have already "clickable" documents; with HTML for
    example.

    Yes, and some tools use that. But then, a command like "apropos" does
    not find that page.


    (Although it should still be available in one page, and ideally also searchable by regexps in easy ways. (As opposed to click on a search
    icon, move the mouse to a new sub-window, (optionally) click another
    time in that window to "activate" it for input, type in only a fixed non-regexp text (often without possibility to distinguish caps, or,
    if you're lucky, only with an extra click in some control-box), and
    hit enter (if you're lucky) or have to again move the mouse to click
    on some Okay button.) - I certainly hate to have no '/search-pattern'
    or '<Ctrl-F>search-pattern' available; with emphasis on "pattern".)

    Personally I typically want (at least) three levels of information.
    Terse usage information, complete interface description, and thorough explanations of all details in case of the more complex tools.


    And an examples section. How to do this or that.

    Mostly we (now) have all that information; if only through the Web.
    (But often inconsistent or even unreliable.)

    Should we have everything just in one (clickable) format like HTML?
    I don't think so. Should we have all the spread existing information rewritten in some other format? Well, who would do that job?

    What I (also) criticize is that we don't have a consistent level of information with some newer Linux platforms. I wished for the "second
    level" of information that the man page format would have been kept/ maintained instead of trying to deprive that format in favor of the
    'info' format.

    Well, I find "info date" (for me "pinfo date") better for finding the information than "man date". Or "pinfo gcc".


    Janis, preferring to avoid mouse-devices in the first place

    Sure, point and click can also work without a mouse. Use the cursor to
    select an entry in the table of contents, then hit enter.

    Yes, sure. For long documents ("level three" information) with a lot
    content where a "table of contents" is sensible that makes completely
    sense. (Even pure mouse-control would be fine here [for me] in this
    case.)

    For the information level where I'd see the man-pages I wouldn't even
    need a "table of contents", since that type of information shouldn't
    be that voluminous, IMO.

    Yes, but I have trouble finding the information for commands with very
    long pages, like "man zypper" (2559 lines).
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 13:03:44 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01 02:08, Nuno Silva wrote:
    On 2026-10-31, Carlos E. R. wrote:
    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    A question is how much of that is already possible using the current
    format.

    And another question is whether the current format, which could easily
    be printed besides being installed as an online manual, does make for
    better documentation to read than something focused on having more
    internal references.

    Printed documentation did have indexes and tables of content, with page numbers, so that you could find where something was in the paper.

    As to printing man pages, well.. I can't store that much paper any more.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 13:07:09 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:
    On Sat, 31 Oct 2026 11:40:12 +0100, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index.

    Most man pages are not supposed to be that large. Of course, there
    are some exceptions (like bash). For those I think yourCOll find the
    man page was generated from some other, more navigable form anyway.

    For example, if you look at Perl, you will see its documentation is
    broken up across a whole series of man pages -- over 200 of them.

    (Is that going too far in the other direction, do you think ... ?)

    Tip: if you prefer another form, like PDF, itrCOs quite easy to generate
    that from any man page. I used to use a somewhat convoluted command
    for this, but it turns the usual Linux rCLmanrCY command has an option to directly choose the output format, e.g. view a man page directly in
    typeset form without saving it to a file:

    PDF is fine, but not if the source is a man page, because there are no
    cross references that you can click or tap; ditto table of contents and
    index.


    man -Tpdf 7 unix | okular - &

    (Substitute your choice of favourite PDF reader.)

    Info pages are somewhat better.

    I have tried info pages a few times, but always found them awkward to navigate. IrCOve never heard of anybody who liked them.

    Try "pinfo" as navigator instead.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 17:22:16 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01 10:18, c186282 wrote:
    On 10/31/26 17:11, Janis Papanagnou wrote:
    [...]
    For the information level where I'd see the man-pages I wouldn't even
    need a "table of contents", since that type of information shouldn't
    be that voluminous, IMO.

    -a But what if it BECAME so ?

    There's obviously [only] a couple pathological cases of gigantic
    man-pages. (I seem to recall to have had posted the statistics of
    the man-page length distribution some not too long time ago.) But
    there's certainly also too many that grew to large on Linux.

    It's the responsibility of the authors and publishers to rewrite
    their documentation, so it's all vain to complain about existing
    ones. (And I also don't think this will happen for those tools.)

    I don't see, though, that this would mean that new tools will have
    to follow that path of producing one overly long man-page with all
    information and undifferentiated in one huge file.


    -a Shit turns into a lot MORE shit.

    -a My input to hypertext in the ancient days was the
    -a idea of a sort of 'infinitely-indexed database'
    -a where everything of importance somehow linked to
    -a a huge tree of related info, which linked to a
    -a huge tree of related info .....

    That "somehow" in your thought needs some refinement, I suppose. :-)

    Back in the days (and possibly still prevalent) there was a DB hype
    to put everything in databases. (By "databases" here I mean systems,
    DBMS.) Over the past decades my personal preferences changed insofar
    to prefer a reduce complexity for the many simple application cases.
    I'd certainly reduce all dependencies, and avoid any necessities to
    access tool documentation data only through such a system. I'm not
    sure the textual tools-documentation should have (or would require)
    a comparably complex database. YMMV.


    -a Weren't as many 'computer geeks' back then.

    -a They solved the index-space issue by using html
    -a page links. The giant 'tree' wasn't in one place
    -a any more. Not really possible before the early-80s
    -a alas until DARPA-Net firmly became the Internet.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 17:50:40 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01 12:59, Carlos E. R. wrote:
    On 2026-10-31 22:11, Janis Papanagnou wrote:
    On 2026-10-31 19:56, Carlos E. R. wrote:
    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    But technically we have already "clickable" documents; with HTML for
    example.

    Yes, and some tools use that. But then, a command like "apropos" does
    not find that page.

    Frankly, I don't know the installation process of my Linux distro in
    detail, but I can say that when I add a new tool-binary I instantly
    also have the man page accessible, and I find the respective infos
    through 'apropos' as well. I don't see why there would be a principal
    hindrance to do that for other information sources as well.



    (Although it should still be available in one page, and ideally also
    searchable by regexps in easy ways. (As opposed to click on a search
    icon, move the mouse to a new sub-window, (optionally) click another
    time in that window to "activate" it for input, type in only a fixed
    non-regexp text (often without possibility to distinguish caps, or,
    if you're lucky, only with an extra click in some control-box), and
    hit enter (if you're lucky) or have to again move the mouse to click
    on some Okay button.) - I certainly hate to have no '/search-pattern'
    or '<Ctrl-F>search-pattern' available; with emphasis on "pattern".)

    Personally I typically want (at least) three levels of information.
    Terse usage information, complete interface description, and thorough
    explanations of all details in case of the more complex tools.


    And an examples section. How to do this or that.

    This is often useful. For powerful large tools this might exceed
    what one likes in a man-page, though, and would just contribute
    to making the man-page "unreadable" due to its length. Here again
    I think that the type of the examples is the discriminating info;
    the man-page should certainly contain the technical options and
    examples how to call the tool with those, but (having tools like
    Imagemagick in mind) not the functional usage examples that would
    better be placed in a tutorial type of documentation.


    Mostly we (now) have all that information; if only through the Web.
    (But often inconsistent or even unreliable.)

    Should we have everything just in one (clickable) format like HTML?
    I don't think so. Should we have all the spread existing information
    rewritten in some other format? Well, who would do that job?

    What I (also) criticize is that we don't have a consistent level of
    information with some newer Linux platforms. I wished for the "second
    level" of information that the man page format would have been kept/
    maintained instead of trying to deprive that format in favor of the
    'info' format.

    Well, I find "info date" (for me "pinfo date") better for finding the information than "man date". Or "pinfo gcc".

    One problem I have with 'info' is that I see only a paragraph of
    a subsection of a section of the described thing. I certainly want
    to see more context! I also like to have the typical chapters that
    describe the tools' _interfaces_ (the name with terse description,
    the usage synopsis, a description, the list of options, returned
    status codes, files that affect the tool in some way, example uses,
    and know bugs, for example).

    The 'date' manual you gave as example is certainly not one of the pathologically huge man-pages (with its 200 lines, and most of it
    is anyway just a table of the format specifiers).

    Janis

    [...]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From FF@fflud@linux.rocks to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 18:09:50 2026
    From Newsgroup: comp.unix.shell

    On Sun, 1 Nov 2026 17:50:40 +0100, Janis Papanagnou wrote:


    Frankly, I don't know the installation process of my Linux distro in
    detail, but I can say that when I add a new tool-binary I instantly also
    have the man page accessible, and I find the respective infos through 'apropos' as well. I don't see why there would be a principal hindrance
    to do that for other information sources as well.


    The configuration files that set the global MANPATH* variables are:

    /etc/man.conf

    /etc/man_db.conf

    Only the specified MANPATH* locations are searched for man pages.

    Of course, a package build has to also specify where its man pages
    will be located. These are usually the same as the MANPATH* locations.

    But, again, GNU/Linux allows man pages to be placed anywhere that
    the user desires.

    Most users, however, are not the masters of their own machines and
    the distros will make all decisions for them.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 1 19:13:45 2026
    From Newsgroup: comp.unix.shell

    On Sun, 1 Nov 2026 10:16:14 -0000 (UTC), Thomas Koenig wrote:

    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    If you talk to the staff who worked under him, you wonrCOt find anybody
    with a bad word to say about him. He looked after his people well.

    But, he was very much a Unix-hater, describing it as rCLsnake oilrCY at
    one point.

    After he was ousted, the asset-strippers took charge.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 19:40:09 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31, Nuno Silva <nunojsilva@invalid.invalid> wrote:

    On 2026-10-31, Carlos E. R. wrote:

    On 2026-10-30 20:24, Charlie Gibbs wrote:

    On 2026-10-30, c186282 <c186282@nnada.net> wrote:


    More VOLUME of docs these days ... but "As Good" ???

    Hardly. Most manuals back in the day had a section titled
    "Theory of Operation". I really miss that.

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than a
    flaw of the online manual in itself?

    At least the man command can search a man page for a text string.
    It's not perfect, but it's better than nothing.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 19:40:10 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31, Leroy H <lh@somewhere.net> wrote:

    On Sat, 31 Oct 2026 21:57:58 -0000 (UTC), Lawrence DrCOOliveiro wrote:


    For example, if you look at Perl, you will see its documentation is
    broken up across a whole series of man pages -- over 200 of them.

    (Is that going too far in the other direction, do you think ... ?)


    The record for the number of man pages has to be openssl.

    Here is the list on my Gentoo system. Don't bother counting.

    <list snipped>

    TL;DR :-)
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Christian Weisgerber@naddy@mips.inka.de to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 20:50:14 2026
    From Newsgroup: comp.unix.shell

    On 2026-10-31, Carlos E. R. <robin_listas@es.invalid> wrote:

    No, man pages do not contain links to section of the document. It is not structured.

    There are two roff macro sets for man pages: man(7) and mdoc(7).

    man(7) is poorly structured. mdoc(7), which originated in 4.4BSD
    but is now widely available, provides semantic markup. With mdoc(7),
    the structure is there, it's up to the downstream tools to use it.

    The HTML output mode of Kristaps Dzonsons' mandoc(1) formatter,
    which appears to have spread to all BSDs, seems to mostly limit
    itself to providing lots of #anchors as potential targets for
    linking, e.g.:
    https://man.openbsd.org/ls

    When you are piping formatted text into less(1), there are few
    possibilities. OpenBSD's man(1) uses mandoc(1) to dump various
    definitions into a temporary ctags(1) file that is passed to
    less -T. So when I run "man ls" and want to know what the -u option
    does, I can jump straight to it by entering ":tu". That can be
    very useful when navigating long manpages, such as got(1) from Game
    of Trees, where I can jump directly to the subcommand I want to
    look up.

    mdoc(7)'s semantic markup also allows for a more powerful apropos(1)
    that, for instance, allows you to seach for all man pages that
    mention the type "struct stat":

    $ apropos Vt='struct stat'
    stat(1) - display file status
    fhopen, fhstat, fhstatfs(2) - access file via file handle
    getfsstat(2) - get list of all mounted file systems
    pledge(2) - restrict system operations
    stat, fstat, fstatat, lstat, S_ISBLK, S_ISCHR, S_ISDIR, S_ISFIFO,
    S_ISLNK, S_ISREG, S_ISSOCK(2) - get file status
    statfs, fstatfs(2) - get file system statistics
    ftw, nftw(3) - traverse (walk) a file tree
    ...
    --
    Christian "naddy" Weisgerber naddy@mips.inka.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 22:29:23 2026
    From Newsgroup: comp.unix.shell

    On Sun, 1 Nov 2026 12:59:54 +0100, Carlos E. R. wrote:

    But then, a command like "apropos" does not find that page.

    rCLaproposrCY (aka rCLman -krCY) only searches the synopsis lines, I believe. --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 22:32:35 2026
    From Newsgroup: comp.unix.shell

    On Sun, 1 Nov 2026 13:07:09 +0100, Carlos E. R. wrote:

    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:

    Tip: if you prefer another form, like PDF, itrCOs quite easy to
    generate that from any man page.

    PDF is fine, but not if the source is a man page, because there are
    no cross references that you can click or tap ...

    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    ... ditto table of contents and index.

    Yeah, theyrCyre not (normally) supposed to be long enough to need that
    ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 1 18:17:04 2026
    From Newsgroup: comp.unix.shell

    On 11/1/26 05:16, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:
    On 10/31/26 17:38, Lawrence DrCOOliveiro wrote:
    On Sat, 31 Oct 2026 11:07:47 -0400, jayjwa wrote:

    The DEC systems are more fun, have better docs, and much more
    software.

    If you look at all the vintage docs collected at Bitsavers, out of
    (currently) about 660GB in total, over 40% is from DEC. Number 2 is
    IBM, but the DEC collection is bigger by nearly 3:1.

    Number 3 is CDC, at about a quarter of the size of the IBM collection.

    The DEC boxes were GREAT !

    Not entirely sure why they went out of biz - likely
    idiot management. Daddy builds it, Junior TRASHES it.

    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    Developed giant coke habit maybe ? ;-)

    If you are interested, you could look up "DEC is Dead, Long Live
    DEC", an excellent book.

    Still wish someone would modernize VMS - it was a
    fantastic/powerful system with a ton of prescient
    modern features - could do international internet
    before there WAS an internet.

    Somebody is trying to do so (see https://vmssoftware.com/) but
    that particular train has left the station a long time ago.

    Alas, probably so. It'd take too many fix-ups now
    to go 'modern', to be a rival to Linux/UNIX.

    But it was damned good in its day.

    Anyway, as for 'wealth' the complete usual rule
    is : GrandPa makes it, Junior cruises on it and
    the grandkids BLOW it all. No ancient titled
    families in the USA - no barons, ducs and earls -
    money comes, and goes.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 1 16:45:53 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> writes:
    On 11/1/26 05:16, Thomas Koenig wrote:
    [...]
    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    Developed giant coke habit maybe ? ;-)

    Do you have some basis for this? If it's a joke (yes, I see the
    smiley), I fail to see the humor.

    [...]
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.os.linux.misc,comp.unix.shell on Sun Nov 1 16:49:48 2026
    From Newsgroup: comp.unix.shell

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
    [...]
    I have tried info pages a few times, but always found them awkward to navigate. IrCOve never heard of anybody who liked them.

    You have now: I do. I'm not sure what the objection is.
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 1 21:00:39 2026
    From Newsgroup: comp.unix.shell

    On 11/1/26 19:45, Keith Thompson wrote:
    c186282 <c186282@nnada.net> writes:
    On 11/1/26 05:16, Thomas Koenig wrote:
    [...]
    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    Developed giant coke habit maybe ? ;-)

    Do you have some basis for this? If it's a joke (yes, I see the
    smiley), I fail to see the humor.

    [...]


    Umm ... NOT so unusual for the times :-)

    Gotta wonder. Big powerful cutting-edge corp
    with good history suddenly crashes and burns ......

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 02:16:41 2026
    From Newsgroup: comp.unix.shell

    According to c186282 <c186282@nnada.net>:
    Umm ... NOT so unusual for the times :-)

    Gotta wonder. Big powerful cutting-edge corp
    with good history suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened. The world of microprocessors
    was different from the world of minicomputers, DEC's management never figured that out,
    and its board of directors didn't either.

    Gordon Bell wrote this afterword for the "DEC is Dead" book which explains it well.

    https://gordonbell.azurewebsites.net/CGB%20Files/DEC_Is_Dead_Bell_Appendix_Schein_Book.pdf
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 04:48:32 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 02:16:41 -0000 (UTC), John Levine wrote:

    According to c186282 <c186282@nnada.net>:
    Umm ... NOT so unusual for the times

    Gotta wonder. Big powerful cutting-edge corp with good history
    suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened. The world of microprocessors was different from the world of minicomputers, DEC's management never figured that out, and its board of directors didn't
    either.

    The Rainbow was interesting. Almost, but not quite, compatible with PCs.
    The proprietary diskettes at $5 a pop didn't go over well either.

    Olsen's belief that people didn't need or want a home computer wasn't
    unique in that era. Ward Christensen of xmodem fame worked for IBM.
    Famously he sent a memo up the chain of command saying IBM should look
    into microcomputers. The reply was there was no market for them but if he wanted to screw around with them on his own time feel free.

    We contracted to supply cable assemblies to DEC in Augusta ME in the '70s. Their QA was quite demanding but we could pass inspection. Then they gave
    the contract to the Passamaquoddy tribe. I don't know how that turned
    out.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 14:13:06 2026
    From Newsgroup: comp.unix.shell

    On 11/2/2026 12:48 PM, rbowman wrote:
    On Mon, 2 Nov 2026 02:16:41 -0000 (UTC), John Levine wrote:

    According to c186282 <c186282@nnada.net>:
    Umm ... NOT so unusual for the times

    Gotta wonder. Big powerful cutting-edge corp with good history
    suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened. The world of
    microprocessors was different from the world of minicomputers, DEC's
    management never figured that out, and its board of directors didn't
    either.

    The Rainbow was interesting. Almost, but not quite, compatible with PCs.
    The proprietary diskettes at $5 a pop didn't go over well either.

    Olsen's belief that people didn't need or want a home computer wasn't
    unique in that era. Ward Christensen of xmodem fame worked for IBM.
    Famously he sent a memo up the chain of command saying IBM should look
    into microcomputers. The reply was there was no market for them but if he wanted to screw around with them on his own time feel free.

    We contracted to supply cable assemblies to DEC in Augusta ME in the '70s. Their QA was quite demanding but we could pass inspection. Then they gave
    the contract to the Passamaquoddy tribe. I don't know how that turned
    out.

    Nobody can prevent someone else from inventing something that changes
    the business rules from under you. I'm only theorizing here, but I
    would not be surprised [1] if DOOM sold a lot of home PCs in the early
    90s, then Quake even more.

    Windows 95 helped, but as far as I understand it, it really was meant
    for corporate environments more than the home on the technical side; the
    rest was just marketing.

    The social phenomenon of people building their own home computers, then gathering together to connect them with a LAN, all in order to play DOOM shouldn't be underestimated.

    Side note: there's a marketing book called /Guerilla Marketing/ that
    touches upon this subject.


    Best wishes, and happy victories in DOOM!

    [1] And indeed would be surprised it wasn't a significant factor.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 01:28:55 2026
    From Newsgroup: comp.unix.shell

    On 11/1/26 21:16, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    Umm ... NOT so unusual for the times :-)

    Gotta wonder. Big powerful cutting-edge corp
    with good history suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened. The world of microprocessors
    was different from the world of minicomputers, DEC's management never figured that out,
    and its board of directors didn't either.

    I can believe "board of directors" ... but not
    so much the hands-on people at DEC.

    One factor MAY have been shifting so much to
    the micro-VAX units ... basically good PCs.
    Too much competition at that level. Winders
    and UNIX on x86 and, for awhile, 68xxx, kinda
    had that market sewn up and for cheaper than
    anything DEC could provide.

    Micro-VAX were good - used 'em - still have a
    hugely thick VMS manual.

    One place I did work used a micro-VAX for
    the entire campus. People had PCs, but
    mostly used them as dumb-ish terminals
    for the VAX. Just after I left they moved
    to a little x86 cluster and some kind
    of UNIX (or maybe Solaris ?). More better
    for more cheap.

    IBM dumped its PCs and put more money into
    it's minis and super-duper mainframes and
    systems and all the goodies. IBM is still
    here, DEC is not. NONE of the "Big Old Boyz"
    remain except IBM. People make fun of IBM
    but it IS a survivor, a more sensitive ear
    to the ground, so to speak. Even now loads
    of chip-makers and such are quietly paying
    royalties to IBM.

    Honeywell, Burroughs and friends - you helped
    us Get There, but ... wrong steps .......

    WOULD love one or two of those big black IBM
    mainframe units. Not sure what I'd DO with
    them, but they'd be SO cool ! Anyway they do
    have plenty of customers - govt/uni and big
    industry. Sometimes you NEED a 'mainframe'.

    Apparently the IBM spin of RedHat is now the
    most popular user mainframe OS. Plan-9 WAS
    ported, but I don't think it ever got much
    of a following (actually a good cluster
    system though but RH is better supported).

    Gordon Bell wrote this afterword for the "DEC is Dead" book which explains it well.

    https://gordonbell.azurewebsites.net/CGB%20Files/DEC_Is_Dead_Bell_Appendix_Schein_Book.pdf

    One guy's opinions, probably had a grudge. As usual,
    it's gonna be more complicated, subtle, than that.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 06:47:24 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 14:13:06 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    Windows 95 helped, but as far as I understand it, it really was meant
    for corporate environments more than the home on the technical side; the
    rest was just marketing.

    Enterprises use NT. It wasn't until Windows XP that the the consumer and business branches were merged. NT 4.0 used the Windows 95 UX but Windows
    2000 brought in more features from the consumer lines. I don't think 2000
    was marketed in the consumer market. The lucky consumers got Windows Me as
    a consolation prize since the XP project was moving slowly.

    NT 4.0 was the last release to be called NT but the numbering scheme was carried on so Windows 11 is NT 10.0 formally. It might have been my
    machine but NT 4.0 usually greeted my with the BSOD on Monday morning.
    2000 was an improvement.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 09:41:28 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02 07:28, c186282 wrote:
    [...]

    -a WOULD love one or two of those big black IBM
    -a mainframe units. Not sure what I'd DO with
    -a them, but they'd be SO cool !

    :-)

    There's a couple hardware types I'd have liked to have -
    and I'd also not know what to do with them but to wallow
    in memories.

    Anyway they do
    -a have plenty of customers - govt/uni and big
    -a industry. Sometimes you NEED a 'mainframe'.

    Hmm.. - "need" - really?

    During the 1990's we switched our big telcos from mainframes
    to Unix servers. The huge sports halls where the mainframes
    had been running were almost empty then. It was just more
    economic to run Unix servers (mainframe support was costly,
    as was just running them), also more ecologic (though I'm
    not sure that this mattered that much in practice, but costs
    of electricity might have been an issue), and the much less
    required physical space as said. Basically all cost factors.

    Also computing centers switched. Our LRZ, formerly running
    a CDC 175, is meanwhile running various Unix clusters for
    "super computing". Our university also said goodbye to its
    TR440 and is providing mainly Linux systems to its students
    for the scientific oriented departments.

    The only "need" for a mainframe I observed in some financial
    business area, where they were still running their legacy
    software on mainframes obviously with "no chance" to migrate,
    or not wanting to take the risk and cost (as long as the old
    machinery is doing its task). But it's also difficult to get
    spares, and to find people who can and are willing to operate
    them. (But that information is now a bit dated and things may
    have meanwhile changed even in that business area.)

    Janis

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 03:56:39 2026
    From Newsgroup: comp.unix.shell

    On 11/2/26 01:13, Johann 'Myrkraverk' Oskarsson wrote:
    On 11/2/2026 12:48 PM, rbowman wrote:
    On Mon, 2 Nov 2026 02:16:41 -0000 (UTC), John Levine wrote:

    According to c186282-a <c186282@nnada.net>:
    -a-a Umm ... NOT so unusual for the times

    -a-a Gotta wonder. Big powerful cutting-edge corp with good history
    -a-a suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened.-a The world of >>> microprocessors was different from the world of minicomputers, DEC's
    management never figured that out, and its board of directors didn't
    either.

    The Rainbow was interesting. Almost, but not quite, compatible with PCs.
    The proprietary diskettes at $5 a pop didn't go over well either.

    Olsen's belief that people didn't need or want a home computer wasn't
    unique in that era. Ward Christensen of xmodem fame worked for IBM.
    Famously he sent a memo up the chain of command saying IBM should look
    into microcomputers. The reply was there was no market for them but if he
    wanted to screw around with them on his own time feel free.

    We contracted to supply cable assemblies to DEC in Augusta ME in the
    '70s.
    Their QA was quite demanding but we could pass inspection. Then they gave
    the contract to the Passamaquoddy tribe. I don't know how that turned
    out.

    Nobody can prevent someone else from inventing something that changes
    the business rules from under you.-a I'm only theorizing here, but I
    would not be surprised [1] if DOOM sold a lot of home PCs in the early
    90s, then Quake even more.

    DOOM and DUKE NUKEM were great. QUAKE ... it
    was mostly BLACK SCREEN shit, why bother having
    a monitor ???

    Still have DUKE stashed away somewhere, runs in
    DOSBox. Lots of user-created episodes too. For one
    I had to write a 256 bit binary-2-decimal calculator :-)

    DOOM-1 ... the droning music and pouncing
    monsters ... gave me PTSD. Same for a number
    of people I knew. Got into your head. Heard the
    mil adapted it for commando training because
    of that - get the troops KEYED UP. Remember
    I kept reaching for my "shotgun" when there
    were sudden events for awhile .... PTSD.
    D2 didn't do that.

    Windows 95 helped, but as far as I understand it, it really was meant
    for corporate environments more than the home on the technical side; the
    rest was just marketing.

    The social phenomenon of people building their own home computers, then gathering together to connect them with a LAN, all in order to play DOOM shouldn't be underestimated.

    It was an important milestone - and boosted
    the development of a lot of shit. "Games"
    are, unto themselves, trivial. However the
    tech/knowledge to do them well drove a lot
    of tech. A *large* market segment demanded
    the 'better game computer', so ....

    NVidia came out of that. Now it's a zillion
    dollar concern smack in the middle of 'AI'.

    Side note: there's a marketing book called /Guerilla Marketing/ that
    touches upon this subject.


    Best wishes, and happy victories in DOOM!

    [1] And indeed would be surprised it wasn't a significant factor.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 10:47:52 2026
    From Newsgroup: comp.unix.shell

    On 01/11/2026 23:17, c186282 wrote:
    Not entirely sure why they went out of biz - likely idiot
    management. Daddy builds it, Junior TRASHES it.

    Daddy built it, daddy trashed it (Ken Olsen, he was responsible for
    both).

    Developed giant coke habit maybe ? Efye

    Back in the day minicomputers, built of LSI TTL and Schotttky TTL were
    all there was below mainframes

    Almost none of the manufacturers survived the microprocessor

    A few people built -|P based multi-user computers or high performance workstations. Sun, Irix, HP... etc

    But it was so much easier to take a standard PC and shove a *86 *nix OS
    on it rather than build custom hardware.

    Even IBM went that route.

    Without some USP other than hardware it was hard to sell such systems.

    Only SUN really survived. And where are they now?
    --
    For every complex problem there is an answer that is clear, simple, and
    wrong.

    H.L.Mencken

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 10:52:56 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 00:45, Keith Thompson wrote:
    c186282 <c186282@nnada.net> writes:
    On 11/1/26 05:16, Thomas Koenig wrote:
    [...]
    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    Developed giant coke habit maybe ? ;-)

    Do you have some basis for this? If it's a joke (yes, I see the
    smiley), I fail to see the humor.

    During the 90s and noughties, that was the hallmark of a successful professional [politician]

    Being familiar with its effects on those who I knew in the 70s, I could
    see evidence of it everywhere.

    The rictus smile. The cruelty. The arrogance.

    Think Aztec priests and human sacrifice

    Who DIDN'T have a giant coke habit then?


    [...]

    --
    Socialism is the philosophy of failure, the creed of ignorance and the
    gospel of envy.

    Its inherent virtue is the equal sharing of misery.

    Winston Churchill


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 11:13:35 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 06:28, c186282 wrote:
    I can believe "board of directors" ... but not so much the hands-on
    people at DEC.

    If your hands-on is building boards out of TTL in 100 quantities it
    isn't necessarily relevant to competing with mass produced motherboards
    and Intel chipsets made in millions. Or designing you own -|processor.

    PCs just swept the opposition away.

    And Microsoft surfed the wave to corporate dominance in an era of me-too hardware.

    Unix staggered on for multi-user systems till Linus said 'fuck this for
    a game of soldiers'...

    Even ARM was initially a desperate attempt to create s 'better 6502' for
    the ultra low end home/educational computers, designed to use as few transistors as a struggling British company could afford to have fabbed.

    In the tradition of proper engineering it was 'doing for five bob what
    any damn fool can do for a quid'...and its ultra low hardware footprint
    and elegant instruction set made it first of all incredibly cheap for
    embedded use, and ultimately de facto for low power consumption. An
    entirely unintentional side effect of trying to make it CHEAP.

    Like Microsoft, it happened to be standing in the right place at the
    right time.

    People like to represent themselves as genius visionaries: But my
    experience is more that its a simple question of being in the right
    place at the right time, and the only smarts is in recognising that.

    The rise of LSI in the 70s made minicomputers possible. The rise of mass produced microprocessors in the 1980s made them irrelevant.

    And the 90s was really all about software.
    --
    "When a true genius appears in the world, you may know him by this sign,
    that the dunces are all in confederacy against him."

    Jonathan Swift.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 11:22:25 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 08:41, Janis Papanagnou wrote:
    On 2026-11-02 07:28, c186282 wrote:
    [...]

    -a-a WOULD love one or two of those big black IBM
    -a-a mainframe units. Not sure what I'd DO with
    -a-a them, but they'd be SO cool !

    :-)

    There's a couple hardware types I'd have liked to have -
    and I'd also not know what to do with them but to wallow
    in memories.

    -a-a Anyway they do
    -a-a have plenty of customers - govt/uni and big
    -a-a industry. Sometimes you NEED a 'mainframe'.

    Hmm.. - "need" - really?

    During the 1990's we switched our big telcos from mainframes
    to Unix servers. The huge sports halls where the mainframes
    had been running were almost empty then. It was just more
    economic to run Unix servers (mainframe support was costly,
    as was just running them), also more ecologic (though I'm
    not sure that this mattered that much in practice, but costs
    of electricity might have been an issue), and the much less
    required physical space as said. Basically all cost factors.

    Also computing centers switched. Our LRZ, formerly running
    a CDC 175, is meanwhile running various Unix clusters for
    "super computing". Our university also said goodbye to its
    TR440 and is providing mainly Linux systems to its students
    for the scientific oriented departments.

    Yes. The transition from mainframe, to Unix clusters and then to blade
    servers shrunk machine rooms to almost nothing, amnd high speed internet
    moved them to cloud centres

    The only "need" for a mainframe I observed in some financial
    business area, where they were still running their legacy
    software on mainframes obviously with "no chance" to migrate,
    or not wanting to take the risk and cost (as long as the old
    machinery is doing its task). But it's also difficult to get
    spares, and to find people who can and are willing to operate
    them. (But that information is now a bit dated and things may
    have meanwhile changed even in that business area.)

    That's not quite true. First of all old IBM COBOL and RPG is well
    supported on modern -|P based hardware. and second mainframes are still
    in use where enormous numbers of I/O operations are called for.

    "Mainframes remain the invisible backbone of the global economy in the
    21st century, handling 90% of credit card transactions, powering 92 of
    the top 100 banks, and managing 68% of production IT workloads globally
    while accounting for just a fraction of total IT spending."

    Mainframes remain cost effective alternatives for very large scale low complexcity transactions
    --
    ItrCOs easier to fool people than to convince them that they have been fooled. Mark Twain



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 11:31:22 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 00:49, Keith Thompson wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
    [...]
    I have tried info pages a few times, but always found them awkward to
    navigate. IrCOve never heard of anybody who liked them.

    You have now: I do. I'm not sure what the objection is.


    My beef against man pages is that they are written to answer the
    question no one actually wants the answer to: Namely 'what can your
    shiny new piece of shit do?'

    Whereas the real question is:

    'I know your piece of shiny shit can do this, but have no idea what the
    magic spell is that will enable it to happen?'

    I once spent -u50 and a whole day browsing a 3rd party Solaris manual for
    *one line* of configuration, to tell a SUN SysV computer how to send
    data to a parallel printer.

    Before CUPS and after LPR/LPD (BSD) the dreadful lpadmin/lp interface
    had arrived and no one actually knew how to use it.

    Today AI and the net provides most answers in a few milliseconds

    I don't buy computer manuals any more
    --
    If I had all the money I've spent on drink...
    ..I'd spend it on drink.

    Sir Henry (at Rawlinson's End)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 20:02:01 2026
    From Newsgroup: comp.unix.shell

    On 11/2/2026 2:47 PM, rbowman wrote:
    On Mon, 2 Nov 2026 14:13:06 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    Windows 95 helped, but as far as I understand it, it really was meant
    for corporate environments more than the home on the technical side; the
    rest was just marketing.

    Enterprises use NT. It wasn't until Windows XP that the the consumer and business branches were merged. NT 4.0 used the Windows 95 UX but Windows
    2000 brought in more features from the consumer lines. I don't think 2000
    was marketed in the consumer market. The lucky consumers got Windows Me as
    a consolation prize since the XP project was moving slowly.

    NT 4.0 was the last release to be called NT but the numbering scheme was carried on so Windows 11 is NT 10.0 formally. It might have been my
    machine but NT 4.0 usually greeted my with the BSOD on Monday morning.
    2000 was an improvement.

    That's probably true, but I'll point out that not all /businesses/ are
    at the enterprise level. Lots and lots of small to medium businesses
    had DOS, then Windows machines in the 90s.

    My school had computer labs with Windows 3.1, then '95; the LAN was
    Novell. I wasn't working at place a large enough to have NT machines in
    the 90s -- and I guess I never have.

    But most importantly, none of the businesses I was familiar with in the
    90s had a VAX or knew what to do with it. But that was Iceland. You
    can think of Reykjavik back then as a small town in the sticks.

    DOOM did not come out on VAX -- even today I'm not sure there's a VAX
    port. [There probably is.] So whatever DEC was doing right in the 90s,
    not being part of the video game social phenomenon was not it.


    Best wishes, and happy VAXen!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 20:03:46 2026
    From Newsgroup: comp.unix.shell

    On 11/2/2026 4:56 PM, c186282 wrote:
    The social phenomenon of people building their own home computers, then
    gathering together to connect them with a LAN, all in order to play DOOM
    shouldn't be underestimated.

    -a It was an important milestone - and boosted
    -a the development of a lot of shit. "Games"
    -a are, unto themselves, trivial. However the
    -a tech/knowledge to do them well drove a lot
    -a of tech. A *large* market segment demanded
    -a the 'better game computer', so ....

    -a NVidia came out of that. Now it's a zillion
    -a dollar concern smack in the middle of 'AI'.

    And now people are dreaming NVidia will disappear, the way of DEC. Well
    maybe it /will/ be sold to HP?

    After all, gamers want their affordable graphics cards back.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 20:11:48 2026
    From Newsgroup: comp.unix.shell

    On 11/2/2026 7:22 PM, The Natural Philosopher wrote:
    On 02/11/2026 08:41, Janis Papanagnou wrote:
    On 2026-11-02 07:28, c186282 wrote:
    [...]

    -a-a WOULD love one or two of those big black IBM
    -a-a mainframe units. Not sure what I'd DO with
    -a-a them, but they'd be SO cool !

    :-)

    There's a couple hardware types I'd have liked to have -
    and I'd also not know what to do with them but to wallow
    in memories.

    -a-a Anyway they do
    -a-a have plenty of customers - govt/uni and big
    -a-a industry. Sometimes you NEED a 'mainframe'.

    Hmm.. - "need" - really?

    During the 1990's we switched our big telcos from mainframes
    to Unix servers. The huge sports halls where the mainframes
    had been running were almost empty then. It was just more
    economic to run Unix servers (mainframe support was costly,
    as was just running them), also more ecologic (though I'm
    not sure that this mattered that much in practice, but costs
    of electricity might have been an issue), and the much less
    required physical space as said. Basically all cost factors.

    Also computing centers switched. Our LRZ, formerly running
    a CDC 175, is meanwhile running various Unix clusters for
    "super computing". Our university also said goodbye to its
    TR440 and is providing mainly Linux systems to its students
    for the scientific oriented departments.

    Yes. The transition from mainframe, to Unix clusters and then to blade servers shrunk machine rooms to almost nothing, amnd high speed internet moved them to cloud centres

    The only "need" for a mainframe I observed in some financial
    business area, where they were still running their legacy
    software on mainframes obviously with "no chance" to migrate,
    or not wanting to take the risk and cost (as long as the old
    machinery is doing its task). But it's also difficult to get
    spares, and to find people who can and are willing to operate
    them. (But that information is now a bit dated and things may
    have meanwhile changed even in that business area.)

    That's not quite true. First of all old IBM COBOL and RPG is well
    supported on modern -|P based hardware. and second mainframes are still
    in use where enormous numbers of I/O operations are called for.

    "Mainframes remain the invisible backbone of the global economy in the
    21st century, handling 90% of credit card transactions, powering 92 of
    the top 100 banks, and managing 68% of production IT workloads globally while accounting for just a fraction of total IT spending."

    Mainframes remain cost effective alternatives for very large scale low complexcity transactions



    I've heard -- let's say verbally -- that the relentless transaction pro- cessing done on mainframes is hard to do on different types of machines.

    And what is hard? I haven't worked with mainframes, but last time I
    looked into it, POWER was the only CPU with hardware accelerated decimal arithmetic [1]. This is the kind of computation universities don't do
    as research, so -- based on my stories of academia -- there are none
    there for budding CS doctorates to tinker with.

    So if people think mainframes are somehow /obsolete/, it's because they
    are extrapolating from their own personal experiences and never look un-
    der the hood of the commercial world.


    Best wishes, and happy mainframes!


    [1] I don't have a POWER CPU, and didn't personally verify this.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 20:16:13 2026
    From Newsgroup: comp.unix.shell

    On 11/2/2026 6:47 PM, The Natural Philosopher wrote:
    Only SUN really survived. And where are they now?

    Well, we can say that Solaris got forked. The enterprise behemoth got
    the trade mark, the open source edition got the people.

    So Illumos is still around, and doing well all things considered.


    I personally wish them well.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 13:51:52 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 12:03, Johann 'Myrkraverk' Oskarsson wrote:
    On 11/2/2026 4:56 PM, c186282 wrote:
    The social phenomenon of people building their own home computers, then
    gathering together to connect them with a LAN, all in order to play DOOM >>> shouldn't be underestimated.

    -a-a It was an important milestone - and boosted
    -a-a the development of a lot of shit. "Games"
    -a-a are, unto themselves, trivial. However the
    -a-a tech/knowledge to do them well drove a lot
    -a-a of tech. A *large* market segment demanded
    -a-a the 'better game computer', so ....

    -a-a NVidia came out of that. Now it's a zillion
    -a-a dollar concern smack in the middle of 'AI'.

    And now people are dreaming NVidia will disappear, the way of DEC.-a Well maybe it /will/ be sold to HP?

    After all, gamers want their affordable graphics cards back.

    Companies spread like bacteria. A niche appears., Its has food,. They
    expand to exploit the resource base. Then the resource runs out, and
    they die.

    Same with civilisations.

    Existing ones are based on coal and oil. Upcoming ones will be IT and
    nuclear power
    --
    Climate is what you expect but weather is what you get.
    Mark Twain

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 13:57:19 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 12:11, Johann 'Myrkraverk' Oskarsson wrote:
    So if people think mainframes are somehow /obsolete/, it's because they
    are extrapolating from their own personal experiences and never look un-
    der the hood of the commercial world.

    Yes.

    I've been exposed to computers all the way from LSI TTL, micros and PCs
    , minis and occasionally mainframes, not in that I worked on them, bit I
    was aware of where they fitted into the overall landscape

    COBOL RPG and mainframes were designed to do a job that hasn't really
    changed.

    The minis were designed to do a job that any PC can do better and cheaper.

    And the supercomputer no longer exists as it once was.

    Adapt, or die.

    Most die
    --
    There is nothing a fleet of dispatchable nuclear power plants cannot do
    that cannot be done worse and more expensively and with higher carbon emissions and more adverse environmental impact by adding intermittent renewable energy.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 13:58:48 2026
    From Newsgroup: comp.unix.shell

    On 02/11/2026 12:16, Johann 'Myrkraverk' Oskarsson wrote:
    On 11/2/2026 6:47 PM, The Natural Philosopher wrote:
    Only SUN really survived. And where are they now?

    Well, we can say that Solaris got forked.-a The enterprise behemoth got
    the trade mark, the open source edition got the people.

    So Illumos is still around, and doing well all things considered.


    I personally wish them well.

    Sun is part of Oracle
    They no longer produce any hardware
    --
    How fortunate for governments that the people they administer don't think.

    Adolf Hitler


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 15:35:12 2026
    From Newsgroup: comp.unix.shell

    The Natural Philosopher <tnp@invalid.invalid> writes:
    On 02/11/2026 00:45, Keith Thompson wrote:
    c186282 <c186282@nnada.net> writes:
    On 11/1/26 05:16, Thomas Koenig wrote:
    [...]
    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    Developed giant coke habit maybe ? ;-)

    Do you have some basis for this? If it's a joke (yes, I see the
    smiley), I fail to see the humor.

    During the 90s and noughties, that was the hallmark of a successful >professional [politician]

    There was a certain scene in _Die Hard_ (1988) which exemplified
    the 80's, particularly on the west coast.

    https://www.youtube.com/watch?v=9Gtgo5myxr8
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 16:51:45 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02, rbowman <bowman@montana.com> wrote:

    NT 4.0 was the last release to be called NT but the numbering scheme was carried on so Windows 11 is NT 10.0 formally. It might have been my
    machine but NT 4.0 usually greeted my with the BSOD on Monday morning.

    Some of our NT customers started reporting intermittent crashes.
    They were caused by a program of mine that used DDEML for inter-program communication. The whole box would die, which we thought was novel
    for an operating system that was supposed to be unkillable (at least
    in comparison with 95/98). I never did find a way to make DDEML run
    reliably, although I did manage to "improve" my program so that it
    would take down NT immediately rather than intermittently. I think
    I still have it around somewhere, under the name "NTkiller".

    Since DDEML proved unusable for interprocess communication, I tried
    various other methods, from shared memory to WM_COPYDATA messages.
    Eventually I went to sockets, where I happily am today. (I love
    being able to test my programs with telnet.)

    2000 was an improvement.

    IMHO Windows' usability peaked somewhere between 2000 and XP,
    and has been going downhill ever since.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 16:51:47 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:

    On 2026-11-02 07:28, c186282 wrote:
    [...]

    -a WOULD love one or two of those big black IBM
    -a mainframe units. Not sure what I'd DO with
    -a them, but they'd be SO cool !

    :-)

    There's a couple hardware types I'd have liked to have -
    and I'd also not know what to do with them but to wallow
    in memories.

    I know what you mean. I don't think I'll ever actually
    use that pair of tape drives I have sitting in the hangar -
    but they're a good conversation piece.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 17:01:24 2026
    From Newsgroup: comp.unix.shell

    According to c186282 <c186282@nnada.net>:
    On 11/1/26 21:16, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    Umm ... NOT so unusual for the times :-)

    Gotta wonder. Big powerful cutting-edge corp
    with good history suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened. The world of microprocessors
    was different from the world of minicomputers, DEC's management never figured that out,
    and its board of directors didn't either.

    I can believe "board of directors" ... but not
    so much the hands-on people at DEC. ...

    Gordon Bell wrote this afterword for the "DEC is Dead" book which explains it well.

    https://gordonbell.azurewebsites.net/CGB%20Files/DEC_Is_Dead_Bell_Appendix_Schein_Book.pdf

    One guy's opinions, probably had a grudge. As usual,
    it's gonna be more complicated, subtle, than that.

    Did you read it? He agrees with what you said. The staff was fantastic, the upper management and board failed. I presume you know who he was, not just some random guy.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 09:35:06 2026
    From Newsgroup: comp.unix.shell

    On Sun, 1 Nov 2026 19:13:45 -0000 (UTC)
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    Daddy built it, daddy trashed it (Ken Olsen, he was responsible
    for both).

    If you talk to the staff who worked under him, you wonrCOt find anybody
    with a bad word to say about him. He looked after his people well.

    But, he was very much a Unix-hater, describing it as rCLsnake oilrCY at
    one point.

    After he was ousted, the asset-strippers took charge.
    Yeah, the impression I've gotten is that Olsen was less the kind of Bad Management that drove e.g. Commodore into the ground and more just the
    type who made a couple critical misjudgements about where the industry
    was headed that ultimately doomed them. He was also uninterested in the microcomputer market, as most of the Big Players were at the time, but
    DEC was even later to that than IBM, lacked the cachet with non-techie Management that they had.
    And on top of that, the Rainbow was a dud: more expensive than the IBM
    PC for similar specs with only somewhat more flexible graphics and CP/M compatibility as its advantages. The Professional at least offered one
    of DEC's own architecture, but it was over *twice* the price of the PC.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 19:41:04 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 11:13:35 +0000, The Natural Philosopher wrote:

    The rise of LSI in the 70s made minicomputers possible. The rise of mass produced microprocessors in the 1980s made them irrelevant.

    https://en.wikipedia.org/wiki/IBM_PALM_processor

    I've posted it before but the PALM was IBM's last shot at LSIs for low end business systems. The 5120 successor, the System/23 used the Intel 8085.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 19:48:26 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 20:02:01 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    That's probably true, but I'll point out that not all /businesses/ are
    at the enterprise level. Lots and lots of small to medium businesses
    had DOS, then Windows machines in the 90s.

    For that matter many small businesses used CP/M. The Z-80 Soft Card came
    about because of the lack of business software for the Apple II. Slip in
    the card, run CP/M and you were all set.

    There was a used book store in Tucson, iirc, that was still using a
    carefully preserved KayPro in the mid-90s. When I asked him about it his classic reply was 'It does what I need it to do.'

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 19:56:30 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 20:03:46 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    And now people are dreaming NVidia will disappear, the way of DEC. Well maybe it /will/ be sold to HP?

    After all, gamers want their affordable graphics cards back.

    A viable alternative to CUDA will be needed first.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 20:10:25 2026
    From Newsgroup: comp.unix.shell

    On Mon, 02 Nov 2026 16:51:45 GMT, Charlie Gibbs wrote:

    Since DDEML proved unusable for interprocess communication, I tried
    various other methods, from shared memory to WM_COPYDATA messages.
    Eventually I went to sockets, where I happily am today. (I love being
    able to test my programs with telnet.)

    We used shared memory and message queues but that was with the NutCracker runtime that provided POSIX capabilities on Windows.

    At one point I looked at MSMQ but it was heavy compared to POSIX. I've
    played around with MQTT and it reminds me of the MS version.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 20:27:24 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 09:35:06 -0800, John Ames wrote:

    And on top of that, the Rainbow was a dud: more expensive than the IBM
    PC for similar specs with only somewhat more flexible graphics and CP/M compatibility as its advantages. The Professional at least offered one
    of DEC's own architecture, but it was over *twice* the price of the PC.

    It wasn't fatal but IBM's RS/6000 had the same problem. The Y2K patches
    were only for newer systems. Our clients looked at the cost of replacing
    their existing machines and switched to PCs. Windows 2000 Server came at
    just the right time.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 23:27:13 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01 20:40, Charlie Gibbs wrote:
    On 2026-10-31, Nuno Silva <nunojsilva@invalid.invalid> wrote:

    On 2026-10-31, Carlos E. R. wrote:

    On 2026-10-30 20:24, Charlie Gibbs wrote:

    On 2026-10-30, c186282 <c186282@nnada.net> wrote:


    More VOLUME of docs these days ... but "As Good" ???

    Hardly. Most manuals back in the day had a section titled
    "Theory of Operation". I really miss that.

    Talking of manuals, I find large man pages very difficult to use,
    specially when you need something specific. No clickable table of
    content, no clickable index. Info pages are somewhat better.

    Isn't that more about the viewer using to read the manual pages, than a
    flaw of the online manual in itself?

    At least the man command can search a man page for a text string.
    It's not perfect, but it's better than nothing.


    If you know the string to search for, and it doesn't happen a hundred times.

    For instance, in openSUSE the search is not case sensitive, so looking
    for -l can find -L first. And of course, finds anywhere where -l or -L
    is mentioned in the text, dozen of times.

    For example, the "man zypper" page (specific to *suse systems) has many sections, but there is not a table of contents at the start listing the section so that we know what section to search for.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 23:32:48 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01 17:50, Janis Papanagnou wrote:
    On 2026-11-01 12:59, Carlos E. R. wrote:
    On 2026-10-31 22:11, Janis Papanagnou wrote:
    On 2026-10-31 19:56, Carlos E. R. wrote:
    On 2026-10-31 16:57, Janis Papanagnou wrote:
    On 2026-10-31 11:40, Carlos E. R. wrote:

    Talking of manuals, I find large man pages very difficult to use, >>>>>> specially when you need something specific. No clickable table of >>>>>> content, no clickable index. Info pages are somewhat better.

    I agree with you on the _horrendous large_ 'man' "pages".
    They shouldn't replace exhaustive and thorough documentation, IMO.
    But worse I think are the ("maneuverable") 'info' pages.
    Or the habit of some "Unixes" to have no man-page information but
    only a stub with the hint to look into the (IMO horrendous) 'info'
    pages. (I'm aware that some certainly prefer them; how else would
    their proliferation be otherwise explainable.)

    Concerning "clickable" information generally, mind the time when
    man-pages were introduced!

    Yes, I understand that. Isn't time we get something better?

    But technically we have already "clickable" documents; with HTML for
    example.

    Yes, and some tools use that. But then, a command like "apropos" does
    not find that page.

    Frankly, I don't know the installation process of my Linux distro in
    detail, but I can say that when I add a new tool-binary I instantly
    also have the man page accessible, and I find the respective infos
    through 'apropos' as well. I don't see why there would be a principal hindrance to do that for other information sources as well.



    (Although it should still be available in one page, and ideally also
    searchable by regexps in easy ways. (As opposed to click on a search
    icon, move the mouse to a new sub-window, (optionally) click another
    time in that window to "activate" it for input, type in only a fixed
    non-regexp text (often without possibility to distinguish caps, or,
    if you're lucky, only with an extra click in some control-box), and
    hit enter (if you're lucky) or have to again move the mouse to click
    on some Okay button.) - I certainly hate to have no '/search-pattern'
    or '<Ctrl-F>search-pattern' available; with emphasis on "pattern".)

    Personally I typically want (at least) three levels of information.
    Terse usage information, complete interface description, and thorough
    explanations of all details in case of the more complex tools.


    And an examples section. How to do this or that.

    This is often useful. For powerful large tools this might exceed
    what one likes in a man-page, though, and would just contribute
    to making the man-page "unreadable" due to its length. Here again
    I think that the type of the examples is the discriminating info;
    the man-page should certainly contain the technical options and
    examples how to call the tool with those, but (having tools like
    Imagemagick in mind) not the functional usage examples that would
    better be placed in a tutorial type of documentation.

    Sometimes a tool has a small man page, then a large structured document
    in some other format.



    Mostly we (now) have all that information; if only through the Web.
    (But often inconsistent or even unreliable.)

    Should we have everything just in one (clickable) format like HTML?
    I don't think so. Should we have all the spread existing information
    rewritten in some other format? Well, who would do that job?

    What I (also) criticize is that we don't have a consistent level of
    information with some newer Linux platforms. I wished for the "second
    level" of information that the man page format would have been kept/
    maintained instead of trying to deprive that format in favor of the
    'info' format.

    Well, I find "info date" (for me "pinfo date") better for finding the
    information than "man date". Or "pinfo gcc".

    One problem I have with 'info' is that I see only a paragraph of
    a subsection of a section of the described thing. I certainly want
    to see more context! I also like to have the typical chapters that
    describe the tools' _interfaces_ (the name with terse description,
    the usage synopsis, a description, the list of options, returned
    status codes, files that affect the tool in some way, example uses,
    and know bugs, for example).

    The 'date' manual you gave as example is certainly not one of the pathologically huge man-pages (with its 200 lines, and most of it
    is anyway just a table of the format specifiers).

    Janis

    [...]
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 23:35:43 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:
    On Sun, 1 Nov 2026 13:07:09 +0100, Carlos E. R. wrote:

    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:

    Tip: if you prefer another form, like PDF, itrCOs quite easy to
    generate that from any man page.

    PDF is fine, but not if the source is a man page, because there are
    no cross references that you can click or tap ...

    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.


    ... ditto table of contents and index.

    Yeah, theyrCyre not (normally) supposed to be long enough to need that
    ...
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 00:08:41 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02 12:22, The Natural Philosopher wrote:
    On 02/11/2026 08:41, Janis Papanagnou wrote:
    On 2026-11-02 07:28, c186282 wrote:
    [...]

    -a-a WOULD love one or two of those big black IBM
    -a-a mainframe units. Not sure what I'd DO with
    -a-a them, but they'd be SO cool !

    :-)

    There's a couple hardware types I'd have liked to have -
    and I'd also not know what to do with them but to wallow
    in memories.

    -a-a Anyway they do
    -a-a have plenty of customers - govt/uni and big
    -a-a industry. Sometimes you NEED a 'mainframe'.

    Hmm.. - "need" - really?

    During the 1990's we switched our big telcos from mainframes
    to Unix servers. The huge sports halls where the mainframes
    had been running were almost empty then. It was just more
    economic to run Unix servers (mainframe support was costly,
    as was just running them), also more ecologic (though I'm
    not sure that this mattered that much in practice, but costs
    of electricity might have been an issue), and the much less
    required physical space as said. Basically all cost factors.

    Also computing centers switched. Our LRZ, formerly running
    a CDC 175, is meanwhile running various Unix clusters for
    "super computing". Our university also said goodbye to its
    TR440 and is providing mainly Linux systems to its students
    for the scientific oriented departments.

    Yes. The transition from mainframe, to Unix clusters and then to blade servers shrunk machine rooms to almost nothing, amnd high speed internet moved them to cloud centres

    The only "need" for a mainframe I observed in some financial
    business area, where they were still running their legacy
    software on mainframes obviously with "no chance" to migrate,
    or not wanting to take the risk and cost (as long as the old
    machinery is doing its task). But it's also difficult to get
    spares, and to find people who can and are willing to operate
    them. (But that information is now a bit dated and things may
    have meanwhile changed even in that business area.)

    That's not quite true.

    What specifically are you referring to here?
    That I observed mainframes still in use in commercial contexts?
    Or my speculation that this might meanwhile have changed?
    Or that the reason for not having done a change was something else?

    I've worked in several business areas were mainframes had been used.
    * The computing centers I was aware of changed their architectures
    from mainframe architectures to clusters.
    * The telcos down-scaled the [amount of] metal, yet increased their
    throughput by switching away from mainframes. They made the change
    because they also needed a lot contemporary new functions supported
    and it was far too costly and much more effort to do that on legacy
    mainframe hardware.
    * The business area I worked in where there were still running some
    mainframes did so primarily because of the mentioned reasons. That
    was 20 years ago, so that's the reason why I said that things "may"
    have meanwhile changed. If they need to runs (similar to the telcos)
    significant amounts of new functions they have to do the calculation
    whether it pays to do that on the old systems. And they have to take
    into consideration whether they have (or can find) programmers for
    old legacy languages as far as the legacy software is concerned; two
    decades ago we didn't find any COBOL programmers for those tasks and
    I'd expect that the situation got even worse meanwhile.
    * Most (all?) internet providers I've heard of aren't using mainframes
    but built their systems architecture based on (often Linux-)clusters.

    There must be reasons to change a running mainframe system. As said,
    such a transition process can be risky and is costly (without instant
    gain of any new functions). The reasons I've heard from the financial
    sectors, i.e. not to switch, were exactly those.

    I'm also a bit astonished about your mention of using mainframes for
    efficient I/O. Networking clusters appear to me to be much better able
    than a single mainframe instance. The older mainframe architectures we
    used also had a lot of peripheral processors to specifically handle
    the I/O.

    (But of course I can, as I did, just report about the (certainly non-
    singular) cases I was involved in or heard from reliable sources.)

    Janis

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 00:20:20 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02 14:57, The Natural Philosopher wrote:
    On 02/11/2026 12:11, Johann 'Myrkraverk' Oskarsson wrote:
    So if people think mainframes are somehow /obsolete/, it's because they
    are extrapolating from their own personal experiences and never look un-
    der the hood of the commercial world.

    Not sure to what "people" you are referring to. - My own reports at
    least were from quite a couple different and major commercial areas
    where I had some insights in; computing centers, telecommunications
    sector, insurances financial sector, governmental financial sector.

    But since 'Myrkraverk' is in my killfile don't bother replying to me.

    [...]

    (Just replying to the quoted text, not yours.)

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 23:22:41 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 23:35:43 +0100, Carlos E. R. wrote:

    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:

    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    IrCOm not sure what you mean by rCLman as sourcerCY, if not the troff/groff markup. That *is* the required source form for man pages, after all.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 00:26:05 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02 23:32, Carlos E. R. wrote:

    Sometimes a tool has a small man page, then a large structured document
    in some other format.

    I think that's exactly how it should be.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 02:57:27 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 00:26, Janis Papanagnou wrote:
    On 2026-11-02 23:32, Carlos E. R. wrote:

    Sometimes a tool has a small man page, then a large structured
    document in some other format.

    I think that's exactly how it should be.

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable as
    a modern computer in the XXI can do, not the equivalent of printed paper.

    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your text.
    Seems too difficult to replicate. Not even Lazarus has it.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 03:02:07 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 00:22, Lawrence DrCOOliveiro wrote:
    On Mon, 2 Nov 2026 23:35:43 +0100, Carlos E. R. wrote:

    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:

    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    IrCOm not sure what you mean by rCLman as sourcerCY, if not the troff/groff markup. That *is* the required source form for man pages, after all.

    I have seen documentation PDFs that are just the output of man2pdf.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 21:12:22 2026
    From Newsgroup: comp.unix.shell

    On 11/2/26 18:08, Janis Papanagnou wrote:
    On 2026-11-02 12:22, The Natural Philosopher wrote:
    On 02/11/2026 08:41, Janis Papanagnou wrote:
    On 2026-11-02 07:28, c186282 wrote:
    [...]

    -a-a WOULD love one or two of those big black IBM
    -a-a mainframe units. Not sure what I'd DO with
    -a-a them, but they'd be SO cool !

    :-)

    There's a couple hardware types I'd have liked to have -
    and I'd also not know what to do with them but to wallow
    in memories.

    -a-a Anyway they do
    -a-a have plenty of customers - govt/uni and big
    -a-a industry. Sometimes you NEED a 'mainframe'.

    Hmm.. - "need" - really?

    During the 1990's we switched our big telcos from mainframes
    to Unix servers. The huge sports halls where the mainframes
    had been running were almost empty then. It was just more
    economic to run Unix servers (mainframe support was costly,
    as was just running them), also more ecologic (though I'm
    not sure that this mattered that much in practice, but costs
    of electricity might have been an issue), and the much less
    required physical space as said. Basically all cost factors.

    Also computing centers switched. Our LRZ, formerly running
    a CDC 175, is meanwhile running various Unix clusters for
    "super computing". Our university also said goodbye to its
    TR440 and is providing mainly Linux systems to its students
    for the scientific oriented departments.

    Yes. The transition from mainframe, to Unix clusters and then to blade
    servers shrunk machine rooms to almost nothing, amnd high speed
    internet moved them to cloud centres

    The only "need" for a mainframe I observed in some financial
    business area, where they were still running their legacy
    software on mainframes obviously with "no chance" to migrate,
    or not wanting to take the risk and cost (as long as the old
    machinery is doing its task). But it's also difficult to get
    spares, and to find people who can and are willing to operate
    them. (But that information is now a bit dated and things may
    have meanwhile changed even in that business area.)

    That's not quite true.

    What specifically are you referring to here?
    That I observed mainframes still in use in commercial contexts?
    Or my speculation that this might meanwhile have changed?
    Or that the reason for not having done a change was something else?

    I've worked in several business areas were mainframes had been used.
    * The computing centers I was aware of changed their architectures
    -a from mainframe architectures to clusters.
    * The telcos down-scaled the [amount of] metal, yet increased their
    -a throughput by switching away from mainframes. They made the change
    -a because they also needed a lot contemporary new functions supported
    -a and it was far too costly and much more effort to do that on legacy
    -a mainframe hardware.
    * The business area I worked in where there were still running some
    -a mainframes did so primarily because of the mentioned reasons. That
    -a was 20 years ago, so that's the reason why I said that things "may"
    -a have meanwhile changed. If they need to runs (similar to the telcos)
    -a significant amounts of new functions they have to do the calculation
    -a whether it pays to do that on the old systems. And they have to take
    -a into consideration whether they have (or can find) programmers for
    -a old legacy languages as far as the legacy software is concerned; two
    -a decades ago we didn't find any COBOL programmers for those tasks and
    -a I'd expect that the situation got even worse meanwhile.
    * Most (all?) internet providers I've heard of aren't using mainframes
    -a but built their systems architecture based on (often Linux-)clusters.

    There must be reasons to change a running mainframe system. As said,
    such a transition process can be risky and is costly (without instant
    gain of any new functions). The reasons I've heard from the financial sectors, i.e. not to switch, were exactly those.

    I'm also a bit astonished about your mention of using mainframes for efficient I/O. Networking clusters appear to me to be much better able
    than a single mainframe instance. The older mainframe architectures we
    used also had a lot of peripheral processors to specifically handle
    the I/O.

    (But of course I can, as I did, just report about the (certainly non- singular) cases I was involved in or heard from reliable sources.)

    Janis

    [...]


    "Mainframes" do still have their places - major
    computing/comm performance. Govt, science, big
    international biz.

    This may change sooner or later - all replaced
    by 'cluster' and "Global AI".

    But not yet.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 02:17:15 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 02:57:27 +0100, Carlos E. R. wrote:
    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your text.
    Seems too difficult to replicate. Not even Lazarus has it.

    I happen to have a html document open in VS Code at the moment. If the
    mouse hovers over 'charset' it pops up a dialog:

    "This attribute declares the page's character encoding. It must contain a standard IANA MIME name for character encodings. Although the standard
    doesn't request a specific encoding, it suggests:

    Authors are encouraged to use UTF-8.
    Authors should not use ASCII-incompatible encodings to avoid security
    risk: browsers not supporting them may interpret harmful content as HTML.
    This happens with the JIS_C6226-1983, JIS_X0212-1990, HZ-GB-2312, JOHAB,
    the ISO-2022 family and the EBCDIC family.
    Note: ASCII-incompatible encodings are those that don't map the 8-bit code points 0x20 to 0x7E to the 0x0020 to 0x007E Unicode code points)

    Authors must not use CESU-8, UTF-7, BOCU-1 and/or SCSU as cross-site
    scripting attacks with these encodings have been demonstrated.
    Authors should not use UTF-32 because not all HTML5 encoding algorithms
    can distinguish it from UTF-16."

    html itself is shorter

    "The html element represents the root of an HTML document.

    N++ Widely available across major browsers (Baseline since 2015)

    MDN Reference"

    'MDN Reference' is a link that will open https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/html

    in the browser. For C code, hovering over 'strcmp' pops

    "int strcmp(const char *__s1, const char *__s2)
    Compare S1 and S2."

    That isn't as detailed but it can be helpful. After all these years I sometimes forget which end of the parameter list the FILE* or fd goes on
    for fopen() versus open(). I suppose in the mists of time there was some reason why they are inconsistent.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 21:18:40 2026
    From Newsgroup: comp.unix.shell

    On 11/2/26 18:22, Lawrence DrCOOliveiro wrote:
    On Mon, 2 Nov 2026 23:35:43 +0100, Carlos E. R. wrote:

    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:

    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    IrCOm not sure what you mean by rCLman as sourcerCY, if not the troff/groff markup. That *is* the required source form for man pages, after all.

    On more than one box I've disabled man-db.

    The WAY man pages are written tends to be VERY
    unhelpful. Often NO examples/templates even.
    "You need TWO spaces after <whatever> ?" Won't
    see any good working examples in the man pages.
    Expected to work out every detail yourself from
    the man abstractions - takes ten times as long.

    Sorry, not into 'suffering' - no black leather
    and whips.

    MUCH better docs elsewhere, often with pictures
    and/or videos.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 02:42:44 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:

    I'm also a bit astonished about your mention of using mainframes for efficient I/O. Networking clusters appear to me to be much better able
    than a single mainframe instance. The older mainframe architectures we
    used also had a lot of peripheral processors to specifically handle
    the I/O.

    True, but back in 1970 there wasn't a lot of networking happening,
    largely because people hadn't really figured it out yet. Mainframe
    I/O capacity was prodigious at the time - early minis could hardly
    manage the megabyte-per-second speeds that mainframes dealt with
    routinely. Consider that while the mini people were making a big
    thing of DMA, the term was unheard of in the mainframe world -
    mainframers just took it for granted.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 02:49:06 2026
    From Newsgroup: comp.unix.shell

    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 02:49:50 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03, Carlos E. R. <robin_listas@es.invalid> wrote:

    On 2026-11-03 00:26, Janis Papanagnou wrote:

    On 2026-11-02 23:32, Carlos E. R. wrote:

    Sometimes a tool has a small man page, then a large structured
    document in some other format.

    I think that's exactly how it should be.

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable as
    a modern computer in the XXI can do, not the equivalent of printed paper.

    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your text.
    Seems too difficult to replicate. Not even Lazarus has it.

    Yes, a lot of people (remember Ted Nelson?) have had such a vision. Unfortunately, the modern corporate fascist state has buried it.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 02:50:55 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 03:02:07 +0100, Carlos E. R. wrote:

    I have seen documentation PDFs that are just the output of man2pdf.

    Not sure why you need a separate package/command, when the usual rCLmanrCY command is quite capable of doing that itself.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 02:53:45 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell on Mon Nov 2 22:22:07 2026
    From Newsgroup: comp.unix.shell

    On 11/2/26 20:57, Carlos E. R. wrote:
    On 2026-11-03 00:26, Janis Papanagnou wrote:
    On 2026-11-02 23:32, Carlos E. R. wrote:

    Sometimes a tool has a small man page, then a large structured
    document in some other format.

    I think that's exactly how it should be.

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable as
    a modern computer in the XXI can do, not the equivalent of printed paper.

    I generally agree about how it SHOULD be ... but
    we're not seeing it and thus I don't think we *will*.

    Man pages are a 'specialty' kind of doc.

    Do NOT find them very useful these days.

    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your text.
    Seems too difficult to replicate. Not even Lazarus has it.

    Borland was ahead of its time. Alas few others
    kept up. Phillipe Kahn was a god !

    Ah, Turbo Pascal ... bought it CHEAP, with a
    sent-in paper check initially. Completely
    CHANGED the development experience ! Do
    have a few of the old multi-pass M$/IBM
    compilers in a DOS VM somewhere, even
    fuck with 'em once in awhile for fun.
    But for DOING anything - no no no !!!

    Still strongly pref the Gen-3 development
    IDEs over anything allegedly "better".
    Straight-up, no bullshit, everything you
    need to get it done fast and right.

    Apparently I'm on of the few who still write
    Pascal. Love it ! The Lazarus/FPC environment
    suits me just FINE. Proto in Python, then, if
    desired, re-write in Pascal - tighter, prettier,
    much faster.

    At the boss's request, did an app to do
    a "slide show" (plus video options) to
    put on a big screen in the front office.
    Sorry, the 'mainstream' shit like LibreOffice
    didn't work worth a damn.

    Pi4, sticky-taped to the big screen.

    Proto'ed in Python in two days, then
    re-did the whole thing in Laz/FPC in
    another two days. Worked great. It'd
    pull off our network - AND remember what
    was on the network and play it if you
    took the display to a conference. Mere
    DAYS, Gen3 IDE.

    There IS a Linux distro kinda dedicated to
    this sort of use, but can't remember the name.
    When in doubt, write it yourself.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 22:29:52 2026
    From Newsgroup: comp.unix.shell

    On 11/2/26 21:42, Charlie Gibbs wrote:
    On 2026-11-02, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:

    I'm also a bit astonished about your mention of using mainframes for
    efficient I/O. Networking clusters appear to me to be much better able
    than a single mainframe instance. The older mainframe architectures we
    used also had a lot of peripheral processors to specifically handle
    the I/O.

    True, but back in 1970 there wasn't a lot of networking happening,
    largely because people hadn't really figured it out yet. Mainframe
    I/O capacity was prodigious at the time - early minis could hardly
    manage the megabyte-per-second speeds that mainframes dealt with
    routinely. Consider that while the mini people were making a big
    thing of DMA, the term was unheard of in the mainframe world -
    mainframers just took it for granted.

    OLD mainframes were, well, OLD. Modern versions
    have MANY I/O/net ports. E-Commerce is assumed.
    10k user connections at once, no problems.

    Things HAVE moved on since 1961 after all ...

    The age of the "mainframe" may be coming to an
    end alas. 'Cluster'/AI solutions are going to
    replace them for most uses. However science/govt
    still have uses for big ultra-powerful boxes
    for awhile anyway. SOME advantage in keeping
    access 'local' too - as opposed to spread all
    over the highly-vulnerable net.

    Oh well, maybe I can buy one of those big black
    IBM units for really cheap in a few years ?
    CANDY !!!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 2 22:53:44 2026
    From Newsgroup: comp.unix.shell

    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    Yep ! Even the old mainframes were "smart" - lots
    of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    System interrupts PER-KEYSTROKE ??? Horrible !

    The "minis" were pretty good all in all, had a
    definite 'place'. Lots made. Had some experience
    with the TI-990 minis. Super-funky hardware-
    based multi-user scheme with RAM-based registers.
    Hey, good at the time !

    I guess you COULD call the PDP-11 a "mini", but
    imho it didn't have quite the "feel". More like
    a cut-down mainframe. Good peripheral bus though,
    you could plug in all kinds of goodies.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 04:44:26 2026
    From Newsgroup: comp.unix.shell

    On Tue, 03 Nov 2026 02:53:45 GMT, Charlie Gibbs wrote:

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.

    ThatrCOs not the dichotomy. The dichotomy was that mainframes were
    optimized for throughput at the expense of latency, while
    minicomputers concentrated on minimizing latency to maximize
    interactive responsiveness at the expense of throughput.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 04:49:32 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 02:57:27 +0100, Carlos E. R. wrote:

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable
    as a modern computer in the XXI can do, not the equivalent of
    printed paper.

    Given yourCOre basically talking about a search through /usr/share/doc,
    that isnrCOt actually that hard to do.

    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your
    text. Seems too difficult to replicate. Not even Lazarus has it.

    Help on what, though? Just programming APIs? Or other system stuff as
    well?

    MS-DOS never had an equivalent to /usr/share/doc. Nor does present-day
    Windows.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 07:10:13 2026
    From Newsgroup: comp.unix.shell

    John Levine <johnl@taugh.com> schrieb:
    According to c186282 <c186282@nnada.net>:
    Umm ... NOT so unusual for the times :-)

    Gotta wonder. Big powerful cutting-edge corp
    with good history suddenly crashes and burns ......

    Sheesh, it's not like it's hard to find out what happened. The world of microprocessors
    was different from the world of minicomputers, DEC's management never figured that out,
    and its board of directors didn't either.

    Gordon Bell wrote this afterword for the "DEC is Dead" book which explains it well.

    https://gordonbell.azurewebsites.net/CGB%20Files/DEC_Is_Dead_Bell_Appendix_Schein_Book.pdf

    Reading "DEC is Dead", one gets the distinct impression that Gordon
    Bell walked on water as a computer architect, but with the benefit
    of hindsight, this was not the case.

    The specifics of the VAX (especially its addressing modes) made
    sure that it would not scale very well towards higher peformance.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 07:15:05 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03, c186282 <c186282@nnada.net> wrote:

    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:

    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous
    controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    Yep ! Even the old mainframes were "smart" - lots
    of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    System interrupts PER-KEYSTROKE ??? Horrible !

    The "minis" were pretty good all in all, had a
    definite 'place'. Lots made. Had some experience
    with the TI-990 minis. Super-funky hardware-
    based multi-user scheme with RAM-based registers.
    Hey, good at the time !

    Mainframes in the day used minis as "front-end processors"
    that offloaded things like keystroke processing from the
    main CPU, which could then concentrate on number crunching.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 07:15:04 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 02:53:45 GMT, Charlie Gibbs wrote:

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.

    ThatrCOs not the dichotomy. The dichotomy was that mainframes were
    optimized for throughput at the expense of latency, while
    minicomputers concentrated on minimizing latency to maximize
    interactive responsiveness at the expense of throughput.

    Pick your metaphor. In the end the trade-offs are the same.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Richard Kettlewell@invalid@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 08:36:10 2026
    From Newsgroup: comp.unix.shell

    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-03 00:26, Janis Papanagnou wrote:
    On 2026-11-02 23:32, Carlos E. R. wrote:
    Sometimes a tool has a small man page, then a large structured
    document in some other format.
    I think that's exactly how it should be.

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable
    as a modern computer in the XXI can do, not the equivalent of printed
    paper.

    ThatrCOs what texinfo was supposed to be, and the output does have tables
    of contents, cross-links, etc; but it has failed to displace man,
    probably for multiple reasons but I expect partly due to the poor
    quality of the tools. (For example, cross-document links donrCOt work
    reliably: they are broken in the Emacs info viewer and /bin/info in
    Debian stable, although they do work better in the HTML renditions on
    gnu.org.)

    In practice the answer to global integration was the web, which
    generally does a much better job of it than locally stored
    documentation.
    --
    https://www.greenend.org.uk/rjk/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Richard Kettlewell@invalid@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 08:40:58 2026
    From Newsgroup: comp.unix.shell

    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:
    On Sun, 1 Nov 2026 13:07:09 +0100, Carlos E. R. wrote:
    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:
    Tip: if you prefer another form, like PDF, itrCOs quite easy to
    generate that from any man page.

    PDF is fine, but not if the source is a man page, because there are
    no cross references that you can click or tap ...
    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    Links work fine in PDFs generated from man page sources. See
    link at the bottom of https://terraraq.uk/junk/ccache.pdf to https://ccache.dev/credits.html for an example.
    --
    https://www.greenend.org.uk/rjk/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Wade@g4ugm@dave.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 09:28:46 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 04:44, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:53:45 GMT, Charlie Gibbs wrote:

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.

    ThatrCOs not the dichotomy. The dichotomy was that mainframes were
    optimized for throughput at the expense of latency, while
    minicomputers concentrated on minimizing latency to maximize
    interactive responsiveness at the expense of throughput.

    I think you misunderstand "mainframes" or at least IBM Mainframes. The Mainframe never "saw" keystrokes, they were handled in the terminal
    controller so there never was any possibility of the dreaded
    "type-behind" one saw on an over-loaded VAX.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as good
    as or better than a mini.

    A good friend rolled out "Office Automation" across a large business.
    For the most senior there was All-In-One but he said that just could not
    be scaled across the enterprise, so they got IBM PROFS or Office Vision.
    Not quite a functional as All-In-One but good response times.

    Dave
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 12:24:21 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 04:22, c186282 wrote:
    On 11/2/26 20:57, Carlos E. R. wrote:
    On 2026-11-03 00:26, Janis Papanagnou wrote:
    On 2026-11-02 23:32, Carlos E. R. wrote:

    Sometimes a tool has a small man page, then a large structured
    document in some other format.

    I think that's exactly how it should be.

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable
    as a modern computer in the XXI can do, not the equivalent of printed
    paper.

    -a I generally agree about how it SHOULD be ... but
    -a we're not seeing it and thus I don't think we *will*.

    -a Man pages are a 'specialty' kind of doc.

    -a Do NOT find them very useful these days.

    It is what we have, but large man pages I find too difficult.


    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your text.
    Seems too difficult to replicate. Not even Lazarus has it.

    -a Borland was ahead of its time. Alas few others
    -a kept up. Phillipe Kahn was a god !

    -a Ah, Turbo Pascal ... bought it CHEAP, with a
    -a sent-in paper check initially. Completely
    -a CHANGED the development experience ! Do
    -a have a few of the old multi-pass M$/IBM
    -a compilers in a DOS VM somewhere, even
    -a fuck with 'em once in awhile for fun.
    -a But for DOING anything - no no no !!!

    -a Still strongly pref the Gen-3 development
    -a IDEs over anything allegedly "better".
    -a Straight-up, no bullshit, everything you
    -a need to get it done fast and right.

    https://www.youtube.com/watch?v=KRbBheQ9oTs
    Pascal: The Language That Dominated Computer Education, Then Borland
    Killed It


    -a Apparently I'm on of the few who still write
    -a Pascal. Love it ! The Lazarus/FPC environment
    -a suits me just FINE. Proto in Python, then, if
    -a desired, re-write in Pascal - tighter, prettier,
    -a much faster.

    I also use Lazarus, simple things nowdays. But if have the itch to
    program something, it is Lazarus or bash script.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 12:28:19 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 05:49, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 02:57:27 +0100, Carlos E. R. wrote:

    I would prefer a properly indexed global system that can find me
    keywords and things across the system, and each document properly
    indexed and with proper tables of contents, all linked and browsable
    as a modern computer in the XXI can do, not the equivalent of
    printed paper.

    Given yourCOre basically talking about a search through /usr/share/doc,
    that isnrCOt actually that hard to do.

    Not a human designed cross index.


    Heck, Borland in the 90's had an IDE with integrated help that could
    find the proper help paragraph by clicking on a keyword in your
    text. Seems too difficult to replicate. Not even Lazarus has it.

    Help on what, though? Just programming APIs? Or other system stuff as
    well?

    Programming api, functions/vars/procedures provided by Borland, language constructs... anything we needed. Contextual help.


    MS-DOS never had an equivalent to /usr/share/doc. Nor does present-day Windows.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 12:28:55 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 03:50, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 03:02:07 +0100, Carlos E. R. wrote:

    I have seen documentation PDFs that are just the output of man2pdf.

    Not sure why you need a separate package/command, when the usual rCLmanrCY command is quite capable of doing that itself.

    And is just as useless.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 12:31:52 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 09:40, Richard Kettlewell wrote:
    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:
    On Sun, 1 Nov 2026 13:07:09 +0100, Carlos E. R. wrote:
    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:
    Tip: if you prefer another form, like PDF, itrCOs quite easy to
    generate that from any man page.

    PDF is fine, but not if the source is a man page, because there are
    no cross references that you can click or tap ...
    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    Links work fine in PDFs generated from man page sources. See
    link at the bottom of https://terraraq.uk/junk/ccache.pdf to https://ccache.dev/credits.html for an example.

    That's not what I mean.

    That's just an URL that is detected and activated.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 12:36:35 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02 07:28, c186282 wrote:
    -a WOULD love one or two of those big black IBM
    -a mainframe units. Not sure what I'd DO with
    -a them, but they'd be SO cool ! Anyway they do
    -a have plenty of customers - govt/uni and big
    -a industry. Sometimes you NEED a 'mainframe'.

    Banks.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 12:45:09 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-02 13:11, Johann 'Myrkraverk' Oskarsson wrote:
    On 11/2/2026 7:22 PM, The Natural Philosopher wrote:
    On 02/11/2026 08:41, Janis Papanagnou wrote:
    On 2026-11-02 07:28, c186282 wrote:


    That's not quite true. First of all old IBM COBOL and RPG is well
    supported on modern -|P based hardware. and second mainframes are still
    in use where enormous numbers of I/O operations are called for.

    "Mainframes remain the invisible backbone of the global economy in the
    21st century, handling 90% of credit card transactions, powering 92 of
    the top 100 banks, and managing 68% of production IT workloads
    globally while accounting for just a fraction of total IT spending."

    Mainframes remain cost effective alternatives for very large scale low
    complexcity transactions



    I've heard -- let's say verbally -- that the relentless transaction pro- cessing done on mainframes is hard to do on different types of machines.

    And what is hard?-a I haven't worked with mainframes, but last time I
    looked into it, POWER was the only CPU with hardware accelerated decimal arithmetic [1].-a This is the kind of computation universities don't do
    as research, so -- based on my stories of academia -- there are none
    there for budding CS doctorates to tinker with.

    So if people think mainframes are somehow /obsolete/, it's because they
    are extrapolating from their own personal experiences and never look un-
    der the hood of the commercial world.

    I know at least one guy working on IBM mainframes, and he tells me they
    are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.



    Best wishes, and happy mainframes!


    [1] I don't have a POWER CPU, and didn't personally verify this.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 11:49:43 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me they
    are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for running legacy systems that people couldn't be bothered to port to new hardware/architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 12:50:51 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 04:53, c186282 wrote:
    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous
    controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    -a Yep ! Even the old mainframes were "smart" - lots
    -a of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    -a System interrupts PER-KEYSTROKE ??? Horrible !

    That is what a PC does.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 13:02:49 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 12:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for running legacy systems that people couldn't be bothered to port to new hardware/ architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    No, it is really high i/o and very large databases. I saw some figures
    once and they were impressive.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Wade@g4ugm@dave.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 13:26:01 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 12:02, Carlos E. R. wrote:
    On 2026-11-03 12:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for
    running legacy systems that people couldn't be bothered to port to new
    hardware/ architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    No, it is really high i/o and very large databases. I saw some figures
    once and they were impressive.


    IBM built a lot of intelligence into the IO subsystem. There are
    multiple IO processors, once known as channels, which move data to and
    from devices. They are controlled by a channel program which can perform multiple IOs so a single IO request can read or write multiple blocks of
    data from a tape or disk to or from different locations in memory with
    the main CPU only getting involved when they are all complete.

    So I don't know if this happens in practice but in theory if you want to
    page out one chunk of store and page in another you can do that with a
    single IO request.

    Just to tweak things a bit further, if you have multiple disks,
    controlled by a single controller, the controller can process multiple
    IO requests. To optimise this it also has Rotational Position Sensing so
    it can optimise the order in which they are processed.

    Modern machines, of course use Fibre to connect the IO devices but back
    in the day all this was connected via Bus and Tag channels which ran at 4Mbytes/sec, so 32Mbits with no contention.

    Oh and for terminal IO the link to the screen runs at 1.5MBits/sec so
    rather faster than any minicomputer link.

    of course this complexity cam at a cost...

    Dave



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 05:28:52 2026
    From Newsgroup: comp.unix.shell

    On 11/2/2026 19:53, c186282 wrote:
    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous
    controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    -a Yep ! Even the old mainframes were "smart" - lots
    -a of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    -a System interrupts PER-KEYSTROKE ??? Horrible !

    -a The "minis" were pretty good all in all, had a
    -a definite 'place'. Lots made. Had some experience
    -a with the TI-990 minis. Super-funky hardware-
    -a based multi-user scheme with RAM-based registers.
    -a Hey, good at the time !

    -a I guess you COULD call the PDP-11 a "mini", but
    -a imho it didn't have quite the "feel". More like
    -a a cut-down mainframe. Good peripheral bus though,
    -a you could plug in all kinds of goodies.

    Oh, most PDP-11's were definitely minis. Consider that the address space
    was 16 bits, i.e. 64 KB. On the 11/45 you could set the MMU to separate instruction fetches into a separate 64KB space from the data
    read/writes, but I never got comfortable with that.

    The 11/70 could do multi-user with a larger physical memory, so it could
    run V6 unix (or the 16-bit BSD version). But nobody should confuse it
    with a mainframe.

    The genius of the mainframe version of transaction processing was that
    the queue of incoming transactions did not have too live in CPU memory
    ... it sat in the memory of the terminals, waiting for a poll that would
    bring it inside. This was in complete contrast to the mini computer
    terminals that were ASYNC TTY, requiring the CPU to catch the character
    when the UART interrupted, and the host mini would then decide whether
    the character should be echoed back or not.

    By the time of VMS, there was a new paradigm, where you could push the pre-processing out to the terminal cluster: The TTY device in the OS had
    mode bitmasks, specifying for each character whether it should be echoed
    and whether it should generate a read completion interrupt. Unix got a
    similar set of modes controlled with the stty command and its associated
    ioctl system calls, but I don't think I have ever seen these succesfully
    be used to put the TTY pre-processing in a remote front-end controller,
    like VMS could.

    I know a bit about this, because I have written TTY drivers for Univac
    EXEC-8, VMS, 4BSD. Lots of fun, and a source of pride for a young
    programmer.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 14:28:51 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 11:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for running legacy systems that people couldn't be bothered to port to new hardware/architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    You would guess wrong then
    Think about the number of people a second swiping their cards or
    applePay wotsits across terminals...
    Each transaction is trivial: post a debit, with details of where the
    debt is incurred, and check against customer balance and overdraft
    limits, and issue - or deny - authorisation,
    But you are talking millions per second. All of which demand instant
    response. All of which access centralised databases that cant be split
    across machines
    --
    "And if the blind lead the blind, both shall fall into the ditch".

    Gospel of St. Mathew 15:14


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 14:29:46 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 12:02, Carlos E. R. wrote:
    On 2026-11-03 12:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for
    running legacy systems that people couldn't be bothered to port to new
    hardware/ architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    No, it is really high i/o and very large databases. I saw some figures
    once and they were impressive.

    +1

    TTT Trillions of Trivial Transactions ...
    --
    rCLPuritanism: The haunting fear that someone, somewhere, may be happy.rCY

    H.L. Mencken, A Mencken Chrestomathy

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 14:31:24 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 11:50, Carlos E. R. wrote:
    On 2026-11-03 04:53, c186282 wrote:
    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous >>> controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    -a-a Yep ! Even the old mainframes were "smart" - lots
    -a-a of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    -a-a System interrupts PER-KEYSTROKE ??? Horrible !

    That is what a PC does.

    Indeed it is

    Maybe CP/M did not, but IIRC DOS always did.
    --
    There is something fascinating about science. One gets such wholesale
    returns of conjecture out of such a trifling investment of fact.

    Mark Twain

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 07:31:42 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 04:50, Carlos E. R. wrote:
    On 2026-11-03 04:53, c186282 wrote:
    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous >>> controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    -a-a Yep ! Even the old mainframes were "smart" - lots
    -a-a of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    -a-a System interrupts PER-KEYSTROKE ??? Horrible !

    That is what a PC does.


    But a PC is, by definition, "personal", so this nonsense is not
    affecting anyone else.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 07:35:30 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 06:26, David Wade wrote:
    On 03/11/2026 12:02, Carlos E. R. wrote:
    On 2026-11-03 12:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for
    running legacy systems that people couldn't be bothered to port to
    new hardware/ architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    No, it is really high i/o and very large databases. I saw some figures
    once and they were impressive.


    IBM built a lot of intelligence into the IO subsystem. There are
    multiple IO processors, once known as channels, which move data to and
    from devices. They are controlled by a channel program which can perform multiple IOs so a single IO request can read or write multiple blocks of data from a tape or disk to or from different locations in memory with
    the main CPU only getting involved when they are all complete.

    So I don't know if this happens in practice but in theory if you want to page out one chunk of store and page in another you can do that with a single IO request.

    Lynne Wheeler could probably comment on this better than I, but I think
    that for years now (decades?) paging subsystems have been optimized to
    handle several operations in one I/O request.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 15:13:28 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> writes:
    On 11/2/26 18:08, Janis Papanagnou wrote:
    On 2026-11-02 12:22, The Natural Philosopher wrote:


    I'm also a bit astonished about your mention of using mainframes for
    efficient I/O. Networking clusters appear to me to be much better able
    than a single mainframe instance. The older mainframe architectures we
    used also had a lot of peripheral processors to specifically handle
    the I/O.

    (But of course I can, as I did, just report about the (certainly non-
    singular) cases I was involved in or heard from reliable sources.)

    Janis

    [...]


    "Mainframes" do still have their places - major
    computing/comm performance. Govt, science, big
    international biz.

    Actually, the numbers decline every year. The vast
    majority are legacy installations (particularly for the
    Burroughs/Univac/Unisys mainframes) and there are very
    few, if any, new customers adopting mainframes of any
    flavor.


    This may change sooner or later - all replaced
    by 'cluster' and "Global AI".

    Clusters were two decades ago. Today it is all
    virtualization, particularly in the cloud.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 15:18:15 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous >controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    True for IBM systems. Burroughs systems had/have intelligent I/O controllers to offload I/O handling from both the CPUs and the I/O channels.


    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    No, as a former mainframe designer, there was no horror involved. Our
    customers preferred to offload such workloads to dedicated front-end controllers (in our case, one of which was built around an HP-2000).

    Recalling at the time that interactive used was typically form-based
    (e.g. airline reservation systems, bank teller terminals, etc) and
    the block mode terminals of the day typically transferred the contents
    of the screen (or the form fields on the screen) in a single transmission.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 18:06:33 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 14:26, David Wade wrote:
    On 03/11/2026 12:02, Carlos E. R. wrote:
    On 2026-11-03 12:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for
    running legacy systems that people couldn't be bothered to port to
    new hardware/ architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    No, it is really high i/o and very large databases. I saw some figures
    once and they were impressive.


    IBM built a lot of intelligence into the IO subsystem. There are
    multiple IO processors, once known as channels, which move data to and
    from devices. They are controlled by a channel program which can perform multiple IOs so a single IO request can read or write multiple blocks of data from a tape or disk to or from different locations in memory with
    the main CPU only getting involved when they are all complete.

    So I don't know if this happens in practice but in theory if you want to page out one chunk of store and page in another you can do that with a single IO request.

    Just to tweak things a bit further, if you have multiple disks,
    controlled by a single controller, the controller can process multiple
    IO requests. To optimise this it also has Rotational Position Sensing so
    it can optimise the order in which they are processed.

    Modern machines, of course use Fibre to connect the IO devices but back
    in the day all this was connected via Bus and Tag channels which ran at 4Mbytes/sec, so 32Mbits with no contention.

    Oh and for terminal IO the link to the screen runs at 1.5MBits/sec so
    rather faster than any minicomputer link.

    of course this complexity cam at a cost...

    And extra cost by ensuring it is reliable.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 02:13:14 2026
    From Newsgroup: comp.unix.shell

    On 11/3/2026 10:31 PM, Peter Flass wrote:
    On 11/3/26 04:50, Carlos E. R. wrote:
    On 2026-11-03 04:53, c186282 wrote:
    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous >>>> controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    -a-a Yep ! Even the old mainframes were "smart" - lots
    -a-a of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    -a-a System interrupts PER-KEYSTROKE ??? Horrible !

    That is what a PC does.


    But a PC is, by definition, "personal", so this nonsense is not
    affecting anyone else.

    And it's not nonsense when you want to minimize latency, such as in com- petitive games. I have a /gaming tower/, with -- alas empty -- PS/2
    plug. And I don't know where to buy the splitter cable to connect both
    a mouse and a keyboard.

    Gamers -- at least some of them -- still rant about USB latency.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 19:16:20 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 15:31, The Natural Philosopher wrote:
    On 03/11/2026 11:50, Carlos E. R. wrote:
    On 2026-11-03 04:53, c186282 wrote:
    On 11/2/26 21:49, Lawrence DrCOOliveiro wrote:
    On Tue, 03 Nov 2026 02:42:44 GMT, Charlie Gibbs wrote:

    Consider that while the mini people were making a big thing of DMA,
    the term was unheard of in the mainframe world - mainframers just
    took it for granted.

    The mainframe world had rCLchannelsrCY, which were practically autonomous >>>> controllers with their own ability to obey complex sequences of
    program instructions while the CPU was busy doing application stuff.

    -a-a Yep ! Even the old mainframes were "smart" - lots
    -a-a of optimizations that only later migrated down.

    The mini people were spending a lot of time building systems which
    could efficiently respond to a CPU interrupt on every user keystroke.
    Even the thought of that would have filled mainframers with horror.

    -a-a System interrupts PER-KEYSTROKE ??? Horrible !

    That is what a PC does.

    Indeed it is

    Maybe CP/M did not, but IIRC DOS always did.


    *Something* has to fetch the keystroke from the UART and put it
    in memory. PCs do not have dedicated auxiliary processors, so
    the CPU has to do the job. Not a big deal, really. On occasion,
    I've even let the CPU take over the job of the UART. (Ten
    interrupts per keystroke!)

    Mainframe channels were computers too, and collecting keystrokes
    or punched card bytes was delegated to those.

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Richard Kettlewell@invalid@invalid.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 18:32:07 2026
    From Newsgroup: comp.unix.shell

    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-03 09:40, Richard Kettlewell wrote:
    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:
    On Sun, 1 Nov 2026 13:07:09 +0100, Carlos E. R. wrote:
    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:
    Tip: if you prefer another form, like PDF, itrCOs quite easy to
    generate that from any man page.

    PDF is fine, but not if the source is a man page, because there are
    no cross references that you can click or tap ...
    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    Links work fine in PDFs generated from man page sources. See
    link at the bottom of https://terraraq.uk/junk/ccache.pdf to
    https://ccache.dev/credits.html for an example.

    That's not what I mean.

    Please could you explain clearly what you do mean, then, being specific
    about what exactly file formats yourCOre talking about as inputs, what
    tools yourCOre talking about for any transformations, etc.

    That's just an URL that is detected and activated.

    It is not rCLdetectedrCY, it is specifically marked up as a URL with a .URL directive in the source for the man page.
    --
    https://www.greenend.org.uk/rjk/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 19:51:36 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 19:32, Richard Kettlewell wrote:
    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-03 09:40, Richard Kettlewell wrote:
    "Carlos E. R." <robin_listas@es.invalid> writes:
    On 2026-11-01 23:32, Lawrence DrCOOliveiro wrote:
    On Sun, 1 Nov 2026 13:07:09 +0100, Carlos E. R. wrote:
    On 2026-10-31 22:57, Lawrence DrCOOliveiro wrote:
    Tip: if you prefer another form, like PDF, itrCOs quite easy to
    generate that from any man page.

    PDF is fine, but not if the source is a man page, because there are >>>>>> no cross references that you can click or tap ...
    Actually, you *can* include URLs in the source markup, and the PDF
    version will make them clickable.

    Yes, that happens when the source is used to create several output
    formats. Tpically both man and info, but there can be more.

    But not when the pdf is generated using the man as source.

    Links work fine in PDFs generated from man page sources. See
    link at the bottom of https://terraraq.uk/junk/ccache.pdf to
    https://ccache.dev/credits.html for an example.

    That's not what I mean.

    Please could you explain clearly what you do mean, then, being specific
    about what exactly file formats yourCOre talking about as inputs, what
    tools yourCOre talking about for any transformations, etc.

    man zypper

    Depending on the kind of packages you keep in a local repo you
    may want to adjust the way GPG signature checks are performed.
    See section *GPG checks* for details.

    I want to be able to click on the highlighted text "GPG checks", or
    press enter, and go automatically to that section.



    That's just an URL that is detected and activated.

    It is not rCLdetectedrCY, it is specifically marked up as a URL with a .URL directive in the source for the man page.

    Ah, ok.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 19:28:02 2026
    From Newsgroup: comp.unix.shell

    On Tue, 03 Nov 2026 07:15:05 GMT, Charlie Gibbs wrote:

    Mainframes in the day used minis as "front-end processors" that
    offloaded things like keystroke processing from the main CPU, which
    could then concentrate on number crunching.

    iirc the System 360/30s became satellite processors for the later 360 machines.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 20:25:44 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe thinking: more efficient use of the computer, less efficient for the
    human user.

    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work. The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.
    Minis (and later superminis, like the VAX) had it all over mainframes
    in that regard.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 20:27:15 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year. The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    Valued at approximately $5.33 billion to $5.71 billion in 2025.
    Projected to grow to $5.65 billion to $6.11 billion in 2026.
    Forecasted to reach $7.54 billion to $10.53 billion by
    2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4
    mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident
    armchair experts
    --
    "The most difficult subjects can be explained to the most slow witted
    man if he has not formed any idea of them already; but the simplest
    thing cannot be made clear to the most intelligent man if he is firmly persuaded that he knows already, without a shadow of doubt, what is laid
    before him."

    - Leo Tolstoy


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 20:27:58 2026
    From Newsgroup: comp.unix.shell

    On Tue, 03 Nov 2026 07:15:04 GMT, Charlie Gibbs wrote:

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 02:53:45 GMT, Charlie Gibbs wrote:

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.

    ThatrCOs not the dichotomy. The dichotomy was that mainframes were
    optimized for throughput at the expense of latency, while
    minicomputers concentrated on minimizing latency to maximize
    interactive responsiveness at the expense of throughput.

    Pick your metaphor. In the end the trade-offs are the same.

    Nothing rCLmetaphoricalrCY about it. Sending data across a continent in real-time became commonplace with the coming of ARPAnet. But those
    mainframes couldnrCOt actually connect directly, could they? They had to
    go through one of those rCLIMPrCY boxes from BBN. And those were built
    around ... minicomputers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 20:29:38 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 12:45:09 +0100, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    Something not quite right there. Hand-coded assembly language only
    makes sense for minimizing CPU usage. If yourCOre doing lots of I/O,
    then the CPU is not the bottleneck, so trying to hand-tune assembly
    code is a waste of time.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Wade@g4ugm@dave.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 20:53:29 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 20:25, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe thinking: more efficient use of the computer, less efficient for the
    human user.

    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work. The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.
    Minis (and later superminis, like the VAX) had it all over mainframes
    in that regard.

    Why? I don't need to imagine, I did it all the time. Its not a problem.
    The editor generates a screen full of data.
    The controller handles most of the character editing so you change the
    local buffer which does see every key stroke.
    At some point you send the modified screen back to the host.

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but then
    I am more familiar with it.

    Dave



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 21:35:46 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe >thinking: more efficient use of the computer, less efficient for the
    human user.

    Did you ever use one? They were far more efficient for the human user,
    such as a bank teller or at the airport checkin desk.

    Even for a human programmer, they supplied full-screen editing long before
    vi was even a gleam in Bill Joy's eye.

    Really, just a precursor of the way that the current WWW works.


    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work.

    Don't need to imagine it. Burroughs full-screen editor
    worked just fine (albeit a page at a time).

    The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.

    No, the terminal handles that internally. You update the full
    80x24 screen in place, then transmit the entire page. Burroughs
    terminals even supported multiple pages.

    DAGS CANDE.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 21:37:21 2026
    From Newsgroup: comp.unix.shell

    The Natural Philosopher <tnp@invalid.invalid> writes:
    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year. The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys
    mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    Valued at approximately $5.33 billion to $5.71 billion in 2025.
    Projected to grow to $5.65 billion to $6.11 billion in 2026.
    Forecasted to reach $7.54 billion to $10.53 billion by
    2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4
    mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred >purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident >armchair experts

    Dig into a bit and you'll find that those are refreshes for existing
    customers, not new customers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 21:51:11 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 13:26:01 +0000, David Wade wrote:

    IBM built a lot of intelligence into the IO subsystem. There are
    multiple IO processors, once known as channels, which move data to
    and from devices. They are controlled by a channel program which can
    perform multiple IOs so a single IO request can read or write
    multiple blocks of data from a tape or disk to or from different
    locations in memory with the main CPU only getting involved when
    they are all complete.

    All about high throughput, at the expense of high latency.

    Also there was this assumption that CPU power was scarce and
    expensive, so the more the I/O devices could manage on their own
    without bothering the CPU, the better.

    This model stopped making sense in the 1980s.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 21:52:44 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 18:06:33 +0100, Carlos E. R. wrote:

    And extra cost by ensuring it is reliable.

    Very expensive way of ensuring reliability. Google ensures reliability
    by running (as of a count in a paper published a decade or two ago)
    about half a million servers. So, at any moment, a dozen or a hundred
    of them are down; so what? The customers donrCOt notice.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 21:57:22 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 20:53:29 +0000, David Wade wrote:

    On 03/11/2026 20:25, Lawrence DrCOOliveiro wrote:

    Imagine trying to run a full-screen editor that way: it just
    wouldnrCOt work. The app really needed to be able to respond to every
    keystroke in order to maintain the necessary level of interactive
    response. Minis (and later superminis, like the VAX) had it all
    over mainframes in that regard.

    Why? I don't need to imagine, I did it all the time. Its not a
    problem. The editor generates a screen full of data. The controller
    handles most of the character editing so you change the local buffer
    which does see every key stroke. At some point you send the modified
    screen back to the host.

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but
    then I am more familiar with it.

    Neither one had an incremental-search function like the one in Emacs
    though, did they? That updates the display in real-time, after every
    keystroke, highlighting all the visible matches for the string as
    yourCOve typed it so far.

    Try doing that on a block-mode terminal.

    Now try doing it with a regular-expression search ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:00:19 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 05:28:52 -0800, Lars Poulsen wrote:

    By the time of VMS, there was a new paradigm, where you could push
    the pre-processing out to the terminal cluster: The TTY device in
    the OS had mode bitmasks, specifying for each character whether it
    should be echoed and whether it should generate a read completion
    interrupt.

    You realize, all this was done in *software* in the terminal driver,
    not in the terminal controller?

    So yes, the CPU was still getting an interrupt on every incoming
    character.

    Unix got a similar set of modes controlled with the stty command and
    its associated ioctl system calls, but I don't think I have ever
    seen these succesfully be used to put the TTY pre-processing in a
    remote front-end controller, like VMS could.

    Unix never had a terminal driver as advanced as VMS did, that is true.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:01:13 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 22:37, Scott Lurndal wrote:
    The Natural Philosopher <tnp@invalid.invalid> writes:
    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year. The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys
    mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    Valued at approximately $5.33 billion to $5.71 billion in 2025.
    Projected to grow to $5.65 billion to $6.11 billion in 2026.
    Forecasted to reach $7.54 billion to $10.53 billion by
    2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4
    mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred
    purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident
    armchair experts

    Dig into a bit and you'll find that those are refreshes for existing customers, not new customers.

    I don't expect new banks, either.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:01:36 2026
    From Newsgroup: comp.unix.shell

    On Tue, 03 Nov 2026 07:15:05 GMT, Charlie Gibbs wrote:

    Mainframes in the day used minis as "front-end processors" that
    offloaded things like keystroke processing from the main CPU, which
    could then concentrate on number crunching.

    Except that mainframes (of the IBM kind, anyway) were never very good
    at number crunching. Their job was rCLbusiness data processingrCY (i.e.
    COBOL).

    If you wanted to do number crunching, you got yourself a CDC machine.
    Now *there* was a number cruncher ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell on Tue Nov 3 22:14:09 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 12:28:55 +0100, Carlos E. R. wrote:

    On 2026-11-03 03:50, Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 03:02:07 +0100, Carlos E. R. wrote:

    I have seen documentation PDFs that are just the output of
    man2pdf.

    Not sure why you need a separate package/command, when the usual
    rCLmanrCY command is quite capable of doing that itself.

    And is just as useless.

    The rCLmanrCY command was able to preserve clickable links in PDF, as I
    pointed out.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:15:40 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 14:28, The Natural Philosopher wrote:
    On 03/11/2026 11:49, Pancho wrote:
    On 11/3/26 11:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    What it is exactly they do, I don't know.


    I'm too young for mainframes, but I always assumed they were for
    running legacy systems that people couldn't be bothered to port to new
    hardware/architectures.

    FWIW, my guess is that "high i/o" and "very large" is only by the
    standards of mainframe programmers.

    You would guess wrong then
    Think about the number of people a second swiping their cards or
    applePay wotsits across terminals...
    Each transaction is trivial: post a debit, with details of where the
    debt is incurred, and check against customer balance and overdraft
    limits, and issue - or deny - authorisation,
    But you are talking millions per second. All of which demand instant response. All of which access centralised databases that cant be split across machines




    Traditional banking transactions almost certainly could be parallelised,
    to quite a high degree, whether they were or not, I don't know. They are nowadays.

    My impression was the old software worked reliably, throwing more modern hardware at it was the cheapest solution... But there are better ways to
    do things. Modern companies like Stripe, will be using the same modern hardware as everyone else. I can't see why financial transactions are a heavier burden than other computing transactions, webservers.

    If you want heavy usage, I would guess bank risk calcs, weather calcs,
    lots of science applications, running on compute grids, (or whatever the modern word is), blow this mainframe high i/o away.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:18:36 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 23:01:13 +0100, Carlos E. R. wrote:

    I don't expect new banks, either.

    New banks do keep coming along.

    <https://www.stuff.co.nz/money/361054511/rbnz-registers-revolut-nzs-first-digi-only-bank>

    Also, you think banks donrCOt use more modern tools, like Python?

    Yes, Python. <https://calpaterson.com/bank-python.html>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Wade@g4ugm@dave.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:44:10 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 21:57, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 20:53:29 +0000, David Wade wrote:

    On 03/11/2026 20:25, Lawrence DrCOOliveiro wrote:

    Imagine trying to run a full-screen editor that way: it just
    wouldnrCOt work. The app really needed to be able to respond to every
    keystroke in order to maintain the necessary level of interactive
    response. Minis (and later superminis, like the VAX) had it all
    over mainframes in that regard.

    Why? I don't need to imagine, I did it all the time. Its not a
    problem. The editor generates a screen full of data. The controller
    handles most of the character editing so you change the local buffer
    which does see every key stroke. At some point you send the modified
    screen back to the host.

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but
    then I am more familiar with it.

    Neither one had an incremental-search function like the one in Emacs
    though, did they? That updates the display in real-time, after every keystroke, highlighting all the visible matches for the string as
    yourCOve typed it so far.


    no, but how often do you use that?

    Try doing that on a block-mode terminal.


    Its a bit slower but the XEDIT "all" command shows all lines with a
    string. The command remains in the command line so you can quickly
    refine your search...

    Now try doing it with a regular-expression search ...

    Now that is real geekdom...

    Dave
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:47:07 2026
    From Newsgroup: comp.unix.shell

    According to Pancho <Pancho.Jones@protonmail.com>:
    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.
    ...

    Traditional banking transactions almost certainly could be parallelised,
    to quite a high degree, whether they were or not, I don't know. They are >nowadays.

    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one succeeded and the other failed*, your bank has a problem. The reason they
    need very fast very large databases is that updates have to be serialized
    and there's no way to make them faster than the underlying system. Same
    for airlines allocating seats and any other database reflecting a real world application where there's a finite amount of something to be parcelled out.



    * - yes I know about overdrafts, this is an example
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Wade@g4ugm@dave.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:51:30 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 21:37, Scott Lurndal wrote:
    The Natural Philosopher <tnp@invalid.invalid> writes:
    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year. The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys
    mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    Valued at approximately $5.33 billion to $5.71 billion in 2025.
    Projected to grow to $5.65 billion to $6.11 billion in 2026.
    Forecasted to reach $7.54 billion to $10.53 billion by
    2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4
    mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred
    purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident
    armchair experts

    Dig into a bit and you'll find that those are refreshes for existing customers, not new customers.

    I think all this shows is that IBM is able to force expensive hardware
    refresh by ending support for old machines and old versions of software
    so if you need Payment Card Industry compliance you need supported
    software. I would say most users need PCI compliance so have no choice
    other than to upgrade or migrate and most feel migration will be more expensive and carry more risk...

    .. mind I seem to remember that the recent price rises in VMWare meant
    that migration from there to Linux on "Z" would be a cost effective move...

    Dave
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:02:26 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 22:51:30 +0000, David Wade wrote:

    I think all this shows is that IBM is able to force expensive
    hardware refresh by ending support for old machines and old versions
    of software so if you need Payment Card Industry compliance you need supported software.

    I donrCOt think thatrCOs true. I have hooked up various clients to various payment systems over the years, and there was never a need for any
    particular piece of proprietary software at our end.

    (Well, the very first time I looked at a payment system, over a
    quarter century ago, SSL/TLS had not yet become popular, and this bank
    required a connection via the proprietary rCLFirewall/1rCY package, which
    only ran on Windows NT/Server. But I never heard back about proceeding
    with that, and that kind of thing is ancient history now.)

    In fact, the last one I set up, the payment company offered example
    code for implementing their protocol in a range of languages. They had
    kept things quite simple, while being careful about security, all
    credit to them.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:02:55 2026
    From Newsgroup: comp.unix.shell

    According to Scott Lurndal <slp53@pacbell.net>:
    So, as usual, the facts are not correctly represented by the resident >>armchair experts

    Dig into a bit and you'll find that those are refreshes for existing >customers, not new customers.

    IBM has two markets for z mainframes, the legacy S/360/370/390 market
    and high performance linux servers which they call LinuxONE.

    I agree they're not likely to have new legacy customers but I'd be surprised that they put all that effort into LinuxONE without expecting to get new customers out of it.

    They just announced that the next generation of z will have a
    partnership with ARM so the processors can run ARM64 code as well as
    the three legacy 360 modes. That tells me they're trying to get
    customers who already have the ARM code running in the cloud at AWS or
    Azure.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:04:30 2026
    From Newsgroup: comp.unix.shell

    According to c186282 <c186282@nnada.net>:
    I guess you COULD call the PDP-11 a "mini", but
    imho it didn't have quite the "feel". More like
    a cut-down mainframe. Good peripheral bus though,
    you could plug in all kinds of goodies.

    I can assure you that PDP-11s were minicomputers. I spent quite a while programming them back in the 1970s.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:05:48 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 22:44:10 +0000, David Wade wrote:

    On 03/11/2026 21:57, Lawrence DrCOOliveiro wrote:

    Neither one had an incremental-search function like the one in
    Emacs though, did they? That updates the display in real-time,
    after every keystroke, highlighting all the visible matches for the
    string as yourCOve typed it so far.

    no, but how often do you use that?

    Every day.

    Now try doing it with a regular-expression search ...

    Now that is real geekdom...

    Really basic thing: searching for an identifier in its entirety,
    not just matching part of an identifier.

    E.g. I use rCLirCY quite commonly as a loop index. How to search for that without matching all the names with the letter rCLirCY in the middle of
    them? Simple: use the regexp rCL\bi\brCY.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:18:13 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 22:47, John Levine wrote:
    According to Pancho <Pancho.Jones@protonmail.com>:
    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.
    ...

    Traditional banking transactions almost certainly could be parallelised,
    to quite a high degree, whether they were or not, I don't know. They are
    nowadays.

    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one succeeded and the other failed*, your bank has a problem. The reason they need very fast very large databases is that updates have to be serialized
    and there's no way to make them faster than the underlying system. Same
    for airlines allocating seats and any other database reflecting a real world application where there's a finite amount of something to be parcelled out.



    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with
    me, it can be done in parallel.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:41:51 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 07:15:05 GMT, Charlie Gibbs wrote:

    Mainframes in the day used minis as "front-end processors" that
    offloaded things like keystroke processing from the main CPU, which
    could then concentrate on number crunching.

    Except that mainframes (of the IBM kind, anyway) were never very good
    at number crunching. Their job was rCLbusiness data processingrCY (i.e. COBOL).

    If you wanted to do number crunching, you got yourself a CDC machine.
    Now *there* was a number cruncher ...

    There's a difference between "good" and "good enough".
    Business programs tended to be I/O-bound, so it wasn't
    worth spending a lot of extra bucks on CPU power - that
    money was better spent on a good I/O system instead.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:41:52 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 07:15:04 GMT, Charlie Gibbs wrote:

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 02:53:45 GMT, Charlie Gibbs wrote:

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.

    ThatrCOs not the dichotomy. The dichotomy was that mainframes were
    optimized for throughput at the expense of latency, while
    minicomputers concentrated on minimizing latency to maximize
    interactive responsiveness at the expense of throughput.

    Pick your metaphor. In the end the trade-offs are the same.

    Nothing rCLmetaphoricalrCY about it. Sending data across a continent in real-time became commonplace with the coming of ARPAnet. But those
    mainframes couldnrCOt actually connect directly, could they? They had to
    go through one of those rCLIMPrCY boxes from BBN. And those were built
    around ... minicomputers.

    That's not the only way to get data across the continent. In
    the late '70s our mainframe in Vancouver was driving block-mode
    multidropped terminals in Toronto through a leased line at a
    blazing 2400 bps. From a software standpoint they looked just
    like our local terminals, except that the wires were much longer
    and the speed slower. (Our local terminals ran at 9600 bps.)
    In those days modems cost about a dollar per bps - that's right,
    $2500 for a Bell 202-style modem running synchronously at 2400 bps.
    You could get 9600-bps modems, but they were ten grand a pop.
    And the leased line wasn't cheap either. As ever, we balanced
    price against performance.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 01:13:34 2026
    From Newsgroup: comp.unix.shell

    On Tue, 3 Nov 2026 22:01:36 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    Except that mainframes (of the IBM kind, anyway) were never very good at number crunching. Their job was rCLbusiness data processingrCY (i.e. COBOL).

    https://grokipedia.com/page/ibm_system360_model_44
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 02:42:56 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 21:53, David Wade wrote:
    On 03/11/2026 20:25, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe
    thinking: more efficient use of the computer, less efficient for the
    human user.

    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work. The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.
    Minis (and later superminis, like the VAX) had it all over mainframes
    in that regard.

    Why? I don't need to imagine, I did it all the time. Its not a problem.
    The editor generates a screen full of data.
    The controller handles most of the character editing so you change the
    local buffer which does see every key stroke.
    At some point you send the modified screen back to the host.

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but then
    I am more familiar with it.

    I recall I've used (on a Siemens mainframe) XEDIT on IBM's VM/CMS,
    but all I remember (no details) is that I liked it back these days.

    On the same mainframe we could also run under the VM a UTS (a Unix
    from Amdahl) which (of course) came with Vi as a full-screen visual
    editor.

    So I cannot see why one would think that full-screen editors would
    somehow not be possible. For the editing on the terminal there wasn't
    an allocation of the mainframe CPU(s) necessary, it was basically all
    handled by the peripheral devices of the mainframe architecture, IIRC.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 02:59:34 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 16:18, Scott Lurndal wrote:
    [...]

    Recalling at the time that interactive used was typically form-based
    (e.g. airline reservation systems, bank teller terminals, etc) and
    the block mode terminals of the day typically transferred the contents
    of the screen (or the form fields on the screen) in a single transmission.

    Yes. And it's noteworthy that we (again, or still) have a similar way
    of processing with web-based systems and their HTML forms today. Some unpleasant deviation is that nowadays some higher-level functionality
    gets externalized to the (now much more powerful) clients.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 03:16:01 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 04:29, c186282 wrote:
    [...]
    -a The age of the "mainframe" may be coming to an
    -a end alas. 'Cluster'/AI solutions are going to
    -a replace them for most uses. However science/govt
    -a still have uses for big ultra-powerful boxes
    -a for awhile anyway.

    In practice I see no evidence for that here. And why
    would it for "science" be better to have a mainframe?
    My children actually work "in science" where extremely
    demanding complex (hydrodynamic) simulation models are
    done; all done on such high-performance clusters. And
    this appears to be nowadays quite common as observable.

    SOME advantage in keeping
    -a access 'local' too - as opposed to spread all
    -a over the highly-vulnerable net.

    There had always been non-local access, even back in
    the mainframe days.

    There's a more general problem here; whether a single
    "box" or a "cluster", if it's connected to the Net it
    has to be solidified.

    Janis

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 03:23:51 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me they
    are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should
    meanwhile be at "best" a niche, and systems programming
    with "C" (or similar).

    But, yes. It was now for long a problem getting staff for
    legacy things. Those companies who are too inert to adapt
    [to the technical evolution] will pay, suffer, or demise.

    Janis

    [...]

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 03:12:39 2026
    From Newsgroup: comp.unix.shell

    According to Pancho <Pancho.Jones@protonmail.com>:
    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one
    succeeded and the other failed*, your bank has a problem. The reason they >> need very fast very large databases is that updates have to be serialized
    and there's no way to make them faster than the underlying system. Same
    for airlines allocating seats and any other database reflecting a real world >> application where there's a finite amount of something to be parcelled out. >>


    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone >else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with
    me, it can be done in parallel.

    Sure, but you're not going to put every account on a different disk. Real transactions are more complicated than that -- when they take the $75 out of my account they have to credit it somewhere else, and that debit/credit pair has to
    be atomic, both work or both fail.

    Banks are conservative but they are not stupid. There's a lot of stuff they can push out onto cheap micro based servers, but there's a certain amount of key business logic that Absolutely Has To Work.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:23:59 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 21:16, Janis Papanagnou wrote:
    On 2026-11-03 04:29, c186282 wrote:
    [...]
    -a-a The age of the "mainframe" may be coming to an
    -a-a end alas. 'Cluster'/AI solutions are going to
    -a-a replace them for most uses. However science/govt
    -a-a still have uses for big ultra-powerful boxes
    -a-a for awhile anyway.

    In practice I see no evidence for that here. And why
    would it for "science" be better to have a mainframe?

    Um ... read the lit. A huge amount of science is
    still done by 'super-computers'/mainframes. For
    'defense' shit, *a* mainframe is still far more
    secure than alt solutions.

    However, the distributed 'AI' shit WILL replace
    that for the most part in the next decade. In
    some respects NOT the very best idea alas .....

    My children actually work "in science" where extremely
    demanding complex (hydrodynamic) simulation models are
    done; all done on such high-performance clusters. And
    this appears to be nowadays quite common as observable.

    Umm ... your KIDS are into hydrodynamics ? Are
    they 'kids' anymore ?

    -a-a SOME advantage in keeping
    -a-a access 'local' too - as opposed to spread all
    -a-a over the highly-vulnerable net.

    There had always been non-local access, even back in
    the mainframe days.

    Yep - happened. However it's easier to guard/armor
    ONE mainframe than a vast network.

    There's a more general problem here; whether a single
    "box" or a "cluster", if it's connected to the Net it
    has to be solidified.

    DOES require a lot of 'solidification' - esp now.

    Otherwise you're just working for your worst enemies.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:30:53 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 18:18, Pancho wrote:
    On 11/3/26 22:47, John Levine wrote:
    According to Pancho-a <Pancho.Jones@protonmail.com>:
    I know at least one guy working on IBM mainframes, and he tells me >>>>>> they are in high need of good assembler programmers.

    They need high i/o with very large databases.
    ...

    Traditional banking transactions almost certainly could be parallelised, >>> to quite a high degree, whether they were or not, I don't know. They are >>> nowadays.

    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one
    succeeded and the other failed*, your bank has a problem.-a The reason
    they
    need very fast very large databases is that updates have to be serialized
    and there's no way to make them faster than the underlying system.-a Same
    for airlines allocating seats and any other database reflecting a real
    world
    application where there's a finite amount of something to be parcelled
    out.



    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with
    me, it can be done in parallel.

    NOTICED - my principal bank - a LOT of transactions
    come up with a "pending" label. Might take DAYS. This
    is not some 3rd-tier bank either.

    Two or more larger credit/debit card charges, not
    sure HOW they 'compete' in that system. If too
    near each other one MIGHT get bumped. Problem !

    In short, even 'online/instant' banking may not
    be THAT instant.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:54:38 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 18:02, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 22:51:30 +0000, David Wade wrote:

    I think all this shows is that IBM is able to force expensive
    hardware refresh by ending support for old machines and old versions
    of software so if you need Payment Card Industry compliance you need
    supported software.

    I donrCOt think thatrCOs true. I have hooked up various clients to various payment systems over the years, and there was never a need for any
    particular piece of proprietary software at our end.
    IBM *tends* to Do It Right.

    Don't discount them.

    Yea, yea ... 'Dilbert' made fun of them, and
    not always for bad reasons, but the corp remains
    alive and well and profitable even to this day
    so it must be doing *something* right.

    IBM is 'diverse' - hardware/software/systems/
    development/etc. A good recipe for long-term
    survival. Many baskets. A lot of 'other people's
    tech' pays royalties to IBM for the underlying
    real tech.

    KEEP the corp in my portfolio.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 03:57:31 2026
    From Newsgroup: comp.unix.shell

    According to c186282 <c186282@nnada.net>:
    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with
    me, it can be done in parallel.

    NOTICED - my principal bank - a LOT of transactions
    come up with a "pending" label. Might take DAYS. This
    is not some 3rd-tier bank either.

    That has nothing to do with your bank's database and everything to do
    with the way that credit card charges work. First the charge is
    approved for an approximate amount which is pretty quick, then the
    actual charge is posted which can take anywhere from moments to days.
    The amounts are often different, e.g., when you pump gas it approves
    an amount big enough to cover the largest plausible fill-up, then when
    you're done it posts the final amount. Or at a restaurant, it approves
    the amount on the check, then posts that plus whatever tip you add.

    For historic reasons it's common to wait to post all of a day's
    charges at the end of the day, or even later which is why they can sit
    there pending for a while.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 22:58:20 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 18:02, John Levine wrote:
    According to Scott Lurndal <slp53@pacbell.net>:
    So, as usual, the facts are not correctly represented by the resident
    armchair experts

    Dig into a bit and you'll find that those are refreshes for existing
    customers, not new customers.

    IBM has two markets for z mainframes, the legacy S/360/370/390 market
    and high performance linux servers which they call LinuxONE.

    I agree they're not likely to have new legacy customers but I'd be surprised that they put all that effort into LinuxONE without expecting to get new customers out of it.

    Apparently DO have/gain many customers.

    They just announced that the next generation of z will have a
    partnership with ARM so the processors can run ARM64 code as well as
    the three legacy 360 modes. That tells me they're trying to get
    customers who already have the ARM code running in the cloud at AWS or
    Azure.

    The 'mainframe' era is nearly over - to be replaced
    by cluster/distributed/AI.

    However IBM is already into all that, WILL make money.

    Many baskets ... How To Survive/Thrive.

    Hmmmm ... do remember when IBM was "typewriters" ...

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 3 23:05:29 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 18:04, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    I guess you COULD call the PDP-11 a "mini", but
    imho it didn't have quite the "feel". More like
    a cut-down mainframe. Good peripheral bus though,
    you could plug in all kinds of goodies.

    I can assure you that PDP-11s were minicomputers. I spent quite a while programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe. DEC had the VAX
    line of mainframes ... but there was a
    a market for smaller/cheaper sub-derivatives.
    The "PDP" line was their answer.

    Hey, 'C' was developed on the PDP-11.
    Still remember it as a 'new-fangled'
    language that was intriguing/fun.

    Note, for Linux, 'B' compilers CAN still
    be had. 'B' was kind of a 'less complete'
    idea of 'C'. Still, usable. Wrote a few
    little things in 'B' just last year,
    for fun.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 04:15:04 2026
    From Newsgroup: comp.unix.shell

    According to c186282 <c186282@nnada.net>:
    I can assure you that PDP-11s were minicomputers. I spent quite a while
    programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.
    A 360/30 was considerably slower than a PDP-8, but its
    I/O architecture clearly made it a mainframe.

    The PDP-8 I used had "three cycle data break" which
    did data transfers into or out of memory (that was
    one cycle) using address and word counts also in
    memory (those were the other two cycles.) But that
    was only for the disks, and didn't do all of the other
    chaining and control stuff that channels did.

    DEC had the VAX line of mainframes ...

    A VAX was a super-mini, not a mainframe. I was there.
    Again, simpler I/O even though it was a lot bigger than
    a PDP-8 or PDP-11.

    If you look through the comp.arch archives you'll find arguments
    about whether a PDP-10 was a mainframe or a very large mini. I
    claim it was a mini because its I/O was similar to DEC's other
    minis, including a hack reminiscent of three-cycle data break.
    Others say it was a mainframe because it was marketed that way.

    I will admit that the later KL with a PDP-11 front end and MASSBUS
    disk I/O was a lot more like a mainframe than the original KA-10.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 00:14:13 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 23:15, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    I can assure you that PDP-11s were minicomputers. I spent quite a while >>> programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.

    Kinda true.

    However 'minis' were SUPPOSED to do everything
    mainframes could do - just a a DISCOUNT PRICE.

    Usually true, usually.

    A 360/30 was considerably slower than a PDP-8, but its
    I/O architecture clearly made it a mainframe.

    Yep ! No args. The 360s were VERY versatile on
    MANY levels.

    The PDP-8 I used had "three cycle data break" which
    did data transfers into or out of memory (that was
    one cycle) using address and word counts also in
    memory (those were the other two cycles.) But that
    was only for the disks, and didn't do all of the other
    chaining and control stuff that channels did.

    DEC had the VAX line of mainframes ...

    Yep - and the VAX mainframe lines were GREAT.

    However the 'PDP' lines also had their place
    in the overall equation. Don't piss on them.

    A VAX was a super-mini, not a mainframe. I was there.
    Again, simpler I/O even though it was a lot bigger than
    a PDP-8 or PDP-11.

    Ummmmm ... I suspect we're dealing with
    slightly different defs of 'mainframe'
    and 'mini' and whatever. There is NO
    clear line.

    I'm more centered on What They Could DO.
    The 'exactly HOW' is less relevant.

    If you look through the comp.arch archives you'll find arguments
    about whether a PDP-10 was a mainframe or a very large mini. I
    claim it was a mini because its I/O was similar to DEC's other
    minis, including a hack reminiscent of three-cycle data break.
    Others say it was a mainframe because it was marketed that way.

    I will admit that the later KL with a PDP-11 front end and MASSBUS
    disk I/O was a lot more like a mainframe than the original KA-10.


    Looks like we're gonna have disagreements over
    WHAT 'class' to assign to various units. It
    was always a 'soft' subject - and remains so.
    What 'mainframes'/'minis'/PCs do - it's more
    an emphasis on Certain Features. Nothing SO
    different, just 'emphasis' .

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 06:21:03 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, John Levine <johnl@taugh.com> wrote:

    According to c186282 <c186282@nnada.net>:

    I can assure you that PDP-11s were minicomputers. I spent quite a while >>> programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.
    A 360/30 was considerably slower than a PDP-8, but its
    I/O architecture clearly made it a mainframe.

    I agree. I've always believed that the difference between
    a mainframe and a mini had nothing to do with the size of
    the box, but everything to do with architecture, particularly
    I/O. Mainframes were record-oriented, while minis were
    byte-oriented. Everything else - architecture, protocols,
    philosophy, culture, etc. - was molded by that.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:10:49 2026
    From Newsgroup: comp.unix.shell

    On Wed, 04 Nov 2026 06:21:03 GMT, Charlie Gibbs wrote:

    Mainframes were record-oriented, while minis were byte-oriented.

    Maybe better to say rCLminis were character-orientedrCY. Remember DEC had 18-bit and 12-bit minicomputer architectures before IBM even invented
    the term rCLbyterCY.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 08:26:56 2026
    From Newsgroup: comp.unix.shell

    On 11/4/26 03:12, John Levine wrote:
    According to Pancho <Pancho.Jones@protonmail.com>:
    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one
    succeeded and the other failed*, your bank has a problem. The reason they >>> need very fast very large databases is that updates have to be serialized >>> and there's no way to make them faster than the underlying system. Same >>> for airlines allocating seats and any other database reflecting a real world
    application where there's a finite amount of something to be parcelled out. >>>


    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with
    me, it can be done in parallel.

    Sure, but you're not going to put every account on a different disk. Real transactions are more complicated than that -- when they take the $75 out of my
    account they have to credit it somewhere else, and that debit/credit pair has to
    be atomic, both work or both fail.


    Not something I ever did, but I strongly suspect it is message queues, including acknowledgements. Tricky to get perfect, but standard IT stuff.

    Banks are conservative but they are not stupid. There's a lot of stuff they can
    push out onto cheap micro based servers, but there's a certain amount of key business logic that Absolutely Has To Work.


    Absolutely has to work, means testing. That is why they keep the old
    stuff, it has been tested, in production.

    Newer system reliability will be almost entirely about software design,
    better techniques, but testing is difficult.

    We recently had a scandal in the UK, the Post Office, shocking flaws in design, from the mid 1990s, but over the years they caught most of the
    bugs and made it work. A superficial look at the news reports showed
    they weren't using things like idempotent operations. Modern systems are designed to be much more tolerant of hardware glitches.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 16:57:06 2026
    From Newsgroup: comp.unix.shell

    On 11/4/2026 11:57 AM, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with >>> me, it can be done in parallel.

    NOTICED - my principal bank - a LOT of transactions
    come up with a "pending" label. Might take DAYS. This
    is not some 3rd-tier bank either.

    That has nothing to do with your bank's database and everything to do
    with the way that credit card charges work. First the charge is
    approved for an approximate amount which is pretty quick, then the
    actual charge is posted which can take anywhere from moments to days.
    The amounts are often different, e.g., when you pump gas it approves
    an amount big enough to cover the largest plausible fill-up, then when
    you're done it posts the final amount. Or at a restaurant, it approves
    the amount on the check, then posts that plus whatever tip you add.

    For historic reasons it's common to wait to post all of a day's
    charges at the end of the day, or even later which is why they can sit
    there pending for a while.


    I believe most credit card transactions [1] are batch processed during
    night time. For instance, Wise marks transactions as "pending" until
    the nightly batch process has run through; based on unscientific obser- vations.

    So they'll take the money out of my balance immediately, but probably
    not deposit it on the other end -- whatever that means for Wise -- until
    the nightly batch job. Which can fail -- I guess. And sometimes things
    are even weirder. By casual observation, if I pay some subscriptions in advance, they'll still withdraw the monthly amount, /then/ discover the
    balance was already in plus, and refund it.

    That's the website payment processing system, though; not my bank.

    And add in the fact that I can at any moment re-number my card [2] so it
    is anybody's guess whether a pending transaction with that card number
    will go through or not.

    And that's not touching upon the weirdness that is Microsoft's payment processing system, which can accept my card number, verify it with the
    zero dollar transaction -- and /then/ -- decide I'm in some fraud cate-
    gory and refuse to make the actual transaction. I suspect the billing
    address and geoIP didn't match, but my bank doesn't care so why does
    Microsoft?

    And if you think the fruit vendor is better, you can rest easy, because
    at one time they refused to update my card number. Actually refused.
    After reaching the /right/ support person, that person could not help
    figure out why the website told me the card number had been updated, but
    then the TV application always tried to use the old card number.

    I gave up, and haven't given the fruit vendor a card number since.

    And what does that have to do with mainframes? Not much, I'm sad to say
    I have never worked with payment processing systems at the batch pro-
    cessing level, and don't know which of these shenanigans happen there,
    or if much of this happens at the front end -- namely the web payment processing before it reaches the mainframe.

    All I can say is that payment processing is complex, and it's getting
    more complex by the minute. Right now, someone is brainstorming some
    method to reduce fraud, or try to make a part of it just a little more reliable.


    Thank you for coming to my payment processing rant in alt.folklore.com-
    puters.

    [1] Full disclosure, I don't have a credit card, so my experience is exclusively based on debit cards for the past fifteen or more years.

    [2] Even the physical card, the card number changes, but I can still
    keep using it; I'll just have to read the number from the app or web-
    site.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 10:43:55 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-03 23:47, John Levine wrote:
    According to Pancho <Pancho.Jones@protonmail.com>:
    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.
    ...

    Traditional banking transactions almost certainly could be parallelised,
    to quite a high degree, whether they were or not, I don't know. They are
    nowadays.

    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one succeeded and the other failed*, your bank has a problem. The reason they need very fast very large databases is that updates have to be serialized
    and there's no way to make them faster than the underlying system. Same
    for airlines allocating seats and any other database reflecting a real world application where there's a finite amount of something to be parcelled out.

    I suppose the first transaction arriving blocks the record. Even if both arrives the same microsecond, only one gets the lock.




    * - yes I know about overdrafts, this is an example
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 10:53:41 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 03:23, Janis Papanagnou wrote:
    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should
    meanwhile be at "best" a niche, and systems programming
    with "C" (or similar).

    They need speed that compilers can not achieve. They have a very good
    chap that I happen to know, near retirement, but they need more people:
    one good guy and two average can not cope with all the jobs.


    But, yes. It was now for long a problem getting staff for
    legacy things. Those companies who are too inert to adapt
    [to the technical evolution] will pay, suffer, or demise.

    Janis

    [...]

    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 10:58:41 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 00:41, Charlie Gibbs wrote:
    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 07:15:04 GMT, Charlie Gibbs wrote:

    On 2026-11-03, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 03 Nov 2026 02:53:45 GMT, Charlie Gibbs wrote:

    Yes, there is a dichotomy there. Mainframe protocols were designed
    for sending files across a continent, while mini protocols were
    designed for sending characters across the room. Compromises were
    made on both sides.

    ThatrCOs not the dichotomy. The dichotomy was that mainframes were
    optimized for throughput at the expense of latency, while
    minicomputers concentrated on minimizing latency to maximize
    interactive responsiveness at the expense of throughput.

    Pick your metaphor. In the end the trade-offs are the same.

    Nothing rCLmetaphoricalrCY about it. Sending data across a continent in
    real-time became commonplace with the coming of ARPAnet. But those
    mainframes couldnrCOt actually connect directly, could they? They had to
    go through one of those rCLIMPrCY boxes from BBN. And those were built
    around ... minicomputers.

    That's not the only way to get data across the continent. In
    the late '70s our mainframe in Vancouver was driving block-mode
    multidropped terminals in Toronto through a leased line at a
    blazing 2400 bps. From a software standpoint they looked just
    like our local terminals, except that the wires were much longer
    and the speed slower. (Our local terminals ran at 9600 bps.)
    In those days modems cost about a dollar per bps - that's right,
    $2500 for a Bell 202-style modem running synchronously at 2400 bps.
    You could get 9600-bps modems, but they were ten grand a pop.
    And the leased line wasn't cheap either. As ever, we balanced
    price against performance.


    And we were told that 9600 was the limit, the theory said so. I think it
    was 9600.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 11:27:04 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 00:05, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 22:44:10 +0000, David Wade wrote:

    On 03/11/2026 21:57, Lawrence DrCOOliveiro wrote:

    Neither one had an incremental-search function like the one in
    Emacs though, did they? That updates the display in real-time,
    after every keystroke, highlighting all the visible matches for the
    string as yourCOve typed it so far.

    no, but how often do you use that?

    Every day.

    I'm told that most people do not work directly on a terminal on the
    mainframe. There is not an OS proper...
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 11:08:48 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 21:37, Scott Lurndal wrote:
    So, as usual, the facts are not correctly represented by the resident
    armchair experts
    Dig into a bit and you'll find that those are refreshes for existing customers, not new customers.

    So what?
    So is every new I-phone/Android model.

    And just about every ARM chip.

    THERE ARE NO NEW CUSTOMERS except for AI slop

    Any more than there are for new cars.
    --
    There is nothing a fleet of dispatchable nuclear power plants cannot do
    that cannot be done worse and more expensively and with higher carbon emissions and more adverse environmental impact by adding intermittent renewable energy.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 11:09:39 2026
    From Newsgroup: comp.unix.shell

    On 03/11/2026 22:01, Carlos E. R. wrote:

    So, as usual, the facts are not correctly represented by the resident
    armchair experts

    Dig into a bit and you'll find that those are refreshes for existing
    customers, not new customers.

    I don't expect new banks, either.

    Exactly, though it would be nice to have one or two
    --
    rCLwhen things get difficult you just have to lierCY

    rCo Jean Claud J|+ncker

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 11:19:34 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 09:58, Carlos E. R. wrote:
    You could get 9600-bps modems, but they were ten grand a pop.
    And the leased line wasn't cheap either.-a As ever, we balanced
    price against performance.


    And we were told that 9600 was the limit, the theory said so. I think it
    was 9600.
    for one type of technology, it was...
    --
    "I guess a rattlesnake ain't risponsible fer bein' a rattlesnake, but ah
    puts mah heel on um jess the same if'n I catches him around mah chillun".


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 11:25:48 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 02:23, Janis Papanagnou wrote:
    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should
    meanwhile be at "best" a niche, and systems programming
    with "C" (or similar).

    You don't know what IBM assembler is, do you?

    But, yes. It was now for long a problem getting staff for
    legacy things. Those companies who are too inert to adapt
    [to the technical evolution] will pay, suffer, or demise.

    You don't really know what you are talking about, do you?
    Janis

    [...]

    --
    The difference bweteen a psychopath and a saint is that the psychpoath
    takes what he can and gives only what he must, but the saint gives
    everything he can and takes only what he needs.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:00:13 2026
    From Newsgroup: comp.unix.shell

    On 11/4/26 02:10, Lawrence DrCOOliveiro wrote:
    On Wed, 04 Nov 2026 06:21:03 GMT, Charlie Gibbs wrote:

    Mainframes were record-oriented, while minis were byte-oriented.

    Maybe better to say rCLminis were character-orientedrCY. Remember DEC had 18-bit and 12-bit minicomputer architectures before IBM even invented
    the term rCLbyterCY.

    Well, the 'standard' 8-bit byte kind of evolved,
    or converged. All kinds of byte/word sizes back
    in the day. We still see ez conversions to octal
    if specifying numbers in 'C'.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:32:53 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 13:25, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe thinking: more efficient use of the computer, less efficient for the
    human user.

    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work. The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.
    Minis (and later superminis, like the VAX) had it all over mainframes
    in that regard.

    I violently disagree. Full screen editors provide instant response to
    most operations: Move the cursor around, add, delete, and change text.
    There's only a delay when you're done editing that screen and want to
    move on to something else. On a well-tuned system this is a slight delay.

    It just occurred to me that I'm typing this text into a mail app which
    is basically the same thing. I can edit all I want, and then press SEND
    when I'm done.

    Maybe it's my mainframe background, but I think having "the computer"
    respond instantly to every keystroke is just stupid.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:36:18 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 13:27, The Natural Philosopher wrote:
    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year.-a-a The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys
    mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    -a-a-a-a-a-a-a Valued at approximately $5.33 billion to $5.71 billion in 2025.
    -a-a-a-a-a-a-a Projected to grow to $5.65 billion to $6.11 billion in 2026.
    -a-a-a-a-a-a-a Forecasted to reach $7.54 billion to $10.53 billion by 2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    -a-a-a-a-a-a-a Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4 mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    -a-a-a-a-a-a-a Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident armchair experts


    My only question is how many mainframe shipments represent NEW
    customers, as opposed to additional horsepower for current customers.

    I suppose, given that the trend today is to consolidation of everything,
    that eventually everything will be owned by BigCorp, who will then be
    the only mainframe customer.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:40:12 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 13:29, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 12:45:09 +0100, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    Something not quite right there. Hand-coded assembly language only
    makes sense for minimizing CPU usage. If yourCOre doing lots of I/O,
    then the CPU is not the bottleneck, so trying to hand-tune assembly
    code is a waste of time.

    I kind of agree. As a former assembler programmer - at one time it was
    my first language - I'd like it to be true (although I'm out of the job market), but I can't see it. These days most HLL code is more optimized
    than a lot of assembler. A good assembler programmer would not make a
    lot of these optimizations due to lack of readability.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:43:18 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 13:53, David Wade wrote:
    On 03/11/2026 20:25, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe
    thinking: more efficient use of the computer, less efficient for the
    human user.

    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work. The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.
    Minis (and later superminis, like the VAX) had it all over mainframes
    in that regard.

    Why? I don't need to imagine, I did it all the time. Its not a problem.
    The editor generates a screen full of data.
    The controller handles most of the character editing so you change the
    local buffer which does see every key stroke.
    At some point you send the modified screen back to the host.

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but then
    I am more familiar with it.

    Dave

    I also like XEdit, in fact I run THE on my PC, although it is not my
    primary editor. VAX TPU is also quite good, however, but we had great
    response time on our VAX.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:48:39 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 14:52, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 18:06:33 +0100, Carlos E. R. wrote:

    And extra cost by ensuring it is reliable.

    Very expensive way of ensuring reliability. Google ensures reliability
    by running (as of a count in a paper published a decade or two ago)
    about half a million servers. So, at any moment, a dozen or a hundred
    of them are down; so what? The customers donrCOt notice.

    Until things got cloudy, Google was write-once, read many times. Their
    search database was updated by a bot and lots of users accessed it. The transaction processing world needs to update a single database "simultaneously" from all over the world and maintain consistency. You
    can't distribute an airline reservation system, the data has to live in
    one place.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:52:35 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 14:57, Lawrence DrCOOliveiro wrote:

    Neither one had an incremental-search function like the one in Emacs
    though, did they? That updates the display in real-time, after every keystroke, highlighting all the visible matches for the string as
    yourCOve typed it so far.

    I find this more distracting than useful. Let me type my search,
    including correcting inevitable typos, etc. and then run it instead of continually flashing the screen at me as I type.

    Now try doing it with a regular-expression search ...

    Why would this be a problem? "Yes, ISPF View and Edit support regular expressions."

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 07:54:44 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 15:15, Pancho wrote:

    If you want heavy usage, I would guess bank risk calcs, weather calcs,
    lots of science applications, running on compute grids, (or whatever the modern word is), blow this mainframe high i/o away.

    I think back in the day the quants preferred Sun.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 15:34:52 2026
    From Newsgroup: comp.unix.shell

    John Levine <johnl@taugh.com> writes:
    According to Scott Lurndal <slp53@pacbell.net>:
    So, as usual, the facts are not correctly represented by the resident >>>armchair experts

    Dig into a bit and you'll find that those are refreshes for existing >>customers, not new customers.

    IBM has two markets for z mainframes, the legacy S/360/370/390 market
    and high performance linux servers which they call LinuxONE.

    I agree they're not likely to have new legacy customers but I'd be surprised >that they put all that effort into LinuxONE without expecting to get new >customers out of it.

    It's possible they might pick up one or two, but _if_ their linux
    offering is still running the legacy instruction set, that
    fundamentally limits the third-party software available on
    LinuxOne.

    I have trouble seeing it as a viable alternative to AWS or other cloud offerings (many of which also support similar or better uptime
    SLAs). [Disclaimer - I do own some stock in IBM].


    They just announced that the next generation of z will have a
    partnership with ARM so the processors can run ARM64 code as well as
    the three legacy 360 modes. That tells me they're trying to get
    customers who already have the ARM code running in the cloud at AWS or
    Azure.

    Will be interesting to see how it plays out. The Neoverse IP is
    fairly straightforward to integrate into an existing SoC.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 15:36:55 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Tue, 3 Nov 2026 20:53:29 +0000, David Wade wrote:

    On 03/11/2026 20:25, Lawrence DrCOOliveiro wrote:

    Imagine trying to run a full-screen editor that way: it just
    wouldnrCOt work. The app really needed to be able to respond to every
    keystroke in order to maintain the necessary level of interactive
    response. Minis (and later superminis, like the VAX) had it all
    over mainframes in that regard.

    Why? I don't need to imagine, I did it all the time. Its not a
    problem. The editor generates a screen full of data. The controller
    handles most of the character editing so you change the local buffer
    which does see every key stroke. At some point you send the modified
    screen back to the host.

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but
    then I am more familiar with it.

    Neither one had an incremental-search function like the one in Emacs
    though, did they?

    Probably not. That didn't make them useless. As it happens, I
    personally disable incremental search features in vim; I dislike
    that particular feature immensely.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 15:42:06 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Tue, 3 Nov 2026 05:28:52 -0800, Lars Poulsen wrote:

    By the time of VMS, there was a new paradigm, where you could push
    the pre-processing out to the terminal cluster: The TTY device in
    the OS had mode bitmasks, specifying for each character whether it
    should be echoed and whether it should generate a read completion
    interrupt.

    You realize, all this was done in *software* in the terminal driver,
    not in the terminal controller?

    In my experience with VAX 11/780 installations, it was common
    to use a 'terminal controller' (typically a PDP-11/40) as
    a front-end to the VAX cluster (which allowed any terminal
    on campus to connect to any of the VAXen or to Wylbur).


    So yes, the CPU was still getting an interrupt on every incoming
    character.

    Unix got a similar set of modes controlled with the stty command and
    its associated ioctl system calls, but I don't think I have ever
    seen these succesfully be used to put the TTY pre-processing in a
    remote front-end controller, like VMS could.

    Unix never had a terminal driver as advanced as VMS did, that is true.

    IIRC, there were several solutions to this issue in the heyday
    of proprietary unix systems.

    And I'd argue with the 'as advanced as VMS' statement as well.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 09:09:38 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 20:12, John Levine wrote:
    According to Pancho <Pancho.Jones@protonmail.com>:
    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one
    succeeded and the other failed*, your bank has a problem. The reason they >>> need very fast very large databases is that updates have to be serialized >>> and there's no way to make them faster than the underlying system. Same >>> for airlines allocating seats and any other database reflecting a real world
    application where there's a finite amount of something to be parcelled out. >>>


    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with
    me, it can be done in parallel.

    Sure, but you're not going to put every account on a different disk. Real transactions are more complicated than that -- when they take the $75 out of my
    account they have to credit it somewhere else, and that debit/credit pair has to
    be atomic, both work or both fail.

    Banks are conservative but they are not stupid. There's a lot of stuff they can
    push out onto cheap micro based servers, but there's a certain amount of key business logic that Absolutely Has To Work.

    Banking is a simplistic application anyhow. Most applications need to
    update multiple records in a database atomically.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 09:11:58 2026
    From Newsgroup: comp.unix.shell

    On 11/3/26 20:30, c186282 wrote:
    On 11/3/26 18:18, Pancho wrote:
    On 11/3/26 22:47, John Levine wrote:
    According to Pancho-a <Pancho.Jones@protonmail.com>:
    I know at least one guy working on IBM mainframes, and he tells me >>>>>>> they are in high need of good assembler programmers.

    They need high i/o with very large databases.
    ...

    Traditional banking transactions almost certainly could be
    parallelised,
    to quite a high degree, whether they were or not, I don't know. They
    are
    nowadays.

    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one
    succeeded and the other failed*, your bank has a problem.-a The reason
    they
    need very fast very large databases is that updates have to be
    serialized
    and there's no way to make them faster than the underlying system.-a Same >>> for airlines allocating seats and any other database reflecting a
    real world
    application where there's a finite amount of something to be
    parcelled out.



    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do
    with me, it can be done in parallel.

    -a NOTICED - my principal bank - a LOT of transactions
    -a come up with a "pending" label. Might take DAYS. This
    -a is not some 3rd-tier bank either.

    -a Two or more larger credit/debit card charges, not
    -a sure HOW they 'compete' in that system. If too
    -a near each other one MIGHT get bumped. Problem !

    -a In short, even 'online/instant' banking may not
    -a be THAT instant.

    Some of this is communication between banks, and some is your bank
    milking the float for as long as is legally allowed.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 00:13:42 2026
    From Newsgroup: comp.unix.shell

    On 11/4/2026 10:36 PM, Peter Flass wrote:
    On 11/3/26 13:27, The Natural Philosopher wrote:
    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year.-a-a The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys
    mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    -a-a-a-a-a-a-a-a Valued at approximately $5.33 billion to $5.71 billion in 2025.
    -a-a-a-a-a-a-a-a Projected to grow to $5.65 billion to $6.11 billion in 2026.
    -a-a-a-a-a-a-a-a Forecasted to reach $7.54 billion to $10.53 billion by
    2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    -a-a-a-a-a-a-a-a Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4 >> mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    -a-a-a-a-a-a-a-a Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred
    purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident
    armchair experts


    My only question is how many mainframe shipments represent NEW
    customers, as opposed to additional horsepower for current customers.

    I suppose, given that the trend today is to consolidation of everything, that eventually everything will be owned by BigCorp, who will then be
    the only mainframe customer.

    INC Inc, no doubt; welcome to the /Head Office/.

    https://www.youtube.com/watch?v=bAVXp1oGjHA

    It will not only be the only mainframe manufacturer, it'll sell its own subdivisions the mainframe at double the price.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 09:20:00 2026
    From Newsgroup: comp.unix.shell

    On 11/4/26 03:27, Carlos E. R. wrote:
    On 2026-11-04 00:05, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 22:44:10 +0000, David Wade wrote:

    On 03/11/2026 21:57, Lawrence DrCOOliveiro wrote:

    Neither one had an incremental-search function like the one in
    Emacs though, did they? That updates the display in real-time,
    after every keystroke, highlighting all the visible matches for the
    string as yourCOve typed it so far.

    no, but how often do you use that?

    Every day.

    I'm told that most people do not work directly on a terminal on the mainframe. There is not an OS proper...


    You're told wrong.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Ahlstrom@OFeem1987@teleworm.us to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 11:32:22 2026
    From Newsgroup: comp.unix.shell

    Peter Flass wrote this screed in ALL-CAPS (fixed):

    On 11/3/26 13:25, Lawrence DrCOOliveiro wrote:
    On Tue, 3 Nov 2026 09:28:46 +0000, David Wade wrote:

    I think you misunderstand "mainframes" or at least IBM Mainframes.
    The Mainframe never "saw" keystrokes, they were handled in the
    terminal controller so there never was any possibility of the
    dreaded "type-behind" one saw on an over-loaded VAX.

    ThatrCOs part of what contributed to mainframes having less support
    for interactive operation compared to minis.

    Because the Mainframe only sees blocks of typing there are fewer
    interrupts and less paging so interactive response is generally as
    good as or better than a mini.

    ThatrCOs only if you assume rCLblock moderCY operation. Typical mainframe
    thinking: more efficient use of the computer, less efficient for the
    human user.

    Imagine trying to run a full-screen editor that way: it just wouldnrCOt
    work. The app really needed to be able to respond to every keystroke
    in order to maintain the necessary level of interactive response.
    Minis (and later superminis, like the VAX) had it all over mainframes
    in that regard.

    I violently disagree. Full screen editors provide instant response to
    most operations: Move the cursor around, add, delete, and change text. There's only a delay when you're done editing that screen and want to
    move on to something else. On a well-tuned system this is a slight delay.

    IIRC, the HP system I used in a lab in the late 1980s had a
    monitor where you would edit until the screen had what you wanted,
    then press a key to send it to the minicomputer.

    It just occurred to me that I'm typing this text into a mail app which
    is basically the same thing. I can edit all I want, and then press SEND
    when I'm done.

    Maybe it's my mainframe background, but I think having "the computer" respond instantly to every keystroke is just stupid.

    I demand instant response!
    --
    It is like saying that for the cause of peace, God and the Devil will
    have a high-level meeting.
    -- Rev. Carl McIntire, on Nixon's China trip
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 18:52:04 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 17:32, Chris Ahlstrom wrote:
    Peter Flass wrote this screed in ALL-CAPS (fixed):
    [...]
    It just occurred to me that I'm typing this text into a mail app which
    is basically the same thing. I can edit all I want, and then press SEND
    when I'm done.

    Maybe it's my mainframe background, but I think having "the computer"
    respond instantly to every keystroke is just stupid.

    I demand instant response!

    Yes, but note that "the computer" was written in quotes. That's why I interpreted it (in the sense of most valuations in the thread) that he
    wants to express that the main CPU of a mainframe shouldn't be engaged
    in a response to "every keystroke". The terminal would certainly do all
    the necessary instant response. Or, with his analogon of a news client,
    while typing text the news server is not involved until you hit "Send"
    but you still see the effects your text writing/editing instantly.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:18:26 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 04:23, c186282 wrote:
    On 11/3/26 21:16, Janis Papanagnou wrote:
    [...]
    My children actually work "in science" where extremely
    demanding complex (hydrodynamic) simulation models are
    done; all done on such high-performance clusters. And
    this appears to be nowadays quite common as observable.

    -a Umm ... your KIDS are into hydrodynamics ? Are
    -a they 'kids' anymore ?

    Sorry, I'm a non-native speaker, and we colloquially still
    talk about "our kids" hereabouts even though they are adult.

    It's actually nice if we not only have own insights into the
    topic from former times but also have first-hand contemporary
    information from our "kids". It lets us compare which things
    have changed meanwhile and which principles still apply.

    [...]

    There had always been non-local access, even back in
    the mainframe days.

    -a Yep - happened. However it's easier to guard/armor
    -a ONE mainframe than a vast network.

    It's not only "happening"; what I was referring to was that
    services of computing centers were used through remote access
    by companies and institutes in the whole state.

    But I understand what you meant; and I principally agree. We
    sadly see the issues nowadays and extremely wide-spread, and
    in areas where it's even arguable why systems are connected
    through the Net in the first place. An actual attack case here
    is that _cooling_ shelves of supermarkets all over the country
    have been remotely reprogrammed to heat-up the goods up to 50-#C;
    literally tons of food spoiled and needed to be disposed.

    The "IoT" (Internet of Things) I consider a nightmare, as far
    the the remote control is concerned, but also the sensoring of
    data from private domains and transfer into "clouds"!


    There's a more general problem here; whether a single
    "box" or a "cluster", if it's connected to the Net it
    has to be solidified.

    -a DOES require a lot of 'solidification' - esp now.

    -a Otherwise you're just working for your worst enemies.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 18:24:01 2026
    From Newsgroup: comp.unix.shell

    It appears that c186282 <c186282@nnada.net> said:
    On 11/3/26 23:15, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    I can assure you that PDP-11s were minicomputers. I spent quite a while >>>> programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.

    Kinda true.

    However 'minis' were SUPPOSED to do everything
    mainframes could do - just a a DISCOUNT PRICE.

    Again, I was there, and that's nonsense. They were sold into
    different markets. DEC's original markets were labs and communication
    and other things that the mainframes of the era did not do. I do not
    ever recall a mini as being advertised as even sort of like a
    mainframe, since they obviously weren't/

    A VAX was a super-mini, not a mainframe. I was there.
    Again, simpler I/O even though it was a lot bigger than
    a PDP-8 or PDP-11.

    Ummmmm ... I suspect we're dealing with
    slightly different defs of 'mainframe'
    and 'mini' and whatever. There is NO
    clear line.

    At the time we didn't have any trouble telling the difference. If you
    want to retroactively redefine your terms, well, that's on you.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 18:28:27 2026
    From Newsgroup: comp.unix.shell

    According to c186282 <c186282@nnada.net>:
    On 11/4/26 02:10, Lawrence DrCOOliveiro wrote:
    On Wed, 04 Nov 2026 06:21:03 GMT, Charlie Gibbs wrote:

    Mainframes were record-oriented, while minis were byte-oriented.

    Maybe better to say rCLminis were character-orientedrCY. Remember DEC had
    18-bit and 12-bit minicomputer architectures before IBM even invented
    the term rCLbyterCY.

    Well, the 'standard' 8-bit byte kind of evolved, or converged.

    Nope. Before S/360 there were word addressed scientific computers and
    character or digit (decimal digit) addressed commercial machines. The
    IBM 7030 STRETCH was a one-off with 64 bit words and overimplemented
    bit level variable sized byte addressing.

    Then the 360 came out with 8 bit byte addressing and after that it
    wasn't long before we all know that word and digit addressed machines
    had no future.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:45:15 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 12:25, The Natural Philosopher wrote:
    On 04/11/2026 02:23, Janis Papanagnou wrote:
    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should
    meanwhile be at "best" a niche, and systems programming
    with "C" (or similar).

    You don't know what IBM assembler is, do you?

    "IBM assembler" specifically? No. - I know (and programmed in) a
    couple other "high-level" macro-assemblers. - Do you imply that
    the "IBM assembler" is somehow special, and so different that it
    would somehow invalidate what I said?


    But, yes. It was now for long a problem getting staff for
    legacy things. Those companies who are too inert to adapt
    [to the technical evolution] will pay, suffer, or demise.

    You don't really know what you are talking about, do you?

    I certainly do. - But, given your post, I doubt you intend to
    contribute any substance and prefer just playing the troll.
    (With your stance I don't think it's worthwhile to respond to
    you in future.) Good luck.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 03:33:09 2026
    From Newsgroup: comp.unix.shell

    On 11/5/2026 2:45 AM, Janis Papanagnou wrote:
    On 2026-11-04 12:25, The Natural Philosopher wrote:
    On 04/11/2026 02:23, Janis Papanagnou wrote:
    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should
    meanwhile be at "best" a niche, and systems programming
    with "C" (or similar).

    You don't know what IBM assembler is, do you?

    "IBM assembler" specifically? No. - I know (and programmed in) a
    couple other "high-level" macro-assemblers. - Do you imply that
    the "IBM assembler" is somehow special, and so different that it
    would somehow invalidate what I said?


    But, yes. It was now for long a problem getting staff for
    legacy things. Those companies who are too inert to adapt
    [to the technical evolution] will pay, suffer, or demise.

    You don't really know what you are talking about, do you?

    I certainly do. - But, given your post, I doubt you intend to
    contribute any substance and prefer just playing the troll.
    (With your stance I don't think it's worthwhile to respond to
    you in future.) Good luck.

    Janis

    Dear philosopher of nature,

    I am delighted you've met one of the trolls of comp.lang.c -- though
    that group was not cross posted this time -- and you have been found
    wanting. Of what, I'm not sure, because from my point of view, it's
    Janis whose lack of social skills has deteriorated this discussion into mud-slinging.

    Do I have something to say on this subject? No, not really; I just find
    it amusing when trolls accuse other people of being trolls, and then, presumably, killfile the person. Consider it "trash taking itself out."


    Best wishes, and happy philosophering of natural phenomena!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kerr-Mudd, John@admin@127.0.0.1 to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:48:01 2026
    From Newsgroup: comp.unix.shell

    On Mon, 2 Nov 2026 03:56:39 -0500
    c186282 <c186282@nnada.net> wrote:

    []

    DOOM and DUKE NUKEM were great. QUAKE ... it
    was mostly BLACK SCREEN shit, why bother having
    a monitor ???

    Still have DUKE stashed away somewhere, runs in
    DOSBox. Lots of user-created episodes too. For one
    I had to write a 256 bit binary-2-decimal calculator :-)

    https://dnr.duke4.net/maps.php.html https://rtcm.site/knowledge-base/downloads-rtcm/duke3d-maps/ https://hrp.duke4.net/download.php

    especially the "addons" pack.
    --
    Bah, and indeed Humbug.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:51:29 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, Chris Ahlstrom <OFeem1987@teleworm.us> wrote:

    Peter Flass wrote this screed in ALL-CAPS (fixed):

    Maybe it's my mainframe background, but I think having "the computer"
    respond instantly to every keystroke is just stupid.

    I can understand that. The overhead involved with dealing with every
    character coming in from multiple terminals can be considerable.
    Given the CPU power we had back in the day (maybe 130 KIPS for a small-to-middling mainframe), it would bring the machine to its knees.

    I demand instant response!

    Given typical mainframe protocols of the day (bisync, half-duplex,
    multidropped terminals that get polled maybe once a second), you're
    not going to get that even if you had all the CPU power in the world.

    I remember reading about an experiment done in an IBM shop where
    they shoveled in enough hardware and tweaked the protocols so that
    terminal users got sub-second response time. Apparently it increased throughput even more than one would expect by just scaling the
    response time - users could develop a rhythm and not have their
    minds wander while waiting for a response.

    On the other side of the coin, someone at Univac decided that
    the key to productivity was not so much a quick response time
    as a consistent one - which led to their system inserting
    delays if a response was ready too soon. :-p
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:51:30 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    And if you think the fruit vendor is better, you can rest easy, because
    at one time they refused to update my card number. Actually refused.
    After reaching the /right/ support person, that person could not help
    figure out why the website told me the card number had been updated, but
    then the TV application always tried to use the old card number.

    Ah, you've been around the mulberry bush with Netflix too, I presume.
    We recently found we couldn't log in to Netflix because they didn't
    like our card number - and quoted the last four digits and date of
    a card that expired seven years ago. I wonder how they had managed
    to bill us the previous month.

    I called their customer support line, and the droid became downright belligerent, claiming that it wasn't their fault but our bank's.
    I wound up hanging up on him, and we cancelled our Netflix account.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:51:31 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 11/3/26 13:29, Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 12:45:09 +0100, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    Something not quite right there. Hand-coded assembly language only
    makes sense for minimizing CPU usage. If yourCOre doing lots of I/O,
    then the CPU is not the bottleneck, so trying to hand-tune assembly
    code is a waste of time.

    I kind of agree. As a former assembler programmer - at one time it was
    my first language - I'd like it to be true (although I'm out of the job market), but I can't see it. These days most HLL code is more optimized than a lot of assembler. A good assembler programmer would not make a
    lot of these optimizations due to lack of readability.

    A mediocre assembly language programmer would not let lack of
    readability stand in the way. And once you get into self-modifying
    code there are all sorts of horrible things you can do.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:51:32 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, The Natural Philosopher <tnp@invalid.invalid> wrote:

    On 04/11/2026 09:58, Carlos E. R. wrote:

    You could get 9600-bps modems, but they were ten grand a pop.
    And the leased line wasn't cheap either.-a As ever, we balanced
    price against performance.

    And we were told that 9600 was the limit, the theory said so. I think it
    was 9600.

    for one type of technology, it was...

    The mainframe I worked on could do async (although nobody
    ever did) - but since Everybody Knows that async is a
    low-speed protocol the ports weren't designed to run async
    any faster than 2400 bps, even for direct connections.

    Didn't part of the RS-232 spec say that wiring had to handle
    50-foot runs at 9600 bps? Given cable capacitance it could
    be a crap shoot, but we managed to get async terminals
    (or emulators on PCs) to talk to a Sun workstation at the
    other end of the building at 38400 bps.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:51:33 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 11/3/26 13:53, David Wade wrote:

    Personally I prefer the XEDIT the VM/CMS editor to the VMS one, but then
    I am more familiar with it.

    I also like XEdit, in fact I run THE on my PC, although it is not my
    primary editor. VAX TPU is also quite good, however, but we had great response time on our VAX.

    I used XEDIT a bit and got along with it reasonably well.
    Under MS-DOS I used KEDIT, which was similar.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:59:19 2026
    From Newsgroup: comp.unix.shell

    On 11/4/26 14:54, Peter Flass wrote:
    On 11/3/26 15:15, Pancho wrote:

    If you want heavy usage, I would guess bank risk calcs, weather calcs,
    lots of science applications, running on compute grids, (or whatever
    the modern word is), blow this mainframe high i/o away.

    I think back in the day the quants preferred Sun.


    Not really,-quants used Excel on PCs. Lotus123 ran on Sun, but it was
    second rate. I think prior to Windows NT some IT departments gambled on
    Sun, which had a proper OS, rather than PCs, but it quickly became
    obvious it was a poor choice.

    There was also a buzz about RISC cpus replacing x86, which to be fair
    now seems to be happening, just 35 years late.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 04:48:49 2026
    From Newsgroup: comp.unix.shell

    On 11/5/2026 3:51 AM, Charlie Gibbs wrote:
    On 2026-11-04, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    And if you think the fruit vendor is better, you can rest easy, because
    at one time they refused to update my card number. Actually refused.
    After reaching the /right/ support person, that person could not help
    figure out why the website told me the card number had been updated, but
    then the TV application always tried to use the old card number.

    Ah, you've been around the mulberry bush with Netflix too, I presume.
    We recently found we couldn't log in to Netflix because they didn't
    like our card number - and quoted the last four digits and date of
    a card that expired seven years ago. I wonder how they had managed
    to bill us the previous month.

    I called their customer support line, and the droid became downright belligerent, claiming that it wasn't their fault but our bank's.
    I wound up hanging up on him, and we cancelled our Netflix account.


    I have not had that experience with Netflix to my recollection, but I
    have /scolded/ customer service representatives when they try to gas-
    light me about my card being at fault, when I can clearly see the zero
    dollar verification, and then /nothing/ in my bank statement.

    Their customer service spiel is not at all willing to admit their pay-
    ment processing service can possibly be at fault. They /will/ gaslight
    you that your card is somehow out of balance or expired, or something.

    Full disclosure: I'm not sure if I had that experience with Netflix.

    And for some reason, the "big merchants" -- I believe last time for me
    was Microsoft -- are able to continue to bill expired card numbers. I
    don't know how they get away with it. Then, of course, Microsoft re-
    fused to update the card number. The customer service was of no help.

    That was several years ago, with a subscription I sort of happily "un- subscribed" because they didn't want it anyway. My previous gripe was
    more recent.


    Thank you for coming to my extended payment processing rant here in alt. folklore.computers!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 05:02:15 2026
    From Newsgroup: comp.unix.shell

    On 11/5/2026 3:51 AM, Charlie Gibbs wrote:
    On 2026-11-04, Chris Ahlstrom <OFeem1987@teleworm.us> wrote:

    Peter Flass wrote this screed in ALL-CAPS (fixed):

    Maybe it's my mainframe background, but I think having "the computer"
    respond instantly to every keystroke is just stupid.

    I can understand that. The overhead involved with dealing with every character coming in from multiple terminals can be considerable.
    Given the CPU power we had back in the day (maybe 130 KIPS for a small-to-middling mainframe), it would bring the machine to its knees.

    I demand instant response!

    Given typical mainframe protocols of the day (bisync, half-duplex, multidropped terminals that get polled maybe once a second), you're
    not going to get that even if you had all the CPU power in the world.

    I remember reading about an experiment done in an IBM shop where
    they shoveled in enough hardware and tweaked the protocols so that
    terminal users got sub-second response time. Apparently it increased throughput even more than one would expect by just scaling the
    response time - users could develop a rhythm and not have their
    minds wander while waiting for a response.

    On the other side of the coin, someone at Univac decided that
    the key to productivity was not so much a quick response time
    as a consistent one - which led to their system inserting
    delays if a response was ready too soon. :-p


    And nowadays, we have that kind of stuff artificially. Some websites, I
    can name Facebook for an example, will put so much JavaScript in the
    text editor, that you can wait for quite a few seconds before the text
    starts to show up. This is the major reason I simply deleted my FB acc-
    ount. Zuckerberg is not going to pay for a new computer -- not for me
    -- and there were only a handful of websites that did this; I also del-
    eted at least one more account for the same reason.

    Now, some people may think this is /OK/, and I should just not be poor
    and afford a new computer -- or change my operating system from Windows
    10; or use another browser -- but I take the stand that Zuckerberg is
    not paying for my power bill either, and having a website or an appli-
    cation that eats my battery charge visibly is not welcome.

    These situations persist because people have been accustomed to accept
    this as /normal/. I keep maintaining this is not normal behaviour on
    the part of regular websites or applications. After all, Visual Studio
    Code infamously used 13% CPU for blinking the cursor.


    https://www.reddit.com/r/programming/comments/612v99/vs_code_uses_13_cpu_when_idle_due_to_blinking/



    Thank you for coming to my inefficiency rant in alt.folklore.computers!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich Alderson@news@alderson.users.panix.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 16:44:40 2026
    From Newsgroup: comp.unix.shell

    John Levine <johnl@taugh.com> writes:

    [ snip ]

    If you look through the comp.arch archives you'll find arguments about whether a PDP-10 was a mainframe or a very large mini. I claim it was a mini because its I/O was similar to DEC's other minis, including a hack reminiscent of three-cycle data break. Others say it was a mainframe because it was marketed that way.

    Mainframe computers did I/O the same way before the channel notion came along. Look, for example, at the IBM 1400 and 7xx/7xxx series.

    I will admit that the later KL with a PDP-11 front end and MASSBUS disk I/O was a lot more like a mainframe than the original KA-10.

    The PDP-6 was marketed as a mainframe in 1964, announced 3 weeks before the System/360 and delivered more than a year before the IBM system.

    Channels do not make a mainframe, nor does direct I/O control make a mini.
    --
    Rich Alderson news@alderson.users.panix.com
    Audendum est, et veritas investiganda; quam etiamsi non assequamur,
    omnino tamen proprius, quam nunc sumus, ad eam perveniemus.
    --Galen --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 21:45:07 2026
    From Newsgroup: comp.unix.shell

    On Wed, 4 Nov 2026 07:48:39 -0700, Peter Flass wrote:

    You can't distribute an airline reservation system, the data has to
    live in one place.

    Sure you can. Distributed databases do exist, you know.

    (Subject, of course, to the limitations of the CAP Theorem.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 21:47:21 2026
    From Newsgroup: comp.unix.shell

    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written
    in C, with very little assembly language.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich Alderson@news@alderson.users.panix.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 16:50:11 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:

    On Wed, 04 Nov 2026 06:21:03 GMT, Charlie Gibbs wrote:

    Mainframes were record-oriented, while minis were byte-oriented.

    Maybe better to say "minis were character-oriented". Remember DEC had
    18-bit and 12-bit minicomputer architectures before IBM even invented
    the term "byte".

    ITYM "IBM even adopted the term 'byte' from the telecom industry." Prior to IBM's cooptation of the term, the word "byte" referred to any grouping of continguous bits in a signal string. This older definition is what was adopted into the PDP-6/PDP-10 instruction set, with byte pointers that include the size as well as the position of the starting bit within a word.
    --
    Rich Alderson news@alderson.users.panix.com
    Audendum est, et veritas investiganda; quam etiamsi non assequamur,
    omnino tamen proprius, quam nunc sumus, ad eam perveniemus.
    --Galen --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 21:50:46 2026
    From Newsgroup: comp.unix.shell

    On Wed, 4 Nov 2026 07:52:35 -0700, Peter Flass wrote:

    On 11/3/26 14:57, Lawrence DrCOOliveiro wrote:

    Neither one had an incremental-search function like the one in
    Emacs though, did they? That updates the display in real-time,
    after every keystroke, highlighting all the visible matches for the
    string as yourCOve typed it so far.

    I find this more distracting than useful.

    You do, others donrCOt.

    Let me type my search, including correcting inevitable typos, etc.
    and then run it instead of continually flashing the screen at me as
    I type.

    Except you may not notice your typos until you see what does or
    doesnrCOt match the search. ThatrCOs why the immediate feedback is useful.

    Now try doing it with a regular-expression search ...

    Why would this be a problem? "Yes, ISPF View and Edit support regular expressions."

    But they are even more difficult to get right. Which is why the
    immediate feedback becomes even more useful.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 21:52:52 2026
    From Newsgroup: comp.unix.shell

    On Wed, 4 Nov 2026 10:58:41 +0100, Carlos E. R. wrote:

    And we were told that 9600 was the limit, the theory said so. I
    think it was 9600.

    The theoretical information capacity of an analog telephone line was
    always known to be close to 64kbps. Remember, it was Bell Labs, part
    of AT&T the US phone company, that invented most of the basis of
    information theory in the first place.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 22:22:06 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written
    in C, with very little assembly language.

    Again with the incorrect characterizations.

    The fastest supercomputers are running massive amounts of
    modern (and some ancient) Fortran code.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 00:14:16 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 22:47, Lawrence DrCOOliveiro wrote:
    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written
    in C, with very little assembly language.

    Well, I know for a fact that this machine doesn't run any standard OS. I
    asked him. Also, the disks do not have a filesystem, either (I also
    asked). Of course most of the programmers work in some high level
    language, but there are certain critical operations that are optimized
    in assembler. I don't remember which, and obviously I'm not going to
    quote him breaking confidence. But if anyone is a good programmer in
    those machines, in assembler, they are hiring.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 00:19:11 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04 20:51, Charlie Gibbs wrote:
    On 2026-11-04, The Natural Philosopher <tnp@invalid.invalid> wrote:

    On 04/11/2026 09:58, Carlos E. R. wrote:

    You could get 9600-bps modems, but they were ten grand a pop.
    And the leased line wasn't cheap either.-a As ever, we balanced
    price against performance.

    And we were told that 9600 was the limit, the theory said so. I think it >>> was 9600.

    for one type of technology, it was...

    The mainframe I worked on could do async (although nobody
    ever did) - but since Everybody Knows that async is a
    low-speed protocol the ports weren't designed to run async
    any faster than 2400 bps, even for direct connections.

    Didn't part of the RS-232 spec say that wiring had to handle
    50-foot runs at 9600 bps? Given cable capacitance it could
    be a crap shoot, but we managed to get async terminals
    (or emulators on PCs) to talk to a Sun workstation at the
    other end of the building at 38400 bps.


    I got my PC to talk to another PC at 118K with a serial port across
    perhaps 20 metres, in the 90's.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 01:18:29 2026
    From Newsgroup: comp.unix.shell

    On Thu, 5 Nov 2026 00:14:16 +0100, Carlos E. R. wrote:

    Also, the disks do not have a filesystem, either (I also asked).

    Programming like itrCOs 1975
    <https://vinyl-cache.org/docs/9.1/phk/notes.html>:

    So whatrCOs wrong with 1975 programming ?

    The really short answer is that computers do not have two kinds of
    storage anymore.

    ...

    Virtual memory was meant to make it easier to program when data
    was larger than the physical memory, but people have still not
    caught on.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 01:20:34 2026
    From Newsgroup: comp.unix.shell

    On Wed, 4 Nov 2026 08:26:56 +0000, Pancho wrote:

    Not something I ever did, but I strongly suspect it is message
    queues, including acknowledgements. Tricky to get perfect, but
    standard IT stuff.

    <https://kafka.apache.org/44/design/design/>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 01:24:38 2026
    From Newsgroup: comp.unix.shell

    On Thu, 5 Nov 2026 00:19:11 +0100, Carlos E. R. wrote:

    I got my PC to talk to another PC at 118K with a serial port across
    perhaps 20 metres, in the 90's.

    Apple Mac serial ports using the Zilog Z8530 SCC could run at
    230.4kbps, or 1Mbps with external clocking. That was from 1984.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:02:09 2026
    From Newsgroup: comp.unix.shell

    On 11/4/26 12:51, Charlie Gibbs wrote:
    On 2026-11-04, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 11/3/26 13:29, Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 12:45:09 +0100, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    Something not quite right there. Hand-coded assembly language only
    makes sense for minimizing CPU usage. If yourCOre doing lots of I/O,
    then the CPU is not the bottleneck, so trying to hand-tune assembly
    code is a waste of time.

    I kind of agree. As a former assembler programmer - at one time it was
    my first language - I'd like it to be true (although I'm out of the job
    market), but I can't see it. These days most HLL code is more optimized
    than a lot of assembler. A good assembler programmer would not make a
    lot of these optimizations due to lack of readability.

    A mediocre assembly language programmer would not let lack of
    readability stand in the way. And once you get into self-modifying
    code there are all sorts of horrible things you can do.


    1. "standard" things like converting a branch to a nop or back. I know
    1401 Autocoder people used to do horrible things like using part of an instruction as a constant.
    2. You can do anything as long as you comment it. I once had a sequence
    to test-store-conditional branch, for some reason I don't recall, bit I
    tagged it with comments saying "these three instructions must be kept together".

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 4 19:04:22 2026
    From Newsgroup: comp.unix.shell

    On 11/4/26 12:59, Pancho wrote:
    On 11/4/26 14:54, Peter Flass wrote:
    On 11/3/26 15:15, Pancho wrote:

    If you want heavy usage, I would guess bank risk calcs, weather
    calcs, lots of science applications, running on compute grids, (or
    whatever the modern word is), blow this mainframe high i/o away.

    I think back in the day the quants preferred Sun.


    Not really,-quants used Excel on PCs. Lotus123 ran on Sun, but it was
    second rate. I think prior to Windows NT some IT departments gambled on
    Sun, which had a proper OS, rather than PCs, but it quickly became
    obvious it was a poor choice.

    There was also a buzz about RISC cpus replacing x86, which to be fair
    now seems to be happening, just 35 years late.

    x86 is RISC under the hood. Too bad programmers can't get at it and have
    to deal with the cr*p instruction set.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 03:34:03 2026
    From Newsgroup: comp.unix.shell

    On Wed, 4 Nov 2026 19:04:22 -0700, Peter Flass wrote:

    x86 is RISC under the hood.

    ThatrCOs nonsense. ThatrCOs Intel/AMD PR talking.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 06:27:18 2026
    From Newsgroup: comp.unix.shell

    On Thu, 5 Nov 2026 03:34:03 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Wed, 4 Nov 2026 19:04:22 -0700, Peter Flass wrote:

    x86 is RISC under the hood.

    ThatrCOs nonsense. ThatrCOs Intel/AMD PR talking.

    What do you call micro-operations?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 08:19:58 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, Pancho wrote:

    On 11/4/26 03:12, John Levine wrote:
    According to Pancho <Pancho.Jones@protonmail.com>:
    Only up to a point. Making the read part of databases run in parallel
    is easy. Making the write part is not.

    If you have $100 in your bank account, and two $75 debit transactions
    arrive at the same time, if the result is anything other than that one >>>> succeeded and the other failed*, your bank has a problem. The reason they >>>> need very fast very large databases is that updates have to be serialized >>>> and there's no way to make them faster than the underlying system. Same >>>> for airlines allocating seats and any other database reflecting a real world
    application where there's a finite amount of something to be parcelled out.



    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with >>> me, it can be done in parallel.

    Sure, but you're not going to put every account on a different disk. Real
    transactions are more complicated than that -- when they take the $75 out of my
    account they have to credit it somewhere else, and that debit/credit pair has to
    be atomic, both work or both fail.


    Not something I ever did, but I strongly suspect it is message queues, including acknowledgements. Tricky to get perfect, but standard IT
    stuff.

    Banks are conservative but they are not stupid. There's a lot of stuff they can
    push out onto cheap micro based servers, but there's a certain amount of key >> business logic that Absolutely Has To Work.


    Absolutely has to work, means testing. That is why they keep the old
    stuff, it has been tested, in production.

    Newer system reliability will be almost entirely about software
    design, better techniques, but testing is difficult.

    We recently had a scandal in the UK, the Post Office, shocking flaws
    in design, from the mid 1990s, but over the years they caught most of
    the bugs and made it work.

    At the same time they kept prosecuting innocent people for it, right?

    A superficial look at the news reports
    showed they weren't using things like idempotent operations. Modern
    systems are designed to be much more tolerant of hardware glitches.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 08:27:32 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, John Levine wrote:

    According to c186282 <c186282@nnada.net>:
    * - yes I know about overdrafts, this is an example

    Erm, yep, sequential transactions on my account, but why does everyone
    else's account need to be on the same database/compute server as my
    account? If A and B are doing a transaction, that has nothing to do with >>> me, it can be done in parallel.

    NOTICED - my principal bank - a LOT of transactions
    come up with a "pending" label. Might take DAYS. This
    is not some 3rd-tier bank either.

    That has nothing to do with your bank's database and everything to do
    with the way that credit card charges work. First the charge is
    approved for an approximate amount which is pretty quick, then the
    actual charge is posted which can take anywhere from moments to days.
    The amounts are often different, e.g., when you pump gas it approves
    an amount big enough to cover the largest plausible fill-up, then when
    you're done it posts the final amount. Or at a restaurant, it approves
    the amount on the check, then posts that plus whatever tip you add.

    Possibly all off-line cards and not just credit cards? Although I've
    also seen purportedly on-line cards behave in similar ways. Or maybe
    it's the *initial* approval that may be deferred for off-line cards?

    For historic reasons it's common to wait to post all of a day's
    charges at the end of the day, or even later which is why they can sit
    there pending for a while.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 08:59:47 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-04, Lawrence DrCOOliveiro wrote:

    On Wed, 4 Nov 2026 07:52:35 -0700, Peter Flass wrote:

    On 11/3/26 14:57, Lawrence DrCOOliveiro wrote:

    Neither one had an incremental-search function like the one in
    Emacs though, did they? That updates the display in real-time,
    after every keystroke, highlighting all the visible matches for the
    string as yourCOve typed it so far.

    I find this more distracting than useful.

    You do, others donrCOt.

    Let me type my search, including correcting inevitable typos, etc.
    and then run it instead of continually flashing the screen at me as
    I type.

    Except you may not notice your typos until you see what does or
    doesnrCOt match the search. ThatrCOs why the immediate feedback is useful.

    Not really much relevant, you can see the mistake the same, and,
    depending on what you're dealing with, no immediate search may actually
    be the faster route. (Admittedly an interface problem sometimes, though, especially in "web apps" that are quite slow because each keystroke
    triggers a damn search...)


    Now try doing it with a regular-expression search ...

    Why would this be a problem? "Yes, ISPF View and Edit support regular
    expressions."

    But they are even more difficult to get right. Which is why the
    immediate feedback becomes even more useful.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 09:50:01 2026
    From Newsgroup: comp.unix.shell

    On 11/5/26 08:19, Nuno Silva wrote:


    We recently had a scandal in the UK, the Post Office, shocking flaws
    in design, from the mid 1990s, but over the years they caught most of
    the bugs and made it work.

    At the same time they kept prosecuting innocent people for it, right?


    Yes and no. The software was shit, so gave false figures. Pragmatic users fudged their accounts to allow themselves to keep working, (if
    they disputed the software figures their shops were prevented from
    opening). They were then prosecuted for false accounting, which was
    true. So technically they were guilty, but in a Dilbert sense.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 12:27:51 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-05 02:18, Lawrence DrCOOliveiro wrote:
    On Thu, 5 Nov 2026 00:14:16 +0100, Carlos E. R. wrote:

    Also, the disks do not have a filesystem, either (I also asked).

    Programming like itrCOs 1975 <https://vinyl-cache.org/docs/9.1/phk/notes.html>:

    So whatrCOs wrong with 1975 programming ?

    The really short answer is that computers do not have two kinds of
    storage anymore.

    ...

    Virtual memory was meant to make it easier to program when data
    was larger than the physical memory, but people have still not
    caught on.


    No, simply that the database is written raw to the disk, dispensing with
    a filesystem layer which delays operations.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 15:02:05 2026
    From Newsgroup: comp.unix.shell

    Peter Flass <Peter@Iron-Spring.com> writes:
    On 11/4/26 12:51, Charlie Gibbs wrote:
    On 2026-11-04, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 11/3/26 13:29, Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 12:45:09 +0100, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    They need high i/o with very large databases.

    Something not quite right there. Hand-coded assembly language only
    makes sense for minimizing CPU usage. If yourCOre doing lots of I/O,
    then the CPU is not the bottleneck, so trying to hand-tune assembly
    code is a waste of time.

    I kind of agree. As a former assembler programmer - at one time it was
    my first language - I'd like it to be true (although I'm out of the job
    market), but I can't see it. These days most HLL code is more optimized >>> than a lot of assembler. A good assembler programmer would not make a
    lot of these optimizations due to lack of readability.

    A mediocre assembly language programmer would not let lack of
    readability stand in the way. And once you get into self-modifying
    code there are all sorts of horrible things you can do.


    1. "standard" things like converting a branch to a nop or back. I know
    1401 Autocoder people used to do horrible things like using part of an >instruction as a constant.

    The B300 had a fixed three-operand instruction format. Many
    instructions only used one or two operands, and the programmer
    was _encouraged_ to use the unused operand fields in the
    one and two-operand instructions for temporary (or even
    permanant) storage.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 19:18:00 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-05, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 11/4/26 12:51, Charlie Gibbs wrote:

    On 2026-11-04, Peter Flass <Peter@Iron-Spring.com> wrote:

    I kind of agree. As a former assembler programmer - at one time it was
    my first language - I'd like it to be true (although I'm out of the job
    market), but I can't see it. These days most HLL code is more optimized >>> than a lot of assembler. A good assembler programmer would not make a
    lot of these optimizations due to lack of readability.

    A mediocre assembly language programmer would not let lack of
    readability stand in the way. And once you get into self-modifying
    code there are all sorts of horrible things you can do.

    1. "standard" things like converting a branch to a nop or back.

    When reading about interfacing assembly language subroutines to
    RPG programs, I noted that indicators were stored in one byte as
    0x00 for off, and 0xF0 for on. I suspected (but never confirmed)
    that this would allow code generated by the RPG compiler to stuff
    the indicator byte into the second byte of a branch instruction,
    which on a 360-style architecture would change it to either a NOP
    or a branch.

    I know 1401 Autocoder people used to do horrible things like using
    part of an instruction as a constant.

    Somewhere in my archives I have a slim pamphlet - I think it was
    part of an official IBM series on Autocoder programming - which
    contained tips and techniques for writing self-modifying code.

    2. You can do anything as long as you comment it. I once had a sequence
    to test-store-conditional branch, for some reason I don't recall, bit I tagged it with comments saying "these three instructions must be kept together".

    Sounds like you were counting on the condition code from the test
    surviving through the store instruction so that the conditional branch
    would properly pick it up. Yes, definitely worth a cautionary note.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 19:57:52 2026
    From Newsgroup: comp.unix.shell

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> schrieb:
    On 2026-11-04, John Levine <johnl@taugh.com> wrote:

    According to c186282 <c186282@nnada.net>:

    I can assure you that PDP-11s were minicomputers. I spent quite a while >>>> programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.
    A 360/30 was considerably slower than a PDP-8, but its
    I/O architecture clearly made it a mainframe.

    I agree. I've always believed that the difference between
    a mainframe and a mini had nothing to do with the size of
    the box, but everything to do with architecture, particularly
    I/O. Mainframes were record-oriented, while minis were
    byte-oriented.

    The PDP-8 was anything but byte-oriented, it was a 12-bit machine.

    Plus, DECTape was block-oriented.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 20:58:56 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 14:36, Peter Flass wrote:
    On 11/3/26 13:27, The Natural Philosopher wrote:
    On 03/11/2026 15:13, Scott Lurndal wrote:
    Actually, the numbers decline every year.-a-a The vast majority are
    legacy installations (particularly for the Burroughs/Univac/Unisys
    mainframes) and there are very few, if any, new customers adopting
    mainframes of any flavor.

    "Global mainframe market size and IBM Z mainframe revenue trends
    highlight a cyclical pattern dominated by multi-year refresh waves (such
    as the z16 and z17 cycles):

    Global Mainframe Market Size:

    -a-a-a-a-a-a-a-a Valued at approximately $5.33 billion to $5.71 billion in 2025.
    -a-a-a-a-a-a-a-a Projected to grow to $5.65 billion to $6.11 billion in 2026.
    -a-a-a-a-a-a-a-a Forecasted to reach $7.54 billion to $10.53 billion by
    2031rCo2034, driven by a compound annual growth rate (CAGR) of roughly
    5.95% to 7.05%.

    IBM Z Mainframe Performance & Fluctuations:
    -a-a-a-a-a-a-a-a Late 2025 (z17 Launch / Q4): IBM reported its strongest Q4 >> mainframe revenue in 20 years, with IBM Z sales surging 67%
    year-over-year as enterprises adopted the z17 architecture.
    -a-a-a-a-a-a-a-a Mid-2026 (Q2): IBM Z mainframe revenue experienced a short-term
    42% year-over-year decline in fiscal Q2 2026 due to delayed large
    capital expenditure (capex) deals and client shifts toward
    supply-constrained servers, though management noted these were deferred
    purchases rather than lost contracts (with roughly one-third closing
    shortly after the quarter)."

    So, as usual, the facts are not correctly represented by the resident
    armchair experts


    My only question is how many mainframe shipments represent NEW
    customers, as opposed to additional horsepower for current customers.

    My only question is how many computer sales are to new users, rather
    than upgrades
    My only question is how many car sales are to new users, rather than
    upgrades
    My only question is how many smartphone sales are to new users, rather
    than upgrades

    Completely specious weasel

    I suppose, given that the trend today is to consolidation of everything, that eventually everything will be owned by BigCorp, who will then be
    the only mainframe customer.

    Oh dear.
    --
    If you tell a lie big enough and keep repeating it, people will
    eventually come to believe it. The lie can be maintained only for such
    time as the State can shield the people from the political, economic
    and/or military consequences of the lie. It thus becomes vitally
    important for the State to use all of its powers to repress dissent, for
    the truth is the mortal enemy of the lie, and thus by extension, the
    truth is the greatest enemy of the State.

    Joseph Goebbels




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:00:08 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 19:51, Charlie Gibbs wrote:
    A mediocre assembly language programmer would not let lack of
    readability stand in the way. And once you get into self-modifying
    code there are all sorts of horrible things you can do.

    IBM macro assembler is about as machine code as COBOL
    --
    If you tell a lie big enough and keep repeating it, people will
    eventually come to believe it. The lie can be maintained only for such
    time as the State can shield the people from the political, economic
    and/or military consequences of the lie. It thus becomes vitally
    important for the State to use all of its powers to repress dissent, for
    the truth is the mortal enemy of the lie, and thus by extension, the
    truth is the greatest enemy of the State.

    Joseph Goebbels




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:01:41 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 14:54, Peter Flass wrote:
    On 11/3/26 15:15, Pancho wrote:

    If you want heavy usage, I would guess bank risk calcs, weather calcs,
    lots of science applications, running on compute grids, (or whatever
    the modern word is), blow this mainframe high i/o away.

    I think back in the day the quants preferred Sun.

    Not for transactuon processing
    --
    In theory, there is no difference between theory and practice.
    In practice, there is.
    -- Yogi Berra

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:05:26 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 19:33, Johann 'Myrkraverk' Oskarsson wrote:
    Do I have something to say on this subject?-a No, not really; I just find
    it amusing when trolls accuse other people of being trolls, and then, presumably, killfile the person.-a Consider it "trash taking itself out."


    Best wishes, and happy philosophering of natural phenomena!

    Thank you.
    --
    rCLIt is hard to imagine a more stupid decision or more dangerous way of making decisions than by putting those decisions in the hands of people
    who pay no price for being wrong.rCY

    Thomas Sowell

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:09:15 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 22:22, Scott Lurndal wrote:
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written >> in C, with very little assembly language.

    Again with the incorrect characterizations.

    The fastest supercomputers are running massive amounts of
    modern (and some ancient) Fortran code.

    Strictly he said 'running Linux, and *that* is mostly written mainly in C' Fortran is perfectly good language for scientific modelling, agreed
    --
    Microsoft : the best reason to go to Linux that ever existed.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:12:55 2026
    From Newsgroup: comp.unix.shell

    On 04/11/2026 23:14, Carlos E. R. wrote:
    On 2026-11-04 22:47, Lawrence DrCOOliveiro wrote:
    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me
    they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written >> in C, with very little assembly language.

    Well, I know for a fact that this machine doesn't run any standard OS. I asked him. Also, the disks do not have a filesystem, either (I also
    asked). Of course most of the programmers work in some high level
    language, but there are certain critical operations that are optimized
    in assembler. I don't remember which, and obviously I'm not going to
    quote him breaking confidence. But if anyone is a good programmer in
    those machines, in assembler, they are hiring.

    My mathematical friend needs to use assembler routines to access some of
    the vector processing that the chipset, but not available C libraries, supports.

    IBM Macro assembler is practically a high level language, given the
    scale of macro usage in legacy systems
    --
    Microsoft : the best reason to go to Linux that ever existed.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 22:22:37 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-05 22:12, The Natural Philosopher wrote:
    On 04/11/2026 23:14, Carlos E. R. wrote:
    On 2026-11-04 22:47, Lawrence DrCOOliveiro wrote:
    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me >>>>>> they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written >>> in C, with very little assembly language.

    Well, I know for a fact that this machine doesn't run any standard OS.
    I asked him. Also, the disks do not have a filesystem, either (I also
    asked). Of course most of the programmers work in some high level
    language, but there are certain critical operations that are optimized
    in assembler. I don't remember which, and obviously I'm not going to
    quote him breaking confidence. But if anyone is a good programmer in
    those machines, in assembler, they are hiring.

    My mathematical friend needs to use assembler routines to access some of
    the vector processing that the chipset, but not available-a C libraries, supports.

    IBM Macro-a assembler is practically a high level language, given the
    scale of macro usage in legacy systems

    It fits what I know.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:57:20 2026
    From Newsgroup: comp.unix.shell

    According to Thomas Koenig <tkoenig@netcologne.de>:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> schrieb:
    I agree. I've always believed that the difference between
    a mainframe and a mini had nothing to do with the size of
    the box, but everything to do with architecture, particularly
    I/O. Mainframes were record-oriented, while minis were
    byte-oriented.

    The PDP-8 was anything but byte-oriented, it was a 12-bit machine.

    Well, OK, word or byte depending on the vintage of the mini, but definitely
    not a record at at time.

    When a 360/30 read a card, it did a Start I/O instruction that pointed
    at a channel program that had the address and length of the buffer,
    then went away and did something else until it interrupted after the
    entire card was read in.

    On a PDP-8/I (I have the manual here), to read a card it first did a
    RCSE instruction to start a card moving, then for each column a busy
    wait loop or interrupt, RCSF to check and skip if the column is ready,
    RCRA or RCRB to read in the column, store it with a DCA instruction,
    then repeat for each column until an RCSD instruction said the card
    was done. It had to fetch each column within 1.5ms after its data was
    ready, but a PDP-8 was fast enough that the column routine might take
    50us so there was plenty of time to do other stuft.

    Plus, DECTape was block-oriented.

    It was but it was also pretty slow. The older TU55/TC01 DECtape used data break
    for I/O but for the later Omnibus PDP-8/e and 8/m had a cheaper interface that just read or wrote a word at a time in a tight loop, no data break or DMA.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:57:51 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-05, The Natural Philosopher <tnp@invalid.invalid> wrote:

    On 04/11/2026 19:51, Charlie Gibbs wrote:

    A mediocre assembly language programmer would not let lack of
    readability stand in the way. And once you get into self-modifying
    code there are all sorts of horrible things you can do.

    IBM macro assembler is about as machine code as COBOL

    It can be. Or not. If the 360 assembler didn't support
    extended branch mnemonics, you could do them with macros -
    one line in, one line out.

    I do admit that the other extreme can become hairy.
    I once saw a recursive macro that solved the Towers
    of Hanoi. It generated no code; the solution was
    in the expanded source listing.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 21:57:53 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-05, Thomas Koenig <tkoenig@netcologne.de> wrote:

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> schrieb:

    On 2026-11-04, John Levine <johnl@taugh.com> wrote:

    According to c186282 <c186282@nnada.net>:

    I can assure you that PDP-11s were minicomputers. I spent quite a while >>>>> programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.
    A 360/30 was considerably slower than a PDP-8, but its
    I/O architecture clearly made it a mainframe.

    I agree. I've always believed that the difference between
    a mainframe and a mini had nothing to do with the size of
    the box, but everything to do with architecture, particularly
    I/O. Mainframes were record-oriented, while minis were
    byte-oriented.

    The PDP-8 was anything but byte-oriented, it was a 12-bit machine.

    Plus, DECTape was block-oriented.

    You've got me there. It's amazing how slippery definitions become,
    even when starting from "I know one when I see one." I could say
    that minis tend to process a character at a time (e.g. a PDP-11
    driving a VT50) while mainframes tend to process a record at a
    time (e.g. a 360 filling a 2260's screen in a single operation).
    But exceptions (e.g. your DECTape) creep in...
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 15:59:05 2026
    From Newsgroup: comp.unix.shell

    On 11/5/26 14:12, The Natural Philosopher wrote:
    On 04/11/2026 23:14, Carlos E. R. wrote:
    On 2026-11-04 22:47, Lawrence DrCOOliveiro wrote:
    On Wed, 4 Nov 2026 10:53:41 +0100, Carlos E. R. wrote:

    On 2026-11-04 03:23, Janis Papanagnou wrote:

    On 2026-11-03 12:45, Carlos E. R. wrote:

    I know at least one guy working on IBM mainframes, and he tells me >>>>>> they are in high need of good assembler programmers.

    Wow! - I'd have thought that assembler programmers should meanwhile
    be at "best" a niche, and systems programming with "C" (or
    similar).

    They need speed that compilers can not achieve.

    The worldrCOs fastest supercomputers run Linux. And that is mostly written >>> in C, with very little assembly language.

    Well, I know for a fact that this machine doesn't run any standard OS.
    I asked him. Also, the disks do not have a filesystem, either (I also
    asked). Of course most of the programmers work in some high level
    language, but there are certain critical operations that are optimized
    in assembler. I don't remember which, and obviously I'm not going to
    quote him breaking confidence. But if anyone is a good programmer in
    those machines, in assembler, they are hiring.

    My mathematical friend needs to use assembler routines to access some of
    the vector processing that the chipset, but not available-a C libraries, supports.

    IBM Macro-a assembler is practically a high level language, given the
    scale of macro usage in legacy systems


    It can be. Obviously there are probably a lot of macros in any assembler program, but it also gets down to the nitty-gritty of registers,
    condition codes, etc., and that is probably at least 80% of the lines of
    code.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 16:01:21 2026
    From Newsgroup: comp.unix.shell

    On 11/5/26 14:57, Charlie Gibbs wrote:
    On 2026-11-05, Thomas Koenig <tkoenig@netcologne.de> wrote:

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> schrieb:

    On 2026-11-04, John Levine <johnl@taugh.com> wrote:

    According to c186282 <c186282@nnada.net>:

    I can assure you that PDP-11s were minicomputers. I spent quite a while >>>>>> programming them back in the 1970s.

    AT THE TIME, characterizing the PDP-11 as
    a "mini" is not wrong. I view a "mini" as
    a 'cut-down' mainframe.

    A mini was never a cut-down mainframe. Mainframes
    had channels, minis had simple I/O and fast interrupts.
    A 360/30 was considerably slower than a PDP-8, but its
    I/O architecture clearly made it a mainframe.

    I agree. I've always believed that the difference between
    a mainframe and a mini had nothing to do with the size of
    the box, but everything to do with architecture, particularly
    I/O. Mainframes were record-oriented, while minis were
    byte-oriented.

    The PDP-8 was anything but byte-oriented, it was a 12-bit machine.

    Plus, DECTape was block-oriented.

    You've got me there. It's amazing how slippery definitions become,
    even when starting from "I know one when I see one." I could say
    that minis tend to process a character at a time (e.g. a PDP-11
    driving a VT50) while mainframes tend to process a record at a
    time (e.g. a 360 filling a 2260's screen in a single operation).
    But exceptions (e.g. your DECTape) creep in...


    I usually just felt like mini=16 bits, mainframe=32 bits or more.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 23:04:23 2026
    From Newsgroup: comp.unix.shell

    On Thu, 05 Nov 2026 21:57:51 GMT, Charlie Gibbs wrote:

    I do admit that the other extreme can become hairy. I once saw a
    recursive macro that solved the Towers of Hanoi. It generated no
    code; the solution was in the expanded source listing.

    String-based macro languages in general can be pretty hairy.
    Towers of Hanoi wouldnrCOt even be that hard.

    ----
    dnl
    dnl Example m4 implementation of the GPM example output shown on page 64
    dnl of Bryan Higman's "A Comparative Study of Programming Languages", 1st ed. dnl
    dnl Created 2008 September 10 by Lawrence D'Oliveiro.
    dnl
    define(`repeat', `ifelse($2, 0, `', $2, 1, `$1', `$1`'repeat(`$1', eval($2 - 1))')')dnl
    dnl repeat(str, n) outputs n consecutive repetitions of str
    define(`n', `regexp(` x one two three four five six seven eight nine ten', `^\'repeat(` [^ ]+', $1)` \([^ ]+\)', `\1')')dnl
    dnl n(i) returns the word representation of i. Need to use the "repeat" macro dnl because m4's regexps don't support \{n\} repeat coefficients.
    define(`cap', `regexp(`$1', `^\(.\)\(.*\)$', `translit(`\1', `a-z', `A-Z')\2')')dnl
    dnl cap(s) returns s with the first letter capitalized.
    dnl
    define(`nrverses', 10)dnl
    define(`nmen', `cap(n($1)) ifelse($1, 1, man, men)')dnl
    dnl nmen(i) outputs the phrase "<i> man/men"
    define(`tomow', ` went to mow')dnl
    define(`mow1', `tomow a meadow')dnl
    define(`firstline', `nmen($1)`'tomow,mow1')dnl
    dnl firstline(i) outputs the first line of verse i.
    define(`restlines', `ifelse($1, 1, `nmen(1) and his dog,mow1', `nmen($1) restlines(eval($1 - 1))')')dnl
    dnl restlines(i) outputs the remaining lines of verse i
    define(`verse', `firstline($1)
    restlines($1)')dnl
    dnl verse(i) outputs the complete verse i
    define(`verses', `verse($1)`'ifelse($1, nrverses, `', `

    verses(eval($1 + 1))')')dnl
    dnl verses(i) outputs the verses from i up to the last one.
    dnl here we go...
    verses(1)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 23:06:13 2026
    From Newsgroup: comp.unix.shell

    On Thu, 5 Nov 2026 16:01:21 -0700, Peter Flass wrote:

    I usually just felt like mini=16 bits, mainframe=32 bits or more.

    If yourCOd said rCLmini=ren18 bitsrCY, that would have been consistent with
    the state of the market up to about the mid-1970s.

    And then the 32-bit rCLsuperminisrCY appeared ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 19:15:17 2026
    From Newsgroup: comp.unix.shell

    On 11/5/26 18:04, Lawrence DrCOOliveiro wrote:
    On Thu, 05 Nov 2026 21:57:51 GMT, Charlie Gibbs wrote:

    I do admit that the other extreme can become hairy. I once saw a
    recursive macro that solved the Towers of Hanoi. It generated no
    code; the solution was in the expanded source listing.

    String-based macro languages in general can be pretty hairy.
    Towers of Hanoi wouldnrCOt even be that hard.

    ----
    dnl
    dnl Example m4 implementation of the GPM example output shown on page 64
    dnl of Bryan Higman's "A Comparative Study of Programming Languages", 1st ed. dnl
    dnl Created 2008 September 10 by Lawrence D'Oliveiro.
    dnl
    define(`repeat', `ifelse($2, 0, `', $2, 1, `$1', `$1`'repeat(`$1', eval($2 - 1))')')dnl
    dnl repeat(str, n) outputs n consecutive repetitions of str
    define(`n', `regexp(` x one two three four five six seven eight nine ten', `^\'repeat(` [^ ]+', $1)` \([^ ]+\)', `\1')')dnl
    dnl n(i) returns the word representation of i. Need to use the "repeat" macro dnl because m4's regexps don't support \{n\} repeat coefficients. define(`cap', `regexp(`$1', `^\(.\)\(.*\)$', `translit(`\1', `a-z', `A-Z')\2')')dnl
    dnl cap(s) returns s with the first letter capitalized.
    dnl
    define(`nrverses', 10)dnl
    define(`nmen', `cap(n($1)) ifelse($1, 1, man, men)')dnl
    dnl nmen(i) outputs the phrase "<i> man/men"
    define(`tomow', ` went to mow')dnl
    define(`mow1', `tomow a meadow')dnl
    define(`firstline', `nmen($1)`'tomow,mow1')dnl
    dnl firstline(i) outputs the first line of verse i.
    define(`restlines', `ifelse($1, 1, `nmen(1) and his dog,mow1', `nmen($1) restlines(eval($1 - 1))')')dnl
    dnl restlines(i) outputs the remaining lines of verse i
    define(`verse', `firstline($1)
    restlines($1)')dnl
    dnl verse(i) outputs the complete verse i
    define(`verses', `verse($1)`'ifelse($1, nrverses, `', `

    verses(eval($1 + 1))')')dnl
    dnl verses(i) outputs the verses from i up to the last one.
    dnl here we go...
    verses(1)


    Well, that's totally transparent :-)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Thu Nov 5 18:43:16 2026
    From Newsgroup: comp.unix.shell

    On 11/4/2026 11:51, Charlie Gibbs wrote:
    On the other side of the coin, someone at Univac decided that
    the key to productivity was not so much a quick response time
    as a consistent one - which led to their system inserting
    delays if a response was ready too soon. :-p

    Back in my University Computer Center days around 1972, I was hacking
    a local email feature into the EXEC-8 editor, and decided that less
    variation in response times would be a good thing, so I added a 1/2
    second wait before each editor command prompt. I got in serious trouble
    for this, because the process scheduler assumed that 500 ms was "a long
    time", and a program that was going to wait for a long time should be
    swapped out of memory.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 02:50:35 2026
    From Newsgroup: comp.unix.shell

    According to Peter Flass <Peter@Iron-Spring.com>:
    The PDP-8 was anything but byte-oriented, it was a 12-bit machine.

    Plus, DECTape was block-oriented.

    You've got me there. It's amazing how slippery definitions become,
    even when starting from "I know one when I see one." I could say
    that minis tend to process a character at a time (e.g. a PDP-11
    driving a VT50) while mainframes tend to process a record at a
    time (e.g. a 360 filling a 2260's screen in a single operation).
    But exceptions (e.g. your DECTape) creep in...

    I usually just felt like mini=16 bits, mainframe=32 bits or more.

    Oh you young folks. The 12 bit PDP-8 and the 18 but PDP-1, 4, 7, 9, and 15 were defintiely minicomputers.

    On the other hand the Interdata 7/32 and 8/32 to which Unix was ported (twice) in
    the 1970s was a 32 bit supermini. Its instruction set was reminiscent of S/360 but the simple I/O made it a mini..
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 04:34:00 2026
    From Newsgroup: comp.unix.shell

    On Wed, 04 Nov 2026 19:51:29 GMT, Charlie Gibbs wrote:

    I remember reading about an experiment done in an IBM shop where
    they shoveled in enough hardware and tweaked the protocols so that
    terminal users got sub-second response time. Apparently it increased throughput even more than one would expect by just scaling the
    response time - users could develop a rhythm and not have their
    minds wander while waiting for a response.

    I remember this, too: it was one of the first experiments into
    human-factors aspects of computer systems. And from IBM, too: the
    maker of systems that were not exactly famous for a lot of thought
    going into their human-factors aspects ...

    On the other side of the coin, someone at Univac decided that the
    key to productivity was not so much a quick response time as a
    consistent one - which led to their system inserting delays if a
    response was ready too soon. :-p

    And hererCOs another tale: this was probably from the very earliest days
    of computers, but the story I remember reading involves users entering
    a query, and how long it took to get back a response. Apparently, if
    the response came back *too* quickly, the users felt that the computer
    somehow wasnrCOt treating their question with the importance it
    deserved.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 06:35:23 2026
    From Newsgroup: comp.unix.shell

    The Natural Philosopher <tnp@invalid.invalid> schrieb:

    IBM Macro assembler is practically a high level language, given the
    scale of macro usage in legacy systems

    High-level languages abstract away the underlying machine, which
    I presume the Macro assembler does not.

    Plus, does it do register allocation?

    (OK, then Wirth's PL/360 creeps in, which does not do so either,
    but then I would argue that that is a glorified assembler - it also
    does not do operator precenence).
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 06:38:00 2026
    From Newsgroup: comp.unix.shell

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> schrieb:
    On 2026-11-04, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    And if you think the fruit vendor is better, you can rest easy, because
    at one time they refused to update my card number. Actually refused.
    After reaching the /right/ support person, that person could not help
    figure out why the website told me the card number had been updated, but
    then the TV application always tried to use the old card number.

    Ah, you've been around the mulberry bush with Netflix too, I presume.
    We recently found we couldn't log in to Netflix because they didn't
    like our card number - and quoted the last four digits and date of
    a card that expired seven years ago. I wonder how they had managed
    to bill us the previous month.

    I called their customer support line, and the droid became downright belligerent, claiming that it wasn't their fault but our bank's.
    I wound up hanging up on him, and we cancelled our Netflix account.

    So whoever was at fault for the issue did you a huge favor.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 06:40:43 2026
    From Newsgroup: comp.unix.shell

    Peter Flass <Peter@Iron-Spring.com> schrieb:
    On 11/3/26 20:30, c186282 wrote:

    -a NOTICED - my principal bank - a LOT of transactions
    -a come up with a "pending" label. Might take DAYS. This
    -a is not some 3rd-tier bank either.

    -a Two or more larger credit/debit card charges, not
    -a sure HOW they 'compete' in that system. If too
    -a near each other one MIGHT get bumped. Problem !

    -a In short, even 'online/instant' banking may not
    -a be THAT instant.

    Some of this is communication between banks, and some is your bank
    milking the float for as long as is legally allowed.

    In Europe, you can do "immediate" bank transfers for free. Takes a
    few seconds. Banks are required by law to provide this, but they
    differ in the amount that they allow.

    In principle, this is good. But it also allows scammers to clean out
    accounts more easily, because otherwise you could cancel an order
    if you noticed anything is amiss.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 06:44:31 2026
    From Newsgroup: comp.unix.shell

    On Thu, 5 Nov 2026 18:43:16 -0800, Lars Poulsen wrote:

    I got in serious trouble for this,
    because the process scheduler assumed that 500 ms was "a long time", and
    a program that was going to wait for a long time should be swapped out
    of memory.

    It is a long time :) For example if you click on a button and there is no perceptible change for 500 ms the users will complain about the program
    being slow.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 15:45:23 2026
    From Newsgroup: comp.unix.shell

    The Natural Philosopher <tnp@invalid.invalid> writes:
    On 04/11/2026 14:54, Peter Flass wrote:
    On 11/3/26 15:15, Pancho wrote:

    If you want heavy usage, I would guess bank risk calcs, weather calcs,
    lots of science applications, running on compute grids, (or whatever
    the modern word is), blow this mainframe high i/o away.

    I think back in the day the quants preferred Sun.

    Not for transactuon processing

    You clearly don't know what a "quant" is, in this context.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 20:51:49 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-06, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    And hererCOs another tale: this was probably from the very earliest days
    of computers, but the story I remember reading involves users entering
    a query, and how long it took to get back a response. Apparently, if
    the response came back *too* quickly, the users felt that the computer somehow wasnrCOt treating their question with the importance it
    deserved.

    I wrote a program that searches a large collection of files for
    various data. I noticed the same thing: it ran so fast that
    people weren't taking it seriously. It didn't help that the
    search parameter screen was too easy to use, either.

    I guess that in this modern age, where complexity is equated
    with sophistication, any sign of simplicity or efficiency
    is suspect.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 21:29:00 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-06, Lars Poulsen <lars@beagle-ears.com> wrote:
    On 11/4/2026 11:51, Charlie Gibbs wrote:
    On the other side of the coin, someone at Univac decided that
    the key to productivity was not so much a quick response time
    as a consistent one - which led to their system inserting
    delays if a response was ready too soon. :-p

    Back in my University Computer Center days around 1972, I was hacking
    a local email feature into the EXEC-8 editor, and decided that less
    variation in response times would be a good thing, so I added a 1/2
    second wait before each editor command prompt. I got in serious trouble
    for this, because the process scheduler assumed that 500 ms was "a long time", and a program that was going to wait for a long time should be swapped out of memory.

    You should check whether Microsoft has tried to patent fake bullshit
    system response pauses. This is clear prior art!
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 21:31:52 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-06, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-06, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    And hererCOs another tale: this was probably from the very earliest days
    of computers, but the story I remember reading involves users entering
    a query, and how long it took to get back a response. Apparently, if
    the response came back *too* quickly, the users felt that the computer
    somehow wasnrCOt treating their question with the importance it
    deserved.

    I wrote a program that searches a large collection of files for
    various data. I noticed the same thing: it ran so fast that
    people weren't taking it seriously. It didn't help that the
    search parameter screen was too easy to use, either.

    That's much the same like people not taking a pair of headphones
    seriously if they are light; so Beats famously added hidden metal
    weights to them to create a more premium feel.
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 06:25:12 2026
    From Newsgroup: comp.unix.shell

    On 11/7/2026 4:51 AM, Charlie Gibbs wrote:
    On 2026-11-06, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    And hererCOs another tale: this was probably from the very earliest days
    of computers, but the story I remember reading involves users entering
    a query, and how long it took to get back a response. Apparently, if
    the response came back *too* quickly, the users felt that the computer
    somehow wasnrCOt treating their question with the importance it
    deserved.

    I wrote a program that searches a large collection of files for
    various data. I noticed the same thing: it ran so fast that
    people weren't taking it seriously. It didn't help that the
    search parameter screen was too easy to use, either.

    I guess that in this modern age, where complexity is equated
    with sophistication, any sign of simplicity or efficiency
    is suspect.


    I think it's more /instinctual/ than that. Humans, who dismiss sugges-
    tions without thought, normally do so as a status symbol: they are more important than you.

    It isn't about the idea or suggestion being stupid, because then there
    would be a followup explanation.

    Follow those experiences up with people who do shoddy work fast, and if
    the computer is fast too, it /didn't take the time to do things proper-
    ly/.

    The machine, as a servant, should never /feel/ more important than the
    user. Which unfortunately, seems to be more and more real in the age of
    "A.I." as business owners tend to prefer people who can crank out
    prompts rather than do the work /by hand/. The /machine/ is now more
    important than the employee who wields it. Anyway, that's a rant we
    don't need in alt.folklore.computers.


    Best wishes, and happy search algorithms!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 01:22:40 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-06, Kaz Kylheku <046-301-5902@kylheku.com> wrote:

    On 2026-11-06, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    On 2026-11-06, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    And hererCOs another tale: this was probably from the very earliest days >>> of computers, but the story I remember reading involves users entering
    a query, and how long it took to get back a response. Apparently, if
    the response came back *too* quickly, the users felt that the computer
    somehow wasnrCOt treating their question with the importance it
    deserved.

    I wrote a program that searches a large collection of files for
    various data. I noticed the same thing: it ran so fast that
    people weren't taking it seriously. It didn't help that the
    search parameter screen was too easy to use, either.

    That's much the same like people not taking a pair of headphones
    seriously if they are light; so Beats famously added hidden metal
    weights to them to create a more premium feel.

    I've heard that car manufacturers put padding into the doors
    to give a satisfying thump rather than a clank.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 05:00:51 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-07 02:22, Charlie Gibbs wrote:

    I've heard that car manufacturers put padding into the doors
    to give a satisfying thump rather than a clank.

    Unless the various sounds in cars are created artificially!

    (Not joking. - Inspect the automotive business job offers,
    specifically sound designers and sound engineers, and also
    inspect the information on the Net about where artificial
    sound is actually synthesized and applied to, including the
    doors.)

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Fri Nov 6 23:09:53 2026
    From Newsgroup: comp.unix.shell

    On 11/6/26 01:35, Thomas Koenig wrote:
    The Natural Philosopher <tnp@invalid.invalid> schrieb:

    IBM Macro assembler is practically a high level language, given the
    scale of macro usage in legacy systems

    High-level languages abstract away the underlying machine, which
    I presume the Macro assembler does not.

    Plus, does it do register allocation?

    (OK, then Wirth's PL/360 creeps in, which does not do so either,
    but then I would argue that that is a glorified assembler - it also
    does not do operator precenence).

    I will agree that MASM isn't a good equiv to
    any higher-level language. Used it a fair bit
    in the bad old days, but never to its max cap.
    Served my particular needs however, back when
    ASM was the only way to get tight code with
    lowest-level access. 'C' eventually assumed
    that role for the most part, but not overnight.

    ASM was also *the* way for the older micro-controllers
    for a long time. However some of the optimized 'C'
    compilers can now rival ASM for speed and size and
    you don't have to hand-code bit-banging serial either :-)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 04:12:42 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-07, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:

    On 2026-11-07 02:22, Charlie Gibbs wrote:

    I've heard that car manufacturers put padding into the doors
    to give a satisfying thump rather than a clank.

    Unless the various sounds in cars are created artificially!

    (Not joking. - Inspect the automotive business job offers,
    specifically sound designers and sound engineers, and also
    inspect the information on the Net about where artificial
    sound is actually synthesized and applied to, including the
    doors.)

    I did read recently that they have staffers charged with
    designing the weird noises electric cars make at low speeds.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Janis Papanagnou@janis_papanagnou+ng@hotmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 05:39:08 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-07 05:12, Charlie Gibbs wrote:
    On 2026-11-07, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:

    On 2026-11-07 02:22, Charlie Gibbs wrote:

    I've heard that car manufacturers put padding into the doors
    to give a satisfying thump rather than a clank.

    Unless the various sounds in cars are created artificially!

    (Not joking. - Inspect the automotive business job offers,
    specifically sound designers and sound engineers, and also
    inspect the information on the Net about where artificial
    sound is actually synthesized and applied to, including the
    doors.)

    I did read recently that they have staffers charged with
    designing the weird noises electric cars make at low speeds.

    Yes, that is one application case. Actually its a requirement
    that is even demanded by regulations hereabouts!

    But then there's also other things, like the mentioned door
    sounds, the voluminous sound of the engine, noise reduction
    (adding noise here and reducing it there; somewhat crazy!),
    feedback sounds (with Star Trek as general paragon :-), and
    some gimmicks.

    Janis

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 11:32:29 2026
    From Newsgroup: comp.unix.shell

    On 06/11/2026 15:45, Scott Lurndal wrote:
    The Natural Philosopher <tnp@invalid.invalid> writes:
    On 04/11/2026 14:54, Peter Flass wrote:
    On 11/3/26 15:15, Pancho wrote:

    If you want heavy usage, I would guess bank risk calcs, weather calcs, >>>> lots of science applications, running on compute grids, (or whatever
    the modern word is), blow this mainframe high i/o away.

    I think back in the day the quants preferred Sun.

    Not for transactuon processing

    You clearly don't know what a "quant" is, in this context.

    I do.

    More than you, probably
    --
    If I had all the money I've spent on drink...
    ..I'd spend it on drink.

    Sir Henry (at Rawlinson's End)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 11:37:39 2026
    From Newsgroup: comp.unix.shell

    On 07/11/2026 04:12, Charlie Gibbs wrote:
    I did read recently that they have staffers charged with
    designing the weird noises electric cars make at low speeds.

    My StupidPhone yelps like a puppy that has just been stepped on, on
    receipt of a text message.

    People look for the dog...
    --
    Karl Marx said religion is the opium of the people.
    But Marxism is the crack cocaine.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 11:45:42 2026
    From Newsgroup: comp.unix.shell

    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a for a long time. However some of the optimized 'C'
    -a compilers can now rival ASM for speed and size and
    -a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do it
    in 'C'.
    --
    rCLit should be clear by now to everyone that activist environmentalism
    (or environmental activism) is becoming a general ideology about humans,
    about their freedom, about the relationship between the individual and
    the state, and about the manipulation of people under the guise of a
    'noble' idea. It is not an honest pursuit of 'sustainable development,'
    a matter of elementary environmental protection, or a search for
    rational mechanisms designed to achieve a healthy environment. Yet
    things do occur that make you shake your head and remind yourself that
    you live neither in Joseph StalinrCOs Communist era, nor in the Orwellian utopia of 1984.rCY

    Vaclav Klaus

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 07:37:39 2026
    From Newsgroup: comp.unix.shell

    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C'
    -a-a compilers can now rival ASM for speed and size and
    -a-a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do it
    in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least). When PCs were new I used a compiler
    called "Aztec C" that had almost no overhead in excess libraries,
    start-up code, etc., unless you asked for them.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 22:49:09 2026
    From Newsgroup: comp.unix.shell

    On 11/7/2026 10:37 PM, Peter Flass wrote:
    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C'
    -a-a compilers can now rival ASM for speed and size and
    -a-a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do
    it in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least). When PCs were new I used a compiler called "Aztec C" that had almost no overhead in excess libraries, start-
    up code, etc., unless you asked for them.

    And nonconsensual AVX code. I've heard some CPUs have a lower maximum
    Hz when AVX is enabled. And I have never heard of a benchmark that mea-
    sures the cutoff when doing things the old fashioned way, say REP MOVSB
    is faster or slower than the AVX method(s), due to this difference.

    So, why not tell me this cutoff? Are the GCC devs afraid of something? Shouldn't they be proud of their optimizations?

    Or was I lied to, about modern CPUs stepping down when AVX is in play?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 14:54:06 2026
    From Newsgroup: comp.unix.shell

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> schrieb:
    On 11/7/2026 10:37 PM, Peter Flass wrote:
    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C'
    -a-a compilers can now rival ASM for speed and size and
    -a-a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do
    it in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least). When PCs were new I used a compiler
    called "Aztec C" that had almost no overhead in excess libraries, start-
    up code, etc., unless you asked for them.

    And nonconsensual AVX code.

    -fno-tree-optimize is your friend.

    I've heard some CPUs have a lower maximum
    Hz when AVX is enabled.

    AVX512, yes.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Christian Weisgerber@naddy@mips.inka.de to comp.os.linux.misc,comp.unix.shell on Sat Nov 7 16:07:26 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-01, Carlos E. R. <robin_listas@es.invalid> wrote:

    There is the tool "pinfo", it can highlight somethings like the name of another man page, and jump to it.

    Still, no table of content. No jumping from one section while browsing
    the man page.

    "A more modern man page viewer for our terminals"
    https://github.com/plp13/qman

    Qman [i]s a modern, full-featured manual page viewer featuring
    hyperlinks, web browser like navigation, a table of contents for
    each page, incremental search, on-line help, and more. It also
    strives to be fast and tiny, so that it can be used everywhere. For
    this reason, it's been written in plain C and has only minimal
    dependencies.

    (I haven't tried it myself.)
    --
    Christian "naddy" Weisgerber naddy@mips.inka.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 13:31:06 2026
    From Newsgroup: comp.unix.shell

    On 11/7/26 09:37, Peter Flass wrote:
    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C'
    -a-a compilers can now rival ASM for speed and size and
    -a-a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do
    it in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least). When PCs were new I used a compiler called "Aztec C" that had almost no overhead in excess libraries, start-
    up code, etc., unless you asked for them.

    Used Aztec ... indeed HAVE the compiler and EXTENSIVE
    docs stashed away somewhere. Will have to make a new
    CP/M-86 VM for it first. Not sure you'd get best effect
    on a simulated Z80. Have seen some 'kit' Z80 boards.

    There's also a DOS version - but it's apparently meant
    to run under XP.

    The docs are IMPRESSIVE - endless bit-level and flag
    stuff - exactly what you needed to know if trying to
    shoehorn something into a small system.

    A few versions of Turbo Pascal allowed code overlays
    in a fairly civil fashion, another way to squeeze a
    big pgm into a small machine. But, better have a HDD,
    pulling overlays from a floppy - you don't wanna
    go there :-) Did a couple of large pgms where overlays
    were needed.

    Anyway, if interested in Aztec, try :

    https://www.aztecmuseum.ca/compilers.htm



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 02:56:49 2026
    From Newsgroup: comp.unix.shell

    On 11/8/2026 2:31 AM, c186282 wrote:
    On 11/7/26 09:37, Peter Flass wrote:
    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C'
    -a-a compilers can now rival ASM for speed and size and
    -a-a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do
    it in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least). When PCs were new I used a compiler
    called "Aztec C" that had almost no overhead in excess libraries,
    start- up code, etc., unless you asked for them.

    -a Used Aztec ... indeed HAVE the compiler and EXTENSIVE
    -a docs stashed away somewhere. Will have to make a new
    -a CP/M-86 VM for it first. Not sure you'd get best effect
    -a on a simulated Z80. Have seen some 'kit' Z80 boards.

    -a There's also a DOS version - but it's apparently meant
    -a to run under XP.

    -a The docs are IMPRESSIVE - endless bit-level and flag
    -a stuff - exactly what you needed to know if trying to
    -a shoehorn something into a small system.

    -a A few versions of Turbo Pascal allowed code overlays
    -a in a fairly civil fashion, another way to squeeze a
    -a big pgm into a small machine. But, better have a HDD,
    -a pulling overlays from a floppy - you don't wanna
    -a go there :-) Did a couple of large pgms where overlays
    -a were needed.

    -a Anyway, if interested in Aztec, try :

    https://www.aztecmuseum.ca/compilers.htm

    Thank you. It's mildly unclear if the compiler will run under pure DOS,
    and this XP package is merely a convenience -- alas I was not in the
    mood to find out.

    However, I am perusing the manual library, to see if I find something interesting.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 20:03:01 2026
    From Newsgroup: comp.unix.shell

    On Sat, 7 Nov 2026 07:37:39 -0700, Peter Flass wrote:

    But then you add all the cruft that GCC drags in ...

    You can build programs with GCC that donrCOt use glibc.

    Back when I got my first 64-bit machine, I tried to build the smallest
    program I could: it took a number as a command-line argument, and
    slept for that number of seconds. This gave me time to do a ps listing
    to see how much memory it was using. I built it against one of the
    alternative cut-down libc alternatives -- maybe musl or uclibc.

    ps reported that it was using just 20kB of memory.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 21:53:26 2026
    From Newsgroup: comp.unix.shell

    On 07/11/2026 14:37, Peter Flass wrote:
    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C'
    -a-a compilers can now rival ASM for speed and size and
    -a-a you don't have to hand-code bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do
    it in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least).
    Hardly.


    When PCs were new I used a compiler
    called "Aztec C" that had almost no overhead in excess libraries,
    start-up code, etc., unless you asked for them.

    Well in general you DO ask for them
    --
    Climate Change: Socialism wearing a lab coat.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 01:23:26 2026
    From Newsgroup: comp.unix.shell

    On Sat, 7 Nov 2026 21:53:26 +0000, The Natural Philosopher wrote:

    On 07/11/2026 14:37, Peter Flass wrote:
    On 11/7/26 04:45, The Natural Philosopher wrote:
    On 07/11/2026 04:09, c186282 wrote:
    ASM was also *the* way for the older micro-controllers
    -a-a for a long time. However some of the optimized 'C' compilers can
    -a-a now rival ASM for speed and size and you don't have to hand-code
    -a-a bit-banging serial either

    At some point I idly compiled some gcc C to assembler . I spent a
    pointless half hour trying to work out if I could have done it better.

    I couldn't..

    In terms of modern micros I wouldn't even bother unless I couldn't do
    it in 'C'.


    But then you add all the cruft that GCC drags in and you're back where
    you started (size-wise, at least).
    Hardly.


    When PCs were new I used a compiler called "Aztec C" that had almost no
    overhead in excess libraries, start-up code, etc., unless you asked for
    them.

    Well in general you DO ask for them

    I fixed a 20 year old bug that was caused by the programmer deciding
    adding '-lm' to the compilation would be too heavy. iirc his version of hypot() worked most of the time.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sat Nov 7 16:04:20 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> writes:
    The 'mainframe' era is nearly over - to be replaced
    by cluster/distributed/AI.

    However IBM is already into all that, WILL make money.

    Many baskets ... How To Survive/Thrive.

    Hmmmm ... do remember when IBM was "typewriters" ...

    1988, Nick Donofrio approves HA/6000, originally for NYTimes to move
    their newspaper system ("ATEX") off DEC VAXCluster to RS/6000 (running
    project out at Los Gatos lab). I rename it HA/CMP https://en.wikipedia.org/wiki/IBM_High_Availability_Cluster_Multiprocessing when I start doing technical/scientific cluster scale-up with national
    labs (LANL, LLNL, NCAR, etc) and commercial cluster scale-up with RDBMS
    vendors (Oracle, Sybase, Ingres, Informix) with VAXCluster support in
    same source base with UNIX (planning on using Hursley 9333 for mid-range
    and full FCS for both technical and commercial scaleup). DB2 was still
    all mainframe source, IBM non-mainframe "DB2" had yet to be developed.

    IBM S/88 (relogo'ed Stratus) Product Administrator started taking us
    around to their customers and also had me write a section for the
    corporate continuous availability strategy document (it gets pulled when
    both AS400/Rochester and mainframe/POK complain they couldn't meet requirements). Had coined "disaster survivability" and "geographic survivability" (as counter to disaster/recovery) when out marketing
    HA/CMP.

    One of the first HA/CMP customer installs was new Indian Reservation
    Casino in Connecticut, was suppose to have week of testing before
    opening ... but after 24hrs, they decided to open the doors (based on
    projected revenue; at the time was largest in the US, still one of the
    largest in the country) https://en.wikipedia.org/wiki/Foxwoods_Resort_Casino#Debt_default

    Early Jan92, there was HA/CMP meeting with Oracle CEO and IBM/AWD
    executive Hester tells Ellison that we would have 16-system clusters by
    mid92 and 128-system clusters by ye92. Mid-jan92, I update FSD on HA/CMP
    work with national labs and FSD decides to go with HA/CMP for federal supercomputers. By end of Jan, we are told that cluster scale-up is
    being transferred to Kingston for announce as IBM Supercomputer (SP, technical/scientific *ONLY*) and we aren't allowed to work with anything
    that has more than four systems (we leave IBM a few months later). A
    couple weeks later, 17feb1992, Computerworld news ... IBM establishes laboratory to develop parallel systems (pg8) https://archive.org/details/sim_computerworld_1992-02-17_26_7

    Some speculation that HA/CMP would have eaten the mainframe in the
    commercial market. 1993 industry benchmarks (number of program
    iterations compared to the industry MIPS/BIPS reference platform):

    ES/9000-982 : 8CPU 408MIPS, (51MIPS/CPU)
    RS6000/990 (RIOS chipset) : 1-CPU: 126MIPS

    Executive we had reported to, goes over to head up Somerset/AIM (Apple,
    IBM, Motorola) to do single chip 801/RISC (Power/PC) and uses Motorola
    88k bus/cache enabling SMP implementations.

    In the mid-90s, the i86 chip makers then do hardware layer that
    translates i86 instructions into RISC micro-ops for actual execution,
    largely negating the performance difference with RISC platforms. 1999
    industry benchmarks:
    IBM PowerPC 440: 1,000MIPS
    Intel Pentium3 2,054MIPS

    Dec2000 (IBM mainframe) benchmark:
    IBM z900 16CPU: 2.5BIPS, 156MIPS/CPU

    Also 1988, IBM branch office asked if I could help LLNL (national lab) standardize some serial stuff they were working with ... which quickly
    becomes Fibre Channel Standard ("FCS", including some stuff I had done
    in 1980; initially planning on using 1gbit transfer, full-duplex,
    aggregate transfer 200mbytes/sec & 64-port non-blocking switches, with
    high-end HA/CMP installations). POK mainframe eventually announces its
    serial stuff (when it is already obsolete) as "ESCON" (initially
    10mbytes/sec). Some POK engineers then become involved with FCS and
    define a heavy weight protocol that radically cuts the native
    throughput, eventually announced as FICON.

    Latest public benchmark I've found is 2010 z196 "Peak I/O" getting 2M
    IOPS using 104 FICON (20K IOPS/FICON). About the same time a native FCS
    is announced for E5-2600 server blades getting over million IOPS (two
    such FCS higher throughput than 104 FICON running over FCS). Note IBM
    docs has SAPs (system assist processors that do actual I/O) CPU be kept
    to 70% ... or 1.5M IOPS ... also no CKD DASD have been made for decades
    (just simulated with industry standard fixed-block devices).

    This "Evolution of the System z Channel" (SHARE 2011 presentation at
    wayback machine) https://web.archive.org/web/20170829213251/https://share.confex.com/share/117/webprogram/Handout/Session9931/9934pdhj%20v0.pdf
    talks about after 2010 z196 "Peak I/O" benchmark and "zHPF" that
    increased throughput from 20K IOPS/FICON to 52K IOPS/FICON then to 92K IOPS/FICON (aka from 1/50th to almost 1/10th the native FCS announced in
    2010).
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 05:59:55 2026
    From Newsgroup: comp.unix.shell

    On 11/7/2026 18:04, Lynn Wheeler wrote:
    1988, Nick Donofrio approves HA/6000, originally for NYTimes to move
    their newspaper system ("ATEX") off DEC VAXCluster to RS/6000 (running project out at Los Gatos lab). I rename it HA/CMP https://en.wikipedia.org/wiki/IBM_High_Availability_Cluster_Multiprocessing when I start doing technical/scientific cluster scale-up with national
    labs (LANL, LLNL, NCAR, etc) and commercial cluster scale-up with RDBMS vendors (Oracle, Sybase, Ingres, Informix) with VAXCluster support in
    same source base with UNIX (planning on using Hursley 9333 for mid-range
    and full FCS for both technical and commercial scaleup). DB2 was still
    all mainframe source, IBM non-mainframe "DB2" had yet to be developed.

    Around 2001, my group had developed a T1-over-UDP-over-Ethernet bridge
    to use in tandem with our wireless ethernet bridge product. After we
    spun out from WiLan, and became Afar, we also marketed it separately.
    Our largest sale was to NYT, to replace the dual T1 lines they had to
    their (16?) regional printing plants, connected to the phototypesetters
    in the print shops. At 42nd street they had a rack with 60(?) of our
    boxes. While they wanted the two lines for each remote site to be on
    separate boxes connected to separate IP networks, two lines to different
    sites could share one of our units, which had two T1 jacks.

    System worked well; I once got to visit the Old Lady shortly before they
    moved down the street.

    IBM S/88 (relogo'ed Stratus) Product Administrator started taking us
    around to their customers and also had me write a section for the
    corporate continuous availability strategy document (it gets pulled when
    both AS400/Rochester and mainframe/POK complain they couldn't meet requirements). Had coined "disaster survivability" and "geographic survivability" (as counter to disaster/recovery) when out marketing
    HA/CMP.

    I was curious about S/88, which I did not know about before. CoPilot
    pulled together a nice synopsis, from which I learned that Stratus and
    Tandem both had figured out how to do rolling upgrades in a non-stop environment; I had thought that was an IBM mainframe invention.

    I also learned that both Stratus and Tandem survive to this day, in a
    fashion:
    Tandem-> Compaq-> HP - is now HPE Non-Stop

    Stratus-> Ascend-> Lucent -> spin-out Stratus Tech
    building HA systems on Xeon processors.
    Now called Penguin Solutions.
    Many techies despise System/Z as an overpriced dinosaur with an
    obsolete architechture. But I wonder if it is any less expensive to dip
    the Intel processors in that magic sauce. I bet IBM has better scale to
    their builds.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 08:11:28 2026
    From Newsgroup: comp.unix.shell

    Lars Poulsen <lars@beagle-ears.com> writes:
    Around 2001, my group had developed a T1-over-UDP-over-Ethernet bridge
    to use in tandem with our wireless ethernet bridge product. After we
    spun out from WiLan, and became Afar, we also marketed it
    separately. Our largest sale was to NYT, to replace the dual T1 lines
    they had to their (16?) regional printing plants, connected to the phototypesetters in the print shops. At 42nd street they had a rack
    with 60(?) of our boxes. While they wanted the two lines for each
    remote site to be on separate boxes connected to separate IP networks,
    two lines to different sites could share one of our units, which had
    two T1 jacks.

    System worked well; I once got to visit the Old Lady shortly before
    they moved down the street.

    early 80s, I got HSDT project, T1 and faster computer links (both
    terrestrial and satellite) and battles with SNA group (60s, IBM had 2701 supporting T1, 70s with SNA/VTAM and issues, links were capped at 56kbit
    ... and I had to mostly resort to non-IBM hardware).

    Mid-80s, communication group was also fighting off release of mainframe
    TCP/IP support and when that failed, they said that since they had
    corporate responsibility for everything that crossed datacenter walls,
    it had to be release through them. I then add RFC1044 and in some tuning
    tests at Cray Research between a Cray and 4341, got sustained 4341
    channel throughput using only modest amount of 4341 CPU (something like
    500 times improvement in bytes moved per instruction executed).

    HSDT also was working with NSF director and was suppose to get $20M to interconnect the NSF Supercomputer centers. NSF gave grant to Univ. Cal
    to build Berkeley supercomputer center and I was asked to give them
    talks on the interconnect. Turns out regents had san diego getting the
    next new bldg ... and it became the San Diego Supercomputer center
    instead.

    Then congress cuts the budget, some other things happened and eventually
    there was RFP released (in part based on what we already had
    running). NSF 28Mar1986 Preliminary Announcement: https://web.archive.org/web/20260311074443/https://www.garlic.com/~lynn/2002k.html#12
    The OASC has initiated three programs: The Supercomputer Centers Program
    to provide Supercomputer cycles; the New Technologies Program to foster
    new supercomputer software and hardware developments; and the Networking Program to build a National Supercomputer Access Network - NSFnet.

    IBM internal politics was not allowing us to bid. The NSF director tried
    to help by writing the company a letter (3Apr1986, NSF Director to IBM
    Chief Scientist and IBM Senior VP and director of Research, copying IBM
    CEO) with support from other gov. agencies ... but that just made the
    internal politics worse (as did claims that what we already had
    operational was at least 5yrs ahead of the winning bid), as regional
    networks connect in, NSFnet becomes the NSFNET backbone, precursor to
    modern internet

    ... aka NCSA ... grant for new "supercomputer software" https://www.ncsa.illinois.edu/
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 08:32:30 2026
    From Newsgroup: comp.unix.shell

    Lynn Wheeler <lynn@garlic.com> writes:
    Latest public benchmark I've found is 2010 z196 "Peak I/O" getting 2M
    IOPS using 104 FICON (20K IOPS/FICON). About the same time a native FCS
    is announced for E5-2600 server blades getting over million IOPS (two
    such FCS higher throughput than 104 FICON running over FCS). Note IBM
    docs has SAPs (system assist processors that do actual I/O) CPU be kept
    to 70% ... or 1.5M IOPS ... also no CKD DASD have been made for decades
    (just simulated with industry standard fixed-block devices).

    2010:
    Max configured z196, $30M, 80core, 50BIPS.
    Intel E5-2600, 16cores, 500BIPS

    IBM base list price for E5-2600 server blade was $1815

    2010 Note large cloud operations with multiple megadatacenters around
    the world with half million or more server blades with enormous
    automation and able to run megadatacenter with 70-80 staff and
    assembled their own server blades at 1/3rd the cost of brand
    name vendors.

    There was then industry articles that server chip makers were shipping
    half their products directly to megadatacenters. Shortly later, IBM
    sells off its server blade business.
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 21:31:18 2026
    From Newsgroup: comp.unix.shell

    On Sun, 8 Nov 2026 05:59:55 -0800, Lars Poulsen wrote:

    ... from which I learned that Stratus and Tandem both had figured
    out how to do rolling upgrades in a non-stop environment; I had
    thought that was an IBM mainframe invention.

    The IBM mega-marketing machine strikes again.

    Or past tense, really; IBM no longer has that power. Microsoft
    inherited that mantle, but it, too, is losing its grip.

    Many techies despise System/Z as an overpriced dinosaur with an
    obsolete architechture. But I wonder if it is any less expensive to
    dip the Intel processors in that magic sauce. I bet IBM has better
    scale to their builds.

    There was a paper on how Google did it, published 10 or 20 years ago.
    At that point, they had a total complement of about 460,000 x86
    servers. They would buy the cheapest component they could for every
    component but one: the power supply.

    With that kind of scale, who cares if 100 or 1000 machines are broken
    at any moment? The users certainly wonrCOt notice.

    Mainframes stopped being relevant back in the 1980s; every further
    development since then has just been driven by customer inertia.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 21:32:13 2026
    From Newsgroup: comp.unix.shell

    On Sun, 08 Nov 2026 08:32:30 -1000, Lynn Wheeler wrote:

    There was then industry articles that server chip makers were
    shipping half their products directly to megadatacenters. Shortly
    later, IBM sells off its server blade business.

    Which kind of begs the question, doesnrCOt it: who bought it, and why?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 13:45:03 2026
    From Newsgroup: comp.unix.shell

    On 11/8/2026 13:31, Lawrence DrCOOliveiro wrote:
    There was a paper on how Google did it, published 10 or 20 years ago.
    At that point, they had a total complement of about 460,000 x86
    servers. They would buy the cheapest component they could for every
    component but one: the power supply.

    With that kind of scale, who cares if 100 or 1000 machines are broken
    at any moment? The users certainly wonrCOt notice.

    The parallelism of a Google is a very different beast from the robust parallelism of a banking mainframe.

    Google needs a way to route an incoming connection to a random running
    server instance. It does not matter which one, and if the one that was
    picked has died, the first packet retry will get to a better one.

    That is very different from transactions that must execute exactly once.

    Mainframes stopped being relevant back in the 1980s; every further development since then has just been driven by customer inertia.

    If we define mainframes a large, very robust systems, they are still
    very relevant. Although it may be true that the major technology was in
    place before 1990 (non-stop cluster systems, transaction locking with completion/rollback and strategic redundancy). What you call customer
    inertia is also known as vendor lock-in.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 11:55:20 2026
    From Newsgroup: comp.unix.shell

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
    Which kind of begs the question, doesnrCOt it: who bought it, and why?

    IBM sold server blades to save company that they prevsiouly sold its PC business to. https://www.cnet.com/tech/tech-industry/ibm-sells-its-x86-server-business-to-lenovo-for-2-3-billion/
    (Jan2014) IBM sells its x86 server business to Lenovo for $2.3 billion
    An expected deal to sell off its Intel-based servers to the Chinese
    electronics company has arrived, reflecting the shifting realities of
    the market for powerful networked machines.

    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 12:21:49 2026
    From Newsgroup: comp.unix.shell

    Lars Poulsen <lars@beagle-ears.com> writes:
    If we define mainframes a large, very robust systems, they are still
    very relevant. Although it may be true that the major technology was
    in place before 1990 (non-stop cluster systems, transaction locking
    with completion/rollback and strategic redundancy). What you call
    customer inertia is also known as vendor lock-in.

    trivia, after early 70s "Future System" http://www.jfsowa.com/computer/memo125.htm https://en.wikipedia.org/wiki/IBM_Future_Systems_project https://people.computing.clemson.edu/~mark/fs.html

    imploded, head of POK was convincing corporate to kill the VM370
    product, shutdown the development group and transfer all the people to
    POK for MVS/XA. Endicott eventually acquires VM370 responsibility (for
    the mid-range), but has to recreate a development group from scratch. I
    get asked to help with a 16-CPU 370 and we con the 3033 processor
    engineers into helping in their spare time (a lot more interesting that remapping 168 logic to 20% faster chips). Everybody thought it was great
    until somebody tells the head of POK that it could be decades POK's
    favorite son operating system ("MVS") had effective 16-CPU (MVS
    documents were claiming that MVS 2-CPU support only had 1.2-1.5 times
    the throughput of single CPU, because of high multiprocessor support
    overhead, POK doesn't ship a 16-CPU system until after the turn of the century). Head of POK then invites some of us to never visit POK again
    and directs the 3033 processor engineers, "heads down and no
    distractions".

    About the same time, Endicott talks me into helping with ECPS for the
    138/148 (also used with 4331/4341), identify highest executed 6kbytes of
    VM370 kernel execution for re-implementing directly in machine microcode
    (at 10:1 performance increase, mid-range 370s were avg. 10 native
    instructions for every 370 instruction). Archived post with initial
    analysis, 6kbytes accounted for 79.55% of kernel execution: https://web.archive.org/web/20260416141952/https://www.garlic.com/~lynn/94.html#21

    After being invited to never visit POK again, I transfer out to IBM San
    Jose Research on the west coast and worked with Jim Gray and Vera Watson
    on the original SQL/relational RDBMS, System/R. After Jim Gray left IBM
    SJR for Tandem (fall1980), he did studies of system availability and
    outages. He was finding that hardware was becoming much more reliable
    and outages were shifting to environmental (floods, earthquakes, storms,
    etc) and people mistakes, needing redundant systems at geographically
    separated distances. https://courses.cs.duke.edu/spring11/cps210/papers/Gray_computers_stop.pdf https://web.archive.org/web/20260219063547/https://www.garlic.com/~lynn/grayft84.pdf

    As Jim was leaving, he was foisting off stuff on me including BofA;
    Research had System/R joint study with BofA and they ordered 60 VM4341s
    for System/R. Some amount of resistance from STL, IMS and next great
    DBMS "EAGLE". Was able to do tech transfer to Endicott (under the radar
    while company was pre-occupied with "EAGLE") for SQL/DS. Then when
    "EAGLE" implodes there was request how fast could System/R be ported to
    MVS, eventually released as "DB2" (originally for decision support
    only).

    Also when 1st transfer to west coast, I got to wander around silicon
    valley datacenters (and consolidated HONE was just up the road),
    including disk bldg14/engineering and bldg15/product test across the
    street. They had been doing 7/24, prescheduled stand-alone testing and mentioned that recently they had tried MVS, but it had 15min MTBF (in
    that environment, requiring manual re-ipl). I offer to rewrite I/O
    Supervisor, making it bullet proof and never fail allowing any amount of ondemand, concurrent testing (greatly improving productivity). I then do
    an internal research report "I/O Reliability Enhancement" and happen to
    mention MVS 15min MTBF, bringing down the wrath of the MVS organization
    on my head.

    Bldg15 gets the 1st engineering 3033 outside POK 3033 processor
    engineering (trivia: after 3033s started shipping, 3033 processor
    engineers start on trout/3090). Testing was only percent or two of CPU,
    so we scrounge up a 3830 controller and 3330 string and setup our own
    private online service. Summer 1978, bldg15 also gets engineering
    E5/4341 (year before 1st customer ship). Jan1979, branch office hears
    about it and cons me into doing (CDC6600 Fortran) benchmark for national
    lab that was looking at getting 70 VM4341s for compute farm (sort of
    leading edge of the coming cluster supercomputer tsunami). Spring 1979,
    some USAFDC (in the Pentagon) wanted to come by to talk to me about 20
    VM4341 systems, visit kept being delayed, by the time they came by (six
    months later), it had grown from 20 to 210. Also saw large corporations ordering hundreds of VM4341s at a time for installing out in
    departmental areas (sort of the leading edge of the coming distributed computing tsunami). VM4341s also contributed to HONE system popping up
    all over the world (and inside IBM, departmental conference rooms
    becomes scarce, so many converted to VM4341 rooms).
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 23:51:39 2026
    From Newsgroup: comp.unix.shell

    On Sun, 8 Nov 2026 13:45:03 -0800, Lars Poulsen wrote:

    On 11/8/2026 13:31, Lawrence DrCOOliveiro wrote:

    There was a paper on how Google did it, published 10 or 20 years
    ago. At that point, they had a total complement of about 460,000
    x86 servers. They would buy the cheapest component they could for
    every component but one: the power supply.

    With that kind of scale, who cares if 100 or 1000 machines are
    broken at any moment? The users certainly wonrCOt notice.

    The parallelism of a Google is a very different beast from the
    robust parallelism of a banking mainframe.

    Mainframes have never been that rCLrobustrCY. YourCOve mentioned elsewhere learning about Stratus and Tandem, who took robustness to a new level
    back in the 1980s, beyond anything the mainframe world could match.
    Think of that kind of redundancy multiplied tenfold, a hundredfold, a thousandfold, all built on open-source technologies: thatrCOs the kind
    of world we live in today.

    That is very different from transactions that must execute exactly
    once.

    That technology is pretty commonplace nowadays <https://kafka.apache.org/44/getting-started/introduction/>.

    Mainframes stopped being relevant back in the 1980s; every further
    development since then has just been driven by customer inertia.

    If we define mainframes a large, very robust systems, they are still
    very relevant.

    ThatrCOs kind of a circular definition though, isnrCOt it. IrCOll stick with the traditional definition: one which maximized I/O bandwidth over
    minimizing latency, batch operation efficiency over interactive
    responsiveness. That was very much IBMrCOs core business, and the
    obsolescence of that market directly correlates with IBM dwindling to
    a shadow of its former self.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 21:49:05 2026
    From Newsgroup: comp.unix.shell

    On 11/8/26 16:32, Lawrence DrCOOliveiro wrote:
    On Sun, 08 Nov 2026 08:32:30 -1000, Lynn Wheeler wrote:

    There was then industry articles that server chip makers were
    shipping half their products directly to megadatacenters. Shortly
    later, IBM sells off its server blade business.

    Which kind of begs the question, doesnrCOt it: who bought it, and why?

    Also, how come IBM was smart enough to
    sell it ?

    Of all the Old Biggies, seems only IBM still
    survives/thrives. DEC, Burroughs, Honeywell, DG
    and others - down the toilet. All of those
    made great computers, but SOMETHING went wrong
    and they couldn't cope.

    Somebody at IBM is making smart decisions,
    diversifying properly. Develop, make money,
    then dump (with royalty agreements). No tech
    is 'forever', so exploit "the window" and
    then move on.

    Yea, yea, 'Dilbert' made fun of them - but IBM
    is STILL HERE, and still a 'blue-chip' stock.

    What of their approach might benefit YOUR biz ?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 20:33:45 2026
    From Newsgroup: comp.unix.shell

    On 11/8/26 16:51, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 13:45:03 -0800, Lars Poulsen wrote:

    On 11/8/2026 13:31, Lawrence DrCOOliveiro wrote:

    There was a paper on how Google did it, published 10 or 20 years
    ago. At that point, they had a total complement of about 460,000
    x86 servers. They would buy the cheapest component they could for
    every component but one: the power supply.

    With that kind of scale, who cares if 100 or 1000 machines are
    broken at any moment? The users certainly wonrCOt notice.

    The parallelism of a Google is a very different beast from the
    robust parallelism of a banking mainframe.

    Mainframes have never been that rCLrobustrCY. YourCOve mentioned elsewhere learning about Stratus and Tandem, who took robustness to a new level
    back in the 1980s, beyond anything the mainframe world could match.
    Think of that kind of redundancy multiplied tenfold, a hundredfold, a thousandfold, all built on open-source technologies: thatrCOs the kind
    of world we live in today.


    Mainframes typically achieve an uptime percentage between 99.999% (five
    nines) and 99.9999999% (nine nines)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Sun Nov 8 22:59:21 2026
    From Newsgroup: comp.unix.shell

    On 11/8/26 22:33, Peter Flass wrote:
    On 11/8/26 16:51, Lawrence DrCOOliveiro wrote:
    On Sun, 8 Nov 2026 13:45:03 -0800, Lars Poulsen wrote:

    On 11/8/2026 13:31, Lawrence DrCOOliveiro wrote:

    There was a paper on how Google did it, published 10 or 20 years
    ago. At that point, they had a total complement of about 460,000
    x86 servers. They would buy the cheapest component they could for
    every component but one: the power supply.

    With that kind of scale, who cares if 100 or 1000 machines are
    broken at any moment? The users certainly wonrCOt notice.

    The parallelism of a Google is a very different beast from the
    robust parallelism of a banking mainframe.

    Mainframes have never been that rCLrobustrCY. YourCOve mentioned elsewhere >> learning about Stratus and Tandem, who took robustness to a new level
    back in the 1980s, beyond anything the mainframe world could match.
    Think of that kind of redundancy multiplied tenfold, a hundredfold, a
    thousandfold, all built on open-source technologies: thatrCOs the kind
    of world we live in today.


    Mainframes typically achieve an uptime percentage between 99.999% (five nines) and 99.9999999% (nine nines)

    They ARE very very very good !

    Noted in this group though - I/O arch diffs between
    mainframes and minis.

    Will someone try to elaborate ?

    Started off on a "mini" - PDP-11 - with a PDP-8
    kinda in the background (but wasn't really allowed
    to use it for anything). This I/O diff, didn't
    NOTICE it, but was likely there. Long-after
    insights would be interesting.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 9 04:42:48 2026
    From Newsgroup: comp.unix.shell

    On Sun, 8 Nov 2026 20:33:45 -0700, Peter Flass wrote:

    Mainframes typically achieve an uptime percentage between 99.999%
    (five nines) and 99.9999999% (nine nines)

    The hyperscalers probably manage that well, if not better.

    There is an article from 1986 on Bitsavers which describes having to
    reboot an IBM mainframe to turn daylight saving on and off.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 9 10:01:13 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-09, Lawrence DrCOOliveiro wrote:

    On Sun, 8 Nov 2026 20:33:45 -0700, Peter Flass wrote:

    Mainframes typically achieve an uptime percentage between 99.999%
    (five nines) and 99.9999999% (nine nines)

    The hyperscalers probably manage that well, if not better.

    There is an article from 1986 on Bitsavers which describes having to
    reboot an IBM mainframe to turn daylight saving on and off.

    *That* sounds like complicating a problem that would be made simpler by
    not using the local time, or at least DST-adjusted local time.

    What did they do when the clock moved backwards? Stop operations for one
    hour? Or eventual clashes would be acceptable? Separate, incrementing
    unique IDs?
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 9 11:08:53 2026
    From Newsgroup: comp.unix.shell

    On 09/11/2026 03:33, Peter Flass wrote:
    Mainframes typically achieve an uptime percentage between 99.999% (five nines) and 99.9999999% (nine nines)

    Correcting Lawrence won't change a thing.
    TalkingBollocksrao is a way of life for some people.

    Look at yer president....
    --
    Civilization exists by geological consent, subject to change without notice.
    rCo Will Durant

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 9 15:59:03 2026
    From Newsgroup: comp.unix.shell

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Sun, 8 Nov 2026 13:45:03 -0800, Lars Poulsen wrote:

    On 11/8/2026 13:31, Lawrence DrCOOliveiro wrote:

    There was a paper on how Google did it, published 10 or 20 years
    ago. At that point, they had a total complement of about 460,000
    x86 servers. They would buy the cheapest component they could for
    every component but one: the power supply.

    With that kind of scale, who cares if 100 or 1000 machines are
    broken at any moment? The users certainly wonrCOt notice.

    The parallelism of a Google is a very different beast from the
    robust parallelism of a banking mainframe.

    Mainframes have never been that rCLrobustrCY

    Sure they have. Burroughs had clustered systems by 1968,
    with shared storage and shared peripherals.


    . YourCOve mentioned elsewhere
    learning about Stratus and Tandem, who took robustness to a new level
    back in the 1980s, beyond anything the mainframe world could match.

    Sure, pull the other one. Several of my former Burroughs colleagues
    worked at Tandem, and we at Burroughs/Unisys built systems designed with
    fault tolerance as a key goal (e.g. OPUS, the design of which started
    in 1989).

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Mon Nov 9 07:32:09 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> writes:
    Noted in this group though - I/O arch diffs between
    mainframes and minis.

    previously posted, 1988, ibm branch office asked me if I could help LLNL
    with standardization of some serial stuff they had been working with,
    which quickly becomes fibre-channel standard ("FCS", including some
    stuff I had done in the 80s, initially 1gbit transfer, full-duplex,
    aggregate 200mbytes/sec).
    https://en.wikipedia.org/wiki/Fibre_Channel

    then IBM releases some serial stuff they had been working with for
    nearly a decade (when it is already obsolete) as ESCON (initially 10mbytes/sec). Then some IBM engineers get involved with FCS and define
    a heavy-weight protocol that radically reduced native throughput https://en.wikipedia.org/wiki/FICON

    Latest public benchmark I've found is 2010 z196 "Peak I/O" getting 2M
    IOPS using 104 FICON (20K IOPS/FICON). About the same time a native FCS
    is announced for E5-2600 server blades getting over million IOPS (two
    such FCS higher throughput than 104 FICON running over FCS). Note IBM
    docs has SAPs (system assist processors that now do the actual I/O) CPU
    be kept to 70% ... or 1.5M IOPS ... also no CKD DASD have been made for
    decades (just simulated with industry standard fixed-block devices).

    This "Evolution of the System z Channel" (SHARE 2011 presentation at
    wayback machine) https://web.archive.org/web/20170829213251/https://share.confex.com/share/117/webprogram/Handout/Session9931/9934pdhj%20v0.pdf
    talks about after 2010 z196 "Peak I/O" benchmark and "zHPF" that
    increased throughput from 20K IOPS/FICON to 52K IOPS/FICON then to 92K IOPS/FICON (aka from 1/50th to almost 1/10th the native FCS announced in
    2010).
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 07:09:17 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> schrieb:

    Noted in this group though - I/O arch diffs between
    mainframes and minis.

    I have a somewhat personal definition of a mainframe, which I also
    includes the classical ones.

    A mainframe is a computer that

    - is very expensive
    - takes large resources to run (a computer center)
    - has very good performance in at least one field
    - is not a cluster, massively parallel etc

    As computers have evolved, the field of performance has shifted.
    The 704 and the Cray-1 both had high computing performance for
    their day, but low reliability. The 360/30 was slow, but had
    good I/O capabilities.

    Today's mainframes can no longer compete on compute power, but
    they have extremely high reliability (you can literally fire a
    bullet through a CPU, and things will migrate smoothly - if you
    don't hit the Recovery Unit), good I/O and lots of sub-processors
    to lighten the load on the CPU.

    I read that, when minis came along, their first defining
    characteristic was that they didn't need computer center resources
    and fit in a single room.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 07:27:50 2026
    From Newsgroup: comp.unix.shell

    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to
    take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY
    setup that the big folks operate in your own homelab, because all the foundation software they use is available to you, too <https://docs.xcp-ng.org/vms/vm-migration/>.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alexander Schreiber@als@usenet.thangorodrim.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 10:50:32 2026
    From Newsgroup: comp.unix.shell

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to
    take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY
    setup that the big folks operate in your own homelab, because all the foundation software they use is available to you, too
    <https://docs.xcp-ng.org/vms/vm-migration/>.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    Highly distributed systems like those run and offered by the hyperscalers
    are built on an entirely different design philosophy:
    - _everything_ fails all the time (law of big numbers: take the MTBF
    for a compute component, run a lot of them and you've got a steady
    rain of failures, e.g. say you've got an MTBF of 1 million hours and
    you run 2 million of these devices, then on average you'll have a
    failure every half hour)
    - deal with it
    - run a software stack that is highly distributed and highly redundant,
    e.g. do not just store one or two copies of data, store 4 copies
    of the data plus two copies of the recovery checksums so you still
    recover the data after losing some pieces
    - you will end up with impressive complexity because building a reliable
    system on top of unreliable components is not easy
    - it helps a lot if your workloads can tolerate small to tiny amounts
    of failure (e.g. loading a web page times out, uploading a file fails)
    - but reliable operations (such as a planet scale consistent database)
    are doable, they just need more work and smarts
    - one key aspect: well designed highly distributed system scale very
    well, a scale-up factor of 10 without any system changes aside from
    adding more hardware falls under "baseline capability" and much higher
    scale-ups are the norm

    Kind regards,
    Alex.
    --
    "Opportunity is missed by most people because it is dressed in overalls and
    looks like work." -- Thomas A. Edison
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 07:37:44 2026
    From Newsgroup: comp.unix.shell

    On 11/10/26 02:50, Alexander Schreiber wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher
    reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of
    mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to
    take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY
    setup that the big folks operate in your own homelab, because all the
    foundation software they use is available to you, too
    <https://docs.xcp-ng.org/vms/vm-migration/>.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    Highly distributed systems like those run and offered by the hyperscalers
    are built on an entirely different design philosophy:
    - _everything_ fails all the time (law of big numbers: take the MTBF
    for a compute component, run a lot of them and you've got a steady
    rain of failures, e.g. say you've got an MTBF of 1 million hours and
    you run 2 million of these devices, then on average you'll have a
    failure every half hour)

    Didn't I read somewhere that techs in large datacenters get around on rollerblades to swap out failing components?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 15:16:24 2026
    From Newsgroup: comp.unix.shell

    Thomas Koenig <tkoenig@netcologne.de> writes:
    c186282 <c186282@nnada.net> schrieb:

    Noted in this group though - I/O arch diffs between
    mainframes and minis.

    I have a somewhat personal definition of a mainframe, which I also
    includes the classical ones.

    A mainframe is a computer that

    - is very expensive
    - takes large resources to run (a computer center)
    - has very good performance in at least one field
    - is not a cluster, massively parallel etc

    Some mainframes were clustered. Burroughs, for example,
    could share storage between up to four independent hosts;
    with shared access to files (with hardware record lockout
    for shared updates).

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 15:18:28 2026
    From Newsgroup: comp.unix.shell

    Peter Flass <Peter@Iron-Spring.com> writes:
    On 11/10/26 02:50, Alexander Schreiber wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher
    reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of
    mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to >>> take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY
    setup that the big folks operate in your own homelab, because all the
    foundation software they use is available to you, too
    <https://docs.xcp-ng.org/vms/vm-migration/>.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    Highly distributed systems like those run and offered by the hyperscalers
    are built on an entirely different design philosophy:
    - _everything_ fails all the time (law of big numbers: take the MTBF
    for a compute component, run a lot of them and you've got a steady
    rain of failures, e.g. say you've got an MTBF of 1 million hours and
    you run 2 million of these devices, then on average you'll have a
    failure every half hour)

    Didn't I read somewhere that techs in large datacenters get around on >rollerblades to swap out failing components?


    The Minneapolis Fed Reserve operators were reputed to have worn
    roller skates when sorting checks (the sorters, with full complement
    of pockets, were quite long).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 18:36:50 2026
    From Newsgroup: comp.unix.shell

    On 2026-11-10, Thomas Koenig <tkoenig@netcologne.de> wrote:

    I read that, when minis came along, their first defining
    characteristic was that they didn't need computer center resources
    and fit in a single room.

    And you could plug them into a wall socket.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 19:55:46 2026
    From Newsgroup: comp.unix.shell

    On Tue, 10 Nov 2026 10:50:32 +0100, Alexander Schreiber wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but
    they have extremely high reliability (you can literally fire a
    bullet through a CPU, and things will migrate smoothly - if you
    don't hit the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much
    higher reliability through massive parallelism, based on cheap, yet
    highly redundant hardware running a Free Software stack that is not
    priced per CPU. That is much more cost-effective and any equivalent
    number of mainframes. And there is no rCLRecovery UnitrCY that you can
    shoot at to take it out.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    - The daylight savings change.
    Once you get the GMT time and local offset set correctly the
    other problem is the daylight savings change. Unlike VM, MVS
    allows you to change the local time without an IPL so you should
    be able to make the daylight savings change on the fly. We even
    did it once in production. SMF data uses local time for time
    stamps, so it really got messed up. JES2 automatic commands also
    use local time and they were halted. There are probably other
    problems, but those were enough for us. We IPL for the daylight
    savings change.
    -- Dave Crow, rCLSetting a ComputerrCOs Clock Correctly: Does
    anybody know what time it is?rCY,
    presentation given to SHARE (IBM user group) in 1986
    <https://bitsavers.trailing-edge.com/pdf/ibm/share/SHARE67_Presentation_on_Setting_a_Computers_Clock_Correctly_1986.pdf>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 19:57:28 2026
    From Newsgroup: comp.unix.shell

    On Tue, 10 Nov 2026 18:36:50 GMT, Charlie Gibbs wrote:

    On 2026-11-10, Thomas Koenig <tkoenig@netcologne.de> wrote:

    I read that, when minis came along, their first defining
    characteristic was that they didn't need computer center resources
    and fit in a single room.

    And you could plug them into a wall socket.

    Some kind of power conditioning would have been highly recommended.

    I can remember, during the 1980s, during the least little power
    brownout, our campusrCOs main VAX systems would instantly go down, and
    take about 15 minutes to come back up.

    Meanwhile, the PCs on our desks didnrCOt miss a beat.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Pancho@Pancho.Jones@protonmail.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 20:51:47 2026
    From Newsgroup: comp.unix.shell

    On 11/9/26 10:01, Nuno Silva wrote:
    On 2026-11-09, Lawrence DrCOOliveiro wrote:

    On Sun, 8 Nov 2026 20:33:45 -0700, Peter Flass wrote:

    Mainframes typically achieve an uptime percentage between 99.999%
    (five nines) and 99.9999999% (nine nines)

    The hyperscalers probably manage that well, if not better.

    There is an article from 1986 on Bitsavers which describes having to
    reboot an IBM mainframe to turn daylight saving on and off.

    *That* sounds like complicating a problem that would be made simpler by
    not using the local time, or at least DST-adjusted local time.


    Yep, obvious really, UTC internally, local time only at the presentation layer.

    When apps were just one country, one timezone, you could kind of forgive
    it, but I was working on new multinational apps right up to the late
    noughties that got it wrong.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alexander Schreiber@als@usenet.thangorodrim.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 22:02:01 2026
    From Newsgroup: comp.unix.shell

    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 11/10/26 02:50, Alexander Schreiber wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher
    reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of
    mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to >>> take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY
    setup that the big folks operate in your own homelab, because all the
    foundation software they use is available to you, too
    <https://docs.xcp-ng.org/vms/vm-migration/>.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    Highly distributed systems like those run and offered by the hyperscalers
    are built on an entirely different design philosophy:
    - _everything_ fails all the time (law of big numbers: take the MTBF
    for a compute component, run a lot of them and you've got a steady
    rain of failures, e.g. say you've got an MTBF of 1 million hours and
    you run 2 million of these devices, then on average you'll have a
    failure every half hour)

    Didn't I read somewhere that techs in large datacenters get around on rollerblades to swap out failing components?

    You don't want that in a data center, because just it increases the risk
    of injury even more. You already need aid stations around on the floor
    for when, not if, someone gets hurt (usually scrapes or shallow cuts by sharp-edged parts in the machines).

    Kind regards,
    Alex.
    --
    "Opportunity is missed by most people because it is dressed in overalls and
    looks like work." -- Thomas A. Edison
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 22:19:32 2026
    From Newsgroup: comp.unix.shell

    According to Peter Flass <Peter@Iron-Spring.com>:
    Didn't I read somewhere that techs in large datacenters get around on >rollerblades to swap out failing components?

    I don't think so. I've read that Google has people wandering around with grocery carts full of spare parts that they swap into failed servers.
    You don't want them banging into the racks.

    At the Western Union building at 60 Hudson St in NYC, they did manual
    messge switching, in which one teletype punched out a message on paper
    tape, they tore it off, then girls (we'd call them young women now)
    on skates zipped the tapes to other teletypes to send the message
    onward.

    I gather that one of the earliest large scale uses of minicomputers
    was to automate that process.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Tue Nov 10 23:29:31 2026
    From Newsgroup: comp.unix.shell

    On 11/10/26 09:37, Peter Flass wrote:
    On 11/10/26 02:50, Alexander Schreiber wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher
    reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of
    mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to >>> take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY
    setup that the big folks operate in your own homelab, because all the
    foundation software they use is available to you, too
    <https://docs.xcp-ng.org/vms/vm-migration/>.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    Highly distributed systems like those run and offered by the hyperscalers
    are built on an entirely different design philosophy:
    -a - _everything_ fails all the time (law of big numbers: take the MTBF
    -a-a-a for a compute component, run a lot of them and you've got a steady
    -a-a-a rain of failures, e.g. say you've got an MTBF of 1 million hours and >> -a-a-a you run 2 million of these devices, then on average you'll have a
    -a-a-a failure every half hour)

    Didn't I read somewhere that techs in large datacenters get around on rollerblades to swap out failing components?

    IS an issue !!!

    Linux/UNIX are 'better' at this.

    As for 'failures every half hour' ... can't
    HAVE that !


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alexander Schreiber@als@usenet.thangorodrim.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 11 12:19:16 2026
    From Newsgroup: comp.unix.shell

    c186282 <c186282@nnada.net> wrote:
    On 11/10/26 09:37, Peter Flass wrote:
    On 11/10/26 02:50, Alexander Schreiber wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Tue, 10 Nov 2026 07:09:17 -0000 (UTC), Thomas Koenig wrote:

    Today's mainframes can no longer compete on compute power, but they
    have extremely high reliability (you can literally fire a bullet
    through a CPU, and things will migrate smoothly - if you don't hit
    the Recovery Unit) ...

    Cloud providers like Amazon, Google, Microsoft etc offer much higher
    reliability through massive parallelism, based on cheap, yet highly
    redundant hardware running a Free Software stack that is not priced
    per CPU. That is much more cost-effective and any equivalent number of >>>> mainframes. And there is no rCLRecovery UnitrCY that you can shoot at to >>>> take it out.

    The nice thing is, you can run the same sort of rCLenterprise-classrCY >>>> setup that the big folks operate in your own homelab, because all the
    foundation software they use is available to you, too
    <https://docs.xcp-ng.org/vms/vm-migration/>.

    Not exactly the same. The mainframe design philosophy includes "The
    machine MUST NOT fail", for which one pays in complexity and system
    cost. As long as your workload fits on that single machine (or a
    small cluster (Parallel Sysplex)) and is of the "MUST NOT fail"
    nature, fine.

    Highly distributed systems like those run and offered by the hyperscalers >>> are built on an entirely different design philosophy:
    -a - _everything_ fails all the time (law of big numbers: take the MTBF
    -a-a-a for a compute component, run a lot of them and you've got a steady >>> -a-a-a rain of failures, e.g. say you've got an MTBF of 1 million hours and >>> -a-a-a you run 2 million of these devices, then on average you'll have a >>> -a-a-a failure every half hour)

    Didn't I read somewhere that techs in large datacenters get around on
    rollerblades to swap out failing components?

    IS an issue !!!

    Linux/UNIX are 'better' at this.

    The failures I mentioned are hardware failing. OS and application level failures sit on top of that.

    As for 'failures every half hour' ... can't
    HAVE that !

    True, in real large data center environments the failure frequency is a
    lot higher than one failure per half hour (across all easily replacable component such as RAM, CPU, disk, PSU, mainboard, switches, ...).

    Kind regards,
    Alex.
    --
    "Opportunity is missed by most people because it is dressed in overalls and
    looks like work." -- Thomas A. Edison
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alexander Schreiber@als@usenet.thangorodrim.de to comp.os.linux.misc,comp.unix.shell,alt.folklore.computers on Wed Nov 11 12:09:20 2026
    From Newsgroup: comp.unix.shell

    John Levine <johnl@taugh.com> wrote:
    According to Peter Flass <Peter@Iron-Spring.com>:
    Didn't I read somewhere that techs in large datacenters get around on >>rollerblades to swap out failing components?

    I don't think so. I've read that Google has people wandering around with grocery carts full of spare parts that they swap into failed servers.

    Not exactly "wandering around with grocery carts". The time of the service techs is not cheap, so you want to optimize its use - their repair jobs
    are scheduled to maximize time spent fixing machines and minimize time "wandering around" - so there is software that e.g. figures out if a
    given rack has enough pending repairs to make it worth sending a tech
    with a full cart loaded with spares there. You do not want your techs
    hopping across the DC floor to e.g. replace just a single stuck fan per
    rack as that would give them lots of exercise but the employer would
    receive little in useful work.

    Kind regards,
    Alex.
    --
    "Opportunity is missed by most people because it is dressed in overalls and
    looks like work." -- Thomas A. Edison
    --- Synchronet 3.22a-Linux NewsLink 1.2