On Tue, Feb 9, 2021 at 7:28 AM John Paul Adrian Glaubitz
wrote:
>
> > On Feb 9, 2021, at 1:22 PM, Jeffrey Walton wrote:
> >
> > Hi Everyone,
> >
> > I'd like to install the additional firmware required for PowerPC. It
> > is briefly discussed at
> >
On Tue, Feb 9, 2021 at 9:25 AM Steve McIntyre wrote:
>
> On Tue, Feb 09, 2021 at 06:21:52AM -0800, Peter Ehlert wrote:
> >
> >On 2/9/21 5:00 AM, Jeffrey Walton wrote:
> >> Hi Everyone,
> >>
> >> I think the installer's choice of red for the backgrou
On Tue, Feb 9, 2021 at 9:22 AM Peter Ehlert wrote:
>
> On 2/9/21 5:00 AM, Jeffrey Walton wrote:
> > Hi Everyone,
> >
> > I think the installer's choice of red for the background color can be
> > improved. Red is a color associated with anger and aggression. Red a
Hi Everyone,
I think the installer's choice of red for the background color can be
improved. Red is a color associated with anger and aggression. Red as
an accent would probably be OK, but the installer uses a wall of red.
There's no need to increase anger and aggression when working with an
Hi Everyone,
I'd like to install the additional firmware required for PowerPC. It
is briefly discussed at
https://www.debian.org/releases/jessie/amd64/ch06s04.html.en.
The problem I am having is, PowerMac's don't have an eject button. I
can't eject the installer to add the firmware CD from
Hi Everyone,
I was trying to follow John Paul Adrian Glaubitz instructions for
installing Debian 10 on a PowerMac G5. The instructions are at
https://lists.debian.org/debian-powerpc/2021/02/msg00011.html. The
instructions say to forgo the reboot after installation and perform
some extra steps.
>>> Is anybody else interested in helping? Thoughts/comments?
>>
>>Sorry to bump an old thread
>>
>>Please consider moving to Clang 3.8 or 4.0 as the LLVM front end for
>>the platform.
>>
>>Clang 3.5 and 3.6 are no longer maintained. The bugs we are
>>discovering and reporting are being closed
> There's something I've been pondering for a while, along with some
> other folks - it might be useful to do a "jessie and a half" release,
> similarly to what we did in the etch days. That's *basically* just
> like a normal jessie release, but with a few key updates:
>
> * backports kernel
> *
>>Results from host computer:
>>
>>I: Running command: debootstrap --arch armel --foreign --keyring
>>/usr/share/keyrings/debian-ports-archive-keyring.gpg --variant=buildd
>>--exclude=debfoster unstable debian-armel
>>http://ftp.ports.debian.org/debian-ports
>>I: Retrieving Release
>>I: Retrieving
Package: debootstrap
Version: 1.0.81
Severity: important
The host computer is running Debian Sid, fully patched.
Results from host computer:
I: Running command: debootstrap --arch armel --foreign --keyring
/usr/share/keyrings/debian-ports-archive-keyring.gpg --variant=buildd
--exclude=debfoster
> There's something I've been pondering for a while, along with some
> other folks - it might be useful to do a "jessie and a half" release,
> similarly to what we did in the etch days. That's *basically* just
> like a normal jessie release, but with a few key updates:
>
> * backports kernel
> *
Package: debootstrap
Version: 1.0.67
Severity: important
I have a Debian 8.5 host on amd64/x86_64 with Testing enabled. I am
attempting to setup a Sparc guest with Unstable enabled using the
following command:
qemu-debootstrap --arch=sparc --keyring
Package: debootstrap
Version: 1.0.72
Severity: normal
**
I'm trying to setup a ppc64 QEMU chroot. I'm not sure if PPC64 is
available, but I usually get a different error when its not available.
The following packages are already installed: qemu binfmt-support
qemu-user-static
On Tue, Oct 20, 2015 at 7:03 PM, Vagrant Cascadian <vagr...@aikidev.net> wrote:
> On 2015-10-20, Jeffrey Walton wrote:
>> # qemu-debootstrap --arch=ppc64 --keyring
>> /usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd
>> --exclude=debfoster debian-ppc64 h
Package: debootstrap
Version: 1.0.72
Severity: important
*
I work with a free/open source project (http://www.cryptopp.com/). A
Debian maintainer reported a failure for X32. I'm trying to get a test
rig setup to duplicate the issue. I'm following Debian's X32Port wiki
page
On Mon, Jan 20, 2014 at 8:33 AM, Ben Hutchings b...@decadent.org.uk wrote:
noloa...@gmail.com wrote:
I installed Debian 7.3 x64 on a Core i5 laptop for some testing (real
hardware, not a VM). When testing a program I wrote, I noticed it was
not getting the full number of bytes requested from
16 matches
Mail list logo
