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 ... 4 5 [6] 7 8 ... 10
 51 
 on: September 11, 2017, 07:53:49 am 
Started by StrayBit - Last post by StrayBit
That seems to work.  I did try 4 different disks - the only one that didn't want to be read was the install disk.  As that was the first one tried, it might be just how I tried.

 52 
 on: September 10, 2017, 03:51:08 pm 
Started by black-clover - Last post by roarde
I think /etc/rc.d/rc.X is the only file that needs changing in order to start Lightdm, but I'm not sure about that. Thing is, you still need a working configuration of Lightdm itself. I don't know how Lightdm would choose which greeter to use, for example. That's part of figuring out its configuration.

As for how to modify rc.X, see if you can read it through, or at least chase down references to the various display managers and work from there. I do notice that if DISPLAY_MANAGER is not set, the order of trying display managers is kdm, gdm, wdm, xdm, and none. You'd want to insert ldm naturally, but also may want to change the order of those already there. Because of how VL implements various flavors, you actually do want kdm first. Then gdm, no doubt. Choose between ldm and xdm next, and tag on wdm after that for those waxing nostalgic. For bonus points, the NONE entry isn't really necessary, but further changes would be needed to leave it out.

You can include the new rc.X in any potential slackbuild, but you want to do that without forcing those installing the package to start using Lightdm right away. Take a look at how the .new files are handled in NetworkManager.SlackBuild. You have to look at the config() section that gets added to the doinst.sh to see it. What's missing there is a notice to take a look at the .new files, which would be printed on the screen when the package is installed and the doinst is run.

What you were asking about was the difference between /usr/bin and /usr/sbin. I actually think display managers belong in /usr/sbin, but the case can be made for /usr/bin as well. Make your choice. Adding /usr/sbin/lightdm is not a problem, just do it as the others (like /usr/bin/gdm) are done. If you want lightdm in /usr/bin instead, there's a ./configure option that would do that.

You probably should websearch "lightdm slackbuild" and take a look at some of the results. There are small differences in the way Slackware and VL implement PAM and the display managers, so read carefully.

 53 
 on: September 10, 2017, 01:55:44 pm 
Started by black-clover - Last post by black-clover
is /etc/rc.d/rc.x the only file I would need to edit in order to start lightdm?

Also, considering the binary the lightdm package installed is /usr/sbin/lightdm, how would I have to modify the entry in rc.x?

 54 
 on: September 10, 2017, 12:07:25 pm 
Started by StrayBit - Last post by roarde
I've never tried several filesystems for the same device from fstab. You might try
Code: [Select]
/dev/sr0    /media/cdrom udf,iso9660    user,noauto,unhide,utf8 0 0
That will have "bridge" type udf filesystems, which you've already been mounting as iso9660, mount as udf instead. You might reverse that behavior by swapping udf and iso9660. May also consider the option "noexec" there, and just mount manually when you want to run executables directly from disc.

 55 
 on: September 10, 2017, 11:31:02 am 
Started by StrayBit - Last post by StrayBit
That did it!  ;D ;D  Thank-you - Thank-you!
Should I put that into fstab in addition to the other entry?

 56 
 on: September 09, 2017, 01:06:49 pm 
Started by StrayBit - Last post by roarde
I feel like Columbo. There's just one more thing:
Code: [Select]
root# mount -t udf /dev/sr0 /media/memory
If that fails and cites io errors, I'm betting DRM. Remember to thank BSA.

 57 
 on: September 09, 2017, 07:43:21 am 
Started by StrayBit - Last post by StrayBit
Quote
vector://home/bruce
root:# dd if=/dev/sr0 of=GuessMe bs=1M count=2
dd: error reading '/dev/sr0': Input/output error
0+1 records in
0+1 records out
655360 bytes (655 kB) copied, 4.37813 s, 150 kB/s
vector://home/bruce
root:# file GuessMe
GuessMe: data
vector://home/bruce
root:# 1504966690953   addons.xpi-utils   WARN   Disabling foreign installed add-on modern@themes.mozilla.org in app-global

(seamonkey:13067): GLib-GIO-WARNING **: Failed to execute child process "update-desktop-database" (No such file or directory)
As you can see, I even tried to open Guesme with Seamonkey.
nightflier:  This machine only has VL.  I do know that the disk was recorded on a Win10 machine by a non-techie operator.  I've had the same issue with other disks that he has given me.  Usually, I just fire up my Win10 laptop to read it and copy the files to my Win7 laptop workhorse. 
Speaking of which, I have VL7.0 on the Win7 laptop.  Rebooted it just thinks this is an empty CD-R.  (so did Win7!)
I only use the Win10 once every 2 or 3 months!  It is not mine or I would put VL on it.

 58 
 on: September 09, 2017, 07:13:04 am 
Started by StrayBit - Last post by StrayBit
Might there be someone in SW Idaho that would be willing to visit me to get this resolved?
I've been fighting this since 7.1 and always run into a stone wall!

 59 
 on: September 06, 2017, 03:54:28 am 
Started by black-clover - Last post by Lyn
Edit or create /etc/modprobe.d/blacklist.conf file and add modules:
Code: [Select]
blacklist rt2800usb
blacklist rt2870sta
blacklist rt2860sta

This list came from here: https://superuser.com/questions/738096/how-to-install-mediatek-mt7610u-rt2860-driver
I found this information by searching the web. The list of modules to blacklist is probably not correct nor complete, I don't have that hardware and can not verify any of this information.  :(

Well that worked, thanks very helpful as ever, so posting this from VL 7.2

 60 
 on: September 05, 2017, 06:02:18 pm 
Started by black-clover - Last post by nightflier
Another thing to try:

Start without the USB dongle. Open a root terminal and issue command "tail -f /var/log/messages"

Plug in USB dongle and watch terminal output. Look for module names and any errors or warnings.

Pages: 1 ... 4 5 [6] 7 8 ... 10