VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: September 28, 2017, 07:55:33 pm 
Started by BlueMage - Last post by Ranger.JR
Hello

 22 
 on: September 28, 2017, 02:05:18 am 
Started by black-clover - Last post by roarde
One thing to check:
Code: [Select]
su root -c 'diff -u /home/<user that fails>/.bashrc /home/<user that works>/.bashrc | less'

 23 
 on: September 28, 2017, 12:03:42 am 
Started by black-clover - Last post by black-clover
I got  a strange thing.
I installed slim several times on VL Light using the same config files, without any problem.
But, when I installed it on VL-STD I got the following error, when attempting to open the USB memory with spacefm:

Code: [Select]
Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address (polkit-error-quark, 0)
Error mounting /dev/sdb1: GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation

However I do not get this error if I login as another user.
The only files I changed on the account with this problem were .xinitrc and .bashrc
I changed those to match the config of the user that works, but to no avail.


 24 
 on: September 26, 2017, 08:05:57 pm 
Started by bigpaws - Last post by bigpaws
The website is being upgraded over the next several days. There may be
outages as the updates are being done. The length of the outage maybe
from hours to days depending on any failures during the upgrade. There may
also be broken links on the website until the new one is done.

If you can not access the website and wish to be updated on the status
you can log in to the Vector Linux  irc channel at freenode #vectorlinux.

The irc channel is not very active if you ask a question please ask it
and do not logout until you receive your answer. If you logout after
asking the question you will not see the response from a member.

Thank you,

Bigpaws

 25 
 on: September 26, 2017, 07:44:30 pm 
Started by bigpaws - Last post by bigpaws
The forum is being upgraded over the next several days. There may be
outages as the updates are being done. The length of the outage maybe
from hours to days depending on any failures during the upgrade.

If you can not access the forum and wish to be updated on the status
you can log in to the Vector Linux  irc channel at freenode #vectorlinux.

The irc channel is not very active if you ask a question please ask it
and do not logout until you receive your answer. If you logout after
asking the question you will not see the response from a member.

Thank you,

Bigpaws

 26 
 on: September 21, 2017, 06:56:42 pm 
Started by black-clover - Last post by roarde
In your normal, working VL installation, take a look at /boot/initrd-tree. That's what's missing if you don't load an initrd. In VL's initrd, "init" is a shell script, not a binary. I think reading it (/boot/initrd-tree/init) might help. Hints: device creation and mounting.

If you're already trying to mount an initrd, check that it's properly built with all the necessary contents. Since you're producing a machine-specific OS, there are surely several things in VL's initrd you won't find necessary. Pay attention to how the bootloader (or your manual instructions) refer to the device holding the root filesystem.

Yes, this can be done without an initrd just as you want, but some parts of the initial, read-only mount of root will have to be very specific.

 27 
 on: September 21, 2017, 06:04:54 pm 
Started by black-clover - Last post by black-clover
Hello,

I used the kernel4.4.SlackBuild to build a custom kernel, which config-32 file I created using make localyesconfig.
Upon reboot, after the kernel begins to load, I got this error message:

Code: [Select]
No kernel modules found for Linux 4.4.80.
mount: mounting /dev/sda4 on /mnt failed: No such device.
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try to fix it. Type 'Exit' when things are done.
/bin/bash: can't access tty; job control turned off.

However the modules are all there in /lib/modules/4.4.80.
Is there a way to make the kernel find the modules or else anything I should change in the .config previous to building the kernel to avoid this error?

 28 
 on: September 19, 2017, 08:03:38 pm 
Started by black-clover - Last post by roarde
That "flash" of text is rc.vlinit being run again, as the exit from X is treated like a change of runlevel. Early on, rc.vlinit detects an executable rc.sysvinit and uses that instead of itself. Following that and the remainder of the chain it restarts will show you where that text comes from.

I can only think of two choices:
    Run a daemon like plymouth to "eat" the screen with pretty pictures, not releasing it for text output.
    Or send all of the text from any involved script to a logfile, and write out anything that would clear the screen.

 29 
 on: September 19, 2017, 04:13:09 pm 
Started by black-clover - Last post by black-clover
Hello,

I started a new thread so whomever is interested in setting uo Slim will find the information more easily.
I've got everything pretty much working editing two files (besides /etc/rc.d/rc.x).

In ~/.Xinitrc I put just:

Code: [Select]
exec $1
In /etc/slim.conf the lines I've changed are:

Code: [Select]
# Available sessions (first one is the default).
sessiondir /usr/share/xsessions/

and:

Code: [Select]
login_cmd           exec /bin/bash -login ~/.xinitrc %session
That besides setting the theme of choice.

As Roarde pointed out, Slim is very smooth passing from the login screen to the WM desktop, with Jwm too.
However I was curious if someone was able to get the same smooth transition on logout, without a flash of the black screen before returning to the login screen.



 30 
 on: September 19, 2017, 09:56:17 am 
Started by nightflier - Last post by nightflier
Ran into that error a couple times. It was not consistent and I never figured out what caused it. I would recommend doing this in a virtual machine so you can quickly and inexpensively test the images.

Pages: 1 2 [3] 4 5 ... 10