From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QpNBn-00080O-4k for garchives@archives.gentoo.org; Fri, 05 Aug 2011 16:23:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1344121C031; Fri, 5 Aug 2011 16:23:51 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id DC67521C031 for ; Fri, 5 Aug 2011 16:23:50 +0000 (UTC) Received: by ywa8 with SMTP id 8so2442531ywa.40 for ; Fri, 05 Aug 2011 09:23:50 -0700 (PDT) Received: by 10.42.89.70 with SMTP id f6mr2228619icm.48.1312561430216; Fri, 05 Aug 2011 09:23:50 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user-br@lists.gentoo.org Reply-to: gentoo-user-br@lists.gentoo.org MIME-Version: 1.0 Received: by 10.42.5.213 with HTTP; Fri, 5 Aug 2011 09:23:30 -0700 (PDT) In-Reply-To: References: <1312256386.34929.YahooMailClassic@web36708.mail.mud.yahoo.com> <4E3BD4CF.4050602@yahoo.com.br> <4E3BF030.3080903@gmail.com> From: Raphael Bastos Date: Fri, 5 Aug 2011 13:23:30 -0300 Message-ID: Subject: =?ISO-8859-1?Q?Re=3A_=5Bgentoo=2Duser=2Dbr=5D_C=F3pia_de_um_sistema_para_outro?= =?ISO-8859-1?Q?_HD?= To: gentoo-user-br@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 25b84347a1b64d8dfaecdfada0057a41 Sim, estamos falando de dd sim. ;) PS: tenho experi=EAncias do que citei, nos dois exemplos. Att, Raphael Bastos =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Bastos Service Manuten=E7=E3o Industrial Ltda. www.bastosservice.com.br Linux Reg. User: 388431 =A0// =A0LPI ID: LPI000214711 email:~> $ echo "vgepqnqikcBdcuvquugtxkeg0eqo0dt" | perl -pe \ 's/(.)/chr(ord($1)-2)/ge' =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Em 5 de agosto de 2011 12:48, Daniel da Veiga escreveu: > 2011/8/5 Raphael Bastos >> >> Na verdade n=E3o h=E1 problema nenhum em c=F3pia de discos com tamanhos >> diferentes, bastando ap=F3s a c=F3pia tu redimensionar a parti=E7=E3o vi= a >> gparted, ou at=E9 mesmo o partition magic do wind=E3o. >> Ex 1: >> cen=E1rio: disco origem de 20GB e destino de 30GB >> resultado ap=F3s usar o dd: 10GB livres no disco destino. >> >> Ex 2: >> cen=E1rio: disco origem de 30GB e destino de 20GB >> resultado ap=F3s usar o dd: se na origem tiver 15GB livres, o disco >> destino ter=E1 seus 15GB preenchidos, e 15GB livres. >> > > Mas a=ED n=E3o estamos falando de dd certo? > > Estou teorizando aqui, mas numa c=F3pia bit a bit o tamanho das parti=E7= =F5es vai > junto com o resto, e al=E9m disso, a c=F3pia n=E3o sabe o quanto est=E1 p= reenchido > (ou se =E9 uma parti=E7=E3o, ou se est=E1 particionado, nada...) e vai si= mplesmente > copiando, at=E9 dar erro de falta de espa=E7o em disco. Quando isso acont= ecer, > se o sistema de arquivos estiver fragmentado, pode ocorrer perda de dados= e > eu imagino que a parti=E7=E3o se tornaria in=FAtil (pois ela n=E3o termin= a em um > setor do disco dispon=EDvel)... > > Posso estar errado (nunca testei isso na pr=E1tica, exatamente pq imagine= i que > o que descrevi acima aconteceria). > > -- > Daniel da Veiga >