Re: [SD4L-user] Questions about compiling Scramdisk from Source

[Stewart M. <smm...@gm...>]

On Thu, 2011-03-03 at 19:10 -0500, Jonathan Coles wrote:

> >> I have experienced the same thing. Try running the make as
> >> root.  That solved the problem for me. You might want to run
> >> "make clean" first to make sure that everything gets rebuilt.
> > When you say "trying running 'make' as root, do you mean:
> >
> > $ sudo make
> Yes.

*Eureka*! It worked! Thanks Jonathan.

Compiling SD4L from source code proved to be surprisingly easy, like
most riddles and problems--once you see the answer. 

Hans-Ulrich, I created the .deb file for 2.6.32-29 for Ubuntu. I would
be happy to share any Scramdisk .deb files I create, provided that they
are suitable for distribution. Reading this page, however, makes me
wonder if they would be as-is when created on my system this way:

https://wiki.ubuntu.com/PackagingGuide/Complete

Some of these requirements I think you've already addressed in your
distribution, but I'm such a "caveman" at this. I still think it would
be wonderful if SD4L were included amongst the maintained Ubuntu program
distribution, as it's better maintained than some programs that *are*
listed.

> >> You could even try starting your current ScramDisk -- the
> >> one that has the problem -- as root. If it works, then there
> >> really isn't another problem. Just remake the .deb as root
> >> and reinstall.
> > you mean:
> >
> > $ gksudo scramdisk
> >
> > I take it?
> I use sudo when I need root powers. I'm not sure what the 
> difference is between sudo and gksudo.
> Usually I use the shell command sdmount to mount my container.
> So, my test would have been "sudo sdmount ...."
> If you prefer the graphical version, "sudo scramdisk" should 
> work too.

http://www.psychocats.net/ubuntu/graphicalsudo

Explains the difference, and why it's generally better to use gksudo
instead of sudo for graphical applications. 

Once again, thanks for all the help.

Stewart