You are not logged in.
I put the following in /root/.bashrc. It gives me root's normal path when I use 'su' in a user's terminal. The advantage is it keeps me in the user's home instead of moving me to /root, where I'd have to cd to user's home again. (for example to install a deb package I just downloaded). It also allows me to run graphical apps as root. (e.g. I use gparted a lot).
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"Apparently experimental.
I've used it many times without fail now.
Good to hear. I'm pretty sure that all it does is make an fstab entry for the home partition. And I think you don't get the new desktop config files that way. Also, if the user name and uid don't match, you have serious problems.
Change the directory name to your user name and you should be good to go.
There are also instances of "/home/$username" in various config files that might need to be changed. The live installer can do this when you select a new user name, but ONLY if you take the new /home that the installer gives you (i.e. it copies the home from the live system.)
First user gets id 1000:1000 in debian and probably all debian-based systems. It's the number that determines who owns the files, not the name.
I say not to use that feature because it does not work right or work the way anyone expects it to work. I've removed it from later versions of the installer.
You can do a clean install and copy files from backups. If you have a lot of big files, that could take some time. (I'm a little sensitive about this issue now because I recently had to move a terabyte of wav files.) Also, if you copy files from backup as some user, that user will own the copied files.
And if you just keep the files on the hard drive, keep the same user name and user ID number, then permissions and ownership of your files will be correct.
If you're planning on using refractainstaller's "keep old home" option, my advice is "Don't do it!" Install everything to one partition and then manually move your home to the old home partition. Or make a symlink in your new home that goes to the old home. If you want more details on how to do it manually, just ask.
Search for an exact match
Put a word or phrase inside quotes. For example, "tallest building".
I've tried that many times, and it never seems to work. At this point, I'd be happy to know how to get google to return hits that contain my search terms.
I believe this problem and others with the repo have been fixed. Please let us know if that's not the case.
FTR: With plain openbox, setting the theme in:
obconf - just changes the title bar, buttons (and borders?) but not
the highlights.
lxappearance - changes the highlights. (gets rid of the raleigh blue)
lxappearance-obconf - apparently does nothing, and it's described as a
theme switcher for LXDE.
gtk2-engines - didn't seem to do anything in openbox.
To get the cinnabar highlights in synaptic or other root apps, you can copy ~/.config/gtk-3.0/settings.ini to root's home after you set the theme with lxappearance.
Oops. My typo. Should be headers not header. I did it with dollar sign and parentheses, but you can also do it with backticks, which are easier to type but not easier to see in a post.
apt-get install build-essential linux-headers-`uname -r`The most guified and clicky package manager is synaptic
If you're going to compile stuff from source you'll need to install build-essential and linux-headers-$(uname -r)
deb.devuan.org was fixed (today?)
another option for using mirrors is auto.mirror.devuan.org which was upgraded to the same software as deb.devuan a few months ago.
Edit: fixed typo - it's headers not header. (and it's build-essential, not essentials in case anyone was wondering)
pkgmaster.devuan.org should be replaced with deb.devuan.org. That way you will pull from the nearest mirror, and we won't have everyone hitting on the main server. Thanks.
Thanks, I knew there had to be other ways. (It's linux.)
OMG, I've been using feh for years, and I just read the man page for the first time. I had no idea it could do so much.
The command to allow PCManFM to set wallpapers and enable the use of desktop icons is:
pcmanfm --desktopThe native desktop menu of the window manager will be replaced with that provided by PCManFM. However, it can easily be restored from the PCManFM menu itself by selecting
Desktop preferencesand then enabling the
Right click shows WM menuoption in the Desktop tab.
Thanks, that works.
If you do get the native window manager menu on right-click, you need to run pcmanfm --display-pref to get the the desktop settings. (to change the wallpaper again after enabling the wm menu)
For plain encrypted filesystems without lvm, you can do the fix that changes the timeout.
Edit this function in /lib/cryptsetup/cryptdisks-functions. (And keep a spare copy of this file those times when an update wipes out your edits. )
_do_stop_callback() {
local i rv=0
for i in 1 2 4 8 16 32; do
remove_mapping "$CRYPTTAB_NAME" 3<&- && break || rv=$?
if [ $rv -eq 1 ] || [ $rv -eq 2 -a $i -gt 16 ]; then
log_action_end_msg $rv
break
fi
log_action_cont_msg "$CRYPTTAB_NAME busy..."
sleep $i
doneTo look more like this. You can make it 'for i in 1' instead of 'for i in 1 2' if you want.
_do_stop_callback() {
local i rv=0
for i in 1 2 ; do
remove_mapping "$CRYPTTAB_NAME" 3<&- && break || rv=$?
if [ $rv -eq 1 ] || [ $rv -eq 2 -a $i -gt 16 ]; then
log_action_end_msg $rv
break
fi
log_action_cont_msg "$CRYPTTAB_NAME busy..."
sleep $i
doneI know two ways to get the desktop background image in openbox.
1. spacefm - add the following line to ~/.config/openbox/autostart
spacefm --desktop &
To select a background, open spacefm and go to View, Preferences, then check the Wallpaper box and select an image. That image will come up as the background when you start openbox.
2. nitrogen - add the following line to ~/.config/openbox/autostart
nitrogen --set-scaled /usr/share/images/desktop-base/desktop-background
3. If you use lxdm, openbox will take the background and gtk theme set in /etc/lxdm/lxdm.conf
(Nobody expects the Spanish Inquisition!)
I checked pcmanfm, but I couldn't find a setting for the desktop background.
You don't say what card you have. It looks like that package is for optimus. For other nvidia cards, you would install nvidia-drive. Both of those are metapackages which should pull in any dependencies.
The problem is you keep trying to install the xfce4 package when you don't want it. It's a metapackage that pulls in parts of the xfce4 desktop that you don't want. Just install the parts you do want as I posted above.
Here it is again, without the extra backslash at the end:
apt install xfconf xfdesktop4 xfwm4 xfce4-terminal xfce4-session xfce4-xkb-plugin xfce4-panel \
thunar thunar-volman thunar-archive-plugin xfce4-notifyd libnotify-bin mesa-utils \
xfce4-power-manager xfce4-cpugraph-plugin xfwm4-themesMore info:
$ apt-cache show xfce4
Package: xfce4
Version: 4.12.3
Installed-Size: 16
Maintainer: Debian Xfce Maintainers <pkg-xfce-devel@lists.alioth.debian.org>
Architecture: all
Depends: xfwm4 (>= 4.12.0), xfconf (>= 4.12.0), xfce4-settings (>= 4.12.0), xfce4-panel (>= 4.12.0), xfdesktop4 (>= 4.12.0), thunar (>= 1.6.6), gtk2-engines-xfce (>= 3.2.0), xfce4-session (>= 4.12.0), xfce4-appfinder (>= 4.12.0), xfce4-pulseaudio-plugin, orage (>= 4.12.0), libxfce4ui-utils (>= 4.12)
Homepage: http://www.xfce.org/
Recommends: xorg, desktop-base (>= 5.0.4), thunar-volman (>= 0.8.1), tango-icon-theme (>= 0.8.90), xfce4-notifyd
Description: Meta-package for the Xfce Lightweight Desktop Environment
Description-md5: 53123f9cf40a71f1a87679634af17db3
Suggests: xfce4-goodies, xfce4-power-manager (>= 1.4.0), gtk3-engines-xfce (>= 3.2.0)
Tag: admin::configuring, interface::graphical, interface::x11, role::dummy,
scope::utility, suite::xfce, uitoolkit::gtk, use::configuring,
x11::application
Section: xfce
Priority: optional
Filename: pool/DEBIAN/main/x/xfce4/xfce4_4.12.3_all.deb
Size: 8014
MD5sum: f3c63bd59ac3aecd6d96ceeeea5f011c
SHA256: 72242e290d6efd1e672f25ec5eaf3c45925be2206e329081b02c19032b69397a
I think you can remove consolekit and lxpolkit and install libpolkit-backend-elogind-1-0 and libpolkit-gobject-elogind-1-0 (to replace the consolekit versions of the same libraries.)
I have xfce working with lxdm in refracta9. You're probably missing some polkit package(s). Run the following command and compare the output. (Note that there are duplicates in the list.)
user@refracta:~$ dpkg -l | egrep "consolekit|elogind|policykit|polkit|libpam"
ii elogind 234.4-2 amd64 user, seat and session management daemon
ii libelogind0:amd64 234.4-2 amd64 user, seat and session management library
ii libpam-elogind:amd64 234.4-2 amd64 elogind PAM module
ii libpam-modules:amd64 1.1.8-3.6 amd64 Pluggable Authentication Modules for PAM
ii libpam-modules-bin 1.1.8-3.6 amd64 Pluggable Authentication Modules for PAM - helper binaries
ii libpam-runtime 1.1.8-3.6 all Runtime support for the PAM library
ii libpam0g:amd64 1.1.8-3.6 amd64 Pluggable Authentication Modules library
ii libpolkit-agent-1-0:amd64 0.105-25+devuan0~bpo2+1 amd64 PolicyKit Authentication Agent API
ii libpolkit-backend-1-0 0.105-25+devuan0~bpo2+1 all PolicyKit Authorization API
ii libpolkit-backend-elogind-1-0:amd64 0.105-25+devuan0~bpo2+1 amd64 PolicyKit backend API
ii libpolkit-gobject-1-0 0.105-25+devuan0~bpo2+1 all PolicyKit Authorization API
ii libpolkit-gobject-elogind-1-0:amd64 0.105-25+devuan0~bpo2+1 amd64 PolicyKit Authorization API
ii policykit-1 0.105-25+devuan0~bpo2+1 amd64 framework for managing administrative policies and privileges
ii policykit-1-gnome 0.105-6 amd64 authentication agent for PolicyKit
user@refracta:~$ I've used this guide in the past for creating kernel packages the debian way. I think it still works.
http://forums.debian.net/viewtopic.php? … 209aa52a2f
Hm.. I just checked and kernel-package is available in ceres (sid), ascii (stretch) backports and jessie, but it's not in beowulf or buster. Not sure what to make of that.
Be aware you need to run the command boot-update after (re-)installing Grub or replacing a kernel. And you need to run it as root
That won't work so well in debian-based distros. (Won't work at all.)
grub-install [target] installs the bootloader. target is a drive or partition for legacy/bios systems, omitted for uefi systems.
update-grub creates the boot menu
neutrinosteak: if it's a uefi system, this may help:
https://dev1galaxy.org/viewtopic.php?id=2676
If you have a minimal Devuan install it can be copied to the target partition with rsync
We do have that:
https://files.roundr.devuan.org/devuan_ … imal-live/
That thing that looked like a dialog box was a dialog box. It won't respond to clicks. Use arrows and tab to navigate, space bar to select/unselect and enter to confirm an OK.
Future releases will have a real graphical debconf frontend. (thanks, miyo!)
You should not have to install grub manually. If you saw a "copy files" button, then that was the right one to pick. That causes the grub-pc package to be installed and gives you the blue debconf windows for choosing the location.
When it hangs, take a look in /var/log/refractainstaller.log (or refractainstaller_error(s).log depending on the version) or post/paste it somewhere for me to see.
Does your hard drive have msdos or gpt partition table?
See the section on "### Starting X from a console (TTY)"
https://files.devuan.org/devuan_ascii/Release_notes.txt