You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(21) |
Jul
(6) |
Aug
(6) |
Sep
|
Oct
(3) |
Nov
(4) |
Dec
|
2009 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(1) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
(5) |
Mar
|
Apr
(10) |
May
(7) |
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(6) |
Oct
(2) |
Nov
(1) |
Dec
|
2011 |
Jan
|
Feb
(7) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(2) |
2012 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Hans-Ulrich J. <han...@t-...> - 2009-05-15 13:57:56
|
Hi Stewart, Stewart Millen wrote: > Thanks Ulrich. You're the greatest! No need to rush on your end, I > always can boot to the previous kernel until a new package is > distributed. > > One of these days I guess I ought to start compiling the code myself on > my machine to address the times a kernel upgrade breaks Scramdisk. > However, I suppose there's also a need to make sure that the Scramdisk > packages stay current, so I guess these alerts do serve a good purpose. > > Stewart yes, I appreciate these alerts. Often I haven't booted the particular distro for some time. In particular your mail informed me that the kernel had changed in Ubuntu 8.10. Best regards, Ulrich |
From: Stewart M. <smm...@gm...> - 2009-05-15 13:28:51
|
On Thu, 2009-05-14 at 22:21 +0200, Hans-Ulrich Juettner wrote: > Hi Stewart, > > Stewart Millen wrote: > > On Wed, 2009-05-13 at 16:17 -0400, Stewart Millen wrote: > >> Greetings; > >> > >> Just to let everyone know that SD4L (1.3-2) stopped working today after > >> the kernel upgrade (2.6.27-11 generic to 2.6.27-14 generic). > >> > >> I've not upgraded to SD4L 2.0-0 yet; if the upgrade (which I'll see if I > >> can get to doing later today) fixes the problem I apologize for the > >> unnecessary note (though I suspect it won't). > > > > Upgraded today to version 2.0-0. As I suspected, it did not fix the > > problem (error message was (from memory) that "mounting device does not > > exist". > > > > Stewart > > I've just uploaded packages for SD4L 2.0-0, Ubuntu 8.10 with kernel > 2.6.27-14. That should fix your problem. > > Best regards, > Ulrich Thanks Ulrich. You're the greatest! No need to rush on your end, I always can boot to the previous kernel until a new package is distributed. One of these days I guess I ought to start compiling the code myself on my machine to address the times a kernel upgrade breaks Scramdisk. However, I suppose there's also a need to make sure that the Scramdisk packages stay current, so I guess these alerts do serve a good purpose. Stewart |
From: Hans-Ulrich J. <han...@t-...> - 2009-05-14 20:21:42
|
Hi Stewart, Stewart Millen wrote: > On Wed, 2009-05-13 at 16:17 -0400, Stewart Millen wrote: >> Greetings; >> >> Just to let everyone know that SD4L (1.3-2) stopped working today after >> the kernel upgrade (2.6.27-11 generic to 2.6.27-14 generic). >> >> I've not upgraded to SD4L 2.0-0 yet; if the upgrade (which I'll see if I >> can get to doing later today) fixes the problem I apologize for the >> unnecessary note (though I suspect it won't). > > Upgraded today to version 2.0-0. As I suspected, it did not fix the > problem (error message was (from memory) that "mounting device does not > exist". > > Stewart I've just uploaded packages for SD4L 2.0-0, Ubuntu 8.10 with kernel 2.6.27-14. That should fix your problem. Best regards, Ulrich |
From: Stewart M. <smm...@gm...> - 2009-05-14 14:05:17
|
On Wed, 2009-05-13 at 16:17 -0400, Stewart Millen wrote: > Greetings; > > Just to let everyone know that SD4L (1.3-2) stopped working today after > the kernel upgrade (2.6.27-11 generic to 2.6.27-14 generic). > > I've not upgraded to SD4L 2.0-0 yet; if the upgrade (which I'll see if I > can get to doing later today) fixes the problem I apologize for the > unnecessary note (though I suspect it won't). Upgraded today to version 2.0-0. As I suspected, it did not fix the problem (error message was (from memory) that "mounting device does not exist". Stewart |
From: Stewart M. <smm...@gm...> - 2009-05-13 20:17:28
|
Greetings; Just to let everyone know that SD4L (1.3-2) stopped working today after the kernel upgrade (2.6.27-11 generic to 2.6.27-14 generic). I've not upgraded to SD4L 2.0-0 yet; if the upgrade (which I'll see if I can get to doing later today) fixes the problem I apologize for the unnecessary note (though I suspect it won't). Stewart |
From: Hans-Ulrich J. <han...@t-...> - 2009-04-23 12:20:10
|
Hello, the stable version 2.0-0 of ScramDisk for Linux has been released. It now supports TrueCrypt 5 and 6 containers. The new features of handling partitioned containers or whole partitioned hard disks and of creating a swap space within a container and using such an encrypted swap space have been added. Moreover, some bugs have been fixed. Packages for CentOS 5.3, Debian 3.1, 4.0 and 5.0, Fedora 10, Mandriva 2009, SUSE 11.0 and 11.1 and Ubuntu 8.04 and 8.10 are provided for i386 and AMD64 architectures. Packages for Ubuntu 9.04 will follow soon. The kernel version is part of the filename of binary packages and must match the kernel version of the system it is installed on. The architecture i386 or x86_64 in the filename should also match the architecture of the distribution on which it is installed. Best regards Ulrich |
From: Martinveg <mar...@gm...> - 2009-03-17 18:23:15
|
Hi Ulrich, On Tue, Mar 17, 2009 at 4:28 AM, Hans-Ulrich Juettner <han...@t-...> wrote: > Hi Martin, > > Martinveg wrote: >> Hi, Hans-Ulrich, >> >> This is a follow-up to my previous message of yesterday: >> >> Today I tried again to mount the container, and when it wouldn't >> mount, I followed your instructions again, doing the fsck -t vfat >> /dev/scramdisk/vol01 command. And the result appeared to be exactly >> the same as yesterday. This suggests to me that the command did not >> change my container file at all -- indeed, the notation: "Leaving file >> system unchanged" suggests this. I commanded it to correct the >> problems and delete the bad files, but it seems that it didn't do it. >> >> How do I get it to actually make the required changes? >> >> Thanks again, >> >> Martin >> > > Yes that means, that the changes haven't been written. Okay, but why weren't they written? I should point out that I'm a newbie to Linux. I just installed Mint two weeks ago and have a lot to learn. When the fsck -t vfat /dev/scramdisk/vol01 command was executing, the Terminal asked me several times what to do, for example, correct a problem or leave it alone. It would give me a choice of 1 or 2, and I would key 1 or 2 and then press enter. I don't even know if that is the correct thing to do in Terminal. Did I do that correctly? Can that command be changed so that it will actually fix the file and save the changes? > There are a number of further options you may try. > By the command > > man fsck.msdos > > a manual page of the msdos/vfat file system checker, > which fsck calls with the option -t vfat, is displayed. > You can always find such man pages in the internet > if they are not installed on your computer or you > like a more friendly presentation in the browser. > Especially the options (copied from the man page) > > -w for "Write changes to disk immediately." > -t for "Mark unreadable clusters as bad." > and perhaps > -a for "Automatically repair the file system. > No user intervention is necessary. > Whenever there is more than one method > to solve a problem, the least destructive > approach is used." Thanks. But, again, I'm a novice to Linux. Can you give me a complete command to use man fsck.msdos to automatically fix the container mounted on scramdisk Vol01? Since you mentioned man fsck.msdos first, i assume i should try it before the one that follows: > > of fsck.msdos might be worth trying. You may also > call fsck.msdos directly without instructing fsck > by the option -t vfat to call it. So a possible > approach would be > > fsck.msdos -w -t /dev/scramdisk/vol01 > > or > > fsck.msdos -w -t -a /dev/scramdisk/vol01. > > I hope this helps, but there is no guaranty that > the file system will be repaired successfully. > > >> Unfortunately, after doing this in Terminal, I still can't mount the >> container. when I click on the Volume 01 (none (don't mount)) >> container and click Mount, I get the error: "Container file already >> mounted." And it gives the file system location of my container file. >> But of course it is NOT mounted there. And it is not mounted in the >> folder I selected as the Mount Point either. > > You first have to unmount the container which was > mounted with the special option "none (don't mount)". > > Perhaps you are confused by the two meanings of the phrase > "mount" in the context of SD4L. The first meaning is > to read the header of the container and decrypt it with > the passphrase. The second meaning is to mount the file > system within the container to make it accessible by your > Linux machine. The option "none (don't mount)" results > in only doing a "mount" in the first meaning. If this > option isn't chosen, both meanings of "mount" are performed. > So either you unmount the container before doing the normal > mount or you may perform the second meaning of "mount" > in your root terminal by the command > > mount -t vfat /dev/scramdisk/vol01 /mnt > > where /mnt may also be any other directory where you like > to have your container mounted. Is this the same thing as doing it with the GUI? I prefer to use the GUI. > Another possibility of mounting is to replace vfat with > msdos. The difference is that with the option -t msdos > of the mount command no long file names are available > but only 8.3 dos file names. SD4L has this option msdos > also as a separate mount option. If mounting with -t vfat > fails after all fsck runs this option -t msdos may be a > last trial. Okay, thanks Ulrich. I guess I'd like to know, first, if I can modify your original command, fsck -t vfat /dev/scramdisk/vol01 , to make it really fix the container. Then, I'd like to know an actual command to run for man fsck.msdos. And then, I can try the fsck.msdos -w -t -a /dev/scramdisk/vol01. And if all that fails, I will try to mount it as MS-DOS. Thanks so much for all your assistance. Martin |
From: Hans-Ulrich J. <han...@t-...> - 2009-03-16 21:29:15
|
Hi Martin, Martinveg wrote: > Hi, Hans-Ulrich, > > This is a follow-up to my previous message of yesterday: > > Today I tried again to mount the container, and when it wouldn't > mount, I followed your instructions again, doing the fsck -t vfat > /dev/scramdisk/vol01 command. And the result appeared to be exactly > the same as yesterday. This suggests to me that the command did not > change my container file at all -- indeed, the notation: "Leaving file > system unchanged" suggests this. I commanded it to correct the > problems and delete the bad files, but it seems that it didn't do it. > > How do I get it to actually make the required changes? > > Thanks again, > > Martin > Yes that means, that the changes haven't been written. There are a number of further options you may try. By the command man fsck.msdos a manual page of the msdos/vfat file system checker, which fsck calls with the option -t vfat, is displayed. You can always find such man pages in the internet if they are not installed on your computer or you like a more friendly presentation in the browser. Especially the options (copied from the man page) -w for "Write changes to disk immediately." -t for "Mark unreadable clusters as bad." and perhaps -a for "Automatically repair the file system. No user intervention is necessary. Whenever there is more than one method to solve a problem, the least destructive approach is used." of fsck.msdos might be worth trying. You may also call fsck.msdos directly without instructing fsck by the option -t vfat to call it. So a possible approach would be fsck.msdos -w -t /dev/scramdisk/vol01 or fsck.msdos -w -t -a /dev/scramdisk/vol01. I hope this helps, but there is no guaranty that the file system will be repaired successfully. > Unfortunately, after doing this in Terminal, I still can't mount the > container. when I click on the Volume 01 (none (don't mount)) > container and click Mount, I get the error: "Container file already > mounted." And it gives the file system location of my container file. > But of course it is NOT mounted there. And it is not mounted in the > folder I selected as the Mount Point either. You first have to unmount the container which was mounted with the special option "none (don't mount)". Perhaps you are confused by the two meanings of the phrase "mount" in the context of SD4L. The first meaning is to read the header of the container and decrypt it with the passphrase. The second meaning is to mount the file system within the container to make it accessible by your Linux machine. The option "none (don't mount)" results in only doing a "mount" in the first meaning. If this option isn't chosen, both meanings of "mount" are performed. So either you unmount the container before doing the normal mount or you may perform the second meaning of "mount" in your root terminal by the command mount -t vfat /dev/scramdisk/vol01 /mnt where /mnt may also be any other directory where you like to have your container mounted. Another possibility of mounting is to replace vfat with msdos. The difference is that with the option -t msdos of the mount command no long file names are available but only 8.3 dos file names. SD4L has this option msdos also as a separate mount option. If mounting with -t vfat fails after all fsck runs this option -t msdos may be a last trial. Best regards, Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2009-02-20 21:12:07
|
Hi Stewart, I've uploaded new packages for Ubuntu 8.10 and kernel 2.6.27-11. Best regards Ulrich Stewart Millen wrote: > Hi all, > > I installed SD4L on a fresh install of 8.10 on my Dell Inspiron 1525N > (on a new HD). When I did the updates after the installation, and > acquired a new kernel (2.6.27-11-generic), SD4L does not mount encrypted > volumes. It still works normally under the only other kernel on the > system, 2.6.27-7-generic. > > Stewart |
From: Stewart M. <smm...@gm...> - 2009-02-19 03:38:31
|
Hi all, I installed SD4L on a fresh install of 8.10 on my Dell Inspiron 1525N (on a new HD). When I did the updates after the installation, and acquired a new kernel (2.6.27-11-generic), SD4L does not mount encrypted volumes. It still works normally under the only other kernel on the system, 2.6.27-7-generic. Stewart |
From: Stewart M. <smm...@gm...> - 2008-11-30 16:39:52
|
On Sun, 2008-11-30 at 17:17 +0100, Hans-Ulrich Juettner wrote: > Hi Stewart, > > I built new packages for Ubuntu 8.04 and kernel 2.6.24-22. > Package files are > ScramDisk_1.3-2_Ubuntu-8.04_2.6.24-22_i386.deb > and > ScramDisk_1.3-2_Ubuntu-8.04_2.6.24-22_x86_64.deb > they should work with the new kernel. > > Best regards, > Ulrich Thank you, Ulrich. I can now confirm that they work as they should. One of these days, I'll have to become brave enough to compile the code on my machine from the source (that's the way to fix these problems with kernel upgrades, no?) Stewart |
From: Hans-Ulrich J. <han...@t-...> - 2008-11-30 16:17:34
|
Hi Stewart, I built new packages for Ubuntu 8.04 and kernel 2.6.24-22. Package files are ScramDisk_1.3-2_Ubuntu-8.04_2.6.24-22_i386.deb and ScramDisk_1.3-2_Ubuntu-8.04_2.6.24-22_x86_64.deb they should work with the new kernel. Best regards, Ulrich Stewart Millen wrote: > Hello all, > > I'm running Ubuntu Hardy Heron 8.04.1 with the latest release of SD4L. > Just late last night, I was prompted to upgrade from kernel > 2.6.24-21-generic to 2.6.24-22-generic, which apparently broke Scramdisk > (error message, as I recall, was my mount point was invalid). > > Please confirm. To send this post, I had to reboot to the previous > kernel (my mail folders reside inside an encrypted partition). SD4L > works as previously under 2.6.24-21-generic. > > Cheers, > > Stewart |
From: Stewart M. <smm...@gm...> - 2008-11-30 15:51:00
|
> Hello all, > > I'm running Ubuntu Hardy Heron 8.04.1 with the latest release of SD4L. > Just late last night, I was prompted to upgrade from kernel > 2.6.24-21-generic to 2.6.24-22-generic, which apparently broke Scramdisk > (error message, as I recall, was my mount point was invalid). > > Please confirm. To send this post, I had to reboot to the previous > kernel (my mail folders reside inside an encrypted partition). SD4L > works as previously under 2.6.24-21-generic. > > Cheers, > > Stewart I restarted the computer today under kernel 2.6.24-22-generic to reproduce the error and obtain the error message. The error message is: "Mounting Failed: No such device or address". Stewart |
From: Stewart M. <smm...@gm...> - 2008-11-29 15:43:44
|
Hello all, I'm running Ubuntu Hardy Heron 8.04.1 with the latest release of SD4L. Just late last night, I was prompted to upgrade from kernel 2.6.24-21-generic to 2.6.24-22-generic, which apparently broke Scramdisk (error message, as I recall, was my mount point was invalid). Please confirm. To send this post, I had to reboot to the previous kernel (my mail folders reside inside an encrypted partition). SD4L works as previously under 2.6.24-21-generic. Cheers, Stewart |
From: Hans-Ulrich J. <han...@t-...> - 2008-10-30 22:09:09
|
Hello Dale Osborn, the package ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb was built with kernel 2.6.24-16. Some changes introduced with the Ubuntu kernel 2.6.24-18 result in the behavior you experienced. As solution I built on Ubuntu kernel 2.6.24-18 the new package ScramDisk_1.3-0_Ubuntu-8.04_2.6.24-18_i386.deb This package still works with later again updated Ubuntu kernels including 2.6.24-21. Please, download this package. It should work for you. Best regards Ulrich Dale Osborn, Jr. wrote: > Hello, Listers, > > Can you help me get ScramDisk running on my system? > dpkg claims the .ko has an invalid format, and > I have been unable to make from the source. > > I would like to use ScramDisk on Ubuntu Hardy: > $ uname -r > 2.6.24-21-generic > > I downloaded from Sourceforge: > ScramDisk_1.3-0_en.pdf > ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb > ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb.sig > > I checked the sig and it is OK: > $ gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 0x68CED9BE > gpg: requesting key 68CED9BE from hkp server keyserver.ubuntu.com > gpg: key 68CED9BE: public key "Ulrich Juettner (Scramdisk for Linux Signature Key) <han...@t-...>" imported > gpg: Total number processed: 1 > gpg: imported: 1 (RSA: 1) > > $ gpg --verify Scr*.sig > gpg: Signature made Sat 26 Apr 2008 02:32:42 PM EDT using RSA key ID 68CED9BE > gpg: Good signature from "Ulrich Juettner (Scramdisk for Linux Signature Key) <han...@t-...>" > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 478E BB6C 740F 0C9D D6A2 95EC 51D3 2249 68CE D9BE > > I tried to install the package and it failed: > $ sudo dpkg -i ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb > [sudo] password: > (Reading database ... 146341 files and directories currently installed.) > Preparing to replace scramdisk 1.3-0 (using ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb) ... > Scramdisk not loaded > Unpacking replacement scramdisk ... > Removing any system startup links for /etc/init.d/scramdisk ... > /etc/rcS.d/K04scramdisk > /etc/rcS.d/S80scramdisk > Setting up scramdisk (1.3-0) ... > Adding system startup for /etc/init.d/scramdisk ... > /etc/rcS.d/K04scramdisk -> ../init.d/scramdisk > /etc/rcS.d/S80scramdisk -> ../init.d/scramdisk > Loading Scramdisk encrypted filesystems > insmod: error inserting '/lib/modules/scramdisk/scramdisk.ko': -1 Invalid module format > > I then downloaded the source into /usr/src: > -rw-r--r-- 1 root root 1291244 2008-10-30 10:13 ScramDisk_1.3-1.tar.gz > -rw-r--r-- 1 root root 287 2008-10-30 10:14 ScramDisk_1.3-1.tar.gz.sig > > I verified the signature: > $ gpg --verify Scr*.sig > gpg: Signature made Sat 12 Jul 2008 08:42:36 AM EDT using RSA key ID 68CED9BE > gpg: Good signature from "Ulrich Juettner (Scramdisk for Linux Signature Key) <han...@t-...>" > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 478E BB6C 740F 0C9D D6A2 95EC 51D3 2249 68CE D9BE > > Then I unpacked the tarball: > $ sudo tar -xzf ScramDisk_1.3-1.tar.gz > > I changed to the source directory: > $ cd ScramDisk-1.3-1 > > And tried run the make, but that failed: > $ sudo make > cd gui && qmake && lrelease scramdisk_de.ts > /bin/sh: qmake: not found > make: *** [all] Error 127 > > So now I am pretty much at the limit of my knowledge. > I do observe that there is no Makefile in the gui directory. > > I would be grateful for any help you can give me to get ScramDisk > working on my system. > > Many thanks, > Dale Osborn > > p.s. I am new to Sourceforge. If I should have put this on > the bug tracker please let me know. > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > SD4L-user mailing list > SD4...@li... > https://lists.sourceforge.net/lists/listinfo/sd4l-user > |
From: Dale O. Jr. <osb...@ea...> - 2008-10-30 16:42:29
|
Please forgive if you received a spam block message from earthlink. I have done what is needed to ensure all mail from sourceforge.net will be accepted without further interference from the spam blocker. |
From: Dale O. Jr. <Pa...@ea...> - 2008-10-30 16:21:21
|
Hello, Listers, Can you help me get ScramDisk running on my system? dpkg claims the .ko has an invalid format, and I have been unable to make from the source. I would like to use ScramDisk on Ubuntu Hardy: $ uname -r 2.6.24-21-generic I downloaded from Sourceforge: ScramDisk_1.3-0_en.pdf ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb.sig I checked the sig and it is OK: $ gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 0x68CED9BE gpg: requesting key 68CED9BE from hkp server keyserver.ubuntu.com gpg: key 68CED9BE: public key "Ulrich Juettner (Scramdisk for Linux Signature Key) <han...@t-...>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) $ gpg --verify Scr*.sig gpg: Signature made Sat 26 Apr 2008 02:32:42 PM EDT using RSA key ID 68CED9BE gpg: Good signature from "Ulrich Juettner (Scramdisk for Linux Signature Key) <han...@t-...>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 478E BB6C 740F 0C9D D6A2 95EC 51D3 2249 68CE D9BE I tried to install the package and it failed: $ sudo dpkg -i ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb [sudo] password: (Reading database ... 146341 files and directories currently installed.) Preparing to replace scramdisk 1.3-0 (using ScramDisk_1.3-0_Ubuntu-8.04_2.6.24_i386.deb) ... Scramdisk not loaded Unpacking replacement scramdisk ... Removing any system startup links for /etc/init.d/scramdisk ... /etc/rcS.d/K04scramdisk /etc/rcS.d/S80scramdisk Setting up scramdisk (1.3-0) ... Adding system startup for /etc/init.d/scramdisk ... /etc/rcS.d/K04scramdisk -> ../init.d/scramdisk /etc/rcS.d/S80scramdisk -> ../init.d/scramdisk Loading Scramdisk encrypted filesystems insmod: error inserting '/lib/modules/scramdisk/scramdisk.ko': -1 Invalid module format I then downloaded the source into /usr/src: -rw-r--r-- 1 root root 1291244 2008-10-30 10:13 ScramDisk_1.3-1.tar.gz -rw-r--r-- 1 root root 287 2008-10-30 10:14 ScramDisk_1.3-1.tar.gz.sig I verified the signature: $ gpg --verify Scr*.sig gpg: Signature made Sat 12 Jul 2008 08:42:36 AM EDT using RSA key ID 68CED9BE gpg: Good signature from "Ulrich Juettner (Scramdisk for Linux Signature Key) <han...@t-...>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 478E BB6C 740F 0C9D D6A2 95EC 51D3 2249 68CE D9BE Then I unpacked the tarball: $ sudo tar -xzf ScramDisk_1.3-1.tar.gz I changed to the source directory: $ cd ScramDisk-1.3-1 And tried run the make, but that failed: $ sudo make cd gui && qmake && lrelease scramdisk_de.ts /bin/sh: qmake: not found make: *** [all] Error 127 So now I am pretty much at the limit of my knowledge. I do observe that there is no Makefile in the gui directory. I would be grateful for any help you can give me to get ScramDisk working on my system. Many thanks, Dale Osborn p.s. I am new to Sourceforge. If I should have put this on the bug tracker please let me know. |
From: Jonathan C. <jco...@ro...> - 2008-08-07 12:15:39
|
Yes. Hans-Ulrich Juettner wrote: > HI Jonathan, > > Jonathan Coles wrote: >> Hi Ulrich, >> >> A solution for this problem is not urgent. >> >> The misreporting of partition size occurs when I create a >> Windows-compatible drive, using the defaults: >> SHA1 digest, Blowfish cipher, vfat/msdos file system. The same disk >> partition was used. >> > > my question where the misreporting occurs was meant with > respect to the window/process. Meanwhile I've seen it myself. > The container creation dialog reports the size of the partition > but the size of the mounted container is later reported as > the size of the whole disk. Does this match your observation? > > Best regards > Ulrich > |
From: Hans-Ulrich J. <han...@t-...> - 2008-08-07 08:17:35
|
HI Jonathan, Jonathan Coles wrote: > Hi Ulrich, > > A solution for this problem is not urgent. > > The misreporting of partition size occurs when I create a > Windows-compatible drive, using the defaults: > SHA1 digest, Blowfish cipher, vfat/msdos file system. The same disk > partition was used. > my question where the misreporting occurs was meant with respect to the window/process. Meanwhile I've seen it myself. The container creation dialog reports the size of the partition but the size of the mounted container is later reported as the size of the whole disk. Does this match your observation? Best regards Ulrich |
From: Jonathan C. <jco...@ro...> - 2008-08-06 22:43:51
|
Hi Ulrich, A solution for this problem is not urgent. The misreporting of partition size occurs when I create a Windows-compatible drive, using the defaults: SHA1 digest, Blowfish cipher, vfat/msdos file system. The same disk partition was used. Thanks. Hans-Ulrich Juettner wrote: > Today I've managed to reproduce the problem. It's a deadlock produced > in some circumstances by scramdisk waiting for the mkfs command to > finish while the mkfs command is waiting for scramdisk to read it's > output. The "Couldn't mount device: Invalid argument" is simply an > aftereffect of the failed mkfs command. > > On the other hand, I haven't seen scramdisk reporting the size of > the whole drive instead of the size of the selected partition, are > you sure about this? If yes, where exactly have you seen the wrong > size? > > Finally, I'd like to ask whether you have an urgent need for a bug fix > package. I'm hesitating to publish a complete new bug fix release for > all the supported distributions since I'm preparing for a major new > version which, however, will take some months to be finished. > I could send you a patch for the sources or a package just for your > distribution. What do you think about that? > > Best regards > Ulrich > |
From: Hans-Ulrich J. <han...@t-...> - 2008-08-05 18:11:37
|
Hi Jonathan, Jonathan Coles wrote: > Hi Ulrich, > >> $ ls -l /dev/sda* >> brw-rw---- 1 root disk 8, 0 2008-08-04 12:44 /dev/sda >> brw-rw---- 1 root disk 8, 1 2008-08-04 12:44 /dev/sda1 >> brw-rw---- 1 root disk 8, 3 2008-08-04 13:43 /dev/sda3 >> brw-rw---- 1 root disk 8, 5 2008-08-04 12:44 /dev/sda5 > sda3 is the partition I used. It is a primary partition. > I belong to the disk group, but I cannot create the volume unless I run > Scramdisk using sudo. > you have no rights to access /dev/sda3 unless you change your active group to "disk" with the command newgrp disk a scramdisk started after that command from the same shell will create the volume. > Nothing is reported to /var/log/messages about the volume creation. > > When I kill the stalled mkfs.ext2 process, I briefly see a Scramdisk > Create dialog showing volume creation 20-30% complete. Then it is > covered by an error dialog "Couldn't mount device: Invalid argument". If > I move that aside, I can see the value in the Scramdisk Create dialog > change to 80% complete. Clicking OK in the error dialog also closes the > create dialog. > > A straight mkfs of an ext2 filesystem on the partition works normally. > Today I've managed to reproduce the problem. It's a deadlock produced in some circumstances by scramdisk waiting for the mkfs command to finish while the mkfs command is waiting for scramdisk to read it's output. The "Couldn't mount device: Invalid argument" is simply an aftereffect of the failed mkfs command. On the other hand, I haven't seen scramdisk reporting the size of the whole drive instead of the size of the selected partition, are you sure about this? If yes, where exactly have you seen the wrong size? Finally, I'd like to ask whether you have an urgent need for a bug fix package. I'm hesitating to publish a complete new bug fix release for all the supported distributions since I'm preparing for a major new version which, however, will take some months to be finished. I could send you a patch for the sources or a package just for your distribution. What do you think about that? Best regards Ulrich |
From: Jonathan C. <jco...@ro...> - 2008-08-04 20:16:08
|
Hi Ulrich, > $ ls -l /dev/sda* > brw-rw---- 1 root disk 8, 0 2008-08-04 12:44 /dev/sda > brw-rw---- 1 root disk 8, 1 2008-08-04 12:44 /dev/sda1 > brw-rw---- 1 root disk 8, 3 2008-08-04 13:43 /dev/sda3 > brw-rw---- 1 root disk 8, 5 2008-08-04 12:44 /dev/sda5 sda3 is the partition I used. It is a primary partition. I belong to the disk group, but I cannot create the volume unless I run Scramdisk using sudo. Nothing is reported to /var/log/messages about the volume creation. When I kill the stalled mkfs.ext2 process, I briefly see a Scramdisk Create dialog showing volume creation 20-30% complete. Then it is covered by an error dialog "Couldn't mount device: Invalid argument". If I move that aside, I can see the value in the Scramdisk Create dialog change to 80% complete. Clicking OK in the error dialog also closes the create dialog. A straight mkfs of an ext2 filesystem on the partition works normally. Hans-Ulrich Juettner wrote: > I'm especially worried about the odd observation that scramdisk > reports the size of the whole drive not of the partition you > wanted to create the container on. If somehow the device of the > whole drive has been chosen, a possible reason of the hanging > might have been that the kernel driver has mounted the device > read only because of missing access rights. If so, it's very > odd that the container has been created that far. But in that > case you have been lucky that the device wasn't overwritten. > > In order to further investigate the problem could you please > check by "ls -l" the access rights of the devices of your whole > drive and the partition in question. Moreover, it might be > helpful to have a look at /var/log/messages what the scramdisk > kernel driver has reported on the event of the failed container > creation. > > Best regards > Ulrich > |
From: Hans-Ulrich J. <han...@t-...> - 2008-08-04 14:03:18
|
Hi Jonathan, Jonathan Coles wrote: > I just tried creating a default Windows-compatible Scramdisk container > on a partition and it worked. > There is one odd thing. The size shows up as 75Gb, the size of the > entire drive, not the 23Gb available in the empty partition. The other > partitions are still there. > > An attempt to create a smaller 15Gb ext2 Scramdisk failed. I might need > to verify that mkfs.ext2 works OK on its own. > > Jonathan Coles wrote: >> Hi Ulrich, >> >> I changed two things from the Windows compatible default: Digest SHA256 >> and file system ext2. The container size was automatically selected at >> 23Gb, the remaining space on the drive. >> >> Here's the end of "ps ax" output showing the sleeping (dead in the >> water?) processes: >> >> 6803 pts/0 R 8:27 scramdisk >> 6829 ? S 0:00 [pdflush] >> 6848 ? S 0:02 [scramdisk01] >> 6849 pts/0 S 0:00 mkfs.ext2 /dev/scramdisk/vol01 >> 6850 ? S 0:00 [pdflush] >> >> Now that I know how to avoid the lengthy mouse-waggling sessions, I can >> try a few more scenarios. Perhaps a smaller volume would work. Perhaps >> the Windows-compatible default would work. >> >> Thanks. thank you for the detailed report. Just a little information on the output of the ps command: scramdisk with PID 6803 is the running GUI, mkfs.ext2 with PID 6849 is the command started by the GUI for making the file system, the two [pdflush] processes with PID 6829 and 6850 are kernel threads generally responsible for writing back file system data, finally [scramdisk01] with PID 6848 is the kernel thread started by the scramdisk kernel driver to handle input and output requests on the first mounted container. I'm especially worried about the odd observation that scramdisk reports the size of the whole drive not of the partition you wanted to create the container on. If somehow the device of the whole drive has been chosen, a possible reason of the hanging might have been that the kernel driver has mounted the device read only because of missing access rights. If so, it's very odd that the container has been created that far. But in that case you have been lucky that the device wasn't overwritten. In order to further investigate the problem could you please check by "ls -l" the access rights of the devices of your whole drive and the partition in question. Moreover, it might be helpful to have a look at /var/log/messages what the scramdisk kernel driver has reported on the event of the failed container creation. Best regards Ulrich |
From: Jonathan C. <jco...@ro...> - 2008-07-28 15:17:52
|
I just tried creating a default Windows-compatible Scramdisk container on a partition and it worked. There is one odd thing. The size shows up as 75Gb, the size of the entire drive, not the 23Gb available in the empty partition. The other partitions are still there. An attempt to create a smaller 15Gb ext2 Scramdisk failed. I might need to verify that mkfs.ext2 works OK on its own. Jonathan Coles wrote: > Hi Ulrich, > > I changed two things from the Windows compatible default: Digest SHA256 > and file system ext2. The container size was automatically selected at > 23Gb, the remaining space on the drive. > > Here's the end of "ps ax" output showing the sleeping (dead in the > water?) processes: > > 6803 pts/0 R 8:27 scramdisk > 6829 ? S 0:00 [pdflush] > 6848 ? S 0:02 [scramdisk01] > 6849 pts/0 S 0:00 mkfs.ext2 /dev/scramdisk/vol01 > 6850 ? S 0:00 [pdflush] > > Now that I know how to avoid the lengthy mouse-waggling sessions, I can > try a few more scenarios. Perhaps a smaller volume would work. Perhaps > the Windows-compatible default would work. > > Thanks. > > Jonathan Coles wrote: > >> I have tried several times to create a Scramdisk container on a hard >> drive partition (about 24Gb). After several minutes of mouse waggling, >> Scramdisk begins encrypting and formatting the partition. This continues >> until the progress bar is near 100%. Then, the Scramdisk application >> becomes unresponsive. If you cover it with another window and then give >> it the focus again, Scramdisk does not restore its window. Running "ps >> ax" reveals that mkfs and Scramdisk are still running, but are asleep. >> >> I am running Ubuntu 8.04 with kernel 2.6.24-19 and ScramDisk 1.3.0. >> Admittedly, this one was built for kernel 2.6.24-18, but container >> creation on flash memory cards and as .svl files works as it should. >> >> Thanks. >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> SD4L-user mailing list >> SD4...@li... >> https://lists.sourceforge.net/lists/listinfo/sd4l-user >> >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > SD4L-user mailing list > SD4...@li... > https://lists.sourceforge.net/lists/listinfo/sd4l-user > > |
From: Jonathan C. <jco...@ro...> - 2008-07-28 14:09:14
|
Hi Ulrich, I changed two things from the Windows compatible default: Digest SHA256 and file system ext2. The container size was automatically selected at 23Gb, the remaining space on the drive. Here's the end of "ps ax" output showing the sleeping (dead in the water?) processes: 6803 pts/0 R 8:27 scramdisk 6829 ? S 0:00 [pdflush] 6848 ? S 0:02 [scramdisk01] 6849 pts/0 S 0:00 mkfs.ext2 /dev/scramdisk/vol01 6850 ? S 0:00 [pdflush] Now that I know how to avoid the lengthy mouse-waggling sessions, I can try a few more scenarios. Perhaps a smaller volume would work. Perhaps the Windows-compatible default would work. Thanks. Jonathan Coles wrote: > I have tried several times to create a Scramdisk container on a hard > drive partition (about 24Gb). After several minutes of mouse waggling, > Scramdisk begins encrypting and formatting the partition. This continues > until the progress bar is near 100%. Then, the Scramdisk application > becomes unresponsive. If you cover it with another window and then give > it the focus again, Scramdisk does not restore its window. Running "ps > ax" reveals that mkfs and Scramdisk are still running, but are asleep. > > I am running Ubuntu 8.04 with kernel 2.6.24-19 and ScramDisk 1.3.0. > Admittedly, this one was built for kernel 2.6.24-18, but container > creation on flash memory cards and as .svl files works as it should. > > Thanks. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > SD4L-user mailing list > SD4...@li... > https://lists.sourceforge.net/lists/listinfo/sd4l-user > > |