Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
..and as it turns out the administrator was trying, and failing, to upgrade lynx to a later edition. In an effort to restore things, we now have an older edition of lynx then was working just fine before the upgrade effort. Karen On Thu, 2 Dec 2021, Bela Lubkin wrote: If you log in and out daily then this wouldn't have helped. The only situation in which 'rehash' would have helped is if some admin moved where the lynx executable was, while you were currently logged in. When the shell successfully runs a program, it keeps a note about where it found it; if the program is moved then that note is invalid. 'rehash' tells it to throw out the current set of notes. The notes are only kept during a single login (actually: single run of the shell). If someone moved the program and 'rehash' was going to fix it, logging out & back in would equally have fixed it. I've been logged into this shell since June 14th (kept in background with GNU `screen`, so despite disconnecting many times and even having had my desktop reboot once due to a power failure, my active shell is still lumping along). So I might actually have need to rehash once in a while, though it's unlikely to surprise me since I'm the admin... :) Bela<
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
If you log in and out daily then this wouldn't have helped. The only situation in which 'rehash' would have helped is if some admin moved where the lynx executable was, while you were currently logged in. When the shell successfully runs a program, it keeps a note about where it found it; if the program is moved then that note is invalid. 'rehash' tells it to throw out the current set of notes. The notes are only kept during a single login (actually: single run of the shell). If someone moved the program and 'rehash' was going to fix it, logging out & back in would equally have fixed it. I've been logged into this shell since June 14th (kept in background with GNU `screen`, so despite disconnecting many times and even having had my desktop reboot once due to a power failure, my active shell is still lumping along). So I might actually have need to rehash once in a while, though it's unlikely to surprise me since I'm the admin... :) >Bela<
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
On 30/11/2021 19:15, Chime Hart wrote: Hi Karen: If you want to try a rehash, you would need to type tcsh then type rehash. Then to get back to your familliar shell, type exit That doesn't make sense. The hash table is internal to tcsh, and will get built when it is launched anyway. So just running it will have done all the work, and the result will not be available to your normal shell.
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Hi chime, While the command worked just fine, it did not impact things for me. Thanks for the idea though. On Tue, 30 Nov 2021, Chime Hart wrote: Hi Karen: If you want to try a rehash, you would need to type tcsh then type rehash. Then to get back to your familliar shell, type exit Hope those will help Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Hi Karen: If you want to try a rehash, you would need to type tcsh then type rehash. Then to get back to your familliar shell, type exit Hope those will help Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
I will take your word for it. At the moment though our situations do not match, save for Lynx being missing from what my email programs use. That is a critical problem for me. what was the rehash command you typed to restore lynx for you. I want to try that in my site workspace to see if it restores lynx for my email inbox. Kare On Tue, 30 Nov 2021, Chime Hart wrote: Hi Karen: Aliases in Linux are no more a risk than writing or running a batch file in DOS, just a short cut to save an amount of typing. Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Hi Karen: Aliases in Linux are no more a risk than writing or running a batch file in DOS, just a short cut to save an amount of typing. Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
No Pannix cannot At least not as of my last try with them. My situation is also rather unique for physical reasons. That price for pannix is more than I pay here too, and I have my site hosted here as well. Pannix was reprehensible when I tried to work with them. On Tue, 30 Nov 2021, Jude DaShiell wrote: Someone don't understand files ownership and files permissions. If a copy of lynx.cfg is put in a user directory the user needs to take ownership of that file. If ownership cannot be taken it's probably a copy of a shared file and since the user in this case has no root privileges they cannot take ownership of the file. In that case, best to download a copy of the entire lynx source and extract the lynx.cfg file from that into the user directory in which case then the user owns that copy and can edit it and use it without effecting the rest of the system. Dreamhost was and maybe still is the internet provider for shellworld.net and they are remote and antisocial as I remember them (best left alone). Panix can get you a telnet account for $100.00 a year and that's where I landed once my shellworld.net account got black listed by some Hungarian who posted his exploit on the web which I later found. He figured me to be an undesireable. On Tue, 30 Nov 2021, Travis Siegel wrote: I'm sorry, but you're not making any sense. First off, My advice was to create a lynx.cfg file in your home directory. That has absolutely nothing to do with system level configuration files. Secondly, if a system user can change system wide configuration files, it's because your system administrators aren't doing their job properly. Those configuration files should not be writable by anyone on the system that is a regular user. Giving advice to create and modify configuration files that live in your home directory is a perfectly reasonable approach, and sometimes, the only way to accomplish something. If your system is hosed from someone messing with system level configuration files, that's not the fault of anybody changing configuration files that live in their own home directory. Whatever happened on dreamhost or shellworld is in no way related to anyone making changes to their own configuration files. Go yell at someone else. On 11/30/2021 5:21 AM, Karen Lewellen wrote: Travis, Please do not ever advise anyone to tamper with a file associated with a shared service like the one we have here. I am expressing this because right now I am experiencing what happens when someone, not myself, does this kind of tampering and not knowing what they are doing, creates problems for everyone. First our lynx startfile disappeared entirely..for two days. then when it returned, it came to a start page that does not work fully with lynx, all the items provided lead to YouTube, which as others have noted no longer really works with lynx at all. Its 5 a. m. I have been up all night waiting until I can call our admin because either we have a security risk, or the same person tampering with lynx has also changed the browser associated with email accounts, meaning I am not going to get any work done today either. Do not ever even hint that I am unwilling to help myself. tampering with config files that are provided by shared hosting services like this ought to be a crime. dreamhost does not even understand how lynx works at all, I provided them with a trace file showing how I cannot reach our work control panel, and even though they duplicated the problem they could, or would not fix the issue. Its one reason why I happily pay so much for shellworld, I can get my work done, at least when no one is damaging the services here. Karen On Sun, 14 Nov 2021, Travis Siegel wrote: You can easily create your own lynx.cfg file, put it in your home directory, then start lynx with a -cfg= command line parameter, and poof, you have full control over your lynx configuration, no need to depend on the system wide one at all. On 11/14/2021 2:29 PM, Karen Lewellen wrote: Russell, Because my access to lynx is tied to a service, I do not edit their lynx.cfg files. In fact, I do not even know where they are kept. Karen On Sun, 14 Nov 2021, russellb...@gmail.com wrote: Quoth Karen Lewellen: 'the shellworld setup for lynx, there is an associated editor. One that allows me, at least if the command "use control x e for editor" is spoken by lynx when I am on a field. If it is a single line, I cannot employ my editor. Meaning I cannot use control r and bring a file into the edit line. I would have to type it manually.' You can edit $HOME/.lynxrc directly useragent=Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.2) > Gecko/20100115 Firefox/3.6 l_y_n_x is mine. russell bell
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
and this is why accounts must make a difference. As of 1:24 eastern, Lynx works for me, although be it with the wrong start page. It is gone from mail accounts, which is disturbing all on its own. Wonder if the Alias thing is a security risk? On Tue, 30 Nov 2021, Chime Hart wrote: Hi Travis: Whats really interesting is that last I looked, L Y N X seems to be gone from Shellworld, whether I use an alias or even type which lynx says "command not found" I am fortunate that mostly I just use Shellworld for rss feeds, a majority of mail I deal with locally. Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Someone don't understand files ownership and files permissions. If a copy of lynx.cfg is put in a user directory the user needs to take ownership of that file. If ownership cannot be taken it's probably a copy of a shared file and since the user in this case has no root privileges they cannot take ownership of the file. In that case, best to download a copy of the entire lynx source and extract the lynx.cfg file from that into the user directory in which case then the user owns that copy and can edit it and use it without effecting the rest of the system. Dreamhost was and maybe still is the internet provider for shellworld.net and they are remote and antisocial as I remember them (best left alone). Panix can get you a telnet account for $100.00 a year and that's where I landed once my shellworld.net account got black listed by some Hungarian who posted his exploit on the web which I later found. He figured me to be an undesireable. On Tue, 30 Nov 2021, Travis Siegel wrote: > I'm sorry, but you're not making any sense. > > First off, My advice was to create a lynx.cfg file in your home directory. > That has absolutely nothing to do with system level configuration files. > > Secondly, if a system user can change system wide configuration files, it's > because your system administrators aren't doing their job properly. Those > configuration files should not be writable by anyone on the system that is a > regular user. > > Giving advice to create and modify configuration files that live in your home > directory is a perfectly reasonable approach, and sometimes, the only way to > accomplish something. If your system is hosed from someone messing with > system level configuration files, that's not the fault of anybody changing > configuration files that live in their own home directory. > > Whatever happened on dreamhost or shellworld is in no way related to anyone > making changes to their own configuration files. > > Go yell at someone else. > > On 11/30/2021 5:21 AM, Karen Lewellen wrote: > > Travis, > > Please do not ever advise anyone to tamper with a file associated with a > > shared service like the one we have here. > > I am expressing this because right now I am experiencing what happens when > > someone, not myself, does this kind of tampering and not knowing what they > > are doing, creates problems for everyone. > > First our lynx startfile disappeared entirely..for two days. > > then when it returned, it came to a start page that does not work fully with > > lynx, all the items provided lead to YouTube, which as others have noted no > > longer really works with lynx at all. > > Its 5 a. m. I have been up all night waiting until I can call our admin > > because either we have a security risk, or the same person tampering with > > lynx has also changed the browser associated with email accounts, meaning I > > am not going to get any work done today either. > > Do not ever even hint that I am unwilling to help myself. tampering with > > config files that are provided by shared hosting services like this ought > > to be a crime. > > dreamhost does not even understand how lynx works at all, I provided them > > with a trace file showing how I cannot reach our work control panel, and > > even though they duplicated the problem they could, or would not fix the > > issue. > > Its one reason why I happily pay so much for shellworld, I can get my work > > done, at least when no one is damaging the services here. > > Karen > > > > > > > > > > On Sun, 14 Nov 2021, Travis Siegel wrote: > > > >> You can easily create your own lynx.cfg file, put it in your home > >> directory, then start lynx with a -cfg= command line parameter, > >> and poof, you have full control over your lynx configuration, no need to > >> depend on the system wide one at all. > >> > >> > >> On 11/14/2021 2:29 PM, Karen Lewellen wrote: > >>> Russell, > >>> Because my access to lynx is tied to a service, I do not edit their > >>> lynx.cfg files. > >>> In fact, I do not even know where they are kept. > >>> Karen > >>> > >>> > >>> > >>> On Sun, 14 Nov 2021, russellb...@gmail.com wrote: > >>> > >>> > > Quoth Karen Lewellen: 'the shellworld setup for lynx, there is > >>> > an associated editor. One that allows me, at least if the command > >>> > "use control x e for editor" is spoken by lynx when I am on a field. > >>> > If it is a single line, I cannot employ my editor. Meaning I cannot > >>> > use control r and bring a file into the edit line. I would have to > >>> > type it manually.' > >>> > You can edit $HOME/.lynxrc directly > >>> > > useragent=Mozilla/5.0 (Windows; U; Windows NT 5.1; > >>> rv:1.9.2) > Gecko/20100115 Firefox/3.6 l_y_n_x > >>> > > is mine. > >>> > > russell bell > >>> > > > > >> > >> > >
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
It may be under a different name, maybe try locate *lynx* if the locate database is up-to-date or if locate is even installed. On Tue, 30 Nov 2021, Chime Hart wrote: > Hi Travis: Whats really interesting is that last I looked, L Y N X seems to be > gone from Shellworld, whether I use an alias or even type > which lynx > says "command not found" > I am fortunate that mostly I just use Shellworld for rss feeds, a majority of > mail I deal with locally. > Chime > > >
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Hi Travis: I am in TCSH, so I thought to type rehash now Lynx is back again. Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Hell, I don't know what shellworld charges (any attempts to go to the site just redirects me to Karen's site), but if you want a shell account where things just work, I'd be happy to sell you one for $5 a month on one of my servers. On 11/30/2021 11:42 AM, Chime Hart wrote: Hi Travis: Whats really interesting is that last I looked, L Y N X seems to be gone from Shellworld, whether I use an alias or even type which lynx says "command not found" I am fortunate that mostly I just use Shellworld for rss feeds, a majority of mail I deal with locally. Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
Hi Travis: Whats really interesting is that last I looked, L Y N X seems to be gone from Shellworld, whether I use an alias or even type which lynx says "command not found" I am fortunate that mostly I just use Shellworld for rss feeds, a majority of mail I deal with locally. Chime
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
I'm sorry, but you're not making any sense. First off, My advice was to create a lynx.cfg file in your home directory. That has absolutely nothing to do with system level configuration files. Secondly, if a system user can change system wide configuration files, it's because your system administrators aren't doing their job properly. Those configuration files should not be writable by anyone on the system that is a regular user. Giving advice to create and modify configuration files that live in your home directory is a perfectly reasonable approach, and sometimes, the only way to accomplish something. If your system is hosed from someone messing with system level configuration files, that's not the fault of anybody changing configuration files that live in their own home directory. Whatever happened on dreamhost or shellworld is in no way related to anyone making changes to their own configuration files. Go yell at someone else. On 11/30/2021 5:21 AM, Karen Lewellen wrote: Travis, Please do not ever advise anyone to tamper with a file associated with a shared service like the one we have here. I am expressing this because right now I am experiencing what happens when someone, not myself, does this kind of tampering and not knowing what they are doing, creates problems for everyone. First our lynx startfile disappeared entirely..for two days. then when it returned, it came to a start page that does not work fully with lynx, all the items provided lead to YouTube, which as others have noted no longer really works with lynx at all. Its 5 a. m. I have been up all night waiting until I can call our admin because either we have a security risk, or the same person tampering with lynx has also changed the browser associated with email accounts, meaning I am not going to get any work done today either. Do not ever even hint that I am unwilling to help myself. tampering with config files that are provided by shared hosting services like this ought to be a crime. dreamhost does not even understand how lynx works at all, I provided them with a trace file showing how I cannot reach our work control panel, and even though they duplicated the problem they could, or would not fix the issue. Its one reason why I happily pay so much for shellworld, I can get my work done, at least when no one is damaging the services here. Karen On Sun, 14 Nov 2021, Travis Siegel wrote: You can easily create your own lynx.cfg file, put it in your home directory, then start lynx with a -cfg= command line parameter, and poof, you have full control over your lynx configuration, no need to depend on the system wide one at all. On 11/14/2021 2:29 PM, Karen Lewellen wrote: Russell, Because my access to lynx is tied to a service, I do not edit their lynx.cfg files. In fact, I do not even know where they are kept. Karen On Sun, 14 Nov 2021, russellb...@gmail.com wrote: > > Quoth Karen Lewellen: 'the shellworld setup for lynx, there is > an associated editor. One that allows me, at least if the command > "use control x e for editor" is spoken by lynx when I am on a field. > If it is a single line, I cannot employ my editor. Meaning I cannot > use control r and bring a file into the edit line. I would have to > type it manually.' > You can edit $HOME/.lynxrc directly > > useragent=Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.2) > Gecko/20100115 Firefox/3.6 l_y_n_x > > is mine. > > russell bell > > >
Re: [Lynx-dev] the frustration of this kind of advice, was about user agent headers
On 30/11/2021 10:21, Karen Lewellen wrote: either we have a security risk The system has a serious security problem if it allows a shared file to be modified by ordinary users.
[Lynx-dev] the frustration of this kind of advice, was about user agent headers
Travis, Please do not ever advise anyone to tamper with a file associated with a shared service like the one we have here. I am expressing this because right now I am experiencing what happens when someone, not myself, does this kind of tampering and not knowing what they are doing, creates problems for everyone. First our lynx startfile disappeared entirely..for two days. then when it returned, it came to a start page that does not work fully with lynx, all the items provided lead to YouTube, which as others have noted no longer really works with lynx at all. Its 5 a. m. I have been up all night waiting until I can call our admin because either we have a security risk, or the same person tampering with lynx has also changed the browser associated with email accounts, meaning I am not going to get any work done today either. Do not ever even hint that I am unwilling to help myself. tampering with config files that are provided by shared hosting services like this ought to be a crime. dreamhost does not even understand how lynx works at all, I provided them with a trace file showing how I cannot reach our work control panel, and even though they duplicated the problem they could, or would not fix the issue. Its one reason why I happily pay so much for shellworld, I can get my work done, at least when no one is damaging the services here. Karen On Sun, 14 Nov 2021, Travis Siegel wrote: You can easily create your own lynx.cfg file, put it in your home directory, then start lynx with a -cfg= command line parameter, and poof, you have full control over your lynx configuration, no need to depend on the system wide one at all. On 11/14/2021 2:29 PM, Karen Lewellen wrote: Russell, Because my access to lynx is tied to a service, I do not edit their lynx.cfg files. In fact, I do not even know where they are kept. Karen On Sun, 14 Nov 2021, russellb...@gmail.com wrote: > > Quoth Karen Lewellen: 'the shellworld setup for lynx, there is > an associated editor. One that allows me, at least if the command > "use control x e for editor" is spoken by lynx when I am on a field. > If it is a single line, I cannot employ my editor. Meaning I cannot > use control r and bring a file into the edit line. I would have to > type it manually.' > You can edit $HOME/.lynxrc directly > > useragent=Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.2) > Gecko/20100115 Firefox/3.6 l_y_n_x > > is mine. > > russell bell > > >
