VectorLinux

Cooking up the Treats => General Development => Topic started by: Joe1962 on October 28, 2006, 07:08:39 pm

Title: The VL-hot thread
Post by: Joe1962 on October 28, 2006, 07:08:39 pm
I'm starting a permanent thread for discussing the development of VL-hot here. For the recent arrivals, VL-hot is the external drive auto-mount system of Vector Linux since SOHO 5.1.
Title: Announcing VL-hot 0.3.7.0 for VL 5.8
Post by: Joe1962 on October 28, 2006, 07:17:31 pm
VL-hot 0.3.7.0 for VL 5.8 is out. Due to a problem on the repo, it is not yet available for downloading, hopefully it will be by tomorrow. It should be is in veclinux-current/testing/ at http://vectorlinux.osuosl.org/veclinux-current/testing/base/vl-hot-0.3.7.0-noarch-4vl58.tlz (http://vectorlinux.osuosl.org/veclinux-current/testing/base/vl-hot-0.3.7.0-noarch-4vl58.tlz). Please test so it can hopefully make it into the 5.8 Standard release.

Here's the changelog since the previous version:

2006-10-28    <joe1962@users.sourceforge.net>

   * Released 0.3.7.0

2006-10-27    <joe1962@users.sourceforge.net>

   * Disabled "read/write" radio button in vl-hot-config for NTFS (kernel rw mount not working).
   * Added radio button in vl-hot-config for NTFS-3G rw mounting.
   * Added NTFS3G variable in vl-hot.conf
   * Implemented NTFS-3G rw mounting in vl-hot_mount.

2006-10-08    <joe1962@users.sourceforge.net>

   * Fixed vl-hot-config tooltips for NTFS write permissions.

Edited by JohnB316 to add URL to the package download.
Title: Re: The VL-hot thread
Post by: Kocil on October 30, 2006, 11:51:31 am
Hi Joe.

Please take a look on the new Slack 11 directory structure.
You might find something interesting about /media.

I've downloaded that newest vl-hot, will test and report it soon.
Title: Re: The VL-hot thread
Post by: Joe1962 on November 09, 2006, 01:56:44 pm
My interpretation of the FHS hasn't changed. I believe /mnt is still the right place for external hard drives and pendrives. They are "removable devices", not "removable media". Removable media is when a device handles some kind of removable data medium, like CDROMs, zip drives, etc. The media is separate from the device in that case.

Quote
/media : Mount point for removeable media
Purpose

This directory contains subdirectories which are used as mount points for removeable media such as floppy disks, cdroms and zip disks.

Tip   Rationale
    

Historically there have been a number of other different places used to mount removeable media such as /cdrom, /mnt or /mnt/cdrom. Placing the mount points for all removeable media directly in the root directory would potentially result in a large number of extra directories in /. Although the use of subdirectories in /mnt as a mount point has recently been common, it conflicts with a much older tradition of using /mnt directly as a temporary mount point.
Specific Options

The following directories, or symbolic links to directories, must be in /media, if the corresponding subsystem is installed:

Directory   Description
floppy   Floppy drive (optional)
cdrom   CD-ROM drive (optional)
cdrecorder   CD writer (optional)
zip   Zip drive (optional)
Quote
/mnt : Mount point for a temporarily mounted filesystem
Purpose

This directory is provided so that the system administrator may temporarily mount a filesystem as needed. The content of this directory is a local issue and should not affect the manner in which any program is run.

This directory must not be used by installation programs: a suitable temporary directory not in use by the system must be used instead.
Title: Re: The VL-hot thread
Post by: Joe1962 on November 14, 2006, 07:18:31 pm
VL-hot 0.3.7.1 for VL 5.8 is out:
http://vectorlinux.osuosl.org/veclinux-current/packages/base/vl-hot-0.3.7.1-noarch-4vl58.tlz

Here's the changelog since the previous version:

Quote
2006-11-14    <joe1962@users.sourceforge.net>

   * Released 0.3.7.1

2006-11-14    <joe1962@users.sourceforge.net>

   * vl-hot_mount: checks for mounted mountpoint after mount, if not found does not create desktop icons.
   * vl-hot_umount: checks for mounted mountpoint after umount, if not found deletes unused mountpoint and desktop icons.
   * vl-hot_umount: fixed caller origin bug that left desktop icons when unplugging before unmount.

Title: Re: The VL-hot thread
Post by: Joe1962 on January 19, 2007, 04:36:53 pm
I want to move the development of vl-hot over to Google Code Projects, like vcpufreq. However, before I do so, I want to resolve the name issue. I need a new name for vl-hot, because it doesn't sound so cool, nor does it really express anything about it anymore. The "hot" part came from the beginning, when vl-hot was called from hotplug, but it was moved to udev a long time ago, and hotplug isn't even there anymore. I figure something more inline with the vasm module names and vcpufreq would be better. Any suggestions?
Title: Re: The VL-hot thread
Post by: Joe1962 on February 07, 2007, 12:12:00 am
vl-hot 1.0.1 has been released. A package is now in the 5.8 testing/ repo.

Changelog:
Code: [Select]
2007-02-07    <joe1962@users.sourceforge.net>

* Released 1.0.1

2007-02-07    <joe1962@users.sourceforge.net>

* Replaced notification sounds.
* Updated vl-hot-config with Notification tab.
* Changed to Aska's new vl-hot-png icon.

2007-02-05    <joe1962@users.sourceforge.net>

* Moved desktop notification so it happens on a per partition basis.

2007-01-15    <joe1962@users.sourceforge.net>

* Added & to return from call to sudo for desktop notification.

2007-01-15    <joe1962@users.sourceforge.net>

* Added desktop notification for unmount and some errors.


Check the package announcement thread for more info:
http://www.vectorlinux.com/forum2/index.php?topic=1919.msg11059#msg11059
Title: vl-hot 1.01 problem
Post by: Brad on March 07, 2007, 05:09:51 pm
My apologies for reviving an old thread but this seems the appropriate spot.  Just installed 5.8 on a Z505R laptop, compiled out the fluff using 2.6.20, udev only, pcmciautils only, no hal/hotplug,  using vl-hot 1.01.  I have a Sandisk 6-in-1 PCMCIA adapter which, when used with a 32M memorystick, gives the above error.  It works fine with a 128M SD card and a separate CF card adapter.

From dmesg |tail:
Code: [Select]
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia: registering new device pcmcia0.0
Probing IDE interface ide2...
hde: MEMORYSTICK, CFA DISK drive
ide2 at 0x100-0x107,0x10e on irq 3
hde: max request size: 128KiB
hde: 63424 sectors (32 MB) w/1KiB Cache, CHS=991/4/16
 hde: hde1
ide-cs: hde: Vpp = 0.0
FAT: Unrecognized mount option "iocharset=iso8859-15" or missing value

