NN 6.7.3 Updates (Hostname problem fixed)
Aaron W. Hsu
A while back I brought NN back into the realm of the working in
Slackware, but I never fixed the hostname issue on Slackware. Additional
problems also remained in the package until now. :-)
I've taken a moment and fixed some problems in the NN package for
Slackware. The hostname.c fix should also be sent upstream, but since
upstream isn't very responsive on this issue, I've decided to make this
available to the public through the appropriate newsgroups.
<gopher://gopher.sacrideo.us/9nn/nn_slack.tar.xz>
You will find the above package contains the updated SlackBuild,
and also has the hostname.c diff in nn.diff.gz, for those who
wish to apply it to a generic and vanilla installation.
The following issues have been resolved:
1) NN now grabs the hostname from /etc/HOSTNAME.
This fixes an issue where nn would quite because
gethostname(3) would not return the FQDN.
2) NN is set to use gpg for signing now instead of pgp.
3) The appropriate machine headers are included for i386 and
x86_64 now.
Previously they included m-sparc.h. Now, i386 gets the right
one, and a new m-x86_64.h file has been added that sets the
right sizes.
4) hostname.c did not include "global.h" correctly, meaning that
compiling with HOSTNAME_FILE support instead of
gethostname() would fail. This has been fixed.
Hope you like it! Let me know what you think.
Aaron W. Hsu
andrew
> Hope you like it! Let me know what you think.
Excellent news Aaron, I will be setting up nn again this weekend. I will
admit to abandoning it a few months ago because of the hostname issue :).
I see your changes are in -current as well:
+---------
n/nn-6.7.3-i486-3.txz: Rebuilt.
Patched to retrieve hostname from /etc/HOSTNAME, use gpg rather than pgp,
and to use correct sizeof(long) depending on the system architecture.
Thanks to Aaron W. Hsu.
+-------
Thanks for making the effort!
Andrew
--
Do you think that's air you're breathing?
Aaron W. Hsu
>Excellent news Aaron, I will be setting up nn again this weekend. I will
>admit to abandoning it a few months ago because of the hostname issue :).
>I see your changes are in -current as well:
Yes, sorry about the delay. Sometimes it takes a while for me to get
around to things. :-)
>+---------
>n/nn-6.7.3-i486-3.txz: Rebuilt.
> Patched to retrieve hostname from /etc/HOSTNAME, use gpg rather than pgp,
> and to use correct sizeof(long) depending on the system architecture.
> Thanks to Aaron W. Hsu.
>+-------
Pat was remarkably friendly and willing to accept the patches.
Aaron W. Hsu
andrew
>Yes, sorry about the delay. Sometimes it takes a while for me to get
>around to things. :-)
Well, it took me a while to relearn nn as well :). I don't suppose
by any wild chance you managed to ever get vim working with nn? I
I have tried and failed several times and I can tell you I am not
really a nano fan!
Lew Pitcher
> Aaron W. Hsu <arcfide@local> writes:
>
>>Yes, sorry about the delay. Sometimes it takes a while for me to
>>get around to things. :-)
> Well, it took me a while to relearn nn as well :). I don't suppose
> by any wild chance you managed to ever get vim working with nn? I
> I have tried and failed several times and I can tell you I am not
> really a nano fan!
If memory serves, nn uses the default editor. You can set the
default editor in your .profile file.
EXPORT EDITOR=/usr/bin/vim
or some such should do it...
LewPi...@LewPitcher.ca
--
Official Website -->> http://lewpitcher.ca/
Something to look at: -->> http://www.emusclemag.com/
Lonely in Brampton? -->> http://gaypros.meetup.com/cities/ca/on/brampton/
Peel HIV/AIDS Network -->> http://www.phan.ca/home.html
Lew Pitcher
> In alt.os.linux.slackware andrew <and...@skamandros.invalid> wrote:
>> Aaron W. Hsu <arcfide@local> writes:
>>
>>>Yes, sorry about the delay. Sometimes it takes a while for me to
>>>get around to things. :-)
>
>> Well, it took me a while to relearn nn as well :). I don't suppose
>> by any wild chance you managed to ever get vim working with nn? I
>> I have tried and failed several times and I can tell you I am not
>> really a nano fan!
>
> If memory serves, nn uses the default editor. You can set the
> default editor in your .profile file.
>
> EXPORT EDITOR=/usr/bin/vim
>
> or some such should do it...
Sorry to followup my own post, but if you are using xterm (or some
such) and your .profile isn't being called, then build yourself a
.bashrc file and include the command:
. ~/.profile
And that will load your profile for your xterm session. Of course
there are other ways of doing this...
Aaron W. Hsu
>Aaron W. Hsu <arcfide@local> writes:
>>Yes, sorry about the delay. Sometimes it takes a while for me to get
>>around to things. :-)
>Well, it took me a while to relearn nn as well :). I don't suppose
>by any wild chance you managed to ever get vim working with nn? I
>I have tried and failed several times and I can tell you I am not
>really a nano fan!
NN uses your default editor. Currently, I have it using NEdit. You just
make sure that your EDITOR environment is set correctly. Also, feel free
to check out the NN FAQ, which is still relevant. There are also
relevant posts about the configuration file in the nn newsgroup which
makes a difference when you're trying to do something that the NN
documentation doesn't make perfectly clear.
Aaron W. Hsu
Lew Pitcher
Um, we already said this. And we said it with more clarity, as
well. Try and keep up.
Aaron W. Hsu
>> andrew <and...@skamandros.invalid> writes:
>>>Aaron W. Hsu <arcfide@local> writes:
>
>>>Well, it took me a while to relearn nn as well :). I don't suppose
>>>by any wild chance you managed to ever get vim working with nn? I
>>>I have tried and failed several times and I can tell you I am not
>>>really a nano fan!
>
>> NN uses your default editor. Currently, I have it using NEdit. You
>> just make sure that your EDITOR environment is set correctly.
>> Also, feel free to check out the NN FAQ, which is still relevant.
>> There are also relevant posts about the configuration file in the
>> nn newsgroup which makes a difference when you're trying to do
>> something that the NN documentation doesn't make perfectly clear.
>Um, we already said this. And we said it with more clarity, as
>well. Try and keep up.
Yeah, you already said it, and he wanted to know if I had ever done
anything like it, so I went ahead and repeated succinctly your
instructions (we?), as well as detailing some other information that
would be helpful to him.
So what?
Aaron W. Hsu
Dan C
>> andrew <and...@skamandros.invalid> writes:
>>>Aaron W. Hsu <arcfide@local> writes:
>
>>>Well, it took me a while to relearn nn as well :). I don't suppose by
>>>any wild chance you managed to ever get vim working with nn? I I have
>>>tried and failed several times and I can tell you I am not really a
>>>nano fan!
>
>> NN uses your default editor. Currently, I have it using NEdit. You just
>> make sure that your EDITOR environment is set correctly. Also, feel
>> free to check out the NN FAQ, which is still relevant. There are also
>> relevant posts about the configuration file in the nn newsgroup which
>> makes a difference when you're trying to do something that the NN
>> documentation doesn't make perfectly clear.
>
> Um, we already said this. And we said it with more clarity, as well.
> Try and keep up.
Nobody pays any attention to your posts, you clueless troll.
They just get ignored.
Bugger off, troll.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he wiped the vomit from his chin.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/