> I have trouble installing SXDE. Machine boots fine and after downloading > driver > NIC card is detected SXDE starts configuring network card and after some > delay > it stats to load data from DVD and then install hangs. Kernel seems to be > still working. > > Becuase i have low memory (256MB) i am using Solaris Express Console > install. > > Can some one test SXDE 9/07 installation with 256MB RAM machine in some kind > of > emulator? I cant get kqemu module working and without it, its too slow.
You may need to install some memory to get past the installation hump. Afterwards you can remove RAM. I have a few appliance style hardware things here that would do nicely for a test .. I may just give it a go for fun. Here are two blogs on the topic in which I *crush* Solaris into a very very small place : http://www.blastwave.org/dclarke/blog/?q=node/12 http://www.blastwave.org/dclarke/blog/?q=node/53 Oh .. one other thing to watch out for. If you are not careful you can end up with a machine which can not allocate memory to assign /dev/pts entries so perhaps you would want to allocate no more than 8 or 16 : ********************* from /etc/system ************************* * * Description : pt_max_pty * * Defines the maximum number of ptys the system offers. * * Data Type : Unsigned integer * * Default = 0 (Uses system-defined maximum) * * Range : 0 to MAXUINT * * Units is number of Logins/windows * * Dynamic? = Yes * * Validation : None * * Implicit * * Should be greater than or equal to pt_cnt. Value is not * checked until the number of ptys allocated exceeds the * value of pt_cnt. * * When to Change * * When you want to place an absolute ceiling on the number * of logins supported, even if the system could handle more * based on its current configuration values. set pt_max_pty = 8 Some other things to watch out for : ***************************************************************** * * Description : pt_cnt * * The number of available /dev/pts entries is dynamic up to * a limit determined by the amount of physical memory * available on the system. * pt_cnt is one of three variables that determines the * minimum number of logins that the system can accommodate. * The default maximum number of /dev/pts devices the system * can support is determined at boot time by computing the * number of pty structures that can fit in a percentage of * system memory (see pt_pctofmem). If pt_cnt is zero, the * system allocates up to that maximum. If pt_cnt is non-zero, * the system allocates to the greater of pt_cnt and the * default maximum. * * Data Type : Unsigned integer * Default : 0 * Range : 0 to maxpid * Units : Logins/windows * Dynamic? : No * Validation: None * * When to Change * * When you want to explicitly control the number of users * who can remotely log in to the system. set pt_cnt = 32 ********************************************************************** * * Description : pt_pctofmem * * Specifies maximum percentage of physical memory that * can be consumed by data structures to support /dev/pts * entries. * A system running a 64-bit kernel consumes 176 bytes * per /dev/pts entry. A system running a 32-bit kernel * consumes 112 bytes per /dev/pts entry. * * Default = 5 percent * set pt_pctofmem = 25 You can play with those and rapidly end up with a machine that just sits and swaps. :-P Dennis
