Jump to content

Charles@Bodhi

Member Since 23 Feb 2011
Offline Last Active Private
****-

#103680 System Password with USB boot drive

Posted by Charles@Bodhi on 20 March 2017 - 08:24 PM

Welcome to the forums.

 

I hope I understood your question correct. You "installed" to an USB-drive using Unetbootin. And you don't notice any password present.

 

First off, Unetbootin does not install the OS, it only creates a medium (flashdrive) you can use to do a real install. A Bodhi Linux live-session by default has an empty password. This means you leave the box to fill in your password open when a program asks for it, you just hit Enter.

 

Installing Bodhi Linux to a drive, USB or HDD equally, is done by starting the live-session and use the launcher for the installer, either the icon on the left of the shelf, or the icon in the menu > applications. This will open a window with several steps to follow ending with a dialog to put in your name, the computer name and the username. Next you can provide a password. Username and password you should not forget as you will need those when running the installed system.

 

Let us know if this was the answer you needed or if you need to know more. By the way, most of the basic stuff a beginning Bodhi-user needs to know is explained in the quick start guide that shows when you boot the live-session, really worth reading.

 

Enjoy,

Charles




#103464 Cannot load modules in Moksha [SOLVED]

Posted by Charles@Bodhi on 28 February 2017 - 07:26 PM

charles@B410-64:~$ dpkg -l moksha-flame
dpkg-query: no packages found matching moksha-flame
charles@B410-64:~$ dpkg -l moksha-forecast*
dpkg-query: no packages found matching moksha-forecast*
charles@B410-64:~$

So packages are not installed by default ! (at least in 4.1.0-64)

 

For people that want them loaded, you first need to run:

sudo apt-get install moksha-flame moksha-forecasts

 

Enjoy,

Charles.




#103451 Share your Desktop

Posted by Charles@Bodhi on 28 February 2017 - 10:15 AM

Someone who mess up with your HDD is entering hell, literally. :P :P :P

 

[hint, looks at HDD names in places]

 

Probably Windows partition ??




#103434 Chromium: can't move to other virtual desktop

Posted by Charles@Bodhi on 27 February 2017 - 01:17 PM

Well, talking about alternatives. If you have a visible pager you can drag the chrome icon from your current desktop to another desktop and the window will move to that desktop. More easy than clicking around.  ;)

 

Enjoy,

Charles.




#103395 Desktop settings gone after upgrade?

Posted by Charles@Bodhi on 25 February 2017 - 03:01 PM

Since your .e folder is missing and not automagically rebuilt on reboot your desktop is crippled. You might try the following command in a tty:

sudo apt-get install --reinstall bodhi-deskop

Use CTRL + ALT + F1 to go to a tty.  When done type 'sudo reboot' and you should come back in a default moksha desktop.

 

Enjoy,

Charles

 




#103165 Unwanted desktop icons

Posted by Charles@Bodhi on 09 February 2017 - 08:02 PM

By the way, this does not solve your issue. The new ibar that shows on your desktop can not be told to appear only on the second desktop and nowhere else. If you absolutely want that you need to create a new shelf at the top of your second desktop and add an ibar to it with the items you want to have. That could be set to autohide to be available on mouse over and otherwise it will be out of sight. Just thinking..

 

Enjoy,

Charles




#103107 rendering errors

Posted by Charles@Bodhi on 06 February 2017 - 01:56 PM

@ graywizard

 

If you use CTRL + ALT + END Moksha will reset itself, leaving all your open windows as they were. So that may be worth a try whenever this happens again.

 

Enjoy,

Charles




#102755 Bodhi - Real Time Kernel?

Posted by Charles@Bodhi on 16 January 2017 - 06:53 PM

No need to use a ppa IMHO. Bodhi ships with a LTS kernel 4.4.0-36. The same longterm supported kernel has a lowlatency variant in the repos. The most recent of those can be installed easily:

sudo apt-get install linux-image-4.4.0-59-lowlatency

Reboot and your grub will show this kernel as first choice. Try it and test it out, your previous kernel will still be available and your setup won't change. But risks are that some candies not work as expected as a stock Bodhi uses the extra - generic kernel version. Again, no harm done.

Whenever you feel the need to return to the "old" kernel you only need to reboot and use grub (maybe you need to look into the advanced line) and boot into the earlier kernel. In case the new one does not please you it is easy to remove it, as long as you are not running it.

 