from /var/log/messages:
Code: [Select]
Mar  7 17:50:54 VZ505R kernel: pccard: PCMCIA card inserted into slot 0
Mar  7 17:50:54 VZ505R kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Mar  7 17:50:54 VZ505R kernel: pcmcia: registering new device pcmcia0.0
Mar  7 17:50:56 VZ505R kernel: hde: max request size: 128KiB
Mar  7 17:50:56 VZ505R kernel: hde: 63424 sectors (32 MB) w/1KiB Cache, CHS=991/4/16
Mar  7 17:50:56 VZ505R kernel:  hde: hde1
Mar  7 17:50:56 VZ505R kernel: ide-cs: hde: Vpp = 0.0
Mar  7 17:50:56 VZ505R vl-hot_mount: Starting vl-hot_mount...
Mar  7 17:50:56 VZ505R vl-hot_mount: devname: hde
Mar  7 17:50:56 VZ505R vl-hot_mount: volname: vol
Mar  7 17:50:56 VZ505R vl-hot_mount: Mounting /dev/vl-hot/hde on /mnt/vl-hot/hde/vol
Mar  7 17:50:56 VZ505R vl-hot_mount: /dev/vl-hot/hde not mountable (MBR) ...
Mar  7 17:50:56 VZ505R vl-hot_mount: Finishing vl-hot_mount...
Mar  7 17:50:56 VZ505R vl-hot_mount: Starting vl-hot_mount...
Mar  7 17:50:56 VZ505R vl-hot_mount: devname: hde1
Mar  7 17:50:56 VZ505R vl-hot_mount: volname: vol1
Mar  7 17:50:56 VZ505R vl-hot_mount: Mounting /dev/vl-hot/hde1 on /mnt/vl-hot/hde/vol1
Mar  7 17:50:56 VZ505R vl-hot_mount: /dev/vl-hot/hde1 Filesystem is FAT12
Mar  7 17:50:56 VZ505R vl-hot_mount: mounting FAT12 filesystem: /dev/vl-hot/hde1 on /mnt/vl-hot/hde/vol1
Mar  7 17:50:56 VZ505R vl-hot_mount: mounting /dev/vl-hot/hde1 failed, not showing desktop icon for /mnt/vl-hot/hde/vol1
Mar  7 17:50:56 VZ505R vl-hot_mount: Finishing vl-hot_mount...

The camera formats these cards like this but I will reformat it to FAT16 and see if the camera can work with it.  I wanted to mention that the above poster's situation is not isolated.  A separate issue which may require a new thread if you desire is that vl-hot does not recognize the Belkin's efilm Pro cardbus 32 CF adapter.  Also, I'm trying to sort out why the built-in memory stick adapter is unusable with driveready seekcomplete errors though this is most likely a separate hardware issue not unique to VL given what I am reading on the net.

Brad
Title: Re: vl-hot 1.01 problem
Post by: JohnB316 on March 07, 2007, 07:35:27 pm
Brad,

I split your post into its own topic, mainly because you appended it to a version of vl-hot that is very deprecated. Also, you're more likely to get a better response if your post isn't buried in an irrelevant thread.

Cheers,
John
Title: Re: The VL-hot thread
Post by: Joe1962 on March 07, 2007, 08:27:22 pm
Merged this to the vl-hot thread, where I'd prefer to discuss the issues. I actually wanted to merge part of the thread where this last was originally posted to, beginning with the 5.8 install, but it was older than the vl-hot thread, so it would have ended up on top.
Title: Re: The VL-hot thread
Post by: Joe1962 on June 13, 2007, 05:55:52 pm
Finally got vl-hot 1.0.3 done and uploaded to the 5.8 patches repo. This has hardwired codepage and charset dropdowns, as it is no longer possible to parse the modules at runtime. As of SOHO 5.8 final, they are built-in to the kernel.

This also has the FAT12 mount options fix which came out in 1.0.2, but it seems that package lost its way and never made it to the repo... :-[

http://www.vectorlinux.com/forum2/index.php?topic=3343.msg20887#msg20887
Title: Re: The VL-hot thread
Post by: caitlyn on June 13, 2007, 08:20:52 pm
I posted this in the package announcement thread but decided to post it here to in case anyone ran into trouble.  I tried to fetch this via a slapt-get --upgrade with less than satisfactory results.  It seems some dependencies haven't made it to the patches repository yet:

Quote
root:# slapt-get --upgrade
Reading Package Lists... Done
Excluding vl-hot, use --ignore-dep to override
The following packages have unmet dependencies:
  vl-hot: Depends: gambas-runtime >= 1.0.18 | gambas >= 1.0.18
The following packages have been EXCLUDED:
  vl-hot kernel-headers
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Hopefully this is just a matter of moving packages from testing to patches.

Regards,
Cait
Title: Re: The VL-hot thread
Post by: Joe1962 on June 13, 2007, 08:34:24 pm
Yes, our package testers seem to be slowing down... ;)
Title: Re: The VL-hot thread
Post by: caitlyn on June 14, 2007, 08:22:09 am
Joe, I had noticed.  Some aspell dictionaries I submitted >2 months ago, about the simplest packages in the world, are still in testing.  I figure most if not all of us are volunteers and they'll get to it when time permits.

Anyway, thank you for taking care of this.  I do have an old 64MB FAT12 memory card.  I don't know when the last time I used it was but it's good to know I can if I want to.

-Cait
Title: Re: The VL-hot thread
Post by: Joe1962 on June 14, 2007, 08:40:07 am
I do have an old 64MB FAT12 memory card.
Then would you please confirm that the fix works?... ;D
Title: Re: The VL-hot thread
Post by: caitlyn on June 14, 2007, 01:07:43 pm
Hi, Joe,

I'll find some time in the evening or over the weekend.  I have to dig it out from wherever it is -- fortunately I think I know where.

-Cait
Title: 1.03 not quite there with FAT-12
Post by: caitlyn on June 16, 2007, 11:38:10 am
Hi, Joe,

Sorry to be the bearer of not so good news but---

1.  Inserted old memory card & got an appropriate icon
2.  I can read from and write to the card

That's all good.

When I tried to unmount (right mouse click on icon) I get:

Quote
[Unable to unmount "64M Volume":

A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error name "(unset)" destination "org.freedesktop.Hal")/quote]

It appears that I'd have to be root to unmount.

-Cait
Title: Re: The VL-hot thread
Post by: Joe1962 on June 16, 2007, 11:43:36 am
That is not the vl-hot icon then. It does not use hal at all. That must be hal showing that icon. If so, you should get 2 icons on KDE and 3 on XFCE, the hal icon and the vl-hot icon, plus the vl-hot unmount icon which is exclusive for xfce.
Title: Re: The VL-hot thread
Post by: easuter on June 16, 2007, 11:56:37 am
Caitlyn, are you using GNOME by any chance?
Title: Re: The VL-hot thread
Post by: caitlyn on June 16, 2007, 12:19:39 pm
No, Xfce 4.4.0.  I should point out the 4.4.0 was built with hal if I remember correctly.

OK, the VL-hot isn't giving me an icon at all.

-Cait
Title: Re: The VL-hot thread
Post by: caitlyn on June 16, 2007, 12:25:07 pm
OK, I unmounted as root and the icon remained.  I removed the card and it disappeared.

I reinserted the card and got three icons:  two from vl-hot plus the one aforementioned icon.

The vl-hot unmount icon works correctly.  (Joe, when did you add audio cues?)  The hal icon remains but the two vl-hot icons disappear.  I remove the card and the last icon disappears.  I reinsert the card and I get three icons.

The card was inserted when I booted up this time.  It seems vl-hot doesn't provide icons for items that were in place at boot.

-Cait
Title: Re: The VL-hot thread
Post by: easuter on June 16, 2007, 12:35:17 pm
I think an Xfce build with HAL disabled might be in order ;D

Hal is probably interfering with VL-Hot's work.
Honestly, I don't know why the Xfce dev team shoved Hal support into Xfce 4.4 at the last minute like they did...  :-X

Title: Re: The VL-hot thread
Post by: Joe1962 on June 16, 2007, 01:06:10 pm
Joe, when did you add audio cues?
Hehe, a few versions ago, and you should also get a nice popup message if you have libnotify and notification-daemon-xfce. Had to find some use for dbus, right?... ;D

The card was inserted when I booted up this time.  It seems vl-hot doesn't provide icons for items that were in place at boot.
It should, and it works for me. I am using the non-hal xfce build however, so it might conceivably be interference from hal.

I think an Xfce build with HAL disabled might be in order ;D
There always was one... I strongly insisted... ;D

http://vectorlinux.osuosl.org/veclinux-5.8/fixes/xfce-4.4.0-no-hal-i586-4vl58.tlz
http://vectorlinux.osuosl.org/veclinux-5.8/fixes/Thunar-0.8.0-no-hal-i586-4vl58.tlz
http://vectorlinux.osuosl.org/veclinux-5.8/fixes/xfprint-4.4.0-no-hal-i586-3vl58.tlz

