On Friday 03 June 2016 15:32:14 David Wright wrote:
> I did discover that it's obvious if you try to Xorg -configure
> while X is running
There's a hole in the bucket, dear Eliza
This is why I was trying to do it at single user level, to be *certain* that X
wasn't running. :-)
X is there,
On Fri 03 Jun 2016 at 10:28:32 (+0100), Lisi Reisz wrote:
> On Friday 03 June 2016 10:07:13 Lisi Reisz wrote:
> > I wanted to log in without X
> > and runlevel 1 has no X.
>
> So I next tried to shut X down. I have tried this before without success, so
> I googled again, and gathered that what
Lisi Reisz wrote:
> On Friday 03 June 2016 10:07:13 Lisi Reisz wrote:
>> I wanted to log in without X
>> and runlevel 1 has no X.
>
> So I next tried to shut X down. I have tried this before without success, so
> I googled again, and gathered that what I needed to do in fact was shut down
> my
On Friday 03 June 2016 09:59:29 Lisi Reisz wrote:
> I didn't know what foo was anyway.
I meant that I didn't know specifically what foo was in that context.
Lisi
On Friday 03 June 2016 10:07:13 Lisi Reisz wrote:
> I wanted to log in without X
> and runlevel 1 has no X.
So I next tried to shut X down. I have tried this before without success, so
I googled again, and gathered that what I needed to do in fact was shut down
my dm. See:
https://wiki.debia
On Wednesday 01 June 2016 18:52:40 David Wright wrote:
> AIUI one can configure a box to run X in all runlevels but 1;
> however, there's no need to do it that way. None of my machines
> run X automatically at runlevel 2: I have to use startx.
This is indubitably true, but irrelevant to the proble
On Wednesday 01 June 2016 14:43:29 Mark Fletcher wrote:
> On Wed, Jun 1, 2016 at 9:10 PM Dan Purgert wrote:
> > Lisi Reisz wrote:
> > > On Tuesday 31 May 2016 23:56:02 Richard Hector wrote:
> > >> On 01/06/16 07:31, Lisi Reisz wrote:
> > >> > Now to do what I really wanted to do all along, and ssh
On Wednesday 01 June 2016 23:07:55 David Wright wrote:
> On Tue 31 May 2016 at 20:31:32 (+0100), Lisi Reisz wrote:
> > On Thursday 31 March 2016 15:08:24 Brian wrote:
> > > On Thu 31 Mar 2016 at 13:27:35 +0100, Lisi Reisz wrote:
> > > > On Thursday 31 March 2016 12:28:57 to...@tuxteam.de wrote:
> >
David Wright wrote:
> On Wed 01 Jun 2016 at 14:47:11 (-), Dan Purgert wrote:
>> [snip]
>>
>> I came "late" to the party myself, and missed the post where I imagine
>> why Lisi is after runlevel 1.
>>
>> Personally, with the exception of my laptop, everything starts in
>> runlevel 3 here.
>
On Tue 31 May 2016 at 20:31:32 (+0100), Lisi Reisz wrote:
> On Thursday 31 March 2016 15:08:24 Brian wrote:
> > On Thu 31 Mar 2016 at 13:27:35 +0100, Lisi Reisz wrote:
> > > On Thursday 31 March 2016 12:28:57 to...@tuxteam.de wrote:
> > > > 1. Each computer should have an SSH server running (on Deb
On Wed 01 Jun 2016 at 14:47:11 (-), Dan Purgert wrote:
> Mark Fletcher wrote:
> > --001a114056c6437ae5053437ad41
> > Content-Type: text/plain; charset=UTF-8
> >
> > On Wed, Jun 1, 2016 at 9:10 PM Dan Purgert wrote:
> >
> >> Lisi Reisz wrote:
> >> > On Tuesday 31 May 2016 23:56:02 Richard Hecto
Mark Fletcher wrote:
> --001a114056c6437ae5053437ad41
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Jun 1, 2016 at 9:10 PM Dan Purgert wrote:
>
>> Lisi Reisz wrote:
>> > On Tuesday 31 May 2016 23:56:02 Richard Hector wrote:
>> >> On 01/06/16 07:31, Lisi Reisz wrote:
>> >> > Now to do what
On Wed, Jun 1, 2016 at 9:10 PM Dan Purgert wrote:
> Lisi Reisz wrote:
> > On Tuesday 31 May 2016 23:56:02 Richard Hector wrote:
> >> On 01/06/16 07:31, Lisi Reisz wrote:
> >> > Now to do what I really wanted to do all along, and ssh in to run
> level
> >> > one as root:
> >> >
> >> > lisi@Tux-II:
Lisi Reisz wrote:
> On Tuesday 31 May 2016 23:56:02 Richard Hector wrote:
>> On 01/06/16 07:31, Lisi Reisz wrote:
>> > Now to do what I really wanted to do all along, and ssh in to run level
>> > one as root:
>> >
>> > lisi@Tux-II:~$ ssh root@192.168.0.5
>> > ssh: connect to host 192.168.0.5 port 2
On Wednesday 01 June 2016 01:20:52 John Hasler wrote:
> Lisi writes:
> > The pipe symbol doesn't work on the keyboard at present attached
>
> Then put the output of ps in a file and search that.
The small part of the problem I am trying to solve at this precise minute is
that I am working almost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/06/16 12:20, John Hasler wrote:
> Lisi writes:
>> The pipe symbol doesn't work on the keyboard at present attached
>
> Then put the output of ps in a file and search that.
>
Or for a general solution to a faulty key, since this is on the
con
On Tue, 31 May 2016 23:27:36 +0100
Lisi Reisz wrote:
>
> Starting Nmap 6.00 ( http://nmap.org ) at 2016-05-31 23:14 BST
> Nmap done: 1 IP address (0 hosts up) scanned in 0.52 seconds
> root@Tux-II:/home/lisi# nmap 192.168.0.5 -Pn 22
For future reference, this should have been nmap 192.168.0.5
On Wednesday 01 June 2016 00:42:47 Stephen Powell wrote:
> On Tue, May 31, 2016, at 19:25, Lisi Reisz wrote:
> > ...
> > Assuming that sshd is actually running at that stage, which it looks as
> > though it isn't
> > ...
>
> Looks as though I've given you mostly information that you don't need.
> S
On Tue, May 31, 2016, at 19:25, Lisi Reisz wrote:
> ...
> Assuming that sshd is actually running at that stage, which it looks as
> though
> it isn't
> ...
Looks as though I've given you mostly information that you don't need.
Sorry about that. At the risk of doing so again, here's how you can
On Tuesday 31 May 2016 23:56:39 Stephen Powell wrote:
> On Tue, May 31, 2016, at 15:31, Lisi Reisz wrote:
> > ...
> > So I need static IPs fast!
> > ...
>
> (The above was actually quoted from an earlier post).
> If you want to convert your computers to use static IP addresses, you might
> want to
On Tuesday 31 May 2016 23:56:02 Richard Hector wrote:
> On 01/06/16 07:31, Lisi Reisz wrote:
> > Now to do what I really wanted to do all along, and ssh in to run level
> > one as root:
> >
> > lisi@Tux-II:~$ ssh root@192.168.0.5
> > ssh: connect to host 192.168.0.5 port 22: No route to host
> > li
On Tue, May 31, 2016, at 15:31, Lisi Reisz wrote:
> ...
> So I need static IPs fast!
> ...
(The above was actually quoted from an earlier post).
If you want to convert your computers to use static IP addresses, you might
want to take a look at the following web page:
http://www.stevesdebianstu
On 01/06/16 07:31, Lisi Reisz wrote:
> Now to do what I really wanted to do all along, and ssh in to run level one
> as
> root:
>
> lisi@Tux-II:~$ ssh root@192.168.0.5
> ssh: connect to host 192.168.0.5 port 22: No route to host
> lisi@Tux-II:~$ ssh lisi@192.168.0.5
Run level one? AKA single us
On Tuesday 31 May 2016 21:51:30 Joe wrote:
> On Tue, 31 May 2016 20:31:32 +0100
>
> Lisi Reisz wrote:
> > ---
> > Now to do what I really wanted to do all along, and ssh in to run
> > level one as root:
> >
> > lisi@Tux-II:~$ ssh root@192.168.0.5
> > ssh
On Tue, 31 May 2016 20:31:32 +0100
Lisi Reisz wrote:
> ---
> Now to do what I really wanted to do all along, and ssh in to run
> level one as root:
>
> lisi@Tux-II:~$ ssh root@192.168.0.5
> ssh: connect to host 192.168.0.5 port 22: No route to host
>
On Thursday 31 March 2016 15:08:24 Brian wrote:
> On Thu 31 Mar 2016 at 13:27:35 +0100, Lisi Reisz wrote:
> > On Thursday 31 March 2016 12:28:57 to...@tuxteam.de wrote:
> > > 1. Each computer should have an SSH server running (on Debian that
> > > would be package openssh-server: in Debian it has p
On Thu 31 Mar 2016 at 14:34:47 (+0200), to...@tuxteam.de wrote:
> On Thu, Mar 31, 2016 at 01:27:35PM +0100, Lisi Reisz wrote:
> > It is installed and running. I can ssh from Eros, but not into it. If I
> > just
> > try to ssh from Tux-II to Eros, I get the error "Could not connect to host
> >
On Thu, 31 Mar 2016, Lisi Reisz wrote:
So I need static IPs fast! or a hosts file?
That's how I do it. Only make that "or" above an "and!"
Also, liberal use of public-keys practically automates the whole
thing, so that you don't have to bother with pesky passwords on
your private 'net.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 31, 2016 at 02:40:58PM +0100, Brian wrote:
> On Thu 31 Mar 2016 at 14:38:05 +0200, to...@tuxteam.de wrote:
>
> > On Thu, Mar 31, 2016 at 01:32:05PM +0100, Brian wrote:
> >
> > [...]
> >
> > > There is also dropbear as a lightweight SSH2
On Thu 31 Mar 2016 at 13:27:35 +0100, Lisi Reisz wrote:
> On Thursday 31 March 2016 12:28:57 to...@tuxteam.de wrote:
>
> > 1. Each computer should have an SSH server running (on Debian that would
> >be package openssh-server: in Debian it has priority "optional": I'd
> >double-check that
On Thu 31 Mar 2016 at 14:38:05 +0200, to...@tuxteam.de wrote:
> On Thu, Mar 31, 2016 at 01:32:05PM +0100, Brian wrote:
>
> [...]
>
> > There is also dropbear as a lightweight SSH2 server and client. Using
> > it in preference to openssh is useful for resource constrained machines.
>
> Yes, ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 31, 2016 at 01:32:05PM +0100, Brian wrote:
[...]
> There is also dropbear as a lightweight SSH2 server and client. Using
> it in preference to openssh is useful for resource constrained machines.
Yes, there are nifty tricks like embeddin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 31, 2016 at 01:27:35PM +0100, Lisi Reisz wrote:
> Great! Thankl you! I now have a starting point for my questions.
>
> On Thursday 31 March 2016 12:28:57 to...@tuxteam.de wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
>
On Thu 31 Mar 2016 at 13:28:57 +0200, to...@tuxteam.de wrote:
> On Thu, Mar 31, 2016 at 12:43:49PM +0100, Lisi Reisz wrote:
> > I want all the computers on my private network to be able to shh into each
> > other. In Jessie, what do I have to do where in what config file?
> > Presumably some p
Great! Thankl you! I now have a starting point for my questions.
On Thursday 31 March 2016 12:28:57 to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Mar 31, 2016 at 12:43:49PM +0100, Lisi Reisz wrote:
> > I want all the computers on my private network to be a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 31, 2016 at 12:43:49PM +0100, Lisi Reisz wrote:
> I want all the computers on my private network to be able to shh into each
> other. In Jessie, what do I have to do where in what config file?
> Presumably some port is shut??
0. Each c
I want all the computers on my private network to be able to shh into each
other. In Jessie, what do I have to do where in what config file?
Presumably some port is shut??
Lisi
37 matches
Mail list logo
