java.is.for.desktop's questions

I have OpenSuse 11.4.

I start some on-boot scripts inside /etc/init/boot.local.

Where could I move those scripts so that they would be started after all (most) environment variables got initialized?

These scripts need to be started really once, so things such as /etc/profile.local aren't candidates.

I try to start Sonar, which searches for Java in some strange way (instead just by look up JAVA_HOME), and it fails to find Java (logs don't tell me exactly why). From command line, after boot, it can be started (as root and as user).

I suppose, there are some environment variables which get initialized inside services. Can it be that way?

EDIT: sonar.sh from sonar/bin/linux-x86-64
EDIT: sonar.log from sonar/logs

Practically, I need a process which behaves, as if I had pressed Ctrl+Z just after it started.

Hopefully, it is possible to do such thing using a shell script.

(Also, knowing the resulting PID would be great, so I could continue the process afterwards.)

I am using SSHFS to transfer files under Linux between my notebook and my desktop machine. It's easier then NFS because one doesn't have to configure mount points and permissions a priori.

Now, using SSHFS is slower than I would expect from a 100MBit Ethernet connection (sadly, the notebook has no Gigabit Ethernet). I get about 10MiB/sec, instead of 12.5MiB/sec. Can the overhead of protocols "steel" the "rest" (which would be 2.5MiB/sec)?

Switching from IPv4 to IPv6 didn't improved the speed. Using -C for compression made the process even slower.

SSHFS allows to pass parameters to underlying SSH (using -o SSHOPT=VAL). Well, there are a lot of SSH parameters there.
From experience, which of these parameters could improve speed of an SSHFS connection?

I installed OpenSuse one year ago on my notebook. I created all partitions except /boot inside an LVM partition. I enabled encryption for it during setup. The system asked me a password on each boot later. Everything seemed fine...

But one day I wanted to cancel the boot process and did it with SysRq REISUB. During entering this combination, the system suddenly continued to boot without any password being entered. I had no /home and no swap, but / was mounted! I checked multiple times, it was inside an "encrypted" physical LVM volume.

Later I found out that OpenSuse can't encrypt / at all. There is an option to enable encryption for each logical volume, and indeed it fails for /.

Later I tried Fedora. The options during partitioning were misleading by same means. I could enable "encryption" of a physical volume and each logical subvolume. With the exception that Fedora actually allowed to encrypt /.

Question: What's the point of setting up "encryption" for a physical LVM volume, when it doesn't imply (real) encryption of its logical subvolumes? Did I get something wrong in this whole concept?

I know that I can blacklist a module in /etc/modprobe.conf or /etc/modprobe.d/blacklist, but I have a nasty module which loads before the filesystems are mounted (except /boot of course), so I assume, /etc will not yet be read by then.

Can I prevent a module from loading using a kernel boot parameter?
(I'm using GRUB)

Or are there other ways to do this?

Thank you!

Which characters are allowed and which of them must be escaped on the command line in different operating systems?