Difference between revisions of "Talk:Installing/New To Linux"
(Tag: visualeditor) |
|||
Line 17: | Line 17: | ||
'''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :( | '''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :( | ||
+ | |||
+ | '''didfem''': Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page. | ||
|- | |- | ||
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️ | | style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️ |
Revision as of 18:01, 25 February 2016
Tracking reviews...
☐ | UNetBootIn? (major?) |
reynhout: UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.
Reply didfem: I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic. reynhout: Fair point. I really dislike that it changes the boot menu, though. What does "Default" do? didfem: When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun. reynhout: Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :( didfem: Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page. | |
☑️ | GigaBytes (minor, but important) |
reynhout: SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.
Reply didfem: "Gb" replaced by "GB". | |
☑️ | Hardware Compatibility table (minor) |
reynhout: The Hardware Compatibility table lists all known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.
Reply didfem: Line added to emphasize the need to check that the Chromebook is supported. |