Cloning hdds of different sizes
Hello, In one of my computers I have 2 HDDs. One of them is a 250 GB drive (debian) and the other is a 300 GB (data). I've decided to give one of them to my parents because the one they have right now makes some strange noises. So I've backed up and cleaned up the drive, and as we speak I am cloning my debian install (from the 250 GB disk) onto the other drive. My fstab contains blkids to identify the root, swap, and home partitions. Will the new clone just boot as if it was on the old drive? Also is there a simple method to resize the future home partition and move the root partition so that I don't end up with unallocated space on the drive? Basically I'd like to have a bootable system while also being able to use the entire space on the disk. Thank you for any suggestions, -- Sent from my Brick (TM)
Re: Cloning hdds of different sizes
You can do this several ways. Way 1) Filesystem level copy + grub install. a)Use a rescue or minimal live boot environment, partition your new disk as you like; complete the minimal install. b)Drop to a shell in the live environment, and mount the new root and fstab layout under a tmp target mount point (i tend to use /mnt/newsubfilesystems) creating each of the sub file system mount directorys under the root then mounting them in turn c)Mount the old filesystem (i.e /mnt/old ) and any subfilesystems d) Use rsync to copy everything under /mnt/old to /mnt/new (rsync -pPvra /mnt/old /mnt/new) - you may want to exclude /mnt/old/dev and /mnt/old/proc ) e) Bind mount the live filesystems proc,sysfs and dev mounts to the /mnt/new ( i.e mount -o bind /dev /mnt/new/dev ; mount -t sysfs /mnt/new/sysfs mount -t proc none /mnt/new/proc ) d) chroot to the new directory ( chroot /mnt/new /bin/bash ) e) fix up any device pointers in /etc/fstab (you might need to change around /dev/sdX etc to accord to the new filesystem parition/device ID - a better method is to get the UUID of the block device using blkid and add that into the /etc/fstab for each fo the mount points than using changable /dev entrys) f) run grub-install from the chroot. g) Done. Way2) (actually more risky and less easy than the above IMHO and will only work with an msdos disk label ) Block copy + fixup disk boundrys by hand + add paritions at the end a) Boot a live environment b) ddrescue /dev/old to /dev/new after running sfdisk on the old and new and keeping a copy of the cylinder/layout info somewhere to refer to c) partprobe the new /dev/new e) Run gparted/parted and align sectors etc f) Add/resize the last parition to fill the space g) Cross fingers. -Joel http://gplus.to/aenertia @aenertia On 28 May 2014 11:03, Catalin Soare lolinux.so...@gmail.com wrote: Hello, In one of my computers I have 2 HDDs. One of them is a 250 GB drive (debian) and the other is a 300 GB (data). I've decided to give one of them to my parents because the one they have right now makes some strange noises. So I've backed up and cleaned up the drive, and as we speak I am cloning my debian install (from the 250 GB disk) onto the other drive. My fstab contains blkids to identify the root, swap, and home partitions. Will the new clone just boot as if it was on the old drive? Also is there a simple method to resize the future home partition and move the root partition so that I don't end up with unallocated space on the drive? Basically I'd like to have a bootable system while also being able to use the entire space on the disk. Thank you for any suggestions, -- Sent from my Brick (TM) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKiAkGSDzFQ=fnergtysqwzrtapusfe8qfztgkwogtnp_cj...@mail.gmail.com
Re: Cloning hdds of different sizes
When I say - will only work with an msdos disklabel, I meant will only work for msdos disklabels IF you have free primary parition slots. GPT doesn't have this issue and if you can boot GPT labeled disks you should go with this. On 28 May 2014 12:22, Joel Wirāmu Pauling j...@aenertia.net wrote: You can do this several ways. Way 1) Filesystem level copy + grub install. a)Use a rescue or minimal live boot environment, partition your new disk as you like; complete the minimal install. b)Drop to a shell in the live environment, and mount the new root and fstab layout under a tmp target mount point (i tend to use /mnt/newsubfilesystems) creating each of the sub file system mount directorys under the root then mounting them in turn c)Mount the old filesystem (i.e /mnt/old ) and any subfilesystems d) Use rsync to copy everything under /mnt/old to /mnt/new (rsync -pPvra /mnt/old /mnt/new) - you may want to exclude /mnt/old/dev and /mnt/old/proc ) e) Bind mount the live filesystems proc,sysfs and dev mounts to the /mnt/new ( i.e mount -o bind /dev /mnt/new/dev ; mount -t sysfs /mnt/new/sysfs mount -t proc none /mnt/new/proc ) d) chroot to the new directory ( chroot /mnt/new /bin/bash ) e) fix up any device pointers in /etc/fstab (you might need to change around /dev/sdX etc to accord to the new filesystem parition/device ID - a better method is to get the UUID of the block device using blkid and add that into the /etc/fstab for each fo the mount points than using changable /dev entrys) f) run grub-install from the chroot. g) Done. Way2) (actually more risky and less easy than the above IMHO and will only work with an msdos disk label ) Block copy + fixup disk boundrys by hand + add paritions at the end a) Boot a live environment b) ddrescue /dev/old to /dev/new after running sfdisk on the old and new and keeping a copy of the cylinder/layout info somewhere to refer to c) partprobe the new /dev/new e) Run gparted/parted and align sectors etc f) Add/resize the last parition to fill the space g) Cross fingers. -Joel http://gplus.to/aenertia @aenertia On 28 May 2014 11:03, Catalin Soare lolinux.so...@gmail.com wrote: Hello, In one of my computers I have 2 HDDs. One of them is a 250 GB drive (debian) and the other is a 300 GB (data). I've decided to give one of them to my parents because the one they have right now makes some strange noises. So I've backed up and cleaned up the drive, and as we speak I am cloning my debian install (from the 250 GB disk) onto the other drive. My fstab contains blkids to identify the root, swap, and home partitions. Will the new clone just boot as if it was on the old drive? Also is there a simple method to resize the future home partition and move the root partition so that I don't end up with unallocated space on the drive? Basically I'd like to have a bootable system while also being able to use the entire space on the disk. Thank you for any suggestions, -- Sent from my Brick (TM) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cakiakgrb_uoalxwxpnqvt2c7ok8xoqxmv++zmdnp9vx1+zr...@mail.gmail.com
Re: exim4 fetchmail delivery more than 10 rejected
Jonathan Dowland j...@debian.org writes: Hi, This is a common problem (I remember hitting it myself, once upon a time!) The Debian Exim FAQ recommends changing fetchmail's behaviour, rather than Exim's: https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received Thanks, and yeah I read that before posting and was sort of amazed at the way the burden of getting around what is a quite an unpopular default in exim4 was to shift it to fetchmail. hehe... pretty slick. I saw how to use the fetchmail trick right off but felt like, `hey wait a minute..' I'm ready this to find a way to make a more sensible setting for my situation in exim4. That section tells you the setting can be altered but never says how in any detail, instead slipping right into the fetchmail crutch. I searched the rest of the FAQ thinking surely there would be some details about how to do it... but either I missed it, or it is not there. From there I went to google and found quite a few conflicting opinions about where and how to set such a thing, and I don't mean just the different locations one finds because of the two ways of organizing the setup (monolithic or multi file), but just different opinions. I never did find what seemed like a definitive explanation of how to do it. So, began experimenting... Oh wait a minute. I just looked ahead in this thread and noticed Brian's last respsonse which clears up the where and how of it. So will spare you all from more ill-informed blather... here. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/878upm1xpe@reader.local.lan
Re: exim4 fetchmail delivery more than 10 rejected
Brian a...@cityscape.co.uk writes: On Mon 26 May 2014 at 05:48:53 -0400, Harry Putnam wrote: I've tried adding this line: smtp_accept_queue_per_connection=300 I use smtp_accept_queue_per_connection=0 with the split-file configuration but testing with your setup does not cause any failure when exim4 is reloaded or restarted. I think you really should post the error message you get. Then I tried adding it to: /etc/exim4/update-exim4.conf.conf No. This is the wrong file. The exim4 FAQ tells of a way to put the load on fetchmail and diddle around with its config, but also says one might change it in exim4 but is not clear about where this change is made. I put it right at the start of MAIN CONFIGURATION SETTINGS. Haaa, thank you sir, now I can do some more directed experimenting. Oh, and is it really enough just to run `/etc/init.d/exim4 reload' (after making the edit) or would it be a time to use one or more of exim4's `update' commands. I'll have an excellent test setup.. I just ran fetchmail -c and see I have 227 messages waiting PS - and thanks for the smooth way of handling the thread interruption -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/874n0a1xej@reader.local.lan
Re: exim4 fetchmail delivery more than 10 rejected
Brian a...@cityscape.co.uk writes: [...] The exim4 FAQ tells of a way to put the load on fetchmail and diddle around with its config, but also says one might change it in exim4 but is not clear about where this change is made. I put it right at the start of MAIN CONFIGURATION SETTINGS. Haa... and as is often the case with good coaching... my first experiment of editing in just the way you describe above... then fetching 227 msgs shows conclusively that the ten msg limit is not mentioned at all. Thanks again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zji2zmdl@reader.local.lan
about heirloom mailx
Running jessie Trying to use heirloom mailx to test various exim4 settings and It works, but there is something in it that bugs me. Makes me think I'm doing something wrong. Here is a typical example mailx -v re...@location.com Subject: what ever ble bleh . ENTER And away it goes and outputs the smtp conversation ending in the message [...] LOG: MAIN Completed But then I never get the prompt back. The cmdline is live... that is, if I type a cmd it will be executed and then I get the prompt back. Or I can hit Enter, or ^c to get the prompt back. But shouldn't I get the prompt back when the process completes.. without having to do anything extra? Or am I just not using it correctly from the gate? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87vbsqzlyu@reader.local.lan
Re: exim4 fetchmail delivery more than 10 rejected
On Tue, May 27, 2014 at 09:47:09PM -0400, Harry Putnam wrote: Jonathan Dowland j...@debian.org writes: Hi, This is a common problem (I remember hitting it myself, once upon a time!) The Debian Exim FAQ recommends changing fetchmail's behaviour, rather than Exim's: https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received Thanks, and yeah I read that before posting and was sort of amazed at the way the burden of getting around what is a quite an unpopular default in exim4 was to shift it to fetchmail. hehe... pretty slick. I saw how to use the fetchmail trick right off but felt like, `hey wait a minute..' I'm ready this to find a way to make a more sensible setting for my situation in exim4. That section tells you the setting can be altered but never says how in any detail, instead slipping right into the fetchmail crutch. [...] So I read about this and was wondering why I don't have this problem since I've been using exim and fetchmail for years and years. My memory at this point is fuzzy, but I think I may have encountered the situation where mail was getting queued and one way or another, possibly using fetchmailconf, stumbled upon throwing a batchlimit 10 on each poll line. The result is that fetchmail deliberately ends (and reestablishes, if necessary) the SMTP connection every 10 messages. Yes, it's another fetchmail-based workaround, but I figured it was worth mentioning in this thread for the benefit of anyone else who might stumble upon it in the future. It might even make sense to put it into that FAQ on the wiki; I'd argue it's a better solution than postconnect since it doesn't require the fetchmail user to be in the Debian-exim group, and doesn't require giving up on exim by going straight through procmail. --Greg -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140528021518.ga3...@anthropohedron.net
Re: about heirloom mailx
On 28/05/14 14:16, Harry Putnam wrote: Running jessie Trying to use heirloom mailx to test various exim4 settings and It works, but there is something in it that bugs me. Makes me think I'm doing something wrong. Here is a typical example mailx -v re...@location.com Subject: what ever ble bleh . ENTER And away it goes and outputs the smtp conversation ending in the message [...] LOG: MAIN Completed But then I never get the prompt back. The cmdline is live... that is, if I type a cmd it will be executed and then I get the prompt back. Or I can hit Enter, or ^c to get the prompt back. But shouldn't I get the prompt back when the process completes.. without having to do anything extra? Or am I just not using it correctly from the gate? I'm not currently using heirloom mailx, or exim, so testing it is a bit hard - but are you getting the prompt _before_ the debug output? I suspect it might put itself into the background, which will give you the prompt, then the background process spits out the SMTP session. Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53854a25.8040...@walnut.gen.nz
Re: Cloning hdds of different sizes
On Wed, 28 May 2014, Catalin Soare wrote: In one of my computers I have 2 HDDs. One of them is a 250 GB drive (debian) and the other is a 300 GB (data). I've decided to give one of them to my parents because the one they have right now makes some strange noises. So I've backed up and cleaned up the drive, and as we speak I am cloning my debian install (from the 250 GB disk) onto the other drive. My fstab contains blkids to identify the root, swap, and home partitions. Will the new clone just boot as if it was on the old drive? Also is there a simple method to resize the future home partition and move the root partition so that I don't end up with unallocated space on the drive? Basically I'd like to have a bootable system while also being able to use the entire space on the disk. I found rsync more suitable than dedicated cloning software. I, too, only had three parttions -- /, /home, and swap -- that I wanted to enlarge and rearrange on a new larger drive. Generally, here's the procedure specific to your set up, not mine. 1. Boot with old system. 2. Partition the 300GB drive how you want it, and format the partitions. For safety, I called for a badblock check before formatting. 3. Use blkid to get the UUIDs of each new partition and write them down. 3. Shutdown the system and boot with a Linux LiveCD. Use a 64-bit Live if your system is 64-bit. Similarly, if 32-bit. 4. Use rsync to copy the files on each partition of the 250GB drive to the appropriate one on the 300GB. 5. Once the above copying is done, edit /etc/fstab on the 300GB drive by inserting the new UUIDs for each partition. Change labels, if needed. 6. Set up a chroot to the new cloned system on the 300GB drive. NOTE: I initially used a 32-bit LiveCD when cloning my system, and when I got to this step, the chroot to the 64-bit system on the drive wouldn't work. Booted with a 64-bit LiveCD, and it did. 7. Create a new initrd.img: Use grub-mkimage, IIRC. This is probably not necessary since we're cloning, but I did it on my system anyway. 8. Create a new grub.cfg: Use grub-mkconfig. 9. Install to MBR of the 300GB drive: Use install-grub. 10. Un-chroot, shutdown, remove or disconnect 250GB drive. 11. Reboot and see if it works. That's as best as I can remember. I made notes, but can't find them right now. Be sure to read and study all the mans for rsync, blkid, chroot, and the grub utilites. A search of the web for this procedure wouldn't hurt either, especially the proper procedure for chrooting. I didn't bother using GPT partitioning as MY new drive as it was only 500GB. The old one was 160GB. So, neither should you. Why make trouble for yourself. However, use a contemporary partitioning utility that automatically begins the first partition at the proper sector and aligns all the partitions. Good luck. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140527211545.21de9...@debian7.boseck208.net
Re: preferred overlay/union filesystem?
Chris Angelico ros...@gmail.com writes: On Wed, May 28, 2014 at 5:47 AM, Joe Pfeiffer pfeif...@cs.nmsu.edu wrote: Well, I don't want to keep two separate files (that's what I'm trying to get away from). It seems like the overlay filesystem would be a bit cleaner if it can work, but symbolic links elsewhere would be my second choice. As a variant of Kushal's suggestion of two symlinks to the same file, you could have the real file in one place (preferably where it's written to) and a symlink to it from the other place. If I understand the situation correctly, only one of the locations will be accessible at any time. When the user logs in, the original files will be hidden under the files provided by the encrypted filesystem. So, both files are actually ~/.bogofilter (say), just at different times. So you cannot have a symlink from one location to the other. -- regards, kushal pgpQlTJxpU881.pgp Description: PGP signature
Re: preferred overlay/union filesystem?
On Wed, May 28, 2014 at 3:21 PM, Kushal Kumaran kushal.kumaran+deb...@gmail.com wrote: Chris Angelico ros...@gmail.com writes: On Wed, May 28, 2014 at 5:47 AM, Joe Pfeiffer pfeif...@cs.nmsu.edu wrote: Well, I don't want to keep two separate files (that's what I'm trying to get away from). It seems like the overlay filesystem would be a bit cleaner if it can work, but symbolic links elsewhere would be my second choice. As a variant of Kushal's suggestion of two symlinks to the same file, you could have the real file in one place (preferably where it's written to) and a symlink to it from the other place. If I understand the situation correctly, only one of the locations will be accessible at any time. When the user logs in, the original files will be hidden under the files provided by the encrypted filesystem. So, both files are actually ~/.bogofilter (say), just at different times. So you cannot have a symlink from one location to the other. Ah! Gotcha. Then, yes; symlinks from both to the same destination. Not sure what a suitable destination is, though. ChrisA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAPTjJmrM_8gmDPyU4Bxay-h=ws0hzuk1uhyfa+2qbsynk-e...@mail.gmail.com
Re: Notities toevoegen aan PDF files
op 27-05-14 11:47, Paul van der Vlis schreef: op 26-05-14 22:09, Jan van Gemert schreef: op 26-05-14 18:25, Paul van der Vlis schreef: op 26-05-14 15:11, Matijs van Zuijlen schreef: Ik gebruik meestal Xournal, dat werkt goed. De opties van Evince zijn vrij beperkt vergeleken met wat PDF toestaat. Aan de andere kant heeft Evince het voordeel dat notities in de PDF zelf opgeslagen worden en dus door andere PDF-viewers bekeken kunnen worden. Best een mooie applicatie, maar echte sticky notes kun je er niet meer maken, volgens mij. En welliswaar kun je iets een kleurtje geven met een 'stift', maar een tekst selecteren om hem een kleurtje te geven lukt niet. Groet, Paul. Okular (debian testing 4.12.4-1 ) wel eens gebruikt. O.A notes toevoegen, markeren,omcirkelen, onderstrepen. Het werkt voor mij niet soepel, zeker als je met de muis iets moet omcirkelen. Bedankt voor je reactie, Okular kende ik nog niet Het is een KDE applicatie, onderdeel van het KDE project. Dat is niet ideaal in een Gnome omgeving lijkt me. En zo te horen ondersteund het dus ook niet echt van die sticky notes (gele papiertjes die je kunt verplaatsen). Groet, Paul. Ondersteund Okular ook, daar genoemd pop-up note. Maar Okular is inderdaad niet de 1e keus in een Gnome-omgeving. -- Groeten Jan van Gemert
Re: Mappen met hoofd/kleine letters
Paul van der Vlis schreef op vr 23-05-2014 om 15:11 [+0200]: Hallo, Ik heb op het moment nogal wat problemen met mappen en hoofdletters. Eerder waren mappen als Bureaublad, Documenten, Afbeeldingen, etc. met een hoofdletter, maar nu zie ik ze regelmatig ook met een kleine letter verschijnen. Dit is erg verwarrend. Ook zie ik bij mensen dat alles wat er op het bureaublad stond opeens weg is door dit probleem. Kent iemand dit probleem? Wat is de achtergrond? Ik ken het probleem nog niet. Ging er aan dit verschijnsel iets bijzonders vooraf, zoals een update, upgrade of een crash? Vriendelijke groet, Jan-Rens. -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1401216277.4680.4.ca...@batavia.fritz.box
Re: Mappen met hoofd/kleine letters
op 27-05-14 20:44, Jan-Rens Reitsma schreef: Paul van der Vlis schreef op vr 23-05-2014 om 15:11 [+0200]: Hallo, Ik heb op het moment nogal wat problemen met mappen en hoofdletters. Eerder waren mappen als Bureaublad, Documenten, Afbeeldingen, etc. met een hoofdletter, maar nu zie ik ze regelmatig ook met een kleine letter verschijnen. Dit is erg verwarrend. Ook zie ik bij mensen dat alles wat er op het bureaublad stond opeens weg is door dit probleem. Kent iemand dit probleem? Wat is de achtergrond? Ik ken het probleem nog niet. Ging er aan dit verschijnsel iets bijzonders vooraf, zoals een update, upgrade of een crash? Nee, niets bijzonders. Ik heb het eigenlijk maar bij 1 klant gezien en daar op alle computers (drie stuks). Bij deze klant heb ik automatische updates ingesteld door middel van het pakket unattended-upgrades. De upgrades worden geinstalleerd bij het afsluiten van de computers, dus waarschijnlijk is het de dag ervoor misgegaan. Toevallig was ik daar om een nieuwe printer te installeren. De klant is nogal zuinig met stroom, het zou me niets verbazen als ze 's avonds de stop eruit draaien o.i.d. Misschien waren de updates nog niet klaar toen ze de stroom er af haalden. Zoiets lijkt me mogelijk. Met vriendelijke groet, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5384e4bd.10...@vandervlis.nl
