Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
02-27-2013, 08:01 PM
|
#31
|
|
Moderator
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware
Posts: 12,146
|
I must admit that I have not testet Windows/Linux on UEFI yet, but since I want to repartition my machine anyways in the near future I will give that a try and report back.
|
|
|
1 members found this post helpful.
|
02-27-2013, 08:33 PM
|
#32
|
|
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 3,645
|
Quote:
Originally Posted by Erik_FL
Does giving Microsoft more control over PC hardware and the boot environment benefit or hurt consumers in the long run?
|
It hurts consumers because it limits choices and hinders competition. People should have the option to dual boot, run whatever OS they want on their PC.
|
|
|
|
02-27-2013, 11:35 PM
|
#33
|
|
Senior Member
Registered: Jul 2011
Distribution: Slackware64-14.0, LFS-7.3, FreeBSD 9.1
Posts: 1,096
Rep: 
|
Exactly. Microsoft can claim all they want we "lease" the OS from them, but if that's the case, then are we also "leasing" the hardware from the OEM also? We "buy" copies of software and buy hardware just the same, so why is it Microsoft gets to play pick and choose and nobody short of the US government has attempted to tell them this isn't how it works?
|
|
|
|
02-28-2013, 04:10 AM
|
#34
|
|
Senior Member
Registered: Sep 2004
Distribution: slackware
Posts: 1,682
Rep: 
|
Quote:
Originally Posted by TobiSGD
I must admit that I have not testet Windows/Linux on UEFI yet, but since I want to repartition my machine anyways in the near future I will give that a try and report back.
|
Please do this, because if you can get it to dual boot using BCD, I'd like to know how you did it.
Last edited by rkelsen; 02-28-2013 at 04:12 AM.
|
|
|
|
02-28-2013, 06:39 AM
|
#35
|
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Laptop: Slackware 14.0 // Desktop: Slackware64 14.0 // Netbook: Slackware 14.0
Posts: 6,176
|
Quote:
Originally Posted by H_TeXMeX_H
And yet you ignore the fact that ARM devices with that logo ARE locked-in and can ONLY boot secure boot. How long is it until x86 becomes the same or maybe even disappears, leaving you locked-in.
|
ARM devices are proliferating, ARM processors getting more powerful. And suddenly Microsoft get interested in ARM, and want that lock-in. That should get everybody's alarm bells ringing.
|
|
|
1 members found this post helpful.
|
02-28-2013, 06:39 AM
|
#36
|
|
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 2,422
|
There must be something to this stuff -- the "other" post "Slackware on UEFI" http://www.linuxquestions.org/questi...fi-4175448945/ has, right now, 3,064 views. Somebody's interested, eh? Folks are concerned.
|
|
|
|
02-28-2013, 07:59 AM
|
#37
|
|
Member
Registered: Apr 2005
Distribution: Slackware
Posts: 884
|
Quote:
Originally Posted by volkerdi
Well, here's something to consider. So far, I've only heard about being able to turn Secure Boot on or off. There's no way to set it to on for this OS, and off for another. Windows 8 will work without Secure Boot, but what about Windows 9? Most of the people I've known who have gotten into Linux (including myself) started on a machine where they dual booted it with Windows. I still know many people who don't personally care for Windows, but still have to keep it around because of work, hardware that isn't supported on Linux, or for other reasons. If a future version of Windows refuses to work with secure boot deactivated, that's a pretty big hurdle for a new user who isn't willing to switch entirely away from Windows. And it seems like the technical hurdles for supporting Secure Boot on Linux are much larger for the new user unless we accept Microsoft as the sole key authority, since their key is the only one shipping in firmware.
I can't see how Secure Boot doesn't either result in less Linux adoption, or giving a lot more control over Linux to Microsoft... that's why I care.
|
This has been my main concern about secure boot all along. Anyone who does not at least suspect that this may be the groundwork for some kind of a cynical ploy to lock out *nix systems, is being a little naive.
Quote:
Originally Posted by brianL
ARM devices are proliferating, ARM processors getting more powerful. And suddenly Microsoft get interested in ARM, and want that lock-in. That should get everybody's alarm bells ringing.
|
[sarcasm]No, I'm sure you're just putting two and two together and making five... conspiracy theorist... [/sarcasm]
Last edited by caravel; 02-28-2013 at 11:14 AM.
Reason: It's evening, I'm tired, so I'm not sure what the two posts following mine are about, but I've added some clarification...
|
|
|
|
02-28-2013, 08:11 AM
|
#38
|
|
Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,598
|
Quote:
Originally Posted by caravel
No, I'm sure you're just putting two and two together and making five... conspiracy theorist...
|
No, I'm sure you're just putting two and two together and making three ... ignorant fool ...
|
|
|
|
02-28-2013, 08:47 AM
|
#39
|
|
Moderator
Registered: May 2001
Posts: 24,779
|
Keep it clean, lay off you theoretic ignoramuses and conspirative fools.
|
|
|
|
03-06-2013, 06:10 AM
|
#40
|
|
Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,598
|
Quote:
Originally Posted by H_TeXMeX_H
And yet you ignore the fact that ARM devices with that logo ARE locked-in and can ONLY boot secure boot. How long is it until x86 becomes the same or maybe even disappears, leaving you locked-in.
|
One this note, see:
http://hardware.slashdot.org/story/1...intel-kill-x86
|
|
|
|
03-06-2013, 01:34 PM
|
#41
|
|
Moderator
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware
Posts: 12,146
|
Quote:
Originally Posted by H_TeXMeX_H
|
I can only repeat what I said before on various occasions: On ARM (almost) anyone is locking the devices, yet nobody is blaming Apple or the manufacturers using Android for that, but once Microsoft with its negligible marketshare in the ARM world does the exact same thing the whole world is crying out loud how they are occupying our hardware.
Guess what? The same thing that works on x86 hardware (look out what you are buying and that you can use it in the way you intend to) is also working on ARM devices: Want to use Linux on your ARM device? Then simply don't buy a Windows machine. Why would you do that anyway if you don't plan to use Windows?
|
|
|
|
03-08-2013, 02:04 PM
|
#42
|
|
Member
Registered: Nov 2009
Location: Salina,KS
Distribution: Slackware
Posts: 50
Rep:
|
Quote:
Originally Posted by ReaperX7
I wish Linus would yank Linux away from Red Hat and forbid them to release, work on, or contribute anything to Linux anymore. I won't bring up why, again, but it involves a certain "developer" who shall be known as "He Who Shall Not Be Named".
|
I believe a better term for him would be "The Microshaft Enabler".
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:05 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|