Linux version of Logos Bible Software
Comments
-
Mr. Smiling,
There is need for clarity... I like the part of your ideas that are on-topic...
Much of what you said related to the OS choice in the first place, not whether to "ALLOW" the development of an app for people who have already made the choice for Linux.
Generally, the "Linux" question is a "let" question. "Logos for Linux" means: "Non-Faithlife people build it ON THEIR OWN INITIATIVE or it doesn't happen."
(That is Linux culture. I didn't know that until I started using Linux in 2013.)
This thread was not about whether WE should use Linux in the first place, but whether Faithlife wants to LET US to use Logos on our Linux systems.
The purpose of discussing stats and market share, here, is to observe changes and trends, informing solvency and marketability, not about which OS is "better" for us customers to choose in the first place. Those stats say Linux is growing, which means it's not sinking and has a future. So, "has a future" isn't a bad decision.
I see stats as saying this:
Stats --> Linux growing --> future --> Logos can do Linux and have a growing future
...That is why I discuss them.
...About previous attempt(s) of Logos for Linux...
Perhaps the community development for the Logos 4 engine port to Linux failed because Logos/Faithlife/Libronix/whoeverownsitthisweek tried to do too much. JUST MAKE A GITHUB WITH THE SDK AND FORGET ABOUT IT.
...I haven't seen you respond to "LETTING" or "ALLOWING" the community. You don't have to do everything yourself. That's kind of the idea. If the community never does anything, that's our problem.
...Are the Logos 4 engine binaries published to a GitHub profile? You haven't provided any GitHub URLs. if not, that is probably another reason why it got little community support. Linux users like to develop on GitHub for many reasons you can find with Google, which I won't waste space sharing here. Even Linus Torvalds uses GitHub for developing. No github.com/?????/logos = no Logos on Linux.
And, I am still interested in those stats on the percentage of users using Logos. Of 95%-ish desktop users using Windows in these OS stats, how many of those people use Logos at all? What all OSs do they use? How many Logos customers are developers? How many Logos customers have Debian installed alongside Windows?
And, I didn't think we were talking about video game development. Though, now that you mention those stats, it does seem that the Logos road map aims at high graphics rather than content connecting compatibility. So, maybe game dev stats are relevant. Logos wants something that uses GPU. Linxu users want something else...
Ultimately, "Logos for Linux" means 1. that we can login and access our libraries ALL THROUGH the command line if we want and 2. a GitHub repo of an open source version of the engine that protects proprietary content. We don't want "pretty", we want "command line for Linux". (...not command line or open source on Mac, not on Windows, this thread is about Linux.)
About website support...
You actually brought up Logos integrating with web. I just mentioned that we Linux people are in the know and support a lot you rely on. We are smart people with the power to refer and recommend software. We WANT to recommend Logos more. Using another website engine (from a company that still hasn't ported to Linux) isn't our question. Get a Logos GitHub for Linux that WE can get working, let the community do it, then we might be interested in your Faithlife web products.
About Faithlife web service, as I understand from the stats, most web servers run Linux. If Faithlife wants in on the web-dev world, a Logos for Linux client is all they would need and they would have their foot in the door. That's another reason to get on Linux: web dominance.
As for why a Linux developer might like Logos on his LAMP websites...
...The main functionality would be how/why we like Linux: Backend connectivity.
...Not fancy graphics. Not pretty Flash that doesn't always work.
Like with other software, we install the Logos client on the server, then the backend can talk to our own web interface via the LINUX command line (or XML or a LAMP database if it is on another OS)... Then we can do "stuff"... whatever we imagine for the week.
As for EULA, you know that Logos has some library contents that are public domain. The unspoken agreement in the Linux world is that we would use the public domain part publicly. (I certainly hope that Logos would not prevent us from sharing public domain content in their libraries on their free engine. if they do then I recommend changing that in the next EULA update, which closes that question.)
...As for EULA-applicable proprietary content on websites (again, of course), we awesome Linux developers who make so many websites for so many people would LOVE to have a Logos client working on Linux, which would automatically mean that the client running on the server could use the command interface to talk to a web user's Logos client to share proprietary content through our own web inventions. Then, we can get more of our customers using Logos on ANY OS.
Eg: I do a Bible study, post it on my WordPress blog that has a plugin talking to the Logos for Linux client running on the same LAMP web server, a web visitor can see SOME allowed content (as EULA might allow for printing, etc.) Then, the visitor can see a little, OR, he can sync and share notes with his local Logos client. I tell my website customers that I can do this, they get more of their people using Logos.
...MAYBE, probably not though, that creates an unspoken problem. JUST MAYBE Logos dev doesn't want my Bible study notes going through anything but THEIR server. Maybe Faithlife wants ALL MY BIBLE STUDY NOTES on their cloud server. I don't think Faithlife would want such privacy invasion, but that is the underlying Linux question.
Faithlife can have awesome cloud services. But, the reason people use Linux in the first place, partially, is about content control. What if I don't want my Bible study notes in your cloud? What if Faithlife gets purchased by CNN or a Chinese company looking to spy on Christians... or hires a mole... or... Many books have already been written on basic security questions. So, I won't rehash those discussions here. Reagan called it "trust but verify".
I like Faithlife's cloud idea, though it is definitely a premium service, arguably luxury. But, I don't need it for everything all the time always. Some things I just want on my local client. And, I'm glad to buy more and more and more proprietary books for Logos... IF I CAN USE IT WHERE I WORK, which I and many more than I have already decided is Linux... which is a decision that this thread is not about.
Stepping back to look at where your answers have gone, I am starting to wonder if the Logos on Linux question is about fundamental worldviews. Linux users like to use open, non-centralized sharing. Sure, we have proprietary stuff in secure areas where we all make money. And, NO ONE CONTROLS ALL OF ANYTHING, which allows cooperation and progress. It's not even about privacy so much as it is about giving each other permission to share the work load and therefore share the credit and the control.
...It seems that Logos/Faithlife/Libronix/whateverwecallitthisweek likes to do a lot of the planning themselves. That isn't an OS compatibility discussion, but a worldview compatibility discussion. I certainly hope Logos can get SOME of their awesome proprietary and open libraries into the growing Linux world.
As for the product dev roadmap question, "Is Logos for Linux part of strategy?" Libronix promised long ago that "the engine would always be free". That really means that it needs to be "allowed" on Linux—not "guaranteed", just "allowed" if other people want to do the port. That means, really, that Faithlife should just upload most/all of the Logos 4 binaries to a GitHub, then forget about it and go on to other projects.
The Linux question is not about code or more things on the Logos developer to-do list. It's about "ALLOWING". Please mention this in your next reply, Mr. Smiling.
Logos for Linux is what this thread is about. That question is more about allowing SOME of the Logos products (the free stuff) to live on GitHub as Open Source. "Openness" is what the REAL "Linux" question comes down to, for anyone who "really understands" Linux.
...Again, because you seem to have missed this, Linux is about "allowing" other people to do the leg work where suggestions and problems they find are concerned. It's not about flashy-web-shinyness and cool, high-GPU load experiences. We want the binaries and permission to fork them.
So... Maybe this thread really should be about letting basic back-end stuff be open to Linux developers on GitHub, dump the Logos 4 engine and a proprietary library SDK on to GitHub for us to fork and pull, no extra work for Faithlife/Libronix/whatever....
...Then, the Windows and OSX and web-cloud distros are more about fancy user experience.
See... All those people going to your fancy cloud website and buying Logos 7 beautifulness... Many of them attend a small local church with a website on a LAMP server developed by a Linux geek like us. He won't change his mind about Linux and he's not asking, but he would love to get Logos there too. He just needs Logos 4 on GitHub with an Apache or GNU license.
I am interested in your knowledge and ideas, Mr. Smiling. But, please keep "WHETHER to use Linux on desktop or web" related info on a different thread. This is a thread about whether LOGOS (not we Logos customers and/or web developers) should become part of Linux in the open source/freemium/proprietary/growing platform with the people who already made that choice.
Now, I, personally, would like a clear and official answer from Faithlife staff, approved by the correct responsible management: Would Logos/Libronix/Faithlife allow 1. an SDK for remote command-line login to proprietary content on Logos servers and 2. for the free Logos 4 engine itself to become completely open source and "ALLOWED" for other developers to make it work on Linux if those third party developers do all the legwork?
Mr. Smiling: That is not you, at least I hope Faithlife staff won't call themselves "Keep Smiling" on the forum and work weekends. Though, I would also like to know if you think yes/no Faithlife should offer 1 and/or 2 (above) to we who use an OS that you don't seem to prefer.
0 -
...And, Mr. Smiling,
I have been really thinking about all you have to say. After my morning Bible study, I am thinking...
Maybe YOU are the answer!
You know SO MUCH about all this.
Can you answer my questions and point me in a direction? Can you tell me how to use a command line (even windows) to log on to the Logos server and retrieve my library through the command line?
If I can learn some basic command line stuff, I might be able to get at least a command-line version of Logos working and that should make the "Go Linux" people happy since, frankly, that's what we really want in the first place.
Maybe YOU are the person to help me to help all the rest of us!
Keep smiling!
0 -
Jesse Steele said:
Get a Logos GitHub for Linux that WE can get working, let the community do it, then we might be interested in your Faithlife web products.
Faithlife has 34 GitHub repositories => https://github.com/Faithlife that includes RefTagger, which is already being used by many web sites for pop-up of Bible verse text. Forum RefTagger has threads dating back to Oct 2009 (near the time of conversion from newsgroup to forum discussions).
Jesse Steele said:I see stats as saying this:
Stats --> Linux growing --> future --> Logos can do Linux and have a growing future
Faithlife corporation concurs with online future being profitable so they began actively developing Logos Web App in 2015 that can be used on open source distributions along with Windows, OS X (mac OS), iOS, and Android, which can include tablet devices and ChromeBooks.
Logos UserVoice suggestion now has 382 votes (# 9) => https://logos.uservoice.com/forums/42823-logos-bible-software-6/suggestions/3635847-make-logos-4-and-5-avalible-to-individuals-on-ubun
Jesse Steele said:...As for EULA-applicable proprietary content on websites (again, of course), we awesome Linux developers who make so many websites for so many people would LOVE to have a Logos client working on Linux, which would automatically mean that the client running on the server could use the command interface to talk to a web user's Logos client to share proprietary content through our own web inventions. Then, we can get more of our customers using Logos on ANY OS.
Recommend reading => Fire Someone Today by Bob Prichett, Faithlife CEO
Sharing proprietary content from one Logos library to many web site users has potential contract ramifications with various publishers, which could include royalty payments. Hence, anticipate Faithlife corporation having desires for their own web sites to be used for EULA compliance.
Faithlife has Software Developer job available for an awesome developer => https://faithlife.com/jobs/SoftwareDeveloper
Jesse Steele said:...MAYBE, probably not though, that creates an unspoken problem. JUST MAYBE Logos dev doesn't want my Bible study notes going through anything but THEIR server. Maybe Faithlife wants ALL MY BIBLE STUDY NOTES on their cloud server. I don't think Faithlife would want such privacy invasion, but that is the underlying Linux question.
Faithlife already enables your Notes to be freely shared with other Faithlife users => https://documents.logos.com plus sync between your devices running an app (mobile) or application (desktop/laptop). Also can use the Faithlife documents web site to view your Notes.
Thankful that Visual Filters can be shared => Examples of visual filters (highlighted text is a challenge for command line, perhaps JSON)
Jesse Steele said:And, I am still interested in those stats on the percentage of users using Logos. Of 95%-ish desktop users using Windows in these OS stats, how many of those people use Logos at all? What all OSs do they use? How many Logos customers are developers? How many Logos customers have Debian installed alongside Windows?
Support page => https://www.logos.com/support shows "five platform or devices" with four groups of operating systems:
- Windows
- OS X (mac OS)
- iOS
- Android
The fifth device, Kindle Fire, uses a custom Android variant.
Apologies since this volunteer with many posts (MVP) does not know the operating share usage of Faithlife users.
Jesse Steele said:Mr. Smiling: That is not you, at least I hope Faithlife staff won't call themselves "Keep Smiling" on the forum and work weekends. Though, I would also like to know if you think yes/no Faithlife should offer 1 and/or 2 (above) to we who use an OS that you don't seem to prefer.
Depends on task to be done for my operating system preference; like to use what works well plus readily switch OS to get task done.
Personal user opinions:
- No for remote command line login SDK; recommend using one of the Faithlife web servers to access your library content
- No for open sourcing of Faithlife engine for custom user interface creation
Another suggestion thread => Linux - Ubuntu may be interesting to read.
Jesse Steele said:Maybe YOU are the answer!
Am praying and seeking God's calling; not yet know where God wants me working to join Him for His glory.
Keep Smiling
is my reminder of Philippians 4:4 where Paul was Rejoicing in the Lord always (while in very unpleasant circumstances).Thankful for many friendly forum discussions; have learned a lot plus have a lot to learn.
Keep Smiling [:)]
0 -
If Logos doesn't make this happen, I am willing to help with development of a new Bible study program for Linux.
I can't code, but I can help with graphics somewhat, or wherever I can fit in.
The programs available right now for Linux are noble efforts...but very clunky and ugly. There really needs to be more options.
It's time to set churches and ministries free from abusive, proprietary software. I have no problems paying for good software and tech service, but many churches are getting slapped with unjust DRM lawsuits. The less churches have to rely on Mac, Microsoft, and Adobe, etc. the better. Logos could be the good guy here and help out the Open Source community. It would be good for churches in the long run (in my opinion), and Logos could still make money.
This is just the right thing to do, and Linux really ought to be the future for churches and ministries.
I'll come back and rant in another couple years.
0 -
Joe, I'm jessesteele.com. Hit me up ASAP.
0 -
Mr. Phil 4:4, :-)
Thank you for answering my questions 1 and 2.
I feel we have a lot clarified now. Though, I still don't see what % of Americans are running Logos.
I see from the vote you linked to that Faithlife's president is supposedly a former Microsoft guy, which explains a lot... Including that previous software was probably built on MS stuff, making him a fit to begin with.
PLEASE ANSWER ME THIS: I do NOT want any EULA violations. I don't imply it. If you think that, we misunderstand.
...I was suggesting "whatever" would stay withing EULA.
Please respond that you got that part. I care that you know. :-)
Of awesome programmers, I don't think Linux is the Faithlife president former Microsoft guy's pick.
0 -
Jesse Steele said:
I feel we have a lot clarified now. Though, I still don't see what % of Americans are running Logos.
Friendly discussion helped me appreciate Faithlife's direction. Do recommend Logos Now membership that includes Logos Web App access, which is already noticeably better for Logos library interaction in an open source browser than Biblia.
+1 Curious about Faithlife application and app usage. Thankful for free software, albeit wallet cries [:'(] for many resource purchases. More resources does enable search to find useful articles on a variety of topics.
Jesse Steele said:...I was suggesting "whatever" would stay withing EULA.
Without an account, Faithlife offers 51 Bibles for free reading at https://biblia.com that also has an api.biblia.com web site.
For resources licensed to one Logos library to be used by one human being, an intermediate web site would need to either embed a Faithlife web site (e.g. frame) or pass along user credentials (with potential for security disaster). Simplier option is linking to appropriate Faithlife web site(s).
Public domain observation: text is free, but incredible tagging added by Faithlife for insightful Bible study is not.
Jesse Steele said:Of awesome programmers, I don't think Linux is the Faithlife president former Microsoft guy's pick
Prior to Microsoft acquiring Xamarin (with developers that maintain Mono), Faithlife was using Ceph from Red Hat in their Data Center => Data Center Storage Failure, 11/21 and => Data Center Storage Failure, 11/21 (Continued) includes more Linux insights: e.g. XFS kernel bug triggered by load. plus Inktank support discount in 2014
Jim Straatman said:I just want to take a moment and express how blessed I am to be working with such a talented team. Inktank has many enterprise customers, and according to them, we (and by we I mean Richard) are one of the most sophisticated outfits they’ve encountered. So much so, they are discounting our support contract by 15%, representing the value we’ll provide back into their product. Moreover, the Faithlife Operations team is one of the first in the world to deploy Joyent SmartDataCenter 7 under new open source licensing terms, all under duress and in a matter of hours.
Keep Smiling [:)]
0 -
Steven Yu said:
Once again, I am pushing foward for a Linux version of Logos, a lot of user are using Linux, and we have been struggling to break away from Windows, but Logos has always been the single software that require us to either dual boot or run a virtual machine with Linux OS.
Anyone share the same view?
I never ceased to be blown away by the number of views the Linux topic generates, even though I would not think there are that many Linux users, LOL. I mean, 279,000 ??? WOW! Crazy!
Myke Harbuck
Lead Pastor, www.ByronCity.Church
Adjunct Professor, Georgia Military College0 -
Myke Harbuck said:
even though I would not think there are that many Linux users, LOL. I mean, 279,000 ??? WOW! Crazy!
There must be more users than one has been told. The Linux system is excellent, fast, and getting much more popular. It can be a clear replacement for Windows. It is much better. There are only two reasons why I have not completely switched. One is the concern I have for protecting my children (parental filters) and the other is my investment in Logos Bible Software.
0 -
Myke Harbuck said:
even though I would not think there are that many Linux users, LOL. I mean, 279,000 ??? WOW! Crazy!
Concur crazy plus this thread in the Suggestions forum has the most replies, which is more than the next two suggestion threads combined:
Thankful for Faithlife development of Android mobile apps.
Mark said:There must be more users than one has been told. The Linux system is excellent, fast, and getting much more popular. It can be a clear replacement for Windows. It is much better. There are only two reasons why I have not completely switched. One is the concern I have for protecting my children (parental filters) and the other is my investment in Logos Bible Software.
Internet search for linux parental control finds many results, including Ubuntu community => https://help.ubuntu.com/community/ParentalControls
Apple makes significant contributions to many open source projects => https://www.apple.com/opensource/ OS X (mac OS) System preferences has Parental Controls plus Logos Bible Software.
Thankful for Distrowatch => http://distrowatch.com/ that includes current Top Ten distributions => http://distrowatch.com/dwres.php?resource=major while tracking hundreds. Top Ten list of major distributions has had several changes since this thread began in 2009.
Anticipate open source distributions and Android fragmentation => http://opensignal.com/reports/2015/08/android-fragmentation/ having similar development and support issues for a Logos Bible Software application. Albeit Android has one open source SDK's per version. Yet a number of open source projects have graphical applications running on a variety of open source distributions.
Visual depiction of Android fragmentation in 2014 shows huge variety of hardware and OS variant combinations being used:
image linked from Gizmodo article => http://gizmodo.com/what-android-fragmentation-looks-like-its-growing-1624662310
Firefox installation on Linux => https://support.mozilla.org/en-US/kb/install-firefox-linux?redirectlocale=en-US&redirectslug=Installing+Firefox+on+Linux includes:
Firefox said:Many Linux distributions include Firefox by default, and most have a package management system that lets you easily install Firefox.
Building and distributing package varieties would be similar to Android distribution. Caveat: open source distributions do not have the equivalent of Google Play and Amazon Store so would have to publish to more repositories OR choose a subset of open source distributions for development and support (e.g. Oracle database certification on a smallish number of enterprise server distributions).
James said:Has anyone tried using Logos in ReactOS? I know React is not quite stable yet but it might be an option going forward.
Downloading React has a "Did you know?"
ReactOS said:If just 1 in 10 people downloading ReactOS would donate less than the cost of a beer each month, we'd be able to hire 10 full time developers.
ReactOS has never had the funds to hire a full time dev, but imagine how much quicker we could reach beta if we did. Please, be that 1 in 10 and help us boost development.
In contrast to ReactOS, wikipedia article about Ubuntu => https://en.wikipedia.org/wiki/Ubuntu_%28operating_system%29 mentions initial funding of $ 10 million.
Keep Smiling [:)]
0 -
Realizing that this thread is in its 8th year now, I have little hope in seeing anything from Logos on this. While I was a paying customer before, I've given up on ever seeing something for the Linux users.
For those of you that are willing to help write a Logos for Linux as has been suggested here, I would point you over to http://xiphos.org/ and suggest you put your efforts in there. And put all the lobbying that is going on here into getting the publishers to release works for The Sword Project. That seems the main hurdle right now that is keeping people locked into other platforms. Publishers need to understand that Linux is for serious users that are willing to pay for their works and not just for those that want everything for free. That, along with the understanding that there are protections that can be put on their works. The lobbying needs to be refocused to pressure the publishers to allow their works to be released in this manner.
My 2¢
sjm
0 -
Working on Wine to get Logos Bible Software to run in Wine in Linux would probably be the shortest path. If someone got LBS to work on Wine and set it up in PlayOnLinux, it would automatically do the setup. But, to get it to work would probably take some Wine development.
0 -
Perry Webb said:
Working on Wine to get Logos Bible Software to run in Wine in Linux would probably be the shortest path.
Wine currently is not viable because the open source community does not have an alternative for Windows Presentation Foundation (WPF) so Logos 4, 5, 6, 7 would not be usable due to lack of WPF graphical layer.
Keep Smiling [:)]
0 -
Anyone use Virtualbox lately? It runs things at normal or faster than normal speeds for me. Of course, I use the official Nvidia drivers and such.
0 -
DansGuardian is a great idea, but it's a pain in the butt to get going because of a really old package or sources are needed. I can't remember, but for some of us, when it comes down to having things our way or being faithful to God and my wife, I would rather stay faithful.
0 -
Here's my son's response. He is an avid Linux user who is working on a Ph.D. in computer engineering.
Here is a list of what is provided by that library some of which would need to be implemented in wine for Logos to work: https://msdn.microsoft.com/en-us/library/ms753307(v=vs.110).aspx
0 -
Perry Webb said:
Here's my son's response. He is an avid Linux user who is working on a Ph.D. in computer engineering.
Here is a list of what is provided by that library some of which would need to be implemented in wine for Logos to work: https://msdn.microsoft.com/en-us/library/ms753307(v=vs.110).aspx
Mono is an open source port of .NET whose parent company, Xamarin, has been acquired by Microsoft.
Mono's WPF information => http://www.mono-project.com/docs/gui/wpf/
points out that porting WPF from Windows to open source is impractical.
Keep Smiling [:)]
0 -
Given the topic of this thread (whether to have Logos for Linux, not whether to have users using Linux)... I deduct this as your recommendation of Logos 3 for Wine.
And, frankly, I agree with you and Perry Web: Given all the evidence seen here, getting Logos 3 (or Libronix or whateveritscalled) in Wine's Play on Linux library would probably be the most efficient way to keep Logos solvent.
0 -
Logos UserVoice suggestion with 388 votes => https://logos.uservoice.com/forums/42823-logos-bible-software-6/suggestions/3635847-make-logos-4-and-5-avalible-to-individuals-on-ubun was declined by Faithlife on 6 Sep
Faithlife Development said:
We will not be developing a desktop/offline application for Linux.
https://app.logos.com continues to improve and will be our solution for any platform that supports a web browser.
Hence, offline use on an open source distribution currently needs a Virtual Machine running a legal copy of Windows (for virtual use) or OS X (running on Apple hardware) to run desktop application. When Apple refreshes Mac hardware, anticipating prices for older refurbished models to drop a bit.
Jesse Steele said:Given all the evidence seen here, getting Logos 3 (or Libronix or whateveritscalled) in Wine's Play on Linux library ...
Wine HQ has Libronix 3 rating => https://appdb.winehq.org/objectManager.php?sClass=version&iId=8802 that was last updated in Aug 2013 (garbage).
Codeweavers forum => https://www.codeweavers.com/compatibility/crossover/forum/logos-bible-software-x?msg=36063 has similar Libronix 3 discussion in 2009
Libronix 3 resource compatibility => https://www.logos.com/support/mac/L3/resource_compatibility notes any resource created after 31 Mar 2012 cannot be used in Libronix 3 due to resource file format change.
One idea is improving Darling HQ => https://www.darlinghq.org/source-code/ to enable graphical OS X (mac OS) 64 bit application to run on other open source distributions with a GPL kernel. Technically may be easier to fork Darling for a BSD kernel that has similar system call values as Darwin in OS X (mac OS), which would allow community focus on creating a Cocoa clone using Qt, which could be integrated into Darling after BSD System Call reverse engineering is done. Caveat:open source community does not have many OS X (mac OS) applications that are not already available so motivation is lacking to cleanly clone Apple's graphical user interface.
Darling HQ mentions Rudix: unix packages for OS X (mac OS) => http://rudix.org/
Found a 2007 discussion about cloning Apple's Cocoa and Carbon => https://apple.slashdot.org/story/07/07/30/0230204/Run-Mac-OS-X-Apps-On-Linux and also found Mac-on-Linux with latest news in 2007 => http://mac-on-linux.sourceforge.net/news.php
For OS X (mac OS), Platypus looks useful for Python and PERL scripts => https://github.com/sveinbjornt/Platypus
Apple's EULA for Mac OS X is similar to Faithlife => https://store.apple.com/Catalog/US/Images/MacOSX.htm
Mac OS X EULA said:This License allows you to install and use one copy of the Apple Software on a single Apple-labeled computer at a time.
By the way, nasty rootkit targets Linux on ARM and x86 => http://www.infoworld.com/article/3116908/malware/stealthy-tricky-to-remove-rootkit-targets-linux-systems-on-arm-and-x86.html
Keep Smiling [:)]
0 -
Keep Smiling,
Is there any reason why you mention a new Linux exploit and not new exploits for Mac and Windows? The Trend Micro release makes it clear that for this exploit to work an attacker already needs local access to the machine (i.e. the exploit cannot be triggered remotely, but only if the attacker has already broken into the machine and obtained user access). It doesn't matter what OS you run - if an attacker has already compromised your machine and gained local access, you're pretty much sunk.
0 -
aaylnx said:
Is there any reason why you mention a new Linux exploit and not new exploits for Mac and Windows?
Mentioned new nasty Linux exploit in a thread about Logos on Linux, which has many readers (thread views). New nasty exploits for Mac and Windows were not published concurrently.
Noticed security article while researching open source options; could have included Apple emergency update on 2 Sep 2016 => http://www.infoworld.com/article/3116064/macs/apple-quashes-3-zero-days-with-emergency-mac-update.html about 3 zero day exploits being quashed so recommend updating OS X (mac OS).
Likewise could have mentioned 30 Aug 2016 article about ransomware attack on Linux web servers => http://www.infoworld.com/article/3113816/security/new-ransomware-threat-deletes-files-from-linux-web-servers.html
Flip side is Windows 10 being harder to hack (15 Aug 2016) => http://www.infoworld.com/article/3107132/security/respect-windows-10-security-impresses-hackers.html Albeit Microsoft includes Key Logger in Windows 10 along with altering default dialog behavior for Windows 10 "Free" Update in July 2016 (clicking 'X' to close dialog box was treated as OK to upgrade).
Trend Micro blog => http://blog.trendmicro.com/trendlabs-security-intelligence/pokemon-themed-umbreon-linux-rootkit-hits-x86-arm-systems/ linked from InfoWorld Security article verified three hardware variants: x86, x86-64, and ARM can be exploited. Umbreon user mode (ring 3) execution can hide itself from strace detection on Linux (nasty and sophisticated). Irony is Umbreon author(s) could be helpful for improving Darling.HQ.
InfoWorld article also links to 1 Sep 2016 article => https://blog.sucuri.net/2016/09/iot-home-router-botnet-leveraged-in-large-ddos-attack.html about a distributed attack using Internet connected cameras and network routers running Linux.
As operating systems gain popularity, so do nasty exploits. Apple and Microsoft include anti-malware in their operating systems along with frequent updates. Open source distributions also have security updates for maintained versions. Keeping system(s) up to date is prudent.
aaylnx said:The Trend Micro release makes it clear that for this exploit to work an attacker already needs local access to the machine (i.e. the exploit cannot be triggered remotely, but only if the attacker has already broken into the machine and obtained user access).
Risk is using a client web browser on Linux since the Umbreon root kit could be incorporated into a malicious web site or ad download for local execution and exploit (same delivery technique is a risk on Mac and Windows too).. Another risk is an email client that allows something to be executed (similar to Outlook preview on Windows that has been exploited).
Keep Smiling [:)]
0 -
Risk is using a client web browser on Linux since the Umbreon root kit could be incorporated into a malicious web site or ad download for local execution and exploit (same delivery technique is a risk on Mac and Windows too).. Another risk is an email client that allows something to be executed (similar to Outlook preview on Windows that has been exploited).
True, but this is also a risk for every OS that is not kept up to date and where basic security practices are not followed. Nothing unique about Linux here.
0 -
Thread => Running Logos Android on a Chromebook
Chromium => http://www.chromium.org/chromium-os
Running Chromium on KVM => https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/running-chromeos-image-under-virtual-machines
Caveat: Android mobile app has less capabilities than desktop application.
Keep Smiling [:)]
0 -
I'm not trying to be nit picky here, but why would running Chromium OS under KVM be an advantage to anyone? Chromium is not Android. Chromium is the open source development version of Google's Chrome OS. By itself, Chromium OS can only access Logos through a browser which can be done natively on any OS. If one wants an Android desktop, then their best bet is Remix OS. However, I wouldn't go that way either, because Google has announced that soon people will be able to run Android apps natively on their Chromebooks. This means that soon Logos users will be able to run the Android client for Logos natively under ChromeOS.
I have installed Crouton on my Chromebook, which allows me to run Linux apps w/in ChromeOS. Interestingly, I have run Bibleworks directly on a Chromebook, because Bibleworks works flawlessly under WINE. When I want to access Logos on my Chromebook, I open up Crouton, run Remmina (a multi-protocol remote desktop client for Linux) and connect to my main Windows box using Windows Remote Desktop Protocol (RDP). It actually works quite well. Once Android apps start running on Chrome OS natively, you won't need Crouton, because there are Remote Desktop clients available for Android.
0 -
I have the Android app running on ChromeOS - it works pretty well. The layer in the middle consumes a fair bit of resource, but it works. The app itself has several limitations, but at least I can access my notes.
The web app has a lot of promise, and would put to bet the Linux question for me when it's full function. However, it's an ongoing expense. Since it's cross-platform, it solves a lot of problems and is a smarter investment for Faithlife. It already has a few features that the Android app does not (but it's own set of limitations).
0 -
FYI, recent WINEs (at least on mac) seem to have gotten much better (at least for the apps I run on it). It might be worth giving Logo on WINE another try. I currently run on a mac, but it is a very old one, and when it goes, I will be switching to Linux, if I can. I really don't want to support either Microsoft or Apple for their anti-Christian positions.
0 -
Michael Lindner said:
FYI, recent WINEs (at least on mac) seem to have gotten much better (at least for the apps I run on it). It might be worth giving Logo on WINE another try.
WINE and commercial CrossOver (by Code Weavers) still are not viable for Logos 4 and newer. Open source community does not have Windows graphical alternative for Windows Presentation Foundation (WPF). Hence, WINE lacks software support to show Logos user interface. Mono's WPF information in 2017 => http://www.mono-project.com/docs/gui/wpf/
Thankful for Faithlife developing web sites https://app.logos.com and https://app.verbum.com that can be used on a variety of open source distributions. Browser needs WebGL. Now membership OR Cloud subscription is needed to use Web App(s).
Keep Smiling [:)]
0 -
Logos Linux Please!
0 -
Solution (sort of)... This assumes you have some I.T. knowledge, but you're running Linux, so you're probably good to go.
I tried to find a home-based solution to this, and basically came up with the same dead-ends...However, I found an option through cloud hosting, which seems to be even better, allowing more flexibility.
First of all, let me preface this by saying that Logos has their own related solution in development through their new web-based application, at app.logos.com... I would rather pay for Logos Cloud to do this, versus paying a secular cloud host... but the costs for the cloud host appears to be quite minimal, after paying Logos for the LBS library licensing.
I have now completely installed the Logos Bible Software application, "downloaded" the library material I am paying for, and have begun to learn to use Logos 7...and as long as I have a stable connection at whatever location I am using, I can read til my eyes go blank (or the boss calls) using my Linux box, or another Mac or Windows PC. All of that took me less than an hour, thanks to Amazon, Microsoft, and of course Logos.
0 -
Phil,
Could you explain further the solution you're using? I'm also a Linux user and what I've ended up doing is running Logos in a Windows virtual machine under Linux (KVM). Is that the same thing you're doing? Are you running a virtual machine version of Windows an a cloud host and then remotely accessing it?
Thanks,
Adam
0
said:
