The officially official Devuan Forum!

You are not logged in.

#1 Re: Hardware & System Configuration » Having trouble with tmpfs » 2020-04-02 09:57:32

I just added the user option to every tmpfs line, however whenever I enter mount -a in the terminal, I get this error message.

mount: wrong fs type, bad option, bad superblock on ramdisk[...], 
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try dmesg | tail or so

I tried dmesg | tail and found out that it was the discard option that was stopping my tmpfs folders from being mounted so I removed them, tried mount -a again and then got this message.

mount: /run: filesystem mounted, but mount(8) failed: No such file or directory
mount: mount point /var/lock is a symbolic link to nowhere
mount: /run: filesystem mounted, but mount(8) failed: No such file or directory
mount: /dev/shm: filesystem mounted, but mount(8) failed: No such file or directory
mount: /dev/johndoe/Downloads: filesystem mounted, but mount(8) failed: No such file or directory

However, I tested each and every one of my tmpfs folders by adding an empty file into them and rebooting. They were gone from all of them once I rebooted so it looks like my ramdisk is fully working.

However, during this ordeal, I came across a couple of problems.

Whenever I tried to open /etc/fstab with nano (even with sudo) on the terminal, it opens the file but it shows up blank with a message reading Error reading lock file /etc/.fstab.spwp: Not enough data read.

Also, when inserting USB sticks used to mount them automatically, they are unmounted and clicking them in the file explorer brings up a password prompt to eject them and my user password doesn't work. It happened. I think, after I fixed the tmpfs.

My only guess is that it could be caused by OpenRC (the init software I am using), being in the experimental phase.
I also installed Devuan without any non-free or contrib software

#3 Hardware & System Configuration » Having trouble with tmpfs » 2020-04-01 18:32:17

shiztivr
Replies: 4

I've been taking a stab at making tmpfs ramdisks on a Devuan virtual machine.

Here is my setup in /etc/fstab

ramdisktmp /tmp tmpfs rw,discard,noatime,nosuid,noexec,nodev,mode=1777,size=2G 0 0
ramdiskrun /run tmpfs rw,discard,noatime,nosuid,noexec,nodev,mode=1777,size=2G 0 0
ramdiskvarlock /var/lock tmpfs rw,discard,noatime,nosuid,noexec,nodev,mode=1777,size=2G 0 0
ramdiskvarrun /var/run tmpfs rw,discard,noatime,nosuid,noexec,nodev,mode=1777,size=2G 0 0
ramdisktmp /dev/shm tmpfs rw,discard,noatime,nosuid,noexec,nodev,mode=1777,size=2G 0 0
ramdiskhome /home/johndoe/Downloads tmpfs rw,discard,noatime,nosuid,noexec,nodev,mode=1777,size=8G 0 0

I was hoping to move these directories above into tmpfs ramdisks, including my Home's downloads folder.
I tested it out by putting an empty text file in the downloads folder then reboot the VM.
But upon booting up, I found the file was still there when it should've been wiped out with the RAM.
That same Downloads folder, as I defined in the fstab file, was also visible as a mountable disk, like an external drive, on the desktop although I wasn't able to without root access.

To elaborate, although I can still access the Downloads folder in the file explorer, I can't mount it from the desktop. Whenever I do, I get the following error message.

Mount Failed
mount: only root can mount ramdiskhome on /home/johndoe/Downloads

Any help would be much appreciated.
Thanks.

#4 Installation » How should I set my Devuan root partition? » 2020-04-01 15:45:23

shiztivr
Replies: 3

In the Expert Installer, I can choose special options to set my partitions or Devuan such as noa, nosuid and noexec.

For the most secure OS, what options should I check and what exactly do they do?
Also, what shouldn't I check in order to ensure Devuan functions properly?

Thanks.

#5 Re: Off-topic » Folding@home - You can help find a cure to COVID-19! » 2020-04-01 15:42:20

