UNC extensionsForum: HD Install Topic: UNC extensions started by: MattF Posted by MattF on Sep. 05 2007,13:42
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. Posted by roberts on Sep. 05 2007,14:06
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. Posted by MattF on Sep. 05 2007,14:20
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. Posted by curaga on Sep. 05 2007,15:35
There are some Python extensions, could they work for you?
Posted by lucky13 on Sep. 05 2007,16:03
It's pretty straightforward once you have your compiler set up (via gcc extension):
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:
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. Posted by curaga on Sep. 05 2007,16:42
The tar.gz ver will stay, no need to mydsl-load it after the first time..
Posted by lucky13 on Sep. 05 2007,18:44
Right, "it" refers to the python-2.5 UCI.
Posted by MattF on Sep. 06 2007,06:06
Thanks. The uci testing version for 2.5 did the trick. Also thanks for the tip on re-loading it. (And I may get around to trying the compile out when I'm a bit more experienced.)I thought I had read that if I put the extension in the root directory it would automatically load up when it booted. That didn't seem to work for me though. Still, re-loading each time is fine. Thanks for the help. Posted by roberts on Sep. 06 2007,06:51
Been moved to a level 1 directory named mydsl
Posted by MattF on Sep. 06 2007,07:42
got it. thanks.
Posted by mikshaw on Sep. 06 2007,13:12
You can also make a uci permanent in a harddrive install by copying its contents:1) Mount the extension 2) Copy /opt/python-2.5 3) Unmount the extension 3) Rename the copy to /opt/python-2.5 4) Remove the extension from /mydsl There was one recent Python extension that was built including development files for compiling Python-based apps, but I can't remember if it was python-2.5.uci Posted by Juanito on Sep. 06 2007,13:20
There are header files in python-2.3.uci (actually 2.3.6) in testing and Robert's original .tar.gz (python2.3 ?) also has the headers.
|