You are not logged in.
Thanks. I don't actually use that, but I'm glad to know about it. It might come in handy some time.
Check the other dirs in /usr/share/doc. It's possible that it was all removed to save space. My doc/mpv is full of files that have some content. A reinstall of mpv should fix it.
I don't know about gparted. What you describe is different from the other permission/authentication problems reported for gparted, but it might be related. (consolekit, policykit-1, policykit-1-gnome, libpam-ck-connector, udisks...) If synaptic is installed, does that work ok?
This is not exactly what you're looking for, but maybe it can be adapted or maybe it will give you an idea. I set up xscreensaver to run a script that would stop if I clicked the mouse or keyboard. You could either have it run/stop somescript or have it run a script that did something with somescript. Maybe looking in the xscreensaver source code will give you ideas, too.
http://forums.debian.net/viewtopic.php? … 55#p591933
An even easier solution than switching to gnewsense would be to avoid upgrading wheezy. Do they have any plans for a jessie release? And do they offer non-free wireless firmware? That would be a deal-breaker for a lot of people.
Here's what's in the current download from gnewsense.org:
$ uname -a
Linux gnewsense 3.2.0-4gnewsense1-amd64 #1 SMP Debian 3.2.57-3+deb7u1gnewsense1 x86_64 GNU/Linux$ cat /etc/issue
gNewSense GNU/Linux 4 \n \l$ cat /etc/debian_version
7.5$ dpkg -l |grep systemd
ii libsystemd-daemon0:amd64 44-11+deb7u4 amd64 systemd utility library
ii libsystemd-login0:amd64 44-11+deb7u4 amd64 systemd login utility library
Man, I keep adding more and more to my plate.
Been doing it for six years here, and it never seems to end. And whatever install or upgrade scripts you make for jessie to ascii, there will be things that break in them when it's time to go ascii to beowulf. I'm not trying to discourage you. Just letting you know what to expect so you won't get discouraged when it happens.
There is no default firewall front-end installed in debian or devuan. There is iptables, but no rules are in place. If you install some services that listen for connections, then you will have open ports. (examples: openssh-server, mysql-server, apache2, samba)
If you're behind a router, the router is being scanned, and unless you set up port-forwarding in the router, the outside world can't see the open ports on your computer.
For shutdown and reboot, check that you have consolekit, policykit-1, libpam-ck-connector, and maybe policykit-1-gnome. Maybe something else, too, and that might depend on what desktop you're using.
For dns, I just set it in my router. To set it in the system, you can put it in /etc/resolv.conf (nameserver) or /etc/dhcp/dhclient.conf (prepend domain-name-servers) or /etc/network/interfaces.
sort -u ~/.bash_history > temporary-file
cat temporary-file > ~/.bash_history
nl temporary-file > index_file
Use the index file for reference. You don't want to number the lines in .bash_history, but you do want a numbered list.
This will work until you reach the limit of bash_history, and the commands start scrolling off the top. See 'man bash' for the HISTSIZE setting if you want to change the number of lines that get saved. I don't remember what the default is - maybe 1000 or 2000.
When a .so file is missing, you usually need to install the -dev package of whatever.
sort -u ~/.bash_history
I turned it off temporarily. Waiting to get clarification from tapatalk on something. Ask here or in freenode #devuan if you need help.
fsmithred
Actually it's in the devuan ascii repo (or so says this pkg list) http://devuanpackages.viralds.it/ascii/package/yad
The version of yad (0.38) in the ascii repo uses gtk3 and does not work will with refracta tools - buttons are off-screen. I made gtk2 verions in jessie, but they seem to be working fine in ascii -
http://distro.ibiblio.org/refracta/file … _packages/
Or, you could package them yourself. I already made the one or two small changes for gtk2.
https://git.devuan.org/fsmithred/yad
Maybe soon, for real. I already know that amprolla3 works, because I tried it when it was on a test server. And I noticed today in #devuan-dev that a new devuan-keyring was being built. This is all just circumstantial evidence, but I'm hopeful.
I'm not aware of any problems with leaving ascii-proposed-updates enabled.
Make sure you have ascii-proposed-updates enabled in sources.list. Some of the security updates can be found there.
Use the full path. (without sudo)
export PATH="$PATH:/home/devur/scripts"
I don't know anything about arm or pi, but I have to ask: why does it need to be tar.gz? Do you need to install xz-utils to manipulate a file compressed with xz?
'xz -d <file>' to decompress
or
'tar -xvJf <file>' if it's a tar.xz.
I'm not sure what the best solution is. One thing you could try is downgrading all those packages to the version you had previously. The deb packages can be found in /var/cache/apt/archives. But that could be messy.
If everything seems to be working, you might just leave it alone. Wait for us to do some work on ascii and then switch your sources from jessie to ascii and upgrade the rest of your packages so they are from the same release as the ones you just pulled from stretch. No guarantees that it won't be messy, too. But maybe it will work ok.
If you are adventurous and know your way around the package manager pretty well, you could try upgrading the rest of the system to ascii now. You will probably run into conflicts. Don't do it unless you are comfortable with the idea of solving those problems and would not mind reinstalling if it turns out badly.
jessie = jessie
ascii = stretch
beowulf = buster
ceres = sid
Devuan is all about removing that library,.
I don't know where you're getting your information, but that bit is just plain wrong. The default desktop install includes libsystemd0. Devuan is about removing dependency on systemd itself. The lead devs are not concered with that library and don't intend to spend any energy on removing it.
I don't know if it's related, but thunar has a similar bug. Sometimes it locks up when it's in detailed list view. If I catch it soon enough, I can press ctrl-1 or ctrl-3 to change to icon or simple list view or else close the window by clicking on the x in the corner. If I wait, it totally locks up and has to be killed from command line. It's a known bug in thunar that's been around for years.
While it took two years to get a final release of devuan jessie, it was usable long before that. A lot of the delay was just some loose ends to tie up. (Couple of problems came up in the installer.)
We don't expect the next release to take that long. If you test it out in a VM or on a spare computer or even one of the live isos, you'll feel like you're using the debian you remember.
Faster boot times. (no more 5-minute waits for a start job)
Predicatable interface names. (I know it's going to be eth0 unless I changed my hardware.)
An init system that's been well-tested. (I might switch to systemd once they're done developing it and it's had time to mature.)
An init system that knows it's an init system and is OK with that.
Probably more, but it's time to let the dogs out.
Could be a trick question, so I'll give the trick answer first - Devuan didn't use any compile options. Now I'll explain.
Caja is not a devuanized package. You can tell by looking at the version number, which does not have "devuan" appended to it. So it's exactly the same package that debian provides. The compile options can be found in the rules file of the source package, and you can get the source package with the command (as unprivileged user)
apt-get source caja
(Make sure you have deb-src lines enabled in /etc/apt/sources.list)
There are good instruction for what to do with that source package here -
http://forums.debian.net/viewtopic.php?f=16&t=38976
If you do it this way and make a .deb package, then the package manager will know that it's installed. That might be helpful with getting dependencies or if you ever want to install something that depends on caja.
So then hd-media would be the way to go. Follow the debian instructions here, but use the devuan files I linked in my previous post.
French:
https://www.debian.org/releases/stable/ … 02.html.fr
Relevant part in English:
A.2.4. Booting from hard disk
It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download hd-media/initrd.gz, hd-media/vmlinuz, and a Debian CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in .iso. Now it's just a matter of booting linux with the initrd. Section 5.1.5, “Booting from Linux using LILO or GRUB” explains one way to do it.
https://packages.devuan.org/merged/dist … /hd-media/
https://packages.devuan.org/merged/dist … /hd-media/
What new installer of Debian are you talking about? I just booted a new 9.1 debian netinstall iso, and it looks like the same debian-installer that I'm used to. I did notice that the graphical installer needs more than 256mb to boot, but other than that, it looks the same.
Are you looking for this? (Note: if you look around in nearby directories, you can find the mini.iso "business card iso")
https://packages.devuan.org/merged/dist … /hd-media/
If you use one of the Devuan live isos, you can install with refractainstaller, which copies the live system to hard drive.
It's also possible to do a debootstrap install of devuan. You can use a Refracta live-iso for that if you don't already have devuan installed.
https://sourceforge.net/projects/refrac … isohybrid/