This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When installing the NB 4.1 RCs (both 1 and 2), the installer gives the following message after specifying that the install should be under /usr/local and picking the JVM: WARNING: / partition has insufficient space to install the items selected. 8.9 MB additional space would be needed to install the selected items. At that moment my / partition has about 6.5Mb available I have 2 issues with this message: 1. My / is indeed rather small and full, but I wouldn't know why that is a problem as the installation is in /usr/local (a separate filesystem), /tmp is in swap (tmpfs) and /var/tmp on another partition with sufficient diskspace 2. The message states this as a warning, but it is preventing me to commence with the installation. This should either not be a warning (as I can not continue) but an error, or allow me to proceed anyway. If I clean up my / (by temporarily removing files), the installation does work properly. As far as I can see, no files are created in / during the installation. For the NB 4.1RC packages I can still work around this, but this does prevent me to install the Sun Java Application Server cobundle.
Installer uses some space in temp dir /tmp which is usually located on / partition. (InstallShield native installer launcher puts installer jar in /tmp dir.) How do you know your /tmp is not at / but at swap space? Message is generated by InstallShield. It is standard way how it is done.
I know that /tmp is in swap as that is how I set it up :-) df -k /tmp shows: Filesystem 1K-blocks Used Available Use% Mounted on swap 524288 2204 522084 1% /tmp mount shows that /tmp is mounted in swap as well: swap on /tmp type tmpfs (rw,size=512m,mode=1777) If you need additional information, just let me know.
Ok. In such case I do not know why installer requires free space on /. I will try to setup some testing machine in the same way to reproduce it. Anyway I am afraid I will not be able to change this behavior as this this is standard install check (including diskspace check) provided by InstallShield. (Is there some easy way how to setup /tmp on another patition? Say I have some data partition vfat but I can also use ext3. Can I use following line in fstab?: /dev/hda6 /tmp ext3 defaults 1 1 Shall I do anything with content of /tmp on /? I know /tmp dir on / will be mapped on another partition. But is it possible to do it this way? Please can you also run installer with command line switch -is:log <log file> eg. -is:log a.log? It will create log file from native launcher with system properties set to installer including tempdir. Attach resulting file here using 'Create a new attachment'. Thanks.
Created attachment 22103 [details] Logfile when running the 4.1 installer on a system with /tmp in swap
OK, it seems you have pointed me in the right direction, but I am not quite sure where the problem is though.... I just downloaded and installed the NB4.1 release version. The problem still occurs without specifying any command-line parameters (see the attached log). I am able to install normally however when I add -is:tempdir /var/tmp to the command line of the installer, while when I add -is:tempdir /tmp the problem reoccurs. Apparently this has something to do with the fact that /tmp is not on a normal device but in swap (so commands like df and mount return output a device name without a / in it). providing the -is:tempdir parameter on the command line when starting the installer eliminates this problem and is alsa a work-around for this.
I am goign to report this to InstallShield. I have 2 questions: 1.Does it happen with current dev build installer? (In summer we migrated to new version of InstallShield so I need to confirm that this is still valid issue.) 2.How can I set tmp to swap? Does it mean that your swap is not used by OS as swap? Can you show me list of your partitions from fdisk and also /etc/fstab? Thanks
This bugreport is passed to InstallShield. Hopefuly they will fix it somehow. It is out of our hands. Closing.