| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69635
|
Sat Jan 28 14:26:07 2023 |
 | David Pilgram | David.Pilgram@epost.org.uk | Request | All | - | Re: Wikipedia Article deleted | I am rather with John on this.
I deliberately stopped contributing to Wikipedia years ago after I added an observation to an entry. That is, a piece of what could be called original research. It was shot down in flames for being precisely that: original research. From what I read in the Draft:Elog and the Talk section, I think that the same issue in some guise or other will come up. All of us use and love Elog - I think I use it for all of the listed purposes - but apart from being in the Debian distro (which I did not know about) there is very little published primary sources. Mind you, the quality of publications as primary sources can be questioned, I can bore on with several examples.
Has anyone ever published a paper citing their filing cabinet organisation? Elog's obviously different, but has the same problem when it comes to citations. It is a utility, a very useful one, but the sort of utility that might just make an aside in a paper these days. If we were in the 1980s and (hypothetically) Elog was available and as functional, that would probably make it the subject in computer research papers and magazines.
David.
| John Kelly wrote: |
|
Wikipedia has been an unreliable source for a very long time, just for the reasons that we are seeing here now with psi and Elog. Those that 'run' Wikipedia are political and authoratative. I have not only had these negative experiences with 'them' but know of many others that have as well. I see no reason why an organization as ours with such great ideas, programs and people need to be on their site. I think it would 'say more' if we left this as is and let others see how unreliable Wikipedia really is.
John
| Andreas Luedeke wrote: |
|
It appears to me that this is a really stupid problem: the article provides many links to sources, but they are just links, not "references". That does not count, since links could be something else than references.
I'll try to edit it and transform the list of external links into references to verify the text. Lets hope that this will suffice.
Okay: found three articles about applications of ELOG and put them under references. I took the liberty to submit the draft: it shows that they expect some month delay for a review. I have no idea if that was what they want, but it is worth a try.
| Edmund Blomley wrote: |
|
If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else
| Stefan Ritt wrote: |
|
I added some more references, that's about all I can do. Not sure if that is enough.
Stefan
| Edmund Blomley wrote: |
|
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
| Sebastian Schenk wrote: |
|
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
| Andreas Luedeke wrote: |
|
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
| Stefan Ritt wrote: |
|
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
| Sebastian Schenk wrote: |
|
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
|
|
|
|
|
|
|
69757
|
Sat Mar 9 17:17:02 2024 |
 | Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Suggestion to update Mac OS X instructions in ELOG Administrator's Guide | The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.
After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.
|
|
69758
|
Sun Mar 10 04:25:43 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide | Here's a more complete/correct set of the updated commands:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Cheers,
Andreas
| Andreas Warburton wrote: |
|
The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.
After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.
|
|
|
69784
|
Mon Apr 15 18:05:27 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide | Thanks for the info, I updated the adminguide.
Stefan
| Andreas Warburton wrote: |
|
Here's a more complete/correct set of the updated commands:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Cheers,
Andreas
| Andreas Warburton wrote: |
|
The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.
After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.
|
|
|
|
69785
|
Tue Apr 16 13:20:01 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide | Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:
In one case, "launchctl" is misspelled.
Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" (no space), whereas the two lines containing the 'bootstrap' and 'bootout' commands use the phrase "system /Library/LaunchDaemons/ch.psi.elogd.plist" (note space after 'system').
Many thanks, Andreas W.
|
Stefan Ritt wrote:
|
|
Thanks for the info, I updated the adminguide.
Stefan
| Andreas Warburton wrote: |
|
Here's a more complete/correct set of the updated commands:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Cheers,
Andreas
| Andreas Warburton wrote: |
|
The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.
After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.
|
|
|
|
|
69786
|
Tue Apr 16 13:31:02 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide | Thanks, fixed.
Stefan
| Andreas Warburton wrote: |
|
Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:
In one case, "launchctl" is misspelled.
Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" (no space), whereas the two lines containing the 'bootstrap' and 'bootout' commands use the phrase "system /Library/LaunchDaemons/ch.psi.elogd.plist" (note space after 'system').
Many thanks, Andreas W.
|
|
|