Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hello, I thought I post something to this forum while using Damn Small Linux. This little thing is great. I couldn't find a blank business card CD around town so I went with a Mini-CDR. No biggie! No pun intended!
There's a text file that talks about it inside the CD. I have not tried to install onto a hard drive myself. For me it will defeat the purpose of having a Live Linux Distro on CD. So far I've successfully loaded that CD on a bunch of different hardware configurations at work and at home. It rocks! I guess if you have the need for that small of a Linux distro to run on small hard drive, then that's another excellent use. Try the web site and see if they have something on how to do it:
Originally posted by hecresper There's a text file that talks about it inside the CD. I have not tried to install onto a hard drive myself. For me it will defeat the purpose of having a Live Linux Distro on CD. So far I've successfully loaded that CD on a bunch of different hardware configurations at work and at home. It rocks! I guess if you have the need for that small of a Linux distro to run on small hard drive, then that's another excellent use. Try the web site and see if they have something on how to do it:
here's the situation. i have a p166 mb (ru430hx - lpx form factor+ daughter bd w/ 2 isa, and 2 pci slots) w/ 98meg ram, that i'm trying to set up for a DC project. i did a mod to the case that it was originally in for a micro atx athlon xp/ ddr mb, which has left it as a pile of pc parts. so i have to open a case and connect to the cd-rom, and floppy of the case (no spares), and use a spare 540 meg hdd. i have a 1.6gig hdd that fails a wdc evaluation (code 0207), but i can zero fill it w/ seagate disk wizard, and format it- but it's questionable. so this is what happens, all my cd-s that i go for aren't read in that cd-rom drive, except for SOT (2002) linux, and damn small linux. i wanted to put vector linux on it, but same as all my other cd's it comes up w/ some isolinux- winging it error (not correct el torrito, or outside of the cd-roms capacity, or the cd-rom is screwed up???). now the way i see it sot linux puts a grub loader first (it's actually a cdr/w disk), and i would think that damn small linux put's something different for the bios to see. at this point, i see it's a bios issue, or the el torrito standard is some how not read correctly (perhaps all the disks are larger than the standard that the cd-rom is designed for). perhaps it's the 600+ meg disks verses the 700meg disks??? anyway, the only two distros that i currently have, and have a desire for are vector linux 3.2, and damn small. damn small on the hdd, plus a DC project would rock. the smaller the better. perhaps it can be tweaked for the diskless/ headless crunch farm boys (it's so small- easily fit in a ram drive!).
ok, thanks for the info. i looked around for documentation at damn small linux's web site, and in the distro itself- perhaps i need to pop it in, and find a read me like i have to believe that your suggesting.
btw, i tried SOT on that flakey 1.6gig hdd, and i think i either give up on it, or someone that knows what an error 0207 means, can suggest something that i can do to ressurrect it?
ok, here's an update. sent an e-mail to john at damnsmall linux regarding how to install on hdd. his reply: "There is a short HOWTO in the root/ dir -- it is a little out of date, but you will get the idea."
ok, what i did was pull up a terminal, and typed in dir<enter>, and got a line:
digiot- fastest reply in the west (richocet sound effect)
anyway, i am actually not in windows, but w/ in damn small, using rxvt.
less HD_install_HOWTO.txt tab, and HD tab pulls up a list of topics including the desired one (i have to hold down tab to get the topic list),
less HD tab adds the remaining line _install_HOWTO.txt to HD, if i then hit enter, it comes up "bash: less: command not found.
i tried tab, then enter, and tab + enter w/ o any luck
i also tried 'HD_install_HOWTO.txt | more' in rxvt. perhaps i'll stick the cd in the windows cd-rom drive, and try some command prompt just to see what comes up?
tried in windows at command prompt w/o luck - it's actually 0.3.10 version in the windows cd drive, and damnsmall is running in a seperate comp (0.4.2)
btw, i did try to install firebird, and use it to give some screen shots, but it looks like it didn't load. possible that the ethernet cable that i crimped up needs to be tested (i didn't make a tester yet?), to verify what's at fault. perhaps i'll try 0.3.10 version that i have to see if any different.
Wait, that can't be a directory listing. Not if its supposed to be the / listing.
I think I'm confused. You're trying to display the contents of a text file on the root of your filesystem? This can't be this hard. How are you posting? If nothing else, you could open it with your browser. 'cd /' and 'ls' and you see 'HD_install_HOWTO.txt'? And you can't 'less' it? Or 'vi HD_install_HOWTO.txt' or 'mc HD_install_HOWTO.txt' or 'mybrowser HD_install_HOWTO.txt'? I'm lost. If 'ls -al' shows lHD_install_HOWTO.txt to be larger than 0 bytes and 'file HD_install_HOWTO.txt' shows a text file, then it's got to open with virtually anything.
digiot, thanks for the reply. i don't have damnsmall linux booted up right now, as i'm in the process of determining if a used floppy that i just bought is bad (it is), which was supposed to keep me from swapping stuff around. i need to get things sorted out first, then i'll retry your command recommendations.
did it. for some reason, it was the first thing i tried out of your list of possiblities. i'll try the other commands that you mentioned as well to see what works, and if somehow different. thanks for sticking w/ it!
well, it's not over. tried the command to set up a format on the partitions that i created, and i must be doing something either wrong, or the instructions aren't for as green a noob as myself. i actually created the partitions w/ aefdisk due to familiarity, but i just sa that cfdisk<enter> in a shell pulls up the program (nice!)!
ok, after the partitions are created, it states to execute
and enter the just created partition (ec. /dev/sda2)- not sure if that's supposed to be ex. /dev/sda2, or some linux code line
anyway, the ./dsl-hdinstall line in a shell isn't working- should this go in a command line instead (saw a command line feature in mandrake).
ok i tried some alternatives- had the thought of knoppix, so i tried
and that worked (varies a little from the instructions- try variables- is this how it usually is???).
ok, created the file system (/ (root) which is ext2), and it's copying the cd at this moment. one thing i did was to create a swap space, which wasn't a part of the instructions. think that i'd like to have a swap partition- esp. as this is for a DC project, which more than likely will need it. perhaps i can do this after? what is the command for formatting swap?
ok,"the installation process is finished"
which will probably mean mkliloboot- here goes- asked for the root partition, which i added (/dev/hda1). states that the liloboot installation is finished.
time to reboot, to see what happens! (perhaps i shouldn't smile just yet).
some concernes are that i will desire to set up a seperate user account, and a swap partition.
question- if in a shell, does the ./ mean to execute as root?
No - your current directory is not on the path (I mean, unless you're current directory happens to be on the path anyway. Point is, being in a directory doesn't automatically put it on your path. So the ./ indicates you want to execute the command after the slash in the current directory (the '.'). It's really weird to me that that command didn't work and leaving it off did unless you weren't in the right directory when you ran the command and the command was in your path anyway. But if it works... *shrug*
I don't recognize 'ec. /dev/sda2)' as code - I think you're right and it's just a typo for ex. (example) - and so you need to substitute what yours actually is there.
And I should have thought of more. It's just that less is so much more. *g* But *every* system that I know of has 'vi' because it's usually just a symlink to whatever basic editor is on the system.