Do UNC extensions work on a HDD install? They seem not to for me. But when I started up from my boot CD they did work. Can someone confirm?
Background: I'm completely new to linux and got into it to make use of an old computer. DSL seemed to work best of various things I tried. I followed the Hard disk install instructions on the wiki exactly (I think).
More info: For example. I tried installing the Abiword UNC extension. It didn't seem to do anything. Then I booted from CD. I installed the abiword unc extension again. It worked (though not the fluxbox menu item but I'm guessing I could fix that by looking at the menu file). Then I re-installed from CD. Abiword was there! That was a surprise. Then I tried installing another UNC extension (mplayer). It didn't work. PS when I get the pop-up asking me where to install ('To Dir:') I accepted the default /tmp.
Thanks for any help.UNC extensions are ignored on a traditional hard drive installation. They were developed for merging the read-only KNOPPIX image and the ramdisk, i.e., live CD and frugal type installations.Thanks that's helpful. I'll add that info to the wiki.
Also, any suggestions on how to get Python 2.5 to work on a hard drive install? If I go to python's website and download it, I get the idea I have to compile it, but I have no clue how I would go about that.There are some Python extensions, could they work for you?
Quote
I get the idea I have to compile it, but I have no clue how I would go about that.
It's pretty straightforward once you have your compiler set up (via gcc extension):
Code Sample
./configure && make && sudo make install
You may also want to change variables to suit your needs. This, along with the standard INSTALL and README (read them both!) files in the folder which the tarball extracts, will give you some guidance:
Code Sample
./configure --help | less
IIRC, the extension for 2.5 is UCI (testing); other extensions for 2.3 are likewise tar.gz and UCI (so they also will install in /opt). It'll work on hard drive install, but you'll need to mydsl-load it whenever you want to use python and the binary won't go to a typical path -- a consideration you'll have to keep in mind if you compile anything else that requires python (usually --with-python=path-to-python). If you won't use it for anything else, the extension will probably be adequate. If you're going to use it a lot, compiling makes more sense.Next Page...
original here.