Vec7 mentioned that 4.4.1 probably won't build without hal though. We should give it a good try anyway, I guess.
Title: Re: The VL-hot thread
Post by: caitlyn on June 16, 2007, 01:38:20 pm
Is someone working on building Xfce 4.4.1?  I was going to try it but I don't want to duplicate efforts.

-Cait
Title: Re: The VL-hot thread
Post by: Joe1962 on June 16, 2007, 01:39:40 pm
Vec7 built it.


EDIT: OK, doesn't seem to be in the 5.8 repo, but it is in the VL6 dev isos. So maybe a 5.8 package isn't done yet?
Title: Re: The VL-hot thread
Post by: GrannyGeek on June 18, 2007, 10:02:52 pm
I installed the no-HAL XFce 4.4.0 plus Thunar and xfprint on my test machine today. What's different compared with the versions that come with VL 5.8 Standard Gold?

In the spirit of "if it ain't broke, don't fix it" I won't install 4.4.0 on my other two systems unless there is some advantage I don't know about.
--GrannyGeek
Title: Re: The VL-hot thread
Post by: Joe1962 on June 18, 2007, 10:08:24 pm
What's different compared with the versions that come with VL 5.8 Standard Gold?
No dependency on the hal demon.
Title: Re: The VL-hot thread
Post by: The Headacher on June 19, 2007, 02:10:58 am
What's different compared with the versions that come with VL 5.8 Standard Gold?
No dependency on the hal demon.
The version that was on 5.8 gold didn't (doesn't) depend on the Hell-demon either, that was a last minute addition to Xfce 4.4.0 IIRC.
I'm not sure what the advantages of the newer versions are over the version in 5.8 standard.
Title: Re: The VL-hot thread
Post by: Joe1962 on June 19, 2007, 04:01:11 am
What's different compared with the versions that come with VL 5.8 Standard Gold?
No dependency on the hal demon.
The version that was on 5.8 gold didn't (doesn't) depend on the Hell-demon either,
Indeed not, but it was the last release candidate, not the final. "Hell-demon", nice word-play... ;D

that was a last minute addition to Xfce 4.4.0 IIRC.
Yes, because it was somewhat hard to build without hal, IIRC.

I'm not sure what the advantages of the newer versions are over the version in 5.8 standard.
If you mean hal, neither am I... ::) but it is the final and had some bugs removed, I guess.
Title: Re: The VL-hot thread
Post by: GrannyGeek on June 19, 2007, 07:09:16 pm
If I encounter a bug, I'll install no-HAL XFce 4.4 on my other two computers. Until then, I think I'll stick with what I have unless I notice something on XFce 4.4 on the one desktop that's not in the older version included with 5.8 Standard Gold.

Either way, it seems no harm would be done.
--GrannyGeek
Title: Re: The VL-hot thread
Post by: caitlyn on June 22, 2007, 12:19:34 pm
There are many bugs in Xfce 4.3.99rc2 which is why I went to 4.4.0.  The most common one is that trying to change the icon theme in 4.3.99 will crash Xfce and leave some config files in an unusable state which leaves you without a working Xfce desktop.  There are also issues with xfmedia under 4.3.99rc2 which will cause slowness, stutter in playback, etc...

-Cait
Title: Re: The VL-hot thread
Post by: easuter on June 26, 2007, 03:08:47 am
Joe1962, the vl-hot 1.0.3 FAT12 mounting isn't working :(

I managed to get my parent's camera-card today (FAT 12 formatted by the camera) to test with, and this is my dmesg and /var/log/messages output:

dmesg

Code: [Select]
usb 4-1: new high speed USB device using ehci_hcd and address 7
usb 4-1: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
scsi 6:0:0:0: Direct-Access     F Generi 6 IN  HS-CF      1.97 PQ: 0 ANSI: 0
sd 6:0:0:0: Attached scsi removable disk sda
sd 6:0:0:0: Attached scsi generic sg0 type 0
scsi 6:0:0:1: Direct-Access     F Generi 6 IN  HS-MS      1.97 PQ: 0 ANSI: 0
sd 6:0:0:1: Attached scsi removable disk sdb
sd 6:0:0:1: Attached scsi generic sg1 type 0
scsi 6:0:0:2: Direct-Access     F Generi 6 IN  HS-SM      1.97 PQ: 0 ANSI: 0
sd 6:0:0:2: Attached scsi removable disk sdc
sd 6:0:0:2: Attached scsi generic sg2 type 0
scsi 6:0:0:3: Direct-Access     F Generi 6 IN  HS-SD/MMC  1.97 PQ: 0 ANSI: 0
SCSI device sdd: 125440 512-byte hdwr sectors (64 MB)
sdd: Write Protect is off
sdd: Mode Sense: 03 00 00 00
sdd: assuming drive cache: write through
SCSI device sdd: 125440 512-byte hdwr sectors (64 MB)
sdd: Write Protect is off
sdd: Mode Sense: 03 00 00 00
sdd: assuming drive cache: write through
 sdd: sdd1
sd 6:0:0:3: Attached scsi removable disk sdd
sd 6:0:0:3: Attached scsi generic sg3 type 0
usb-storage: device scan complete

tail -f /var/log/messages