GNUser wrote:

Lopsided, like I said. They expect blind trust but are themselves unwilling to trust.
Trust should go both ways, especially in times of crisis.

We can disagree on this, but I don't think it's ever acceptable to ask someone to run closed source software. Principles don't just fly out the window when times are tough. I think it should be the opposite--good principles provide guidance, should be like light beams to help us find our way when the path is dark.

These folks need to come up with an algorithm that disallows data manipulation/cheating, then open up the code. Keeping the code closed for the highlighted reason is just a copout for bad software design.

I am still running F@h as I speak but you do give a good point about everything.
Have you considered contacting the team behind the software and telling them that?

#6 Off-topic » Folding@home - You can help find a cure to COVID-19! » 2020-03-31 14:58:10

shiztivr
Replies: 7

Lately, I've heard of Folding@home.

It's a project that is researching diseases like Cancer and Parkinson's.
It's pouring its focus into researching the Coronavirus and we can help out by downloading their client software for free. What it does is that it shares some of our unused computer power to help process protein simulations that universities abroad conduct to further understand how viruses work.

With our help, they can find a cure to the coronavirus and the more of us know about this and contribute, the sooner that happens and the more lives we save.

I'd say check it out everyone.
https://foldingathome.org/

#7 Installation » How do I make a triple-boot system, starting with Devuan? » 2020-03-31 14:52:57

shiztivr
Replies: 5

I have a 120GB SSD and I want to make a triple-boot system, starting with Devuan and I want all of my OS's to be encrypted. I prefer to install Devuan with the Expert Install option from the installer-iso so I have more control over it (i.e. init software and non-free blobs).

I know that, in GParted, I can make an extended partition with as many logical partitions inside as I like.
But how do I do that in Devuan's installer (Again, in Expert Install) and make sure all the logical partitions are encrypted?

Thanks.

#8 Installation » Issues with Broken Packages and Updating » 2020-03-30 14:53:20

shiztivr
Replies: 1

I am testing out Devuan 2.1 ASCII on a virtual machine.
I installed it from the Installer ISO via Expert Install with full disk encryption.
I did NOT install any non-free software and I installed OepnRC as my init software.

Upon my first bootup, I tried to update the OS through the terminal but got this error message (at the very bottom of the code down here).

johndoe@devuan:~$ sudo apt-get update && sudo apt-get upgrade
Ign:1 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii InRelease
Ign:2 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii Release
Ign:3 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib all Packages
Hit:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:5 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en
Ign:6 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en_GB
Ign:7 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main all Packages
Hit:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:9 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en_GB
Ign:10 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en
Hit:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:12 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free all Packages
Ign:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:13 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en_GB
Ign:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:14 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en
Ign:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:3 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib all Packages
Ign:5 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en
Ign:6 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en_GB
Ign:7 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main all Packages
Ign:9 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en_GB
Ign:10 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en
Ign:12 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free all Packages
Hit:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:13 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en_GB
Hit:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:14 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en
Hit:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:3 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib all Packages
Ign:5 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en
Ign:6 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en_GB
Ign:7 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main all Packages
Ign:9 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en_GB
Ign:10 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en
Ign:12 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free all Packages
Hit:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:13 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en_GB
Hit:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:14 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en
Hit:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:3 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib all Packages
Ign:5 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en
Ign:6 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en_GB
Ign:7 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main all Packages
Ign:9 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en_GB
Ign:10 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en
Ign:12 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free all Packages
Hit:4 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib amd64 Packages
Ign:13 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en_GB
Hit:8 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main amd64 Packages
Ign:14 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en
Hit:11 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free amd64 Packages
Ign:3 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib all Packages
Ign:5 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en
Ign:6 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en_GB
Ign:7 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main all Packages
Ign:9 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en_GB
Ign:10 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en
Ign:12 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free all Packages
Ign:13 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en_GB
Ign:14 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en
Ign:3 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib all Packages
Ign:5 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en
Ign:6 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/contrib Translation-en_GB
Ign:7 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main all Packages
Ign:9 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en_GB
Ign:10 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/main Translation-en
Ign:12 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free all Packages
Ign:13 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en_GB
Ign:14 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii/non-free Translation-en
Hit:15 http://deb.devuan.org//merged ascii InRelease   
Hit:16 http://deb.devuan.org//merged ascii-security InRelease
Hit:17 http://deb.devuan.org//merged ascii-updates InRelease
Hit:18 http://deb.devuan.org//merged ascii-backports InRelease
Reading package lists... Done                       
W: The repository 'cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-12-21 07:24:54 UTC] ascii Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  linux-image-amd64
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

