)

Well, I thought the answer to how to make two live distros "communicate" would be rather straightforward, so I neglected giving my reason. On my main machine, with a Nvidia-based Gigabyte mboard and a Radeon X600 video card, Frugalware Live boots X with a frozen mouse. Incidentally(?) the same happens on my old Compaq Presario box. In order to perhaps help the developer find out what is going on, I am trying to fish out the "Xorg.0.log", which only exists while the system is booted. This was successful with the Compaq, but since I don't have a Linux with ssh installed on the Compaq, I thought I would try using a live distro to grab the log from my Gigabyte machine...

The main problem is that I can't get back to a root or other prompt once the Frugalware Live X has booted - not even with another tty.

As a Linux newbie I have tried Ubuntu, Mandriva and PCLOS, and I like them all, but I thought I might be forced to learn a little bit more by trying a Slackware variant. I really like Bluewhite64 - what I understand of it - but I still have PCLOS installed too. Nothing beats Synaptic for comfort!

Oh, about the "service sshd restart" - this is probably the correct invocation in Frugalware, but I need the "sesam-sesam" for SLAX (or Wolvix), where there's no preconfigured user...

I am sorry, but these strange distros mean nothing to me. I am sure their developers are having fun, and I hope you are too, but I think it's time for me to butt out if you are having to invoke commands like sesam-sesam.

I appreciate your enthusiasm, and hope you enjoy yourself, learn and contribute, but all this is getting a bit too "fringe" for me.

Best wishes

Whoa, we need to back up a couple steps here.

Good. This means sshd is running.

Good. This means we're not doing any filtering.

This is not ok. 169.254.0.0/16 is link-local address space, and you are getting an address in this range because you aren't able to get a successful offer via dhcp.

Until you resolve that problem you're not going to be ssh'ing to or from anywhere.

Earlier you said:
What happened to those two?

OK, that's Frugalware Live on my Gigabyte machine. Does not happen with Wolvix and SLAX. Since it is the Frugalware distro I am trying to work with, it seems I can stop trying then.


I used them in order to find out if connecting two live distros is at all possible. Perhaps it is, after all, but I needed to connect to the Frugalware one. If that is not possible, given that it does not get a workable inet address, most of the point of this exercise is gone. Thanks a lot for your help anyway!

Thanks, and thanks for trying to help!

The "sesam-sesam" was just me being 'funny'

Looks like we must all give up on this.

Yes, it is possible. And it's not difficult. Let us know if you're able to get your frugalware box working as a dhcp client. (In other words, you should get a 10.0.0.0/24 address like the other two.)

Alternatively, burn another copy of one of the working live cds and let us know when that's up and running with a proper IP address.

The other two do get proper IP addresses on this box; Frugalware doesn't. The problem is how to make Frugalware get a usable address, it seems, but I wouldn't know where to even start... Frugalware does get a proper address on my old Compaq, though, but that doesn't solve my particular problem. Another question is how much time and effort I should spend on this "academic" problem...

If the "academic problem" is: how can I ssh between two live cd systems? Then I'd say either use frugalware with the old Compaq, or dump frugalware and use something else.

If the "academic problem" is: how can I ssh between two live cd systems, and the sshd server side has to be frugalware on this particular box and no other? Then I'd agree with your rhetorical question -- how much effort is this worth?

I may have been too unclear

Yes, the Linux OS I want to connect *to*, *has* to be Frugalware Live on *this* box. The reason is that Frugalware Live boots to KDE with a frozen mouse and I therefore want to fish out Frugalware's "Xorg.0.log". I could do this in Frugalware itself, had it not been for the fact that I am unable to get (to) a CLI prompt after X has been started (producing the log).

SSH'ing to Frugalware live worked fine on my other machine, but on this machine Frugalware is apparently being assigned an unworkable IP address. Or do you think I could connect to that address with some kind of remote connection program?

So, unless you can think of a(nother) way out, I am stuck. Now, I am not a Frugalware user, but thought I should give something back to "the community" for a change. Oh well.

Can you use CTRL-ALT-F2 on your keyboard to get to terminal mode to read the file? Or is more than the mouse frozen? How about CTRL-ALT-BACKSPACE to exit X?

Well, I said in an earlier post that changing tty does not work (CTRL-ALT-F2 or F3, etc.). It seems to change to a new tty: the frozen mouse disappears, but I only get a black screen - no prompt. However, I can issue Ctrl-Alt-Del, something which does not work on the screen with the frozen mouse (tty0, or is that tty1?). Ctrl-Alt-Backspace does not work on the initial screen either. Then there is the problem with a faulty IP address. I won't pursue this anymore.

So this is not just an issue with a "frozen mouse".
And these commands result in what?

Are you able to pass "noapic" to the kernel at boot?
Or "acpi=off"?
Or "nodma"?

These are options that have made live distributions work for me.

You are probably fighting with a known hardware issue.

Obviously not.

Well, that depends on how I start X. I'd have to make some boots with the live cd in order to give accurate descriptions, but I've thrown Frugalware in the dustbin.

I did try with acpi on and off, but there was no difference.

The developer told me Frugalware 0.8 had not been tested on a Nvidia-based motherboard, which is what I have. After it turned out that Frugalware does not get a correct IP (LAN) address, I have heard nothing from him. This tells me I should not waste more time on this distro.

Correct me if I am wrong, but this sounds a bit like "let me help you out, but if I am not up to the task then the hell with you".
Under what circumstances were you going to "give something back"?

Perhaps you should read this thread in full?
Anyway - the developer asked me to try and get the Xorg.0.log from the live OS, and we spent a couple of days trying various methods. This made me come here and ask. After telling the developer that Frugalware *also* failed to get a workable IP address, I've heard no more from him. What you make of that, is irrelevant. If you have a solution, by all means, share it.