Re: [SLUG] linked in - please block
On Tue, Dec 14, 2010 at 10:56 AM, Nick Andrew n...@nick-andrew.net wrote: On Tue, Dec 14, 2010 at 09:51:56AM +1100, Nigel Allen wrote: I have already complained to linkedin - not received a response yet. I'm not sure how linkedin can know that slug@slug.org.au is a mailing list and not an individual's email address. Presumably the slug list should reject email from non-subscribers, or alternately send a confirm request to the sender (which will eliminate automated emails like linkedin). A formal motion passed at a general meeting in 2003 requires that the SLUG mailing lists not reject email from non-subscribers, or even force such emails to be moderated. http://lists.slug.org.au/archives/slug/2003/10/msg00645.html has details on the proposed options and the voting. Nick. -- PGP Key ID = 0x418487E7 http://www.nick-andrew.net/ PGP Key fingerprint = B3ED 6894 8E49 1770 C24A 67E3 6266 6EB9 4184 87E7 -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] DD images and checksums
Hey guys. I've searched the Ubuntu forums for an answer and couldn't find one, so I figured I'd ask here instead. If I use DD to back up my USB drive to a file, should I expect the checksum of the image file created to be the same as the checksum produced by the device (for instance, /dev/sdb)? I've been getting different checksums and I wanted to know if it was because of an error writing the image file, or because of something else. Regards, Robert W. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] DD images and checksums
On Thu, Dec 23, 2010 at 13:07, Robert W robertw...@gmail.com wrote: If I use DD to back up my USB drive to a file, should I expect the checksum of the image file created to be the same as the checksum produced by the device (for instance, /dev/sdb)? I've been getting different checksums and I wanted to know if it was because of an error writing the image file, or because of something else. I discovered this with dd if=/dev/scd0 may be 2 years ago. dd produces an output file which is a certain size (has a one or more trailing sectors from memory). Then I burnt that image back to disc, ran dd on the new disc and got an _additional_ sector or so over and above the extra I already got the first time. So I did some research and came across wodim and readom (aptitude install wodim). wodim/readom knows the magic to not include extra sectors. At least AFAICT/remember. hth zen PS Here's my rough n hacky cheat sheet for cd/dvd commands (sorry about any line wrapping): genisoimage -J -r -f -V myvolname -o image.iso -graft-points /=symlink-farm-dir # -J, -joliet Generate Joliet directory information # -r, -rational-rock Generate rationalized Rock Ridge directory information # -R, -rock Generate Rock Ridge directory information - -r better/modern # -o FILE, -output FILE Set output file name # -path-list FILE File with list of pathnames to process # -f, -follow-links Follow symbolic links # -V ID, -volid IDSet Volume ID # -graft-points Allow to use graft points for filenames # -T, -translation-table Generate translation tables for systems that don't understand long filenames # -hide-joliet-trans-tbl Hide TRANS.TBL from Joliet tree # -joliet-longAllow Joliet file names to be 103 Unicode characters # -hide-rr-moved Rename RR_MOVED to .rr_moved in Rock Ridge tree # -hide-hfs GLOBFILE Hide HFS file # -g, -apple Add Apple ISO9660 extensions # -h, -hfsCreate ISO9660/HFS hybrid # -split-output Split output into files of approx. 1GB size # -cache-inodes Cache inodes (needed to detect hard links) # RECORD ISO IMAGE, from FILE onto BLANK DISC :: sudo wodim -v -eject dev=/dev/scd0 image.iso #sudo wodim -v -eject speed=4 dev=/dev/sr0 image.iso #If the overall speed of the system is sufficient and the structure of #the filesystem is not too complex, wodim will run without creating an #image of the ISO 9660 filesystem. Simply run the pipeline: # genisoimage -R /master/tree | wodim -v fs=6m speed=2 dev=2,0 - # CREATE/ RIP ISO IMAGE data CD/DVD, from DISC to ISO FILE :: sudo readom dev=/dev/scd0 f=free-nrg.iso # To write a tar archive directly to a CD that will later contain a simple # ISO9660 filesystem with the tar archive call: tar cf - . | genisoimage -stream-media-size 333000 | wodim dev=b,t,l -dao tsize=333000s - # combine gen image/ write: genisoimage -J -r -f -V myvolname -graft-points /=symlink-farm-dir -stream-media-size 333000 | wodim dev=/dev/sr0 -dao tsize=333000s - ???check??? # Example of two alternating (actually, parallel), commands, # to optimally read in a bunch of DVDs into a local mirror: sudo readom dev=/dev/scd0 f=s.img eject # (alternate with filename 't.img' instead of 's.img') sudo mount -o loop s.img u/ sudo nice rsync -av u/ my-mirror/ sudo umount u/ sudo rm s.img # ditto for alternate t.img -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] pdf nup that preserves hyperlinks?
Hi Folks, I want to create an n-up version of slides+txt for a tutorial for LCA11. I used to use standard LaTeX and postscript specials for hyperlinks, then psnup, then ps2pdf. This preserved hyperlinks. But the current version of the style class we're supposed to use for corporate branding is pdflatex only, and produces PDFs. So, is there a reasonable way to munge the PDF file into two-up, and keep hyperlinks? (`reasonable' here means something I can stick as a command into a makefile). Peter C -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] DD images and checksums
On Thu, Dec 23, 2010 at 13:07, Robert W robertw...@gmail.com wrote: I've searched the Ubuntu forums for an answer and couldn't find one, so I figured I'd ask here instead. If I use DD to back up my USB drive to a file, should I expect the checksum of the image file created to be the same as the checksum produced by the device (for instance, /dev/sdb)? I've been getting different checksums and I wanted to know if it was because of an error writing the image file, or because of something else. Assuming that you are not *using* the USB device at the time, you should get the same values; I often use that to verify that a copy of a disc is correct. Regards, Daniel -- ✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Port fat server to slim server - pointers??
Hi All, I have a home server, it's name is jester. Jester is a behemoth compared to what I actually need. It's a quad-core, 4GB, 2x500GB RAID on LVM with GB ethernet, to serve a few files + CUPS, run a squid proxy, some small MySQL DBs, do some basic DHCP/DNS and poll a weather station and solar inverter pumping the results into cacti. Consequently I've shouted myself a new toy: a QNAP TS-459 Pro (see http://bit.ly/eTKLCq) with 4x2TB in RAID5. Here's the plan: 1. Migrate all the file sharing duties to the QNAP 2. Migrate DHCP to the QNAP (or the router...don't really care) 3. Migrate the DBs to the QNAP (yes it does MySQL!) 4. Move the printer over to the QNAP 5. This leaves DNS, SNMP/Cacti, and Squid on Jester. Now migrating my remaining setup (#5) to a single 8GB SSD is where I'm a little stuck. The QNAP supports both iSCSI and NFS, so I was thinking I could use the SSD for /boot and the root fs, then mount the rest from NFS and/or iSCSI. The kicker is; how? How do I migrate this stuff with minimal fuss? I was considering just creating the iSCSI/NFS mounts, rsync all the data over (permissions and everything of course), then drop to single user (or busybox etc) and change the mounts to use the iSCSI/NFS instead of the LVM mirror. So, now we have all the non-rootFS and non-/boot stuff taken care of. Next I rsync the rootFS and /boot onto the SSD (yes, they will fit inside 8GB...with room to spare): FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg00-root 15G 604M 15G 4% / ... /dev/md0 456M 56M 396M 13% /boot --- TOTAL 660M (onto 8GB SSD) --- This leaves GRUB and swap. How the heck do I tell GRUB that the SSD is now groot=(hd0,0)?? Or is this not important once I rip out the 2x500GB drives leaving only the SSD?? Next swap - anyone with experience running swap over iSCSI?? Currently swap barely gets tickled, and removing file/print/SQL duties should significantly reduce the memory footprint so I'm not expecting any serious I/O here. Lastly, iSCSI - anyone feel like pointing me in the direction of a neat iSCSI-on-Ubuntu primer? (don't say google, I've done that - just want to know if there's a kick-butt-doco I missed :) Thanks in advance and Merry Christmas/New Year to you all! Cheers, James PS - once jester is doing basic snmp/cacti/squid/etc and the QNAP doing the heavy-lifting, I intend under-clocking the little dear from 2.66GHz to about 1.6GHz :) Save the planet and all that. smime.p7s Description: S/MIME cryptographic signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Port fat server to slim server - pointers??
On 23/12/10 18:11, James Gray wrote: Hi All, I have a home server, it's name is jester. Jester is a behemoth compared to what I actually need. It's a quad-core, 4GB, 2x500GB RAID on LVM with GB ethernet, to serve a few files + CUPS, run a squid proxy, some small MySQL DBs, do some basic DHCP/DNS and poll a weather station and solar inverter pumping the results into cacti. Consequently I've shouted myself a new toy: a QNAP TS-459 Pro (see http://bit.ly/eTKLCq) with 4x2TB in RAID5. Here's the plan: 1. Migrate all the file sharing duties to the QNAP 2. Migrate DHCP to the QNAP (or the router...don't really care) 3. Migrate the DBs to the QNAP (yes it does MySQL!) 4. Move the printer over to the QNAP 5. This leaves DNS, SNMP/Cacti, and Squid on Jester. Now migrating my remaining setup (#5) to a single 8GB SSD is where I'm a little stuck. The QNAP supports both iSCSI and NFS, so I was thinking I could use the SSD for /boot and the root fs, then mount the rest from NFS and/or iSCSI. The kicker is; how? How do I migrate this stuff with minimal fuss? I was considering just creating the iSCSI/NFS mounts, rsync all the data over (permissions and everything of course), then drop to single user (or busybox etc) and change the mounts to use the iSCSI/NFS instead of the LVM mirror. Any particular reason for using iscsi or nfs to mount local data? (your going to have to mount stuff to share it over nfs anyway, might as well use it) I mean all the drives are inside the box just mount/symlink them where you want. no overhead and simpler on your brain. So, now we have all the non-rootFS and non-/boot stuff taken care of. Next I rsync the rootFS and /boot onto the SSD (yes, they will fit inside 8GB...with room to spare): I'd just make / the SSD and include boot with it, then symlink out any actual data storage needs (/var/lib/mysql say), perhaps make a partition on your raid for /home. (personally I'd use a larger than 8gb SSD but your call) also I'd think about making a few small non raided partitions on your drives, I use them for the various tables for mythtv (different tables different spindles), complete overkill to be sure but ey, why not ;- This leaves GRUB and swap. How the heck do I tell GRUB that the SSD is now groot=(hd0,0)?? Or is this not important once I rip out the 2x500GB drives leaving only the SSD?? just reconfig grub, if its grub2 under ubuntu there is a nice menu system that lets you install it on all drives, you just need to tell it where /boot is, its a bit of a sequence, booting off a livecd or some such generally. Next swap - anyone with experience running swap over iSCSI?? Currently swap barely gets tickled, and removing file/print/SQL duties should significantly reduce the memory footprint so I'm not expecting any serious I/O here. Lastly, iSCSI - anyone feel like pointing me in the direction of a neat iSCSI-on-Ubuntu primer? (don't say google, I've done that - just want to know if there's a kick-butt-doco I missed :) Thanks in advance and Merry Christmas/New Year to you all! Cheers, James PS - once jester is doing basic snmp/cacti/squid/etc and the QNAP doing the heavy-lifting, I intend under-clocking the little dear from 2.66GHz to about 1.6GHz :) Save the planet and all that. I wouldn't under clock it, it should support dynamic clocking (one presumes) that will drop the clock pretty low when idle, then bump it up when in use. This often will save power as the CPU can stay in low power sleep states for longer, at least on the smaller end of the scale. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Port fat server to slim server - pointers??
On 23/12/2010, at 6:32 PM, Jake Anderson wrote: On 23/12/10 18:11, James Gray wrote: 5. This leaves DNS, SNMP/Cacti, and Squid on Jester. Now migrating my remaining setup (#5) to a single 8GB SSD is where I'm a little stuck. The QNAP supports both iSCSI and NFS, so I was thinking I could use the SSD for /boot and the root fs, then mount the rest from NFS and/or iSCSI. The kicker is; how? How do I migrate this stuff with minimal fuss? I was considering just creating the iSCSI/NFS mounts, rsync all the data over (permissions and everything of course), then drop to single user (or busybox etc) and change the mounts to use the iSCSI/NFS instead of the LVM mirror. Any particular reason for using iscsi or nfs to mount local data? (your going to have to mount stuff to share it over nfs anyway, might as well use it) I mean all the drives are inside the box just mount/symlink them where you want. no overhead and simpler on your brain. Though about this approach, but I have two reasons for not going this way: I actually slice up my boxes into more than just rootFS, /boot and swap, so symlinking /usr, /home, /var, etc ... would be pretty evil! Secondly, I've never really played much with network-hosted system volumes and really want to play with stuff like /home on NFS and swap on iSCSI etc. So, now we have all the non-rootFS and non-/boot stuff taken care of. Next I rsync the rootFS and /boot onto the SSD (yes, they will fit inside 8GB...with room to spare): I'd just make / the SSD and include boot with it, then symlink out any actual data storage needs (/var/lib/mysql say), perhaps make a partition on your raid for /home. (personally I'd use a larger than 8gb SSD but your call) also I'd think about making a few small non raided partitions on your drives, I use them for the various tables for mythtv (different tables different spindles), complete overkill to be sure but ey, why not ;- Not sure we're on the same page here. The QNAP (think network storage) will be hosting everything OTHER than rootFS and /boot. The SSD will only have /boot and rootFS. Hence slim server as opposed to pure thin server. My distinction between the two: thin - no local storage at all. Pure net-booting, net-storage. slim - local storage for booting and root file system. All *other* storage on the network. This leaves GRUB and swap. How the heck do I tell GRUB that the SSD is now groot=(hd0,0)?? Or is this not important once I rip out the 2x500GB drives leaving only the SSD?? just reconfig grub, if its grub2 under ubuntu there is a nice menu system that lets you install it on all drives, you just need to tell it where /boot is, its a bit of a sequence, booting off a livecd or some such generally. Cool - been a while since I've messed around with boot loaders (ah the good ol' LI202020202020 days! heheh). I'll dig around the Ubuntu-sphere for some more info. PS - once jester is doing basic snmp/cacti/squid/etc and the QNAP doing the heavy-lifting, I intend under-clocking the little dear from 2.66GHz to about 1.6GHz :) Save the planet and all that. I wouldn't under clock it, it should support dynamic clocking (one presumes) that will drop the clock pretty low when idle, then bump it up when in use. This often will save power as the CPU can stay in low power sleep states for longer, at least on the smaller end of the scale. Yep - will do that as well as under-clocking (which is the plan). THe under-clocking will also reduce heat and power on the FSB etc. too, which wouldn't happen with dynamic scaling alone AFAIK. Happy to be proven wrong on this as the CPU barely breaks out of brrr, I'm freezing, can someone please do something to warm me up mode, and rarely heats up much beyond ambient, so if I can avoid the under-clockingGREAT! The two 15k RPM 3.5 500GB drives though, they generate a metric truck load of heat!! Hence the reason I'm ditching them for an SSD and external NAS. Thanks for the insight Jake! Cheers, James smime.p7s Description: S/MIME cryptographic signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
