On 2022-02-01, Stanislav Vlasov wrote:
> 2022-02-01 17:20 GMT+05:00, Curt :
>> On 2022-01-31, Stefan Monnier wrote:
Technically correct, but Curt's response was good enough for Richard
Owlett to make progress. Richard Owlett is very unlikely to be using
a 64-bit kernel with 32-bit
2022-02-01 17:20 GMT+05:00, Curt :
> On 2022-01-31, Stefan Monnier wrote:
>>> Technically correct, but Curt's response was good enough for Richard
>>> Owlett to make progress. Richard Owlett is very unlikely to be using
>>> a 64-bit kernel with 32-bit userspace.
>>
>> BTW, for the twisted-minded
On Tue, Feb 01, 2022 at 12:32:24AM -0500, Stefan Monnier wrote:
that's not running a 64bit userspace on a 32bit kernel,
Why not? You have a 64bit system on top, a 32bit kernel at the bottom
and whether execution of those 64bit binaries is performed directly by
the CPU or via binfmt + qemu is
On 2022-01-31, Stefan Monnier wrote:
>> Technically correct, but Curt's response was good enough for Richard
>> Owlett to make progress. Richard Owlett is very unlikely to be using
>> a 64-bit kernel with 32-bit userspace.
>
> BTW, for the twisted-minded it's probably possible to run a 64bit
>
On 02/01/2022 12:12 AM, songbird wrote:
Richard Owlett wrote:
...
My hardware can support either 32 or 64 bit OS.
I *ONLY* use one or the other.
My goal is to determine which I chose at installation.
that should be somewhere in:
/var/log/installer
Yes but ;/
"dpkg --print-architecture"
Am Montag, 31. Januar 2022 schrieb Richard Owlett:
> >> 2. As superuser, how can I determine which is installed on a
> >> different partition?
> >> [ My typical installation routine has been a descriptive
> >> label for each root partition. But not always done ;{ ]
> >
> > If the superuser
Richard Owlett wrote:
...
> My hardware can support either 32 or 64 bit OS.
> I *ONLY* use one or the other.
> My goal is to determine which I chose at installation.
that should be somewhere in:
/var/log/installer
songbird
On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
> > Technically correct, but Curt's response was good enough for Richard
> > Owlett to make progress. Richard Owlett is very unlikely to be using
> > a 64-bit kernel with 32-bit userspace.
>
> BTW, for the twisted-minded it's
On Mon, Jan 31, 2022 at 09:02:17PM -0500, Stefan Monnier wrote:
Greg Wooledge [2022-01-31 16:45:52] wrote:
On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
BTW, for the twisted-minded it's probably possible to run a 64bit
userspace on a 32bit kernel.
No. Or at least, not that
On Mon 31 Jan 2022 at 21:02:17 (-0500), Stefan Monnier wrote:
> Greg Wooledge [2022-01-31 16:45:52] wrote:
> > On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
> >> BTW, for the twisted-minded it's probably possible to run a 64bit
> >> userspace on a 32bit kernel.
> > No. Or at
On 01/31/2022 03:37 PM, Stefan Monnier wrote:
Technically correct, but Curt's response was good enough for Richard
Owlett to make progress. Richard Owlett is very unlikely to be using
a 64-bit kernel with 32-bit userspace.
BTW, for the twisted-minded it's probably possible to run a 64bit
On 01/31/2022 02:01 PM, Brian wrote:
On Mon 31 Jan 2022 at 11:38:17 -0500, Greg Wooledge wrote:
uname -m
Are you saying that that doesn't reveal whether I've installed a 64 or a 32
bit release?
It does not. It only reveals which kernel is running.
As I said in another message, you
On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
> > Technically correct, but Curt's response was good enough for Richard
> > Owlett to make progress. Richard Owlett is very unlikely to be using
> > a 64-bit kernel with 32-bit userspace.
>
> BTW, for the twisted-minded it's
On Mon 31 Jan 2022 at 11:38:17 -0500, Greg Wooledge wrote:
> > >> uname -m
>
> > Are you saying that that doesn't reveal whether I've installed a 64 or a 32
> > bit release?
>
> It does not. It only reveals which kernel is running.
>
> As I said in another message, you could have a 32-bit
On Mon 31 Jan 2022 at 06:32:23 (-0600), Richard Owlett wrote:
> Due to historical circumstances, I have laptops which multi-boot
> various Debian releases. There be 32 bit and 64 bit versions of the
> same release on a particular machine.
>
> 1. From current console, how can I determine which is
On Mon 31 Jan 2022 at 08:26:35 (-0500), Greg Wooledge wrote:
> On Mon, Jan 31, 2022 at 08:23:45AM -0500, Stefan Monnier wrote:
> > > 1. From current console, how can I determine which is running?
> > >[ equivalent of /etc/debian_version would be ideal ]
> >
> > Depends what you mean. The
> >> uname -m
> Are you saying that that doesn't reveal whether I've installed a 64 or a 32
> bit release?
It does not. It only reveals which kernel is running.
As I said in another message, you could have a 32-bit userspace with
a 64-bit kernel. If that's the case, then uname -m gives you
On 2022-01-31, Richard Owlett wrote:
> On 01/31/2022 06:37 AM, Curt wrote:
>> On 2022-01-31, Richard Owlett wrote:
>>> Due to historical circumstances, I have laptops which multi-boot various
>>> Debian releases. There be 32 bit and 64 bit versions of the same release
>>> on a particular
On 01/31/2022 06:37 AM, Curt wrote:
On 2022-01-31, Richard Owlett wrote:
Due to historical circumstances, I have laptops which multi-boot various
Debian releases. There be 32 bit and 64 bit versions of the same release
on a particular machine.
1. From current console, how can I determine
On Mon, Jan 31, 2022 at 03:24:51PM +0200, Teemu Likonen wrote:
> * 2022-01-31 06:32:23-0600, Richard Owlett wrote:
>
> > Due to historical circumstances, I have laptops which multi-boot
> > various Debian releases. There be 32 bit and 64 bit versions of the
> > same release on a particular
* 2022-01-31 06:32:23-0600, Richard Owlett wrote:
> Due to historical circumstances, I have laptops which multi-boot
> various Debian releases. There be 32 bit and 64 bit versions of the
> same release on a particular machine.
>
> 1. From current console, how can I determine which is running?
>
On Mon, Jan 31, 2022 at 08:23:45AM -0500, Stefan Monnier wrote:
> > 1. From current console, how can I determine which is running?
> >[ equivalent of /etc/debian_version would be ideal ]
>
> Depends what you mean. The answer may also be "both" depending on what
> you care about. E.g. many
On 2022-01-31, Richard Owlett wrote:
> Due to historical circumstances, I have laptops which multi-boot various
> Debian releases. There be 32 bit and 64 bit versions of the same release
> on a particular machine.
>
> 1. From current console, how can I determine which is running?
> [
Due to historical circumstances, I have laptops which multi-boot various
Debian releases. There be 32 bit and 64 bit versions of the same release
on a particular machine.
1. From current console, how can I determine which is running?
[ equivalent of /etc/debian_version would be ideal ]
2.
ion with /home in it's
> >> own partition, and I'm wondering if I can expect to just
> >> unlink /home and install a new amd64 version, and then link
> >> in the home parition again.
Later I realised my answer doesn't directly address your query regarding
i386 (32 bits) -&
That's interesting in itself. Makes some sense.
Thanks much.
On 1/28/22, Andrei POPESCU wrote:
> On Mi, 26 ian 22, 17:33:04, Joseph Brenner wrote:
>> I was wondering if the on-disk data format for btrfs is
>> compatible between the i386 and amd64 code bases--
>> e.g. would yo
On Mi, 26 ian 22, 17:33:04, Joseph Brenner wrote:
> I was wondering if the on-disk data format for btrfs is
> compatible between the i386 and amd64 code bases--
> e.g. would you expect to be able to swap data drives
> between machines running either?
In general yes.
> I've
Sorry, last word in last mail is wrong,
it should be inconvenience, not incontinence
Thank David!
my mail provider blocks your reply without informing me, so i can't
receive it on time, i get your reply by some other way
it's amazing that you get my history of getting help here,
actually i've just bought 2nd-hand pc, it's core2 Q8200, 2.33G, it's my
fastest pc though others
I was wondering if the on-disk data format for btrfs is
compatible between the i386 and amd64 code bases--
e.g. would you expect to be able to swap data drives
between machines running either?
I've got an old i386 installation with /home in it's
own partition, and I'm wondering if I can expect
Thank Polyna-Maude Racicot-Summerside!
it's only for curiosity.
for most users, their performance have little difference
On Wed 26 Jan 2022 at 05:44:50 (-0500), Polyna-Maude Racicot-Summerside wrote:
> On 2022-01-25 19:35, David Wright wrote:
> > On Tue 25 Jan 2022 at 01:37:29 (-0500), a wrote:
> >> Thank David and Polyna-Maude!
> >>
> >> it's surprising that "The x64 binary are also somewhat larger than the
> >>
On 2022-01-25 19:35, David Wright wrote:
> On Tue 25 Jan 2022 at 01:37:29 (-0500), a wrote:
>> Thank David and Polyna-Maude!
>>
>> it's surprising that "The x64 binary are also somewhat larger than the
>> i386 binaries"
>>
>> i compare some packages of bullseye for both arch, they happen to be
On Tue 25 Jan 2022 at 01:37:29 (-0500), a wrote:
> Thank David and Polyna-Maude!
>
> it's surprising that "The x64 binary are also somewhat larger than the
> i386 binaries"
>
> i compare some packages of bullseye for both arch, they happen to be
> contrary
>
> though difference is small and IMO
On Tue, Jan 25, 2022 at 03:29:17PM +0100, to...@tuxteam.de wrote:
> On Tue, Jan 25, 2022 at 09:18:55AM -0500, Stefan Monnier wrote:
> > > it's surprising that "The x64 binary are also somewhat larger than the
> > > i386
> > > binaries"
> >
> > There is no fundamental reason why a 64bit
On Tue, Jan 25, 2022 at 09:18:55AM -0500, Stefan Monnier wrote:
> > it's surprising that "The x64 binary are also somewhat larger than the i386
> > binaries"
>
> There is no fundamental reason why a 64bit architecture (like amd64) would
> require more code than a 32bit architecture (like x86),
Hello,
On Mon, Jan 24, 2022 at 08:30:20PM -0500, a wrote:
> i've installed debian 11 for both arch on same PC, amd64 seems faster
>
> is there some tool to demonstrate performance of PC?
Regardless of performance you should be more concerned that 32-bit
x86 parts of the Linux kernel have more
Thank David and Polyna-Maude!
it's surprising that "The x64 binary are also somewhat larger than the
i386 binaries"
i compare some packages of bullseye for both arch, they happen to be
contrary
though difference is small and IMO has little impact on performance
firefox-esr for i386: size=
On 2022-01-24 22:02, David Wright wrote:
> On Mon 24 Jan 2022 at 20:30:20 (-0500), a wrote:
>> i've installed debian 11 for both arch on same PC, amd64 seems faster
>>
>> is there some tool to demonstrate performance of PC?
>>
Yes there is standardized benchmark available. LinPack for example,
On Mon 24 Jan 2022 at 20:30:20 (-0500), a wrote:
> i've installed debian 11 for both arch on same PC, amd64 seems faster
>
> is there some tool to demonstrate performance of PC?
>
> they say it's not possible to say which is faster without defining
> computing task
>
> is performance difference
i've installed debian 11 for both arch on same PC, amd64 seems faster
is there some tool to demonstrate performance of PC?
they say it's not possible to say which is faster without defining
computing task
is performance difference significant if computing task is web browsing
Valentim Carlos
Em 01 de ago de 2017 às 14:26, Henrique de Moraes Holschuh <h...@debian.org>
escreveu:
Olha, trocar um Debian de i386 para amd64 é possível via "Multiarch".
Chamamos isso de "cross-grade". Mas é uma dor de cabeça que não é
recomendada nem para quem é
Olha, trocar um Debian de i386 para amd64 é possível via "Multiarch".
Chamamos isso de "cross-grade". Mas é uma dor de cabeça que não é
recomendada nem para quem é usuário avançado.
Se for simples reinstalar, reinstale. Se não for, e quiser tentar um
cross-grade, *FAÇA BACK
Le mardi 01 août 2017 à 20:33 +, Paulo Alexandre A.P. de Oliveira a
écrit :
> Em princípio se não houver umas magias de shellscript, tens que
> reinstalar com amd64
Não há, é impossível. Um SO de 32 bits não tem como executar código 64
bits, porque ele não tem como gerir os endereços de
Le mardi 01 août 2017 à 20:13 +, Valentim Carlos a écrit :
> gostaria de saber se tem como migrar a Arquitetura
> Estrangeira i386 para amd64 ?
Não. Não há como um SO 32 bits executar código 64.
--
skype:leandro.gfc.dutra?chat Yahoo!: ymsgr:sendIM?lgcdutra
+55 (61) 354
rde,
>
> Estou com uma máquina Debian em arquitetura i386 porém com processador
> amd64, não sei o motivo pelo qual foi instalado 32 bits, todas outras
> máquinas que instalei, estão em amd64 e em multiarch nas necessidades.
> Bom, gostaria de saber se tem como migrar a Arquitetura Estra
ou com uma máquina Debian em arquitetura i386 porém com processador
amd64, não sei o motivo pelo qual foi instalado 32 bits, todas outras
máquinas que instalei, estão em amd64 e em multiarch nas necessidades.
Bom, gostaria de saber se tem como migrar a Arquitetura Estrangeira
i386 para amd64 ?
Ob
i386 para amd64 ?
Obrigado
Valentim Carlos
On Wed 05 Jul 2017 at 11:34:20 (-0400), Gene Heskett wrote:
> On Wednesday 05 July 2017 07:58:26 Matthew Crews wrote:
>
> > >Now that I know that I'm 64 bit capable. Would I see any benefit in
> > >switching?
> >
> > I would switch to AMD64 if you are comfortable with reinstalling
> > Debian. You
On Wednesday 05 July 2017 07:58:26 Matthew Crews wrote:
> >Now that I know that I'm 64 bit capable. Would I see any benefit in
> >switching?
>
> I would switch to AMD64 if you are comfortable with reinstalling
> Debian. You will see a performance increase, even on a minimally
> spec'd system.
>Now that I know that I'm 64 bit capable. Would I see any benefit in
>switching?
I would switch to AMD64 if you are comfortable with reinstalling Debian. You
will see a performance increase, even on a minimally spec'd system. (I'm not
sure its possible to convert a live install from 32-bit to
Richard Owlett composed on 2017-07-05 06:26 (UTC-0500):
> Now that I know that I'm 64 bit capable. Would I see any benefit in
> switching?
> [I don't have any interest in grapic intensive apps. I don't do anything
> that my old WinXP machine didn't handle OK.]
Is more than 3G RAM is installed?
On 07/04/2017 02:10 PM, Sven Joachim wrote:
On 2017-07-04 20:19 +0200, Dejan Jocic wrote:
On 04-07-17, Sven Joachim wrote:
On 2017-07-04 17:33 +0200, Dejan Jocic wrote:
Several. To see your cpu, type lscpu. Architecture is first in output.
That's not correct, or at least not useful. The
On 07/04/2017 01:20 PM, Felix Miata wrote:
Curt composed on 2017-07-04 17:53 (UTC):
Richard Owlett wrote:
Thank you. I've i686 processors on both machines within reach
[as I suspected] I'll have to spend some time on man page for
inxi to fully appreciate it.
But i686 is 32 bit isn't it?
On 2017-07-04 20:19 +0200, Dejan Jocic wrote:
> On 04-07-17, Sven Joachim wrote:
>> On 2017-07-04 17:33 +0200, Dejan Jocic wrote:
>> >
>> > Several. To see your cpu, type lscpu. Architecture is first in output.
>>
>> That's not correct, or at least not useful. The architecture is what
>>
On 2017-07-04 18:39 +, Curt wrote:
> On 2017-07-04, Sven Joachim wrote:
>>>
>>> Several. To see your cpu, type lscpu. Architecture is first in output.
>>
>> That's not correct, or at least not useful. The architecture is what
>> uname(2) reports, and if the system is
On 2017-07-04, Sven Joachim wrote:
>>
>> Several. To see your cpu, type lscpu. Architecture is first in output.
>
> That's not correct, or at least not useful. The architecture is what
> uname(2) reports, and if the system is currently running a 32-bit
> kernel, it will be
Curt composed on 2017-07-04 17:53 (UTC):
> Richard Owlett wrote:
>> Thank you. I've i686 processors on both machines within reach ]as I
>> suspected]
>> I'll have to spend some time on man page for inxi to fully appreciate it.
> But i686 is 32 bit isn't it?
Some are 32, others are 64. 'cat
On 04-07-17, Sven Joachim wrote:
> On 2017-07-04 17:33 +0200, Dejan Jocic wrote:
>
> > On 04-07-17, Richard Owlett wrote:
> >> I have been running Debian i386 since Squeeze. At that time it was required
> >> as I was considering supporting some donated 32 bit machines at church. I
> >> don't
On 2017-07-04 17:33 +0200, Dejan Jocic wrote:
> On 04-07-17, Richard Owlett wrote:
>> I have been running Debian i386 since Squeeze. At that time it was required
>> as I was considering supporting some donated 32 bit machines at church. I
>> don't recall what processor was in my personal machine
On 2017-07-04, Richard Owlett wrote:
>> informations.
>>
>
> Thank you. I've i686 processors on both machines within reach ]as I
> suspected]
> I'll have to spend some time on man page for inxi to fully appreciate it.
But i686 is 32 bit isn't it?
> I'm not aware of
On 07/04/2017 10:33 AM, Dejan Jocic wrote:
On 04-07-17, Richard Owlett wrote:
I have been running Debian i386 since Squeeze. At that time it was required
as I was considering supporting some donated 32 bit machines at church. I
don't recall what processor was in my personal machine at that
On 04-07-17, Richard Owlett wrote:
> I have been running Debian i386 since Squeeze. At that time it was required
> as I was considering supporting some donated 32 bit machines at church. I
> don't recall what processor was in my personal machine at that time. I've
> never had cause to investigate
I have been running Debian i386 since Squeeze. At that time it was
required as I was considering supporting some donated 32 bit machines at
church. I don't recall what processor was in my personal machine at that
time. I've never had cause to investigate the processors in my current
laptops
2016-04-27 13:56 GMT-03:00 SamuelOPH :
>
> Mas de fato 32 bits deve ser usado apenas se realmente necessário.
Isso só na arquitetura Intel, onde o i386 tem menos registros que a
AMD64, impedindo otimizações de compilação. Em arquiteturas Risc,
pode-se ter o sistema
Em 27 de abril de 2016 12:51, Diego Rabatone Oliveira
escreveu:
> Se você optar por um sistema 32bits não irá conseguir fazer uso dos 8Gb de
> RAM que seu computador terá.
Na verdade isso só é problema de Windows, com Linux você pode usar até 64Gb
de memória usando um SO
Caro Guilherme,
com relação a AMD64 ou i386, não tenha dúvida, vá de AMD64. Se você optar
por um sistema 32bits não irá conseguir fazer uso dos 8Gb de RAM que seu
computador terá. E em termos de drivers, como o Leandro comentou, a
compatibilidade hoje em dia com AMD64 é tão boa quanto, senão
2016-04-27 12:12 GMT-03:00 Guilherme Oliveira Magalhães
<magalhaes.guiolive...@gmail.com>:
> Bom dia caros, estou retornando aos estudos deste SO, e fico no momento na
> dúvida se os módulos dos drivers para os modelos i386 ou amd64 são estáveis,
> no que tange ao hardware de rede
Bom dia caros, estou retornando aos estudos deste SO, e fico no momento na
dúvida se os módulos dos drivers para os modelos i386 ou amd64 são
estáveis, no que tange ao hardware de redes sem fio.
Eu possuo 2 receptores Wireless externos USB, utilizo apenas um no Windows
segundo dica de um
Hola gente linda de la lista !!
(y tambien a la otra no tan linda que con profundo desagrado tambien
suelo leer y repudiar en silencio)
Me surgio un antiguo fantasma del pasado en lo referente a
arquitecturas. Ese fantasma me supo susurrar al oido que los sistemas
-compilaciones- para 32
El Sun, 16 Nov 2014 16:33:56 -0300, unciegobailando escribió:
(...)
Y a pesar de esto no dejo de leer cada tanto en la web recomendaciones
o directamente experiencias en las que se recomienda instalar un sistema
de 32 bits sobre un procesador amd64 para ganar agilidad o velocidad.
Si mal
Não estou conseguindo instalar pacotes da arquitetura i386 em
arquitetura amd64. Mesmo após o --add-architecture a coisa não se
resolve. Parece que o ia32-libs mudou de nome ou há muitos pacotes
quebrados. No Wheezy não há problema.
Alguém consegue instalá-los ou aguarda-se a resolução de
Aqui ele instala nada do tipo pacote:i386. P. ex: wine:i386.
Em Thu, 24 Jul 2014 11:16:00 -0300
Guimarães Faria Corcete DUTRA, Leandro l...@dutras.org escreveu:
2014-07-24 10:59 GMT-03:00 Listeiro 037 listeiro_...@yahoo.com.br:
Não estou conseguindo instalar pacotes da arquitetura i386 em
Hello,
As the subject says, I'm having problems installing libgtk2.0-0:i386 on my
amd64 sid system. The problem is that I am using the cisco anyconnect
client, which requires the i386 version, but when I attempt to install at
one (the amd64 version is installed), I get a bunch of dependency
Was able to get this going by pulling the package from experimental...
Thanks all,
--b
On Thu, Jun 6, 2013 at 8:26 AM, Brad Alexander stor...@gmail.com wrote:
Hello,
As the subject says, I'm having problems installing libgtk2.0-0:i386 on my
amd64 sid system. The problem is that I am using
On Thu, 6 Jun 2013 08:26:56 -0400
Brad Alexander stor...@gmail.com wrote:
Hello,
As the subject says, I'm having problems installing libgtk2.0-0:i386
on my amd64 sid system. The problem is that I am using the cisco
anyconnect client, which requires the i386 version, but when I
attempt
On 06/06/13 13:26, Brad Alexander wrote:
Hello,
As the subject says, I'm having problems installing libgtk2.0-0:i386 on
my amd64 sid system. The problem is that I am using the cisco anyconnect
client, which requires the i386 version, but when I attempt to install
at one (the amd64 version
lo hago yo o si vas a
descargar las dos: --arch=i386, amd64
--method http si vas a descargar desde http o ftp
Y al final seleccionas la ruta donde vas a guardar local tu mirror. Si
utilizas un externo, lo montas y le especificas la ruta dentro de él.
Saludos y espero te sirva.
--
Yordanis
amigos necesito alguna forma de separar los repos del tipo i386 de
los que son amd64 porque me ocupan mucho espacio en el disco duro y se
que solo usare los de i386, los de amd64 nunca los usare, como puedo
hacer esto, los repos los tengo en un disco de externo.
es medio bestia (o mas bien, bestia
a las 17:40 +0100, juan alejandro martines linares
escribió:
Hola amigos necesito alguna forma de separar los repos del tipo i386 de
los que son amd64 porque me ocupan mucho espacio en el disco duro y se
que solo usare los de i386, los de amd64 nunca los usare, como puedo
hacer esto, los repos los
Por que no haces dos carpetas una i386 y otra amd64
# mkdir i386 amd64
# mv *amd64.deb amd64
# mv *i386.deb i386
El 23 de febrero de 2011 10:40, juan alejandro martines linares
isla...@infomed.sld.cu escribió:
Hola amigos necesito alguna forma de separar los repos del tipo i386 de
los que
Hola amigos necesito alguna forma de separar los repos del tipo i386 de
los que son amd64 porque me ocupan mucho espacio en el disco duro y se
que solo usare los de i386, los de amd64 nunca los usare, como puedo
hacer esto, los repos los tengo en un disco de externo.
gracias de antemano
El mié, 23-02-2011 a las 17:40 +0100, juan alejandro martines linares
escribió:
Hola amigos necesito alguna forma de separar los repos del tipo i386 de
los que son amd64 porque me ocupan mucho espacio en el disco duro y se
que solo usare los de i386, los de amd64 nunca los usare, como puedo
Anyway, I think the huge **WARNING** notes should have been enough to let
you know the whole thing was not without risk ;)
Regards,
Angus
You're right Angus, and I did take precautions, that is why I was still able
to post to the newsgroup, however I thought maybe an extra emphasis
I think I'll just wait for:
aptitude -a amd64 --arch_upgrade
Surely that's right around the corner... Maybe for Squeeze?
:)
James
Damn right, keep a watch on your /etc/dpkg/dpkg.cfg file for an upgrade.
--
C.
--
--
To UNSUBSCRIBE, email to
On Tue, Mar 2, 2010 at 6:35 PM, Charles Kroeger
ckro...@frankensteinface.com wrote:
snip
You're right Angus, and I did take precautions, that is why I was still
able
to post to the newsgroup, however I thought maybe an extra emphasis
wouldn't
hurt. I'm not confident that getting the
On Sat, Feb 27, 2010 at 17:44 -0500, Charles Kroeger wrote:
I would hope someone knows a command line solution. Is there a way
to safely morph the old architecture into the new, like purging the i686
kernel for instance or configuring APT or dpkg to upgrade with amd64
versions.
You were
You were already told that a reinstall is most definitely the easiest,
fastest and safest procedure. But if you want to try it:
http://teddyb.org/~rlpowell/hobbies/debian_arch_up/
Thanks for all the suggestions.
I had a go with the above site using the powerful command:
#dpkg
On Mon, Mar 1, 2010 at 6:10 PM, Charles Kroeger
ckro...@frankensteinface.com wrote:
snip
Thanks for all the suggestions.
I had a go with the above site using the powerful command:
#dpkg --force-depends --force-architecture --force-overwrite -i
to install the suggested libs:
I think I'll just wait for:
aptitude -a amd64 --arch_upgrade
Surely that's right around the corner... Maybe for Squeeze?
:)
James
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Andrew Sackville-West put forth on 2/27/2010 7:53 PM:
It's been a while, but as I understand it, there is an -amd64 kernel
available in the -i686 repos, but that doesn't mean you're running in
the 64 bit architecture. That requires a number of other things to
happen, including changing to a
However, it has transpired that it wasn't that simple to change from the i686
kernel to amd64 even though my 32 packages will work under the amd64 kernel
Apt and Dpkg for instance don't seem to know this has happened.
Others have already answered the how to move from i386 to amd64, but
I'll
I've made a new computer my first ever and I'm very pleased with it. It uses
an AMD phenon II 505 build cpu on an Ausus board with 8GB ram.
I used an amd64 net-installer to create the partitions and swap file
on the new and larger hard drive of the new machine.
Before moving an image of the old
On Sat, Feb 27, 2010 at 05:44:46PM -0500, Charles Kroeger wrote:
[...]
Before moving an image of the old [i686] partition to the new computer I
installed the amd64 kernel. I completed the install by using gparted from a
rescue disk to merge the larger new partition with the old smaller one from
Svenn Are Bjerkem wrote:
2009/7/19 MRH misiek_s...@o2.pl:
I'm pretty confused with the latest changes in sid on amd64. Do ia32-*
packages replace -i386 packages or they are alternatives? After 'upgrading'
to ia32-apt-get I lost wine (however I found there is ia32-wine, which
unfortunately is
2009/7/19 MRH misiek_s...@o2.pl:
I'm pretty confused with the latest changes in sid on amd64. Do ia32-*
packages replace -i386 packages or they are alternatives? After 'upgrading'
to ia32-apt-get I lost wine (however I found there is ia32-wine, which
unfortunately is not displayed in synaptic
I'm pretty confused with the latest changes in sid on amd64. Do ia32-*
packages replace -i386 packages or they are alternatives? After
'upgrading' to ia32-apt-get I lost wine (however I found there is
ia32-wine, which unfortunately is not displayed in synaptic and I'm not
sure if it replaces
On Sun, Jul 19, 2009 at 14:09, MRHmisiek_s...@o2.pl wrote:
I'm pretty confused with the latest changes in sid on amd64. Do ia32-*
packages replace -i386 packages or they are alternatives? After 'upgrading'
to ia32-apt-get I lost wine (however I found there is ia32-wine, which
unfortunately is
On Fri, Jul 10, 2009 at 03:15:27PM -0300, Pablo Armando wrote:
Should we use Debian amd64 here o i386? Why we see 4 CPU's when we only have
2 CPUs (Intel Core 2 Duo)? Is stable amd64 or it is not recommended for a
server setup?
You'll want to use amd64, it's stable. Even before
-Mensaje original-
De: lee [mailto:l...@yun.yagibdah.de]
Enviado el: Sábado, 11 de Julio de 2009 03:13 p.m.
Para: debian-user@lists.debian.org
Asunto: Re: E7400 - i386 and AMD64
Did you use any weird kernel settings when you made the kernel for
your server? Did you try an older (like
1 - 100 of 210 matches
Mail list logo