In case you're wondering, I got my ISO image from this mirror.
https://mirror.leaseweb.com/devuan/

I tried installing some apps but I got an error message in the Synpatic Package Manager saying "Could not apply changes! Fix broken packages first.".

So I tried to fix the broken package in question, which was firejail-profiles, but then I got another error...

An error occurred.
The followin details are provided:
E:Unable to correct problems, you have held broken packages.
E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

#9 Desktop and Multimedia » Does Devuan's Cinnamon DE work with graphics tablets? » 2020-03-30 11:57:18

shiztivr
Replies: 1

Cinnamon is one of my favourite desktop environments about, even if it isn't one of the lightest.
I grew a soft spot for it from Linux Mint which was my very first distro and it allowed me to be able to use and calibrate my Wacom graphics tablet out of the box so I could use Linux for all my productive work.

Before I consider installing Devuan with Cinnamon for real, I want to know how well it works with graphics tablets.
I ask this because I tried Cinnamon on MX Linux several times but it never detected my graphics tablet and, as far as I know, there have been no updates since it is still sitting in MX's test repository.

Thanks.

#10 Re: Installation » How do I make an encrypted Devuan install with a separate boot? » 2020-03-22 16:09:24

fsmithred wrote:

Is there something unusual about your setup? How did you partition the drive? Gparted? Something else? Is there 1MB free space before the first partition? Does it use gpt partition table? What's in the log around the grub-install command?

I used GParted to create an mdos partition table.
In that table, I made three ext4 partitions: boot (/dev/sda1 512mb), root (/dev/sda2 30gb) and home (/dev/sda3 8gb).
No. There isn't any free space BEFORE the partitions but I left 60gb reserved space in my 120gb virtual hard drive.
Where do I even find this log? (Yes, I'm using live boot here)

#11 Re: Installation » How do I make an encrypted Devuan install with a separate boot? » 2020-03-22 13:32:21

fsmithred wrote:

The other way to do the install would be to install the grub-pc package before running refractainstaller, but do not let it install the bootloader at that time.  Run dpkg -i /grub-pc*.deb

I tried that method just now and here is the error message I got.

GRUB failed to install to the following devices:
/dev/sda

Do you want to continue anyway? If you do, your computer may not start up properly.
Writing GRUB to boot device failed - continue?

#12 Installation » How do I make an encrypted Devuan install with a separate boot? » 2020-03-22 09:02:05

shiztivr
Replies: 5

Yesterday, I tested doing an encrypted installation of Devuan on a virtual machine with separate boot and home partitions.
The boot partition was 512MB large, the root was 30GB large and the home partition was 8GB.

During the installation, when I was asked to install the GRUB bootloader, I chose the "Copy Files" option
and then given a choice where to install it - either sda (which was the 200GB virtual disk I made the partitions in) or dm-o, which was
the root partition.

I tried installing it in both but it failed to do so in either options. So I skipped it and because of that, I wasn't able to boot up Devuan at all.

How am I not able to install the bootloader if I'm given the choice to make a boot partition?
Where did I go wrong?

Can anyone please help me?
Thanks.

Board footer

Forum Software