Enjoy,

Charles




#102717 Linux noobie

Posted by Charles@Bodhi on 14 January 2017 - 09:07 PM

Sorry we must disappoint you at the moment. The appcenter currently is not fully laid out for Bodhi 4 because we only have a small staff but a lot of stuff to handle and compiling Open Office to work with Bodhi4 does not have high priority. The Libreoffice full suite is functional for install though.

 

Enjoy,

Charles




#102680 Swappiness and Trim - Recommendations?

Posted by Charles@Bodhi on 12 January 2017 - 06:59 PM

Hmm,

 

- Sleep means saving your machine state to memory and if needed to Swap.

- Hybernation means saving your machine state to Swap only, as power needed for memory is cut off.

 

Two reasons normal users don't encounter? 

 

Running  a video player, a browser with a few tabs open, compiling some stuff in the background, Gimp open for another image you plan to edit and having a virtual machine running at the same time, even in Bodhi this adds up. 

 

Just looking at my RAM usage with only Chromium with 4 tabs open shows over 1.7Gib (out of 4Gib) of Ram in use.

An idle system here takes 260 Mib. Count your blessings with todays internet.

 

Enjoy,

Charles

 

PS. I would prefer to run TRIM (or UNMAP) in a cronjob. The built in "cleaner" on modern SSDs does not all of what trim does, so the risk of wear slower performance is still present.




#102659 Idea: a conky fork suited for Moksha

Posted by Charles@Bodhi on 11 January 2017 - 08:47 PM



I didn't know that conky didn't work with Moksha...I was planning on giving it a try - glad this topic exists!

 

So it sounds like the Mythbusters would call this one "plausible" at most?

 

True, there is no Conky module, but conky is an application that can be used freely and is present in the ubuntu repos.

Reading the manpages of conky is laborious but has the info about the opacity settings.

But:

Conky for the most of its effects needs a compositor. ATM there is no native compositing module that is working as wanted on BodhiLinux. However a valid alternative is "compton" (in the repos too) that allows for transparency and a more fluid behavior of the desktop. The same conky config that I had in Bodhi 1, 2 and 3 with various E17 versions still provides me lots of info on screen with Moksha.

 

I'd say, start playing and show us some of the resulting desktops in the desktop topic.

 

Enjoy,

Charles

 

Screenshot 2011

5XCWa.png

 

Screenshot today

UG4VwAw.png




#102594 container image?

Posted by Charles@Bodhi on 08 January 2017 - 12:51 PM

Thanks for sharing. Containers are interesting stuff for debugging issues.

 

Enjoy,

Charles




#102528 Low Performance on Bodhi

Posted by Charles@Bodhi on 05 January 2017 - 07:44 PM

The command sudo gives you temporary root permissions for a task. So in your case instead of just "sh" use " sudo sh" 

It will ask for your password. When you type it in there will be nothing shown on screen, finish with ENTER to continue.

 

Enjoy,

Charles

 

PS: Sudo should be used with care ! 




#102482 Share your Desktop

Posted by Charles@Bodhi on 04 January 2017 - 01:00 PM

Just curious is Compton in the Bodhi repo?

 

apt-cache search compton
compton - compositor for X11, based on xcompmgr

So, yes it is. Only one command away:

sudo apt-get install compton

Enjoy,

Charles

 
 

  • Kev likes this


#102471 Setting up Raid 0 on two HDD with separate OS SSD - Considering ZFS?

Posted by Charles@Bodhi on 03 January 2017 - 07:51 PM

...is there an intermediate step I possibly missed?  

 

 Can't tell you, but the order of things might be part of it. The step where you introduced the GPT might be a factor, not sure. 

 

Maybe starting afresh is a good idea. 

- check /proc/mdstat for a running raid device and stop it. Unmount the running raid when needed.

- Use Gparted (or gdisk) to replace the partition table of the future raid disks. Make sure to choose GPT.

- use gdisk to set the raid type (0xFD00) to your raid disks

- perform the mdadm --create command

- check /proc/mdstat

- when positive for md0 presence perform the scan to register it in the config file

- time to format your raid device, I assume you know how to calculate the stride and stripe-width

- check /proc/mdstat again

- mount the raid to its mountpoint.

- check the presence in /proc/mounts

The command df -h should list the raid too.