Code: [Select]
Jun 26 10:01:04 vector kernel: usb 4-1: new high speed USB device using ehci_hcd and address 7
Jun 26 10:01:04 vector kernel: usb 4-1: configuration #1 chosen from 1 choice
Jun 26 10:01:04 vector kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Jun 26 10:01:09 vector kernel: scsi 6:0:0:0: Direct-Access     F Generi 6 IN  HS-CF      1.97 PQ: 0 ANSI: 0
Jun 26 10:01:09 vector kernel: sd 6:0:0:0: Attached scsi removable disk sda
Jun 26 10:01:09 vector kernel: sd 6:0:0:0: Attached scsi generic sg0 type 0
Jun 26 10:01:09 vector kernel: scsi 6:0:0:1: Direct-Access     F Generi 6 IN  HS-MS      1.97 PQ: 0 ANSI: 0
Jun 26 10:01:09 vector kernel: sd 6:0:0:1: Attached scsi removable disk sdb
Jun 26 10:01:09 vector kernel: sd 6:0:0:1: Attached scsi generic sg1 type 0
Jun 26 10:01:09 vector kernel: scsi 6:0:0:2: Direct-Access     F Generi 6 IN  HS-SM      1.97 PQ: 0 ANSI: 0
Jun 26 10:01:09 vector kernel: sd 6:0:0:2: Attached scsi removable disk sdc
Jun 26 10:01:09 vector kernel: sd 6:0:0:2: Attached scsi generic sg2 type 0
Jun 26 10:01:09 vector kernel: scsi 6:0:0:3: Direct-Access     F Generi 6 IN  HS-SD/MMC  1.97 PQ: 0 ANSI: 0
Jun 26 10:01:09 vector kernel: SCSI device sdd: 125440 512-byte hdwr sectors (64 MB)
Jun 26 10:01:09 vector kernel: sdd: Write Protect is off
Jun 26 10:01:09 vector kernel: SCSI device sdd: 125440 512-byte hdwr sectors (64 MB)
Jun 26 10:01:09 vector kernel: sdd: Write Protect is off
Jun 26 10:01:09 vector kernel:  sdd: sdd1
Jun 26 10:01:09 vector kernel: sd 6:0:0:3: Attached scsi removable disk sdd
Jun 26 10:01:09 vector kernel: sd 6:0:0:3: Attached scsi generic sg3 type 0
Jun 26 10:01:10 vector vl-hot_mount: Starting vl-hot_mount...
Jun 26 10:01:10 vector vl-hot_mount: devname: sdc
Jun 26 10:01:10 vector vl-hot_mount: volname: vol
Jun 26 10:01:10 vector vl-hot_mount: Mounting /dev/vl-hot/sdc on /mnt/vl-hot/sdc/vol
Jun 26 10:01:10 vector vl-hot_mount: Starting vl-hot_mount...
Jun 26 10:01:10 vector vl-hot_mount: devname: sda
Jun 26 10:01:10 vector vl-hot_mount: volname: vol
Jun 26 10:01:10 vector vl-hot_mount: Mounting /dev/vl-hot/sda on /mnt/vl-hot/sda/vol
Jun 26 10:01:10 vector vl-hot_mount: Starting vl-hot_mount...
Jun 26 10:01:10 vector vl-hot_mount: devname: sdb
Jun 26 10:01:10 vector vl-hot_mount: volname: vol
Jun 26 10:01:10 vector vl-hot_mount: Mounting /dev/vl-hot/sdb on /mnt/vl-hot/sdb/vol
Jun 26 10:01:10 vector vl-hot_mount: Starting vl-hot_mount...
Jun 26 10:01:10 vector vl-hot_mount: devname: sdd
Jun 26 10:01:10 vector vl-hot_mount: volname: vol
Jun 26 10:01:10 vector vl-hot_mount: Mounting /dev/vl-hot/sdd on /mnt/vl-hot/sdd/vol
Jun 26 10:01:11 vector vl-hot_mount: /dev/vl-hot/sdc not mountable...
Jun 26 10:01:11 vector vl-hot_mount: Finishing vl-hot_mount...
Jun 26 10:01:11 vector vl-hot_mount: /dev/vl-hot/sda not mountable...
Jun 26 10:01:11 vector vl-hot_mount: Finishing vl-hot_mount...
Jun 26 10:01:11 vector vl-hot_mount: /dev/vl-hot/sdb not mountable...
Jun 26 10:01:11 vector vl-hot_mount: Finishing vl-hot_mount...
Jun 26 10:01:11 vector vl-hot_mount: /dev/vl-hot/sdd not mountable (MBR) ...
Jun 26 10:01:11 vector vl-hot_mount: Finishing vl-hot_mount...
Jun 26 10:01:11 vector vl-hot_mount: Starting vl-hot_mount...
Jun 26 10:01:11 vector vl-hot_mount: devname: sdd1
Jun 26 10:01:11 vector vl-hot_mount: volname: vol1
Jun 26 10:01:11 vector vl-hot_mount: Mounting /dev/vl-hot/sdd1 on /mnt/vl-hot/sdd/vol1
Jun 26 10:01:11 vector vl-hot_mount: /dev/vl-hot/sdd1 Filesystem is FAT12
Jun 26 10:01:11 vector vl-hot_mount: mounting FAT12 filesystem: /dev/vl-hot/sdd1 on /mnt/vl-hot/sdd/vol1
Jun 26 10:01:11 vector vl-hot_mount: mounting /dev/vl-hot/sdd1 failed, not showing desktop icon for /mnt/vl-hot/sdd/vol1
Jun 26 10:01:11 vector vl-hot_mount: Finishing vl-hot_mount...

I'm not getting codepage errors like I used to in vl-hot 1.0.2 and lower, but it still doesn't mount.
Also, when vl-hot 1.0.3 fails to mount the device, it leaves an empty sdd/vol1 directory in /mnt/vl-hot.

The card mounts fine manually, with no special arguments to mount.
Title: Re: The VL-hot thread
Post by: Joe1962 on June 26, 2007, 08:34:11 am
Thanks for testing this easuter, I had no card small enough for FAT12. Turns out I missed the ending quote after removing the codepage stuff from the FAT12 part. Can you download and replace a fixed (I hope) vl-hot_functions to test? I don't want to roll another version till I'm sure this time.

http://jjrweb.byethost.com/vl/dev/vl-hot/downloads/development/vl-hot_functions

It goes in /lib/udev and has to be executable, owned by root and permissions set to 755.
Title: Re: The VL-hot thread
Post by: easuter on June 26, 2007, 02:40:52 pm
I downloaded the file directly into /lib/udev, set the permissions, and its working great now. :)
Title: Re: The VL-hot thread
Post by: Joe1962 on June 26, 2007, 02:53:48 pm
Great, thanks! I should have an updated package up tonight.
Title: Re: The VL-hot thread
Post by: Joe1962 on June 27, 2007, 01:40:28 pm
Package is up: http://vectorlinux.osuosl.org/veclinux-5.8/patches/base/vl-hot-1.0.4-noarch-1vl58.tlz
Title: Re: The VL-hot thread
Post by: caitlyn on September 13, 2007, 01:30:19 pm
One suggestion for whatever version ends up in VL 6.0:

/mnt/vl-hot/sdc/vol1 is long and not terribly intuitive. 

Other distros (Wolvix is a great example) use HAL but keep the path simple, something like:
 /media/disk-1

Any chance the vl-hot path can be simplified?
Title: Re: The VL-hot thread
Post by: Joe1962 on September 13, 2007, 04:31:02 pm
Caitlyn, I posted once asking for suggestions on this, but I can't find that post now. Anyway, I'm open as long as it meets 2 criteria:

- under /mnt, not /media (at least until the FHS changes on this).
- the naming convention can properly handle multiple partitions in an external HDD.

Just to explain things a bit, the vl-hot subdir was conceived as a way to keep things organized, that is to separate them from mounts that were done manually or via /etc/fstab. Also it could be used linked by a desktop icon, which would open up a sort of "External Drives Neighborhood"... ;)
Title: Re: The VL-hot thread
Post by: Joe1962 on May 27, 2008, 08:59:12 pm
Well, after a long time I finally got to hacking away on vl-hot again... ;D

The bad news is I can't use my Google Projects svn or filehosting anymore ("You are accessing this page from a forbidden country"), and my free website host has done something so files can't be directly linked to for download... ::)

The good news is, I have an alpha version of what will hopefully be vl-hot 2 for you brave testers to muck about with, and I put up a package on Hyperupload (link below)... ;D

http://hyperupload.com/download/027000ed89/vl-hot-1.9.0-noarch-1vl59.tlz.html

What's new:

Caveats:

TODO:

HOWTO set up a device in vl-hot-names.conf:

OK, so testers are essential, coders welcome... with a little luck we can get this into VL 5.9 Light final!!!
Title: Re: The VL-hot thread
Post by: nightflier on May 27, 2008, 09:13:46 pm
Great! I will be testing this one out on Light.  8)
Title: Re: The VL-hot thread
Post by: Joe1962 on May 27, 2008, 09:18:09 pm
Now that you mention that, I only tested on Standard, but I expect it will work on Light too.

EDIT: also only tested on FAT16, FAT32 and NTFS devices so far.
Title: Re: The VL-hot thread
Post by: rbistolfi on May 27, 2008, 09:23:45 pm
Wow Joe, my favorite software will have another version, awesome!
Can we post feature requests here? ;D

The new features are exciting, you have a tester here :)

PS:
Quote
The bad news is I can't use my Google Projects svn or filehosting anymore ("You are accessing this page from a forbidden country"), and my free website host has done something so files can't be directly linked to for download...

