Please login or register.

Login with username, password and session length
Advanced search  


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 ... 8 9 [10]
 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.

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

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?

 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.

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

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/


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.

 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.

 on: September 19, 2017, 05:37:37 am 
Started by nightflier - Last post by overthere
Any thoughts on how to boot the resulting iso on dvd?

With the above I get a boot prompt then a repeating error../boot/vesamenu.c32:not a com32r image
I did try /boot/vmlinuz- and other random guess

 do I need to edit the script first?

thanks for any

 on: September 16, 2017, 06:38:53 am 
Started by 93EXCivic - Last post by nightflier
My apologies, I just realized we were talking about two different animals.

The "Anaconda Python Data Science Platform" can be downloaded from their web site:

I tested the 32-bit Python 2.7 installer. After downloading it, I ran command "sh" and followed the prompts. It installed to ~/anaconda2. Executing ~/anaconda2/bin/anaconda-navigator brought up the UI.

Looks like an impressive package, hope this helps.

 on: September 16, 2017, 01:01:41 am 
Started by black-clover - Last post by black-clover
localmodconfig seems a great way to start.
 Thanks for the tip.

 on: September 15, 2017, 01:31:21 pm 
Started by black-clover - Last post by black-clover
thanks for your input.

Everything you say makes a lot of sense, as usual.
I just hacked away whatever I didn't need in the rc.x file and now Slim starts as default display manager in my project VL.
Since it is going to be the only DM installed I think that's ok.

It's nice to know that Slim allows a smooth transition into the desktop, which was the real issue in the first place.
I haven't had time  to deal with the graphic setup yet, since I want to deal with functionality first.
I copied Slim sample .xinitrc to ~/ and it starts Jwm all right.
I also tried

Code: [Select]
login_cmd       exec /bin/bash -login -c ". ~/.xinitrc || . /etc/X11/xinit/xinitrc"
In the slim.conf file but I get an error, it just can't execute login.

Slim seems to be a versatile DM, and I just got started, so there's quite a bit to learn about its functions.


 on: September 14, 2017, 10:20:34 pm 
Started by black-clover - Last post by roarde
The "vxdmset" mentioned was part of vasm originally, but the most recent vasm-legacy doesn't have it; it's unavailable unless one grabs the old source. Setting display manager manually by editing rc.X is a valid method. Why not list all of the display managers up front, comment each out, then uncomment the one used. A cheap way of documenting the possibly available display managers.

and so on.

The entries as you have them are fine, though it would be more consistent to add slim to the "for" list too, so it can be tested when DISPLAY_MANAGER isn't set, like the rest are.

Because of the chance of breaking someone's configured, working system (and a few other reasons), I'm guessing that an offer of a new official rc.X for 7.2 may not be accepted. It's easy enough for interested users to customize on their own while 7.2 is the current version.

The problem is in slim's configuration. If you installed slim from the command line, you were shown a note to check out /etc/ and /etc/logrotate.d/ If you haven't, rename each of those without the .new extension.

Now look at /etc/slim.conf:
Code: [Select]
login_cmd       exec /bin/bash -login ~/.xinitrc %sessionThat's only going to work when a user has an .xinitrc that looks very similar to the sample provided with the Slim source code. (It would be nice to have that copied to /usr/doc/slim-*/, but I'm not taking the time to do that.) Comment out that login_cmd line in slim.conf. There must be better ways to do this, but here's a working line so you can get on with what you're doing:
Code: [Select]
login_cmd       exec /bin/bash -login -c ". ~/.xinitrc || . /etc/X11/xinit/xinitrc"
A Bash shell is started with a fresh environment just as in a terminal login, except that what follows "-c" is executed: That shell tries to source a user's .xinitrc; should that fail -- usually because the user doesn't have one --, then /etc/X11/xinit/xinitrc is sourced. That's usually a link to the system's default desktop session, as distinguished from the default session that's just an xterm. A VL installation has that linking done by default.

Gdm, and I think Kdm, use a different method. The user's preferred session type is given in ~/.dmrc. I once chased down exactly how things end up there, but have forgotten. Can anyone remind me? Anyway, whatever Session= is pointing to, the desktop file /usr/share/xsessions/<Session>.desktop is read and its Exec= setting is executed, with "default" being  a special case.

A lot of different ways to go here, but the edit above to slim.conf will get you something working. The flash you mentioned elsewhere that GDM has isn't present for Slim. I resized my desktop wallpaper to fit my screen so that it wouldn't have to be resized on the fly. Icewmvmods is my DE. Because spacefm has a flash of its own and doesn't handle background transparency on startup, I disabled spacefm control of the desktop in the IceWM startup file, then set IceWM preferences to have icewmbg handle the background. Then I set both Slim and icewmbg to use the background made from the wallpaper above. As far as can be seen, all that happens after login is that the word "Login:" and the text-typing box disappear, leaving me in my desktop and looking at the same wallpaper, with no flash at all.

Nice find. I think we'd all forgotten about Slim.

Pages: 1 ... 8 9 [10]