<div dir="ltr"><div><div>Hi Jonathan, I'm very interested in learning CLI from Grub, never done it before and I,m pretty new to (advance CLI) as I would look at it. is there a link or a tut that you can point me to.<br>
</div>Thanks<br></div>Jose Lopez<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 31, 2013 at 11:36 PM, Jonathan Marsden <span dir="ltr"><<a href="mailto:jmarsden@fastmail.fm" target="_blank">jmarsden@fastmail.fm</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 05/31/2013 09:10 PM, Phill Whiteside wrote:<br>
<br>
> you can also utilise the abilities built into the linux kernel.<br>
<br>
Those kernel parameters *are* "abilities built into the Linux kernel",<br>
aren't they? :)<br>
<br>
> I know at times I seem like a fan boi of virt-manager, but it is a<br>
> GUI that uses the kvm abilities that are in built to the linux<br>
> kernel. I'm sure the purists will prefer using virsh exactly, but I<br>
> do ask why we need to learn so much command line stuff :)<br>
<br>
(1) When your machine doesn't boot, knowing enough to play with Grub a<br>
little is something that suddenly seems well worth knowing :) Grub is<br>
command based and text-file-configured, so unless you can point me to a<br>
100% GUI-configured boot manager to use instead of Grub, I think that<br>
means learning a few keystrokes and config items, in order to understand<br>
and manage how your PC boots.<br>
<br>
(2) Creating a test VM and installing a fresh Lubuntu OS into it, then<br>
booting the VM and testing, and then (if you have limited disk space)<br>
deleting the VM afterwards, takes *way* more time and effort than<br>
rebooting a PC with an existing Lubuntu installation on it and typing<br>
<br>
mem=512M nosmp<br>
<br>
into one line of boot info and pressing Ctrl-X.<br>
<br>
I was responding to someone who said they "couldn't" test a Lubuntu in a<br>
low RAM low-CPU environment because they had a dual-core CPU and 1GB...<br>
my point was and remains that they absolutely *can* do such testing on<br>
that hardware, with minimal time investment and in a way that leaves<br>
their PC "just like it was before" once they are done testing and reboot<br>
normally.<br>
<br>
Are you *sure* "use KVM to create a VM to test in" is an appropriate<br>
response to a user with a Pentium D and 1 GB RAM? I think it's possibly<br>
more appropriate for users with later CPUs and 4GB or more.<br>
<br>
Finally, even *if* the Pentium D the user concerned has supports VT-x<br>
(which is needed for KVM, and the Smithfield Pentium D CPUs don't have<br>
it, only the later Presler ones do!),<br>
<a href="https://help.ubuntu.com/community/KVM" target="_blank">https://help.ubuntu.com/community/KVM</a> says that KVM in Ubuntu is<br>
intended for server, not GUI workstation virtualization, for which<br>
Virtualbox is better suited... that info may be out of date now, but it<br>
used to be valid...<br>
<span class="HOEnZb"><font color="#888888"><br>
Jonathan<br>
<br>
--<br>
Lubuntu-users mailing list<br>
<a href="mailto:Lubuntu-users@lists.ubuntu.com">Lubuntu-users@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/lubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/lubuntu-users</a><br>
</font></span></blockquote></div><br></div>