|
|
| Author |
Message |
| 25 new of 467 responses total. |
keesan
|
|
response 225 of 467:
| 
Oct 22 03:37 UTC 2004 |
Joe at nextgrex is still not usable. Large sections at starts and end of
lines get blocked out (in my case by amber) when I type.
No such problem at thisgrex.
|
gelinas
|
|
response 226 of 467:
|
Oct 22 05:07 UTC 2004 |
Outbound ftp from the new grex machine to the current grex machine works
because we let everyone use our own network; pf is configured to allow
these connections.
I'll change the rules to use the group later today, after I get some sleep.
|
janc
|
|
response 227 of 467:
|
Oct 22 13:31 UTC 2004 |
The URL for the preliminary info about nextGrex is
http://www.unixpapa.com/nextgrex.html . nextGrex is web accessible in any
useful way yet.
|
janc
|
|
response 228 of 467:
|
Oct 22 14:35 UTC 2004 |
Excuse me. Lost a "not" in that last sentance.
|
mfp
|
|
response 229 of 467:
|
Oct 22 14:39 UTC 2004 |
When do I get to have a neXtGreX beta account?
|
janc
|
|
response 230 of 467:
|
Oct 22 18:18 UTC 2004 |
Probably in a couple weeks.
|
janc
|
|
response 231 of 467:
|
Oct 22 19:05 UTC 2004 |
Cindi pointed out that when you run 'lynx' under screen on the new Grex, it
becomes very slow. This doesn't happen with 'lynx' outside of screen, nor
with lynx/screen on oldGrex.
When I run lynx under screen, it seems to paint the whole screen background
light grey. Each time you scroll or go to a new page it first paints the
whole screen black, one character at a time, and then overwrites the black
by reprinting every character of the screen in black-on-grey mode. It also
frequently draws screens twice. I'm guessing this is all lynx responding to
the particular termcap provided by screen in a gruesome manner. I feel like
there may be some additional slowdown just from screen's extra processing,
but that is relatively small. I suspect the fix is either a change in lynx's
config file or in the termcap.
Googling for any information on 'screen' is a dismal task.
I'm not going to work on this issue right now. It's just not that high
priority. If anyone has any clues about it, I'd be interested though.
|
janc
|
|
response 232 of 467:
|
Oct 22 19:05 UTC 2004 |
Correction: Sindi.
|
janc
|
|
response 233 of 467:
|
Oct 22 19:20 UTC 2004 |
Sindi reports w3m loads slowly. I thought it did fine. Does a nice job of
rendering table formatted pages.
She also asked about the links browser. It is installed, as 'links'. The
version installed is links+-2.1pre14. I think it's a links2 version, and
fairly recent.
|
naftee
|
|
response 234 of 467:
|
Oct 22 21:24 UTC 2004 |
Your page, janc, says that NextGreX will have Picospan installed for sure.
Does that mean that you are effectively nullifying a potential vote issue?
|
keesan
|
|
response 235 of 467:
|
Oct 23 01:45 UTC 2004 |
Links works for me now. Lynx and w3m both loaded slowly BECAUSE I was using
'screen'. Lynx pages load twice or even five times in both grex's even
without screen. Screen may slow this down enough for you to see it on a
faster connection but when I dial in it is very noticeable at all times. A
friend said ncurses might be involved. The latest links is links-2.1pre15.
Sindi Sindy Syndi Cyndi etc. are all aliases for Cynthia and all work.
My grandfather thought I was Cinty.
It would be handy to use screen in order to copy between lynx and pine but
I can also just send mail from within lynx with pine and mailto:. It would
be handy to copy pieces of web pages to bbs and that requires a few more steps
without screen (print to a file, exit lynx, start bbs, import the file - edit
it at some point).
|
janc
|
|
response 236 of 467:
|
Oct 23 02:03 UTC 2004 |
I'm wondering. Do you actually think that suggestion has any merit, or
are you just raising it to make sure there won't be any overlong hiatus
in the stream of criticism that any staff person who does anything
receives around here?
As it happens, Picospan was installed on NextGrex before the vote was
proposed. It wasn't installed be me. I just fixed some things that got
incidentally broken when it was installed.
And I'm reasonably confident that nobody wants to delay working on nextGrex
in deference to this vote. The fundamental question is whether we want to
move away from Picospan. Whether or not Picospan is installed on nextGrex
when we come up on it does not influence that fundamental question. It
can always be removed.
Is that a good enough defense? Am I cleared of this charge of pursuing
a devious anti-democratic conspiracy against Grexers by spending all my
scant free time for the last month working on nextGrex?
Ah well. It's only natural to suspect that I'd be up to something sneaky
to ensure that my conferencing software isn't used on nextGrex. I mean,
anybody'd think that.
|
janc
|
|
response 237 of 467:
|
Oct 23 02:04 UTC 2004 |
Sindi Sindy Cindy Cyndi Cinty slipped in.
|
mfp
|
|
response 238 of 467:
|
Oct 23 03:42 UTC 2004 |
Jan, I'm curious. Will NeXtGreX allow users to delete their own items, even
if they include thousands of responses from hundreds of other users?
Also, will NXGX support any sort of mechanism allowing users to easily delete
years of their responses, while inconveniencing other users by running up the
load averages and making millions of not thousands of items that haven't been
used for years seem to be new?
|
gelinas
|
|
response 239 of 467:
|
Oct 23 06:05 UTC 2004 |
I've now removed the rules permitting specific users (except staff and
daemons) Internet access and replaced them with a rule permitting group
"inet" that access.
I tried chmodding /usr/bin/telnet to set-group-ID, but I still couldn't
get an outbound connection. (I also changed the group to "inet.")
You might try your wrapper, now, Jan, to see if it works.
|
cross
|
|
response 240 of 467:
|
Oct 23 06:19 UTC 2004 |
(The last part isn't surprising, as /usr/bin is probably mounted
nosuid.)
|
janc
|
|
response 241 of 467:
|
Oct 24 01:58 UTC 2004 |
We don't want /usr/bin/telnet to be set-group-id. That would give everyone
access. The set-group-id wrapper has the brains to throw away it's
set-group-id status if the user isn't actually qualified for it.
I'll get this all into CVS if it isn't there already. I think I might want
a separate subdirectory for the pf stuff.
|
gelinas
|
|
response 242 of 467:
|
Oct 24 02:42 UTC 2004 |
I see you've already created the separate directory. :)
I updated 01-inet_wrap to reflect Mark's suggestion/request on the group name.
|
janc
|
|
response 243 of 467:
|
Oct 24 03:27 UTC 2004 |
Yeah. I created a 'pf' directory, moved the installation of the pf.conf
script into there from the 'openbsd' partition, and moved the symlinking
of the various files into there from the 'misc' directory, and added in my
new inet_wrap.c program. Thought all this stuff needed pulling together.
As I look at it, I think this solution is more restrictive that the previous
one, where all the users were listed in the pf.conf file. The only programs
that group 'internet' users can run as group 'internet' are the ones linked
into the directory, currently ftp, rcp, rsh, scp, sftp, ssh, and telnet.
They can't for example, compile their own irc client and be able to run it.
I don't think this is a problem. We can certainly link more programs in ther
as needed.
I notice that nextGrex doesn't have rlogin. I don't think this is necessarily
bad. rlogin is pretty obsolete.
We should probably get an irc client for members to use. Dunno which one.
|
gelinas
|
|
response 244 of 467:
|
Oct 24 03:43 UTC 2004 |
Yes, it is more restrictive. However, we _could_ document the use
of inet_wrapper, and let them add things they want in their own bin
directory. :)
|
mfp
|
|
response 245 of 467:
|
Oct 24 05:19 UTC 2004 |
Thanks, Jan!
|
mfp
|
|
response 246 of 467:
|
Oct 24 05:20 UTC 2004 |
oh. by the way: for as much as it matters, i would PERSONALLY recommend
installing irssi as the irc client. it's neat and popular, in my experience.
|
naftee
|
|
response 247 of 467:
|
Oct 24 05:50 UTC 2004 |
BitchX is better.
|
mfp
|
|
response 248 of 467:
|
Oct 24 06:30 UTC 2004 |
It really isn't. irssi is, uh, not tacky.
|
janc
|
|
response 249 of 467:
|
Oct 24 15:05 UTC 2004 |
Both bhoward (in Tokyo) and tweenex (in England) have had problems
connecting to NextGrex. There has been some speculation among
people who know more about these things than I do that it might be
due to the packet filter handling fragmented packets incorrectly.
This seems to me to be a serious problem, and not one I know
anything about.
I managed to get nethack to install. The ports tree makefile for
the non-x11 version was incorrect - hackdata is not a dependency.
|
