| |
| |
| |
|
Page: 1 2 3 4 5
Comments:
<0> Oh, rly?
<0> Well, have to test that then.
<0> It does not matter even it is BSD if I can make that computer work fine without hard disk on that machine
<1> I know for certain that / over nfs works in 2.0 because I've done it
<0> It makes terrible sound and I want diskless comp :)
<0> Oh. In what distro?
<1> but that was many many moons ago
<1> back then I was using slackware 2 from memory
<1> im sure if you used a search engine you'd find a good mini dist for doing what you want
<0> Well, can I install graphical modes to them?
<1> depends on the term & the dist
<0> Right.
<1> if it's an old beefed up wyse50 term then my guess is no :)
<1> ]all the ones I've seen were mono running off serial anyhow
<0> Well, that computer I try to make diskless is 300 MHz AMD-K6 with 256 Mt
<1> the term I used was basically a 486 with 17" graphics term attached
<1> you have a bootrom that tries too mount / via nfs?
<1> & that works?
<0> Bootrom?
<1> yes plugs into your nic too tell machine too grab / via tftp or why from nfs
<0> I bot that 300 MHz computer with CD wich load EtherBoot with my network card support. Then it looks around and finds my DHCP-server (Same as NFS server) and loads kernel and initrd via TFTP
<0> bot = boot
<0> wich = which
<1> oh ok thats different & not a diskless boot then
<0> Dang, I can't write today fine
<0> Yep, not totally diskless but silent enough for me :)
<0> I can take cd off later ;)
<0> But hard disk
<1> diskless means no disk, not cd, not floppy, not hdd
<0> Yep
<0> But that sound of hard disk, it really drives me crzy
<0> Too noisy
<1> so get a different disk or boot into ram & then power it down
<0> Booting in the ram... I have thinked that lot
<0> But I don't fully understand that
<1> avoid nfs / because you genberally need a bootrom too do it
<0> I can make it work
<0> I mean, if I use to load root in /dev/ram0 it works fine
<0> But, I need to use graphical mode etc, so that is why I need root over NDFS
<0> NFS, even.
<1> or just boot off cd into ram & nfs whatever off you need off the server
<0> Or can it be done in other ways?
<1> I've done that too which is fairly easy, except I did it via floppy :)
<1> so burn a cd with your kernel that boots off rom & mounts whatever you need off the server
<1> running off a live cd should be fairly straight forward but I've always done it the old fashioned way
<0> So... If I just ask stupid question, can you answer? :D My point is that I need to use that 300 MHz computer and KDE but I don't want to use Hard Disk on it. I want that I can edit my settings etc, so that is wht I don't use liveCD
<0> Should I use Root Over NFS or just load it in RAM?
<0> :/
<1> ok you're only wanting x on the box so / can run outa ram
<0> Too little ram?
<1> how little?
<0> 256 Mt of RAM
<1> hahaha, I was thinking 8 or 16meg
<0> :D
<0> I don't even think of KDE or GNome if I have no more memory than 128
<1> the beuty of / on cd is noone can break it & a reboot fixes any hacking attempts :)
<0> Right, but I don't care about hackers
<0> It is just test computer anyway
<0> And I live alone
<0> And keep my doors locked :D
<1> anyway my caffiene is taking effect n I must sleep while I can
<1> nini
<0> Nuight
<0> Night, even.
<0> And thanks
<2> <rant>guess linus is very right with finally starting bug hunting: mavel gigabit nic being slower than a wlan link, serial_cs generating insanly high error rates making it unusable, sda giving I/O errors on startup, acpi giving parse/exec errors, no sound via realtek alc 861 chipset</rant>
<2> <rant>guess i would never have switched to linux if it would have been in this miserable state eight years ago :-(</rant>
<3> hmm.. I'm having problems with kacpid taking up all cpu in 2.6.16 if I compile acpi stuff as modules.. is this a known problem?
<4> Hi there, is there a way to look at how much memory linux kernel takes?
Return to
#kernel
or
Go to some related
logs:
#linux
sarge etch upgrade 64 bit
pygtk installed but not visible from python
Compiler is not available to compile modules
debian remove netbase
#linux
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-mis
#linux
fglrx(0): Hardware has already been locked.
unable to find /dev/agpgart
|
|