Unbelievable  >:(
Title: Re: The VL-hot thread
Post by: uelsk8s on May 27, 2008, 09:25:02 pm
I am testing it on soho now.
the launcher for vl-hot-config doesnt work here.
the vl-hot-config window says version 1.0.4
everything else seems good so far
Title: Re: The VL-hot thread
Post by: Joe1962 on May 27, 2008, 09:37:01 pm
Can we post feature requests here? ;D
Of course! I always left this thread sticky for that reason.

  • An option to run custom commands on mounting and umounting
Actually I was only thinking of an option to open your fav filemanager window on mount, you went much further. Regarding on unmount, I've tried to chain exec commands with && in the unmount desktop icon, but it doesn't work. So it would mean redesigning the exec logic to call a script instead. However, it wouldn't be too complicated to do something on mount. Let me think about it, but only after the new stuff is stable and tested.

  • Nothing else, SMF adds two li tags
So delete one line, lol. I had to copy/paste lots of li tags for my first post above... ;D


I am testing it on soho now.
the launcher for vl-hot-config doesnt work here.
Strange, I didn't change any of the launchers.

the vl-hot-config window says version 1.0.4
Yes, it's still 1.0.4, haven't got around to it yet, still working on the bash part of vl-hot.
Title: Re: The VL-hot thread
Post by: rbistolfi on May 27, 2008, 10:24:07 pm
Actually I was only thinking of an option to open your fav filemanager window on mount, you went much further. Regarding on unmount, I've tried to chain exec commands with && in the unmount desktop icon, but it doesn't work. So it would mean redesigning the exec logic to call a script instead. However, it wouldn't be too complicated to do something on mount. Let me think about it, but only after the new stuff is stable and tested.

Sure the fm will be handy for many ppl. I thought about that because I use awesome window manager which doesn't do icons, so I mod vl-hot functions to show the vl-hot icon in the awesome statusbar. Well mod is too much, I just append one line for mounting and one line for umounting (so the icon disappears). Then I started to think, people may want to launch file managers or gqview for photos in a sd, maybe a player for listening music from a mp3 player, etc.

Quote
Let me think about it, but only after the new stuff is stable and tested.

Of course...
 
Quote
So delete one line, lol. I had to copy/paste lots of li tags for my first post above... ;D

I know I just love stupid jokes ;D

Quote
I am testing it on soho now.
the launcher for vl-hot-config doesnt work here.
Strange, I didn't change any of the launchers.

Quote from: uelsk8s on May 27, 2008, 11:25:02 PM
the vl-hot-config window says version 1.0.4
Yes, it's still 1.0.4, haven't got around to it yet, still working on the bash part of vl-hot.

It is working fine here, maybe because I used upgradepkg? May be you have some old files still there.
Title: Re: The VL-hot thread
Post by: rbistolfi on May 29, 2008, 05:48:52 pm
I get this while running vlh-umount:

Code: [Select]
rbistolfi@vector [ ~/iso ] %vlh-umount
/lib/udev/vl-hot_umount: line 49: [: missing `]'
rmdir: script: No such file or directory

It mounted my pendrive and sd cards successfully so far :)
Title: Re: The VL-hot thread
Post by: Joe1962 on June 02, 2008, 01:01:35 pm
I can't see anything in line 49 of vl-hot_umount that could cause that. How accurate is the linenumber reported by bash, I wonder? Have you changed the default mountbase by any chance?
Title: Re: The VL-hot thread
Post by: rbistolfi on June 02, 2008, 02:03:34 pm
I can't see anything in line 49 of vl-hot_umount that could cause that. How accurate is the linenumber reported by bash, I wonder? Have you changed the default mountbase by any chance?

Yeah, I did take a look at the moment and the line numbering didn't make sense to me also. IIRC there is a well formed "if" there. The settings are all defaults. I will look deeper when I get home, I wonder if there is a tool to execute the script line by line :)
Title: Re: The VL-hot thread
Post by: Joe1962 on June 03, 2008, 06:28:14 am
As stated before, I did give vlh-umount a quick test with 1 pendrive and it worked, but it hasn't been updated yet WRT the new functionality and I somewhat expected breakage.
Title: Re: The VL-hot thread
Post by: rbistolfi on June 03, 2008, 07:09:04 am
No problem Joe I am glad to test it. Line 49 is about feedback and probably a minor problem but not causing umount to fail. I will keep sniffing. rmdir is taking the "script" value as a dir to remove (rmdir: script: No such file or directory), instead as $SOURCE from /usr/bin/vlh-umount. Looks like there is a problem where the device name is stated.
Title: Re: The VL-hot thread
Post by: M0E-lnx on June 03, 2008, 07:58:58 am
@ Joe1962

Have you switched to gambas2 or still developing it under G1?
Title: Re: The VL-hot thread
Post by: Joe1962 on June 03, 2008, 08:10:51 am
I am just "bashing" away for the moment, working on the "back-end" so to speak. Work on vl-hot-config comes next and I do intend to port it to 2.x, but maybe not till after all the new functions are implemented and a release made.
Title: Re: The VL-hot thread
Post by: caitlyn on June 12, 2008, 02:58:39 pm
Fair warning for Joe1962:

As you know "green computing" is a hot topic now and VL-Hot, as a replacement for HAL, definitely fits in as it doesn't constantly poll and therefore uses less energy and improves performance on low end systems.  I'm planning on doing an article on VL-Hot for O'Reilly News and I will be suggesting that other distros consider incorporating it.

You've been warned...  :)
Title: Re: The VL-hot thread
Post by: Joe1962 on June 12, 2008, 03:32:50 pm
You've been warned...  :)


Wow!!!    :o ;D :o
Title: Re: The VL-hot thread
Post by: M0E-lnx on June 12, 2008, 07:56:09 pm
@ Joe1962

As a suggestion, could you add a feature in the config to allow for user-defined / prefered filemanager ?
I like pcmanfm, but vl-hot insists in PathFinder here for some reason...

Just a thought... it'd be kool
Title: Re: The VL-hot thread
Post by: Joe1962 on June 14, 2008, 10:35:05 am
Actually, the vl-hot desktop icon does not define a filemanager at all. It defines a URL like this:

Code: [Select]
URL=file://$MOUNTPOINT
So, theoretically, all you need to do is change the default handler for such a URL type on your system.
Title: Re: The VL-hot thread
Post by: M0E-lnx on June 14, 2008, 12:42:38 pm
huh!... I wonder how one goes about doing that
Title: Re: The VL-hot thread
Post by: Joe1962 on June 14, 2008, 12:53:37 pm
Well, I'm not exactly sure right now, which is probably why I didn't say how... ;D
Title: Re: The VL-hot thread
Post by: Joe1962 on August 14, 2008, 10:56:21 pm
huh!... I wonder how one goes about doing that
A little help here please... anybody? I just don't have the time to investigate this further. Does this have anything to do with mimetypes?

On to another subject, those on the vectorlinux-devel list have been getting updates on the latest vl-hot and vl-hot-config code, it's time to paste some of that here too (it's a bit long-winded, sorry about that)... :)

Quote
A while back, I lost my working copy of vl-hot 1.0.4 and the backups
were corrupted. No problem I thought, I'll checkout from the svn. But
I have not been able to access googlecode for quite some time now, so
I sshed into uel s box and tried from there. Well, it turns out that
the googlecode svn of vl-hot has somehow been reset to a blank repo,
grrr....

I had already recovered the bash part of vl-hot from the distro, of
course, and this was the base for developing the new 2.0 version. I
was less fortunate with vl-hot-config, which is compiled gambas code,
I only have a much older version available, but there were a lot of
changes towards 1.0.4.

So: does anybody have the source code for vl-hot-config 1.0.4? If so,
please send it to me, as vl-hot 2.0 is pretty much done and ready for
testing, but it needs a matching vl-hot-config, of course.

Quote
I set up a new project on Berlios a couple of months ago, when I
started having trouble accesing googlecode, but I haven't uploaded any
code yet, while trying to fing the vl-hot-config source. Berlios works
pretty fast for me here and I believe they have a long and stable
history hosting open source projects. I didn't try SourceForge as it
is way to slow from here.

Quote
Ok, here is a package of vl-hot-1.9.9 (2.0 beta). I've done a lot of
testing with 2 pendrives, but this is still a beta until others can
test it too. I will do some more testing with an external HDD with
multiple partitions tonight.

http://hyperupload.com/download/022fd59c43/vl-hot-1.9.9-noarch-1vl59.tlz.html

Mount point naming has 3 levels of priority:
1- from /etc/udev/vl-hot_names.conf, if the serial matches a definition
2- from the partition label, if any
3- if none of the above, the default name is "vl-hot" (this might change)

If a second drive/partition has the same name, vl-hot_mount adds
consecutive numbers to the mount point.

NOTE: due to what I explained before, there is no vl-hot-config in
this package, you need to edit /etc/udev/vl-hot.conf manually.

Quote
Notice that to get the nice vl-hot_umount notification popup on XFCE,
you need to install libnotify, notification-daemon-xfce and libsexy.
Still need to work on the KDE notifications, as they use a different
engine.

Quote
Ok, I've mostly managed to update vl-hot-config from an old version.
It even has a (still somewhat crude) custom mountpoints editor, so you
can define a permanent custom fixed mountpoint for a particular
pendrive, etc.

Only one thing to do yet before a beta: In vl-hot-config 1.0.4, I
hardwired the charsets and codepages dropdown lists, because they
became built-in to the kernel, whereas previously, they would be read
from the modules at runtime. However, I would like to find a nice
proper way to get the available charsets and codepages at runtime,
before I go and hardcode them again (I've lost the friggin' lists too,
along with the 1.0.4 source code, lol). So... any ideas?

Quote
I just imported the first code to the Berlios vl-hot project, at
version 1.9.9, which is more or less 2.0 Beta. As stated before,
vl-hot-config desn't do the codepages and charsets yet, hope to get to
that by Monday at latest.

Link to the project page: http://developer.berlios.de/projects/vl-hot/
anonymous svn: svn checkout http://svn.berlios.de/vl-hot/trunk

If anybody wants to be added to the project as developer, just let me know.
(Note: You need to register a user on Berlios first, and let me know
the user name once you get the confirmation.)

Quote
You can download vl-hot-1.9.9 and vl-hot-config-1.9.9 packages for VL
5.9 from the BerliOS project now. As you can see, I decided to
separate them in 2 packages. Let me know your opinions on this, for or
against.


BTW, M0E-lnx: I was switching vl-hot-config to G2, but then I came up agaist a little problem. The settings files management has changed between G1 and G2, and now it seems to have a fixed path (read-only), so until I cook up my own code for it, it stays in G1, which allows settings files to be in a path you define (in this case, /etc/udev/vl-hot.conf). I may post about this on the Gambas list to see what can be done about it, as well.


EDIT: BTW, vlh-umount should work nicely now.
Title: Re: The VL-hot thread
Post by: M0E-lnx on August 15, 2008, 05:43:25 am

BTW, M0E-lnx: I was switching vl-hot-config to G2, but then I came up agaist a little problem. The settings files management has changed between G1 and G2, and now it seems to have a fixed path (read-only), so until I cook up my own code for it, it stays in G1, which allows settings files to be in a path you define (in this case, /etc/udev/vl-hot.conf). I may post about this on the Gambas list to see what can be done about it, as well.


I have not see this to tell you the truth... I thought you could put your settings wherever you want... I have /etc/vpackager.conf now, which has been there since the G1 era. I've made changes to it, but never seen anything like a fixed path
Title: Re: The VL-hot thread
Post by: Joe1962 on August 21, 2008, 10:22:58 am
We now have vl-hot-config working with the codepages and charsets, without them, it was breaking vl-hot.conf, as it would save empty strings to those and so mount would fail. I will be off on vacation/holiday to the beach for a couple of weeks, so I might not have time to build and upload a new package, but you can checkout the HEAD from the BerliOS svn, there is a compiled vl-hot-config in there.

I have not see this to tell you the truth... I thought you could put your settings wherever you want... I have /etc/vpackager.conf now, which has been there since the G1 era. I've made changes to it, but never seen anything like a fixed path

Hmm... I will have to check your code, when I moved from G1 to G2-2.8.0, the settings code broke, when checking the help for the new syntax, it seemed to be saying that it was a fixed path.

Title: Re: The VL-hot thread
Post by: 123456789 on September 18, 2008, 11:13:41 pm
Problem: VL-hot mounted external harddisks
appear to be noexec by default.  Enabling exec
in the Mount tab of vl-hot-config does indeed
cause a line in /etc/udev/vl-hot.conf like this:
        MOUNTSYNC="noatime,exec"
but the volumes still seem to be mounted noexec:
attempts to directly run scripts from them
continue to fail with errors like
        /bin/sh: bad interpreter: Permission denied
Since the volumes don't show up in mtab and
I'm not familiar with udev, I could not determine
whether the problem is on the udev or on the
vl-hot side.  But skimming over the udev changelog
after 118, nothing jumped out at me, so I report this
here.
By the way, neither "excluding" nor "including" the
device in question (/dev/sdb6) in the
Mount tab in vl-hot-config seemed to make
any difference, so maybe I just don't get it
how this tab is supposed to be used.

Workaround: Creating a manual fstab entry
with mount options defaults,noatime,exec,rw
solved this problem for me. 

Configuration:
Approx. VL-current as of 2008-09-12
vl-hot-config 1.0.4
udev 118
Linux 2.6.22.19 SMP
External partition type: reiserfs

For the next vl-hot release, it would be nice to
know if exec is actually supposed to work,
and/or how to debug this further.

In any case: Thanks a lot for VectorLinux!
Title: Re: The VL-hot thread
Post by: Joe1962 on October 18, 2008, 05:53:07 am
Just uploaded vl-hot-1.9.20 and vl-hot-config-1.9.20 packages at the BerliOS project page. I'll have to leave the source code svn commits for another day though.

Main changes are: ported to Gambas2, a rethink of alert and debug messages, extensive debugging and refactoring, UI fixes and a whole other bunch of details I forgot to write down along the way... ::)

https://developer.berlios.de/projects/vl-hot/
Title: Re: The VL-hot thread
Post by: Joe1962 on October 18, 2008, 06:03:38 am
Problem: VL-hot mounted external harddisks
appear to be noexec by default.  Enabling exec
in the Mount tab of vl-hot-config does indeed
cause a line in /etc/udev/vl-hot.conf like this:
        MOUNTSYNC="noatime,exec"
but the volumes still seem to be mounted noexec:
attempts to directly run scripts from them
continue to fail with errors like
        /bin/sh: bad interpreter: Permission denied

I can confirm this. I missed it because I never needed to exec anything from a pendrive or USB drive before. Nobody else reported it before either. This will take some study, because the actual mount command issued seems correct, but the resulting mount is actually "noexec"... :o

actual command executed for my FAT32 pendrive:
Quote
mount -t vfat -o noatime,exec,uid=root,gid=users,fmask=0111,dmask=0000,quiet,user,shortname=mixed,codepage=850,iocharset=iso8859-1 /dev/vl-hot/sda1 /mnt/vl-hot/KINGMAX

result of running the mount command afterwards to check the mount point:
Code: [Select]
/dev/sda1 on /mnt/vl-hot/KINGMAX type vfat (rw,noexec,nosuid,nodev,noatime,uid=0,gid=100,fmask=0111,dmask=0000,quiet,shortname=mixed,codepage=850,iocharset=iso8859-1)
Any ideas?

By the way, neither "excluding" nor "including" the
device in question (/dev/sdb6) in the
Mount tab in vl-hot-config seemed to make
any difference, so maybe I just don't get it
how this tab is supposed to be used.

All the UI elements in vl-hot-config (and my other programs , like vcpufreq, for that matter) have a pop-up message explaining them. In this case, you can see that it says:
"Enter a space-delimited list. Example: sda*, sdb1, sdc2"

IOW, loose the "/dev/" part and trailing slash.
Title: Re: The VL-hot thread
Post by: wcs on October 18, 2008, 09:44:37 am
Quote
Any ideas?

I think it's because "exec" needs to come after "user".

From the "user" option in "man mount":
Quote
This option implies the options noexec, nosuid, and nodev (unless  overridden by subsequent options, as in the option line user,exec,dev,suid).
Title: Re: The VL-hot thread
Post by: Joe1962 on October 20, 2008, 09:29:54 am
I think it's because "exec" needs to come after "user".

Dang, I knew "default" had to be overridden later on the line, if used; missed the same about "user" though"! Thanks, I'll get on it tonight, if I can.
Title: Re: The VL-hot thread
Post by: caitlyn on October 20, 2008, 12:38:18 pm
Thanks for all your hard work on this.
Title: Re: The VL-hot thread
Post by: Joe1962 on October 21, 2008, 03:07:09 pm
Thanks for all your hard work on this.

You're welcome! Version 1.9.21 packages are up on the BerliOS project page now, for your upgradepkg pleasure... ;D

I moved the "user" to the start of mount options in vl-hot-functions, so overrides (like "exec") should work. Please test this, as I didn't have time to format my pendrive into a Linux filesystem and exec obviously does nothing on FAT32. This begs the question: would it be useful/necessary/practical to define mount options per different filesystem type?

The subversion source code repo trunk is now updated and also tag 1.9.21 created.

http://developer.berlios.de/projects/vl-hot/
Title: Re: The VL-hot thread
Post by: caitlyn on October 21, 2008, 10:10:59 pm
Joe:  Would you like the latest version added to the testing repository?

Pls let me know,
Cait
Title: Re: The VL-hot thread
Post by: Joe1962 on October 21, 2008, 11:21:47 pm
I think we should, it seems to be working pretty well, at least for me... ;)

I'm about ready to call it 2.0 after I get some feedback on the exec issue.
Title: Re: The VL-hot thread
Post by: caitlyn on October 21, 2008, 11:30:50 pm
Joe:  I grabbed the two VL 5.9 packages.  I didn't see any for VL 6.0 nor did I see source tarballs or build scripts for our source repositories.  PM me and let me know where I should be looking, please.

I'm actually doing VL 6 repo maintenance now.  I'll get to the VL 5.9 stuff tomorrow.
Title: Re: The VL-hot thread
Post by: Joe1962 on October 21, 2008, 11:57:19 pm
Sorry about that, I haven't gotten around to making source tarballs yet. I could try and set up a packaging script that pulls from the svn repo. Anyway, you can just copy and rename the packages to 1vl6, there's nothing in there that's version specific. One thing though, I have been using Gambas2 2.8.x for some time now and we only have 2.5.0 in the 5.9 and 6.0 repos. This could affect vl-hot-config. I'm not sure who built the last one, but we need to nudge them to set up Gambas2-2.8.2 runtime packages.
Title: Re: The VL-hot thread
Post by: uelsk8s on October 22, 2008, 09:45:39 am
I did the last packages, and i can do current versions, when I get back home next monday.
If anyone want to grab the buildscript before i get back they are welcome to it.
Joe, IIRC it is your buildscript we have been using.
Title: Re: The VL-hot thread
Post by: Joe1962 on October 22, 2008, 10:40:12 am
Hmm... my gambas buildscript was giving me some errors on 2.7.x and upwards, so I had to remove some of the cp instructions, then ended up just removing the "stop on any error" stuff. I've lacked the time to finish the changes necessary to build gambas in separate packages as defined by the developer, and also to make it compatible with the default VL buildscript. Still, I guess it will have to do for now... ;D  However, I won't be around to make and upload a presentable runtime package out of my not-so-presentable full package until Saturday or perhaps even Monday.
Title: Re: The VL-hot thread
Post by: Joe1962 on November 03, 2008, 09:40:19 pm
Has anybody tried "exec" yet?
Title: Re: The VL-hot thread
Post by: M0E-lnx on November 04, 2008, 05:56:05 am
If you mean exec as in the gambas code, then not me... I use SHELL all the time.
Title: Re: The VL-hot thread
Post by: Joe1962 on November 04, 2008, 11:39:12 am
No, I meant setting the exec mount option in vl-hot-config.

BTW, you should only use SHELL in Gambas when absolutely necessary, as it introduces an added overhead by loading a virtual shell.
Title: Re: The VL-hot thread
Post by: M0E-lnx on November 04, 2008, 11:55:53 am
;)
Title: Re: The VL-hot thread
Post by: Joe1962 on November 04, 2008, 12:08:19 pm
 :D
Title: Re: The VL-hot thread
Post by: M0E-lnx on November 04, 2008, 12:16:10 pm
So there is a difference between using SHELL vs EXEC then....
I always thought it was the same thing
Title: Re: The VL-hot thread
Post by: Joe1962 on November 04, 2008, 12:29:10 pm
http://www.gambasdoc.org/help/cat/process

Basically:
EXEC means: execute the following executable and pass it the following list of parameters...
SHELL means: run a virtual shell and pass it the following command line string...

HTH
Title: Re: The VL-hot thread
Post by: wcs on November 13, 2008, 09:57:18 am
I tried it now with a usb flash drive.
This is in /etc/mtab:
Code: [Select]
/dev/sdf1 /mnt/vl-hot/vl-hot vfat rw,nosuid,nodev,noatime,uid=0,gid=100,fmask=0111,dmask=0000,quiet,shortname=mixed,codepage=850,iocharset=iso8859-1 0 0
Should it say "exec" anywhere?
Without checking the option, it does say "noexec", but nothing is there with the "exec" option checked.
Title: Re: The VL-hot thread
Post by: wcs on November 13, 2008, 10:09:12 am
And one other thing:

I was trying unetbootin, to get a bootable Usb drive.
When mounted with vl-hot, unetbootin complains that the dive isn't mounted and there's no mount point (though it is).
No problems when using hal.

Not that there's anything wrong with vl-hot... it might just be a matter of getting the right options. Any ideas?
Thank you!
Title: Re: The VL-hot thread
Post by: caitlyn on November 14, 2008, 12:56:56 pm
I tried installing the new vl-hot and vl-hot-config into VL 6.0 Light.  vl-hot-config wanted to install 50 "dependencies" from gsb.  The package seems to think it needs GNOME installed.
Title: Re: The VL-hot thread
Post by: Joe1962 on November 14, 2008, 04:56:00 pm
Yes, there is a problem with the "gksu OR kdesu" dependency. As kdesu is not a package it will pull gksu anyway. I think it is gksu that wants gnome. I have fixed the vl-hot-config code  so if launched as a non-root user, it searches for kdesu and gksu (in that order), then runs another instance of itself with the first one found and exits. If none is found it will pop up an error message. This will allow me to drop that particular dependency altogether from the package. I will try to release ASAP.
Title: Re: The VL-hot thread
Post by: wcs on November 29, 2008, 06:33:26 pm
I also get this error when doing vlh-umount for a pendrive:
Code: [Select]
/etc/udev/vl-hot.conf: line 1: [General]: command not foundThen it takes quite a bit to unmount.
Title: Re: The VL-hot thread
Post by: Joe1962 on December 01, 2008, 08:10:01 am
I also get this error when doing vlh-umount for a pendrive:
Code: [Select]
/etc/udev/vl-hot.conf: line 1: [General]: command not found
This is merely an aesthetic "bug" due to the use switch to Gambas2 for vl-hot-config and the use of bash scripting for the rest of vl-hot. The Gambas2 config file handling functions define a 2-level nested structure like the Windows ini files. [General] is merely a subsection heading that bash does not understand as a command when merging vl-hot.conf into the scripts. This did not happen with Gambas1 config files.

Though it is not really a functionality problem, I have identified 2 ways to fix this: use lower-level Gambas file access functions in vl-hot-config (writing a custom config file handler), or re-writing the rest of vl-hot in Gambas. The latter option is something I have been thinking of for some time now. It all depends on the limited available programming time for this.


Then it takes quite a bit to unmount.
This can happen if buffered writes are used (the default) and there is a lot to write out to the drive when flushing the cache before unmounting. If the drive has a LED, you would see it flashing during this time. Linux seems to be rather lazy when it comes to writing out the cache to a drive even when left alone for quite a while.
Title: Re: The VL-hot thread
Post by: wcs on December 03, 2008, 07:35:19 am
Quote
Linux seems to be rather lazy when it comes to writing out the cache to a drive even when left alone for quite a while.

Thanks for the answers!
Yea, tried it with hal, and after copying big files it takes a bit to unmount as well...
Title: Re: The VL-hot thread
Post by: Joe1962 on December 10, 2008, 10:51:00 am
Sorry about the delay, but I finally managed to wrap up the changes for 1.9.22 and released it. You can find the corresponding vl-hot and vl-hot-config packages for VL 5.9 (AFAIK, they should also work for VL6) at the BerliOS project page: http://developer.berlios.de/projects/vl-hot/

Notes:
- remember vl-hot-config is now a Gambas2 project.
- source code is on the svn repo at BerliOS, still haven't gotten around to making tarballs.

Changelog:
Code: [Select]
2008-12-10    <joe1962@users.sourceforge.net>

* Removed vlhc-launcher.
* Restored user check and *su call to vl-hot-config.
* Repackaged 1.9.22.

2008-12-10    <joe1962@users.sourceforge.net>

* Released 1.9.22.

2008-11-10    <joe1962>

* Changed check for System.User.Name = "root" to System.User.Id = 0.
* if System.User.Id <> 0, looks for kdesu or gksu.
* If found, executes another instance as root and exits.
* Separated user check and *su call to vlhc-launcher gambas2 cli app.

2008-11-08    <joe1962@users.sourceforge.net>

* Updated TODO.




EDIT:

Forgot to add that this release eliminates the gksu/kdesu dependency issue. Also, I missed removing the vsuper call from some of the .desktop files, but this does not cause problems (at least on VL). Still, I'll fix this and repackage later on.
Title: Re: The VL-hot thread
Post by: Joe1962 on December 18, 2008, 01:00:43 am
Stable release 2.0.0 packages of vl-hot and vl-hot-config (for VL59 and VL60) are now up on the BerliOS project page:
http://developer.berlios.de/project/showfiles.php?group_id=9736

Changelog:
Code: [Select]
2008-12-13    <joe1962@users.sourceforge.net>

* Released 2.0.0.

2008-12-13    <joe1962@users.sourceforge.net>

* Fixed application path when calling with kdesu/gksu.
* Removed remaining vsuper from .desktop files.
* Added new unmount icon by nightflier.
* Fixed vl-hot-config dialog filters for selecting icon and sound files.


I have decided to go back to the traditional even numbered stable/uneven numbered unstable versioning, and so development release 2.1.0 of vl-hot-config is also up on the site. Willing testers please use this with vl-hot 2.0.0, as the "back end" has not changed yet. Screenshots of the heavily redesigned vl-hot-config are here:
http://developer.berlios.de/screenshots/?group_id=9736

I have yet to write a changelog for 2.1.0... ;D


EDIT: oops, forgot to mention that the "File manager" action setting needs back-end changes that are yet to come... ;)
Title: Re: The VL-hot thread
Post by: caitlyn on February 20, 2009, 01:35:27 pm
I've finally gotten back to the idea of writing an article for O'Reilly on VL-Hot.  I've got the latest rc (maybe actually final) of VL 6.0 installed.  I've been testing with HAL up until now. 

First, congratulations on all the progress you've made.  It works very well indeed and VL-Hot Config really makes this an incredibly flexible tool for a user with half a clue.  One niggle, and it's probably more cosmetics or my personal sensibilities that anything else.  The default mount path is /mnt/vl-hot.  That's been the case for a long time and I really don't have a problem with that.  When I insert a USB stick the icons pop up as expected, but the device is at /mnt/vl-hot/vl-hot.  Isn't that redundant?  Why not just make the default path /mnt much as HAL does with /media.  Second device is /mnt/vl-hot/vl-hot1.  Still redundant.

Yes, I know I can change this in VL-Hot Config but the default behavior looks, well... strange.

One other suggestion:  HAL is capable of reading a device name string on a lot of USB sticks so it comes up with a mount point that is often a brand name or model.  Can VL-Hot do the same at some point in the future? 

Anyway, these are just my thoughts.  I haven't found an actual bug yet  ;D
Title: Re: The VL-hot thread
Post by: Joe1962 on February 20, 2009, 01:44:19 pm
Thanks!

Since what is actually mounted are partitions, not devices (although some older pendrives may not have a partition table but the device is treated as a partition anyway), vl-hot in the more recent incarnations looks for a volume label and uses that as the mount name. If no label is found, it defaults to vl-hot, vl-hot1, etc. I looked into using one of the USB device strings for this a long time ago, and it is certainly doable, but they are not always "nice" names, so went for the labels instead.


EDIT: The new naming convention in the latest releases makes it possible to default to /mnt, but I would have to rethink vlh-umount which relies on a specific dir for unmounting all vl-hot mounted partitions.


EDIT2: BTW, there is a bug in the user selection code on the latest release (already fixed on the svn repo) which causes a failure of the notification popups in many cases.
Title: Re: The VL-hot thread
Post by: caitlyn on February 20, 2009, 02:00:39 pm
Let me see if I understand this:

If I change from /mnt/vl-hot to /mnt in VL-Hot Config then unmounting won't work?

When you say "user selection code" are you referring to the selection of the default base directory in VL-Hot Config?

I also think I've finally found a bug:  In the 1.x versions if a device is inserted when a system is shutdown the icons for a device was still in place at the next boot even if the device itself is no longer present.  This has mostly been corrected in version 2.0.0 but I have noticed that if I have two USB sticks inserted when I shutdown the icon for the second one will still be present at next boot in Xfce.  This happens in VL 6.0 rc4.10. 

I'm in the middle of writing the article right now and I'd like to be really clear about what a user can and can't expect.

Thanks,
Cait
Title: Re: The VL-hot thread
Post by: caitlyn on February 21, 2009, 01:51:08 pm
Now I've gone and done it:

http://broadcast.oreilly.com/2009/02/vl-hot-a-non-polling-alternati.html

Joe1962:  I hope you like the write-up.
Title: Re: The VL-hot thread
Post by: Joe1962 on February 26, 2009, 01:04:42 pm
Sorry, I was away for a few days and now I find we are having big problems with the internet connection, I barely managed this reply.

If I change from /mnt/vl-hot to /mnt in VL-Hot Config then unmounting won't work?
Normal unmounting from the desktop icon should work, just vlh-umount won't, as it is still sort of crude... ;D

When you say "user selection code" are you referring to the selection of the default base directory in VL-Hot Config?
No, I meant the code that detects the active GUI user to send the notification as/to.

BTW, I like the article and hope to be able to write a comment next week to clear some things up if the internet connection issue is fixed.
Title: Re: The VL-hot thread
Post by: caitlyn on February 26, 2009, 01:26:27 pm
Glad you like the article.  If there are some errors or things needing clarification and the O'Reilly page is difficult/slow on your network connection feel free to e-mail or PM me and I'll gladly post the corrections in an obvious way.
Title: Re: The VL-hot thread
Post by: Joe1962 on February 27, 2009, 10:51:05 am
We got the net connection back today, sort of... but I managed to post a comment. I will paste it here too, for reference:

Quote
Very nice article, as I have come to expect from Caitlyn. Just a few points of clarification which I did not have time to send her before the article was finished:

The code for opening a filenamager is not yet operational, though the configuration option was already added to vl-hot-config.

The left-over icons cleanup takes place on the next unmount action, so it will eventually catch up, lol. An option is to set up a small script that runs during boot to take care of this.

There are 2 desktop icons for each partition on XFCE due to a limitation of this desktop environment, which does not seem to handle custom icon actions. On KDE there would be only 1 icon. I have not tested on Gnome so this defaults to the 2 icon system, though it may support the custom actions.

The default mountbase is /mnt/vl-hot/, but the actual mount point within that is taken from 3 sources in order of preference:

1- custom name from vl-hot.conf
2- volume label of the partition
3- vl-hot + a sequential number

This means it will use vl-hot# only if the first 2 options are not set.