On Sat, 21 Jul 2018 15:42:41 -0400
Gene Heskett wrote:
> > https://odroidinc.com/products/odroid-xu4
>
> I have one, bricked, it has a uefi bios and at the time, the linux
> installer had no clue how to deal with it. The only option I could find
> in the bios was to disable the tcp chip, which
On Tuesday 24 July 2018 17:19:28 Mark Morgan Lloyd wrote:
> On 24/07/18 20:45, Gene Heskett wrote:
> > On Tuesday 24 July 2018 14:23:33 Mark Morgan Lloyd wrote:
> >
> > haven't tried the ssh -v, which machine? The output of service ssh
> > status, on the pi looks legit as its the log of successful
On Tuesday 24 July 2018 16:40:38 Mark Morgan Lloyd wrote:
> On 24/07/18 20:15, Gene Heskett wrote:
> > On Tuesday 24 July 2018 14:29:49 Mark Morgan Lloyd wrote:
> >> So you get the password prompt which is actually issued by your SSH
> >> client. The two things I'd suggest are (i) if you have one
On 24/07/18 20:45, Gene Heskett wrote:
On Tuesday 24 July 2018 14:23:33 Mark Morgan Lloyd wrote:
haven't tried the ssh -v, which machine? The output of service ssh
status, on the pi looks legit as its the log of successfull stuff from
the data there.
On the machine you run ssh on, obviously
On 24/07/18 20:15, Gene Heskett wrote:
On Tuesday 24 July 2018 14:29:49 Mark Morgan Lloyd wrote:
So you get the password prompt which is actually issued by your SSH
client. The two things I'd suggest are (i) if you have one use a shell
session on the local console to run something like ps fau
On Tuesday 24 July 2018 14:44:32 Alan Corey wrote:
> So you're running an X session tunneled through ssh and then trying to
> log in by ssh inside that? I'm way out of my league here, but what do
> you get in response to just typing env? Should show all your
> environment variables, including SH
On Tuesday 24 July 2018 14:23:33 Mark Morgan Lloyd wrote:
> On 24/07/18 17:45, Gene Heskett wrote:
> >>> Now to see if the pi can be fixed, but the second of those two
> >>> commands does not exist in /etc/ssh/sshd_config on the pi, even
> >>> there but commented out.
> >
> > But I have not made i
On 07/24/2018 08:43 PM, Christoph Biedl wrote:
> Perhaps just babble and FUD: There was (and probably still is) an issue
> in powerpc: In a certain package, upstream's compile options for ppc had
> higher CPU requirements than what Debian uses for that architecture. As
> a result, the buildd (some
On Tuesday 24 July 2018 14:43:02 Christoph Biedl wrote:
> Adrian Bunk wrote...
>
> > I'd like to get a clear picture regarding the situation of building
> > armel for buster on arm64, ideally moving it to arm64 hardwre soon.
>
> JFTR, I'd appreciate if armel/armhf could continue to be part of a
>
On Tuesday 24 July 2018 14:29:49 Mark Morgan Lloyd wrote:
> > I get the pw requester, answer it, get the login blurb I assume
> > from /etc/issue.net, but then no shell prompt in the remote term
> > emulator, and a ctrl-d is also ignored. Kill the tab is the only way
> > out. Thinking I had hit s
> On Jul 24, 2018, at 11:20 AM, Steve McIntyre wrote:
>
> [ Dropped cc to debian-ports etc., switched to debian-arm instead ]
>
>> As for the hardware, you should watch out for hardware with ARM Cortex Cores.
>> Alternatively, X-Gene 1. ThunderX, ThunderX2 and Centriq are definitely not
>> su
Adrian Bunk wrote...
> I'd like to get a clear picture regarding the situation of building
> armel for buster on arm64, ideally moving it to arm64 hardwre soon.
JFTR, I'd appreciate if armel/armhf could continue to be part of a
release.
> 1. What issues are considered possible problems for movi
So you're running an X session tunneled through ssh and then trying to
log in by ssh inside that? I'm way out of my league here, but what do
you get in response to just typing env? Should show all your
environment variables, including SHELL, TERM, DISPLAY, USER, HOME,
PATH, etc. You may have inh
I get the pw requester, answer it, get the login blurb I assume
from /etc/issue.net, but then no shell prompt in the remote term
emulator, and a ctrl-d is also ignored. Kill the tab is the only way
out. Thinking I had hit some limit on this machine. or on the pi, I got
exactly the same results fr
On 24/07/18 17:45, Gene Heskett wrote:
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
there but commented out.
But I have not made it work on the pi, with or without the
X11UseLocalhost no (the default it says)
lin
On Tuesday 24 July 2018 13:22:34 Mark Morgan Lloyd wrote:
> On 24/07/18 17:15, Gene Heskett wrote:
> > On Tuesday 24 July 2018 10:07:45 Lennart Sorensen wrote:
> >> On Tue, Jul 24, 2018 at 04:21:25AM -0400, Gene Heskett wrote:
> >>> And that works, geany now runs on the rock64 from an ssh login!!!
On 24/07/18 17:15, Gene Heskett wrote:
On Tuesday 24 July 2018 10:07:45 Lennart Sorensen wrote:
On Tue, Jul 24, 2018 at 04:21:25AM -0400, Gene Heskett wrote:
And that works, geany now runs on the rock64 from an ssh login!!!.
Now to see if the pi can be fixed, but the second of those two
comman
On Tuesday 24 July 2018 10:07:45 Lennart Sorensen wrote:
> On Tue, Jul 24, 2018 at 04:21:25AM -0400, Gene Heskett wrote:
> > And that works, geany now runs on the rock64 from an ssh login!!!.
> > Now to see if the pi can be fixed, but the second of those two
> > commands does not exist in /etc/ssh
On Tuesday 24 July 2018 04:47:14 Mark Morgan Lloyd wrote:
> On 24/07/18 08:30, Gene Heskett wrote:
> > On Tuesday 24 July 2018 01:28:41 Tixy wrote:
> >> On Mon, 2018-07-23 at 18:53 -0400, Gene Heskett wrote:
> When you said you had isses with ssh -Y not allow X
> connections...
>
>
On Tue, Jul 24, 2018 at 04:21:25AM -0400, Gene Heskett wrote:
> And that works, geany now runs on the rock64 from an ssh login!!!.
> Now to see if the pi can be fixed, but the second of those two commands
> does not exist in /etc/ssh/sshd_config on the pi, even commented out.
> And when added, r
On Mon, Jul 23, 2018 at 06:53:36PM -0400, Gene Heskett wrote:
> Do I have to reboot it (the rock64) after makeing everything as above?
> Logging out, and back in does not shut the error message off.
>
> gene@coyote:~$ ssh -Y rock64@rock64
> rock64@rock64's password:
> X11 forwarding request fail
[ Dropped cc to debian-ports etc., switched to debian-arm instead ]
On Mon, Jul 23, 2018 at 04:11:06PM +0200, John Paul Adrian Glaubitz wrote:
>Hi Roger!
>
>On 07/23/2018 10:42 AM, Roger Shimizu wrote:
>> I talked to a few people about keeping armel in buster, during 1st and
>> 2nd day in debcamp.
On 24/07/18 08:30, Gene Heskett wrote:
On Tuesday 24 July 2018 01:28:41 Tixy wrote:
On Mon, 2018-07-23 at 18:53 -0400, Gene Heskett wrote:
When you said you had isses with ssh -Y not allow X connections...
Check that /etc/ssh/sshd_config on the rock64 has these settings:
X11Forwarding yes
X1
On Tue, Jul 24, 2018 at 11:22:36AM +0300, Adrian Bunk wrote:
>On Tue, Jul 24, 2018 at 07:27:15AM +0100, Steve McIntyre wrote:
>>...
>> The next big problem I can see is in our haskell packages for
>> armhf. From my build log for haskell-zxcvbn-c_1.0.1-4.log (as an
>> example):
>>
>> ...
>> Setting
On Tue, Jul 24, 2018 at 07:27:15AM +0100, Steve McIntyre wrote:
>...
> The next big problem I can see is in our haskell packages for
> armhf. From my build log for haskell-zxcvbn-c_1.0.1-4.log (as an
> example):
>
> ...
> Setting up llvm-3.9 (1:3.9.1-19+b1) ...
> Setting up ghc (8.2.2-4) ...
> Ill
On Tuesday 24 July 2018 01:28:41 Tixy wrote:
> On Mon, 2018-07-23 at 18:53 -0400, Gene Heskett wrote:
> > > When you said you had isses with ssh -Y not allow X connections...
> > >
> > > Check that /etc/ssh/sshd_config on the rock64 has these settings:
> > >
> > > X11Forwarding yes
> > > X11UseLoc
26 matches
Mail list logo
