From: Jonathan C. <jco...@ro...> - 2011-03-04 00:10:23
|
Answers in-line below... Good luck. On 11-03-03 07:47 AM, Stewart Millen wrote: > On Wed, 2011-03-02 at 06:51 -0500, Jonathan Coles wrote: > > Hi Jonathan, > > I posted the output of $ make the orevious night, but because the post > was 80k, the moderators are holding it for review for being too large. > > Didn't get home early enough to try your suggestions yet, but I figured > I could clear up some things before I did. > >> 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. > ? > > Or do you mean going into "Users and Groups" and enabling the root > account? (Not logging in as root, but enabling a root account with a > passphrase and then invoking it by the $ su - command). > >> 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. >> Your .deb file will be owned by root and be read-only, but >> that's not a problem for installation. >> >> I had to re-make ScramDisk last night because of a kernel >> upgrade. If I recall correctly, I just ran "make deb" >> without a plain "make" first. > Thanks for the help, Jonathan. > > Stewart > > > > > |