Re: [gentoo-user] .config file for gentoo guest on vmware workstation 7.1.4

2011-04-09 Thread Adam Carter
>
> I had a working .config. Unfortunately, I left it at office.
>
> The main 'trap' usually would be the SCSI Driver.
>
> If you're using PVSCSI, go into SCSI & RAID, then SCSI Low Level
> Driver, then select VMware PVSCSI as built-in, not module.
>

Do you know which one workstation uses? AFAICT there's no option to choose
which controller is presented to the guest.

>
> If you're using LSI Logic, select Fusion MPT instead.
>

I think i have them both configured.

>
> Don't forget to emerge grub and edit /boot/grub/menu.lst
>

Yep, that's done.

Thanks.


Re: FEATURE: fixlafiles (was: [gentoo-user] Re: revdep-rebuild Not Fixing Broken Links)

2011-04-09 Thread Mick
On Saturday 09 April 2011 02:02:06 Allan Gottlieb wrote:
> On Fri, Apr 08 2011, Mick wrote:
> > On Friday 08 April 2011 19:51:10 Kevin O'Gorman wrote:
> >> I run that manually once in a while, but regularly clean a bunch of
> >> other things with a script I call "cleanup",
> >> -#!/bin/bash
> >> -dispatch-conf
> >> -revdep-rebuild
> >> -lafilefixer --justfixit
> >> -perl-cleaner all
> > 
> > The last one is now an option in /etc/make.conf under FEATURES: 
> > fixlafiles
> 
> This sounds great!  Outside of some extra time in emerging is there any
> reason *not* to add fixlafiles to FEATURES?

I haven't found any problems with it and the time it takes when there are .la 
files to be fixed is very short.  The make.conf man page says:

fixlafiles
 Modifies  .la  files  to  not include other .la files and
 some other fixes (order  of  flags,  duplicated  entries,
 ...)

YMMV ...
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] .config file for gentoo guest on vmware workstation 7.1.4

2011-04-09 Thread Pandu Poluan
On 2011-04-09, Adam Carter  wrote:
>>
>> I had a working .config. Unfortunately, I left it at office.
>>
>> The main 'trap' usually would be the SCSI Driver.
>>
>> If you're using PVSCSI, go into SCSI & RAID, then SCSI Low Level
>> Driver, then select VMware PVSCSI as built-in, not module.
>>
>
> Do you know which one workstation uses? AFAICT there's no option to choose
> which controller is presented to the guest.
>

Hmmm... IIRC there's an option to do that. There *is* one on
VirtualBox, can't remember VMware Workstation (my setup is on top of
ESX)

>>
>> If you're using LSI Logic, select Fusion MPT instead.
>>
>
> I think i have them both configured.
>

If you can boot using the LiveCD, try lsmod and see which driver is
being used. Do rmmod one-by-one until you hit a driver that can't be
removed, but lsmod doesn't list any other module using that one.

>>
>> Don't forget to emerge grub and edit /boot/grub/menu.lst
>>
>
> Yep, that's done.
>
> Thanks.
>


--
Pandu E Poluan - IT Optimizer
My website: http://pandu.poluan.info/



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Neil Bothwick
On Fri, 08 Apr 2011 18:36:28 -0500, Dale wrote:

> > A little time saver, if you have only one VG, set $LVM_VG_NAME to its
> > name and you can leave the VG name out of any lv* commands.

> I'll have more than one before long so may as well learn the long way.  
> Neat to know tho.  I'm hoping for about a 2Tb or maybe a 1.5Tb drive.  
> That should last me a while but I'm going to put my current 750Gb on 
> there too.

No matter how many drives you have, I doubt you'll need more than one
volume group.


-- 
Neil Bothwick

Top Oxymorons Number 7: Definite maybe


signature.asc
Description: PGP signature


Re: FEATURE: fixlafiles (was: [gentoo-user] Re: revdep-rebuild Not Fixing Broken Links)

2011-04-09 Thread Neil Bothwick
On Fri, 08 Apr 2011 21:02:06 -0400, Allan Gottlieb wrote:

> > The last one is now an option in /etc/make.conf under FEATURES:
> > fixlafiles  
> 
> This sounds great!  Outside of some extra time in emerging is there any
> reason *not* to add fixlafiles to FEATURES?

Yes, it's already in FEATURES by default :)

[nelz@yooden ~ 0]% grep fixlafiles /etc/make.conf
[nelz@yooden ~ 1]% emerge --info | grep fixlafiles
FEATURES="assume-digests binpkg-logs buildpkg distlocks fixlafiles
fixpackages news parallel-fetch preserve-libs protect-owned sandbox
sfperms strict unknown-features-warn unmerge-logs unmerge-orphans
userfetch"
[nelz@yooden ~ 0]% 


-- 
Neil Bothwick

Windows Error #02: Multitasking attempted. System confused.


signature.asc
Description: PGP signature


Re: [gentoo-user] .config file for gentoo guest on vmware workstation 7.1.4

2011-04-09 Thread Neil Bothwick
On Sat, 9 Apr 2011 17:02:14 +1000, Adam Carter wrote:

> > If you're using PVSCSI, go into SCSI & RAID, then SCSI Low Level
> > Driver, then select VMware PVSCSI as built-in, not module.
> >  
> 
> Do you know which one workstation uses? AFAICT there's no option to
> choose which controller is presented to the guest.

You get to choose when you create the VM.


-- 
Neil Bothwick

Member, National Association For Tagline Assimilators (NAFTA)


signature.asc
Description: PGP signature


Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Peter Humphrey
On Saturday 09 April 2011 09:52:01 Neil Bothwick wrote:

> No matter how many drives you have, I doubt you'll need more than one
> volume group.

...although I did find not long ago that a second VG for another, temporary 
distro kept things tidy.. This is not to contradict you though.

-- 
Rgds
Peter



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Neil Bothwick
On Sat, 9 Apr 2011 10:43:12 +0100, Peter Humphrey wrote:

> > No matter how many drives you have, I doubt you'll need more than one
> > volume group.  
> 
> ...although I did find not long ago that a second VG for another,
> temporary distro kept things tidy.. This is not to contradict you
> though.

Oh yes, and I have two VGs on my desktop, because I want to keep backups
completely separate. But for the usage Dale has mentioned, one VG is
best. If for no other reason that multiple VGs reduce the flexibility of
LVM.


-- 
Neil Bothwick

We've all heard that a million monkeys banging on a million
typewriters will eventually reproduce the works of Shakespeare.
Now, thanks to the Internet, we know this is not true.


signature.asc
Description: PGP signature


Re: [gentoo-user] mutt $index_format syntax

2011-04-09 Thread Alexey Mishustin
4/8/2011, "Vincent Launchbury"  вы писали:

>On 2011/04/08 02:40PM, Alexey Mishustin wrote:
>> For example, I don't understand what does -15.15 mean (in default value
>> "%4C %Z %{%b %d} %-15.15L (%4l) %s" )
>
>The "-15.15" is the same as the printf(3) format.

That's it. I had read man printf yesterday, but not found man 3 printf.
Seems to contain all information that I need...

>The minus sign means
>left align the field, the first number is the minimum field width, and
>the dot specifies that the next number is the precision, which for a
>string is the max number of characters to print.
>
>E.g "-15.20" would be a left aligned field atleast 15 characters wide,
>expanding upto 20 total, if the string is long enough.  But that could
>make things unaligned, so just keep the values the same.
>
>> why there are no width values for each column,
>
>%4C   -> message number (width 4)
>%Z-> Status flags (always 3 characters)
>%{%b %d}  -> (see below) Short month name, 2 digit day (constant width)
>%-15.15L  -> Address (width 15)
>(%4l) -> # of lines in the message (width 4)
>%s-> Subject (last field, width unimportant)
>
>> what do constructions %{another %s} mean.
>
>From the online manual [1], "%{format}" passes the date (in the sender's
>time zone) to strftime(3), so you could use "%{%Y-%m-%d}" for example,
>or just "%D" to use the setting from date_format.
>
>Perhaps tricky to read, but very flexible. Hope that helps.

Sure that helps! Thanks a lot.

>[1] http://www.mutt.org/doc/manual/manual-6.html#index_format

--
Regards,
Alex



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Neil Bothwick wrote:

On Fri, 08 Apr 2011 18:36:28 -0500, Dale wrote:

   

A little time saver, if you have only one VG, set $LVM_VG_NAME to its
name and you can leave the VG name out of any lv* commands.
   
   

I'll have more than one before long so may as well learn the long way.
Neat to know tho.  I'm hoping for about a 2Tb or maybe a 1.5Tb drive.
That should last me a while but I'm going to put my current 750Gb on
there too.
 

No matter how many drives you have, I doubt you'll need more than one
volume group.


   


Ah, I see what you are saying now.  I may have two or three PV's, and 
several LV's but only one VG.  My bulb got a little brighter.


I could end up putting /usr, /var, and such on LVM one day.  I wouldn't 
want to go as far as having to have the initrd thingy tho.  Basically a 
minimal / with some of the other growing stuff on LVM.


Still trying to grasp making it larger while still online.  Plain 
weird.  O_O


Dale

:-) :-)



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Neil Bothwick wrote:

On Sat, 9 Apr 2011 10:43:12 +0100, Peter Humphrey wrote:

   

No matter how many drives you have, I doubt you'll need more than one
volume group.
   

...although I did find not long ago that a second VG for another,
temporary distro kept things tidy.. This is not to contradict you
though.
 

Oh yes, and I have two VGs on my desktop, because I want to keep backups
completely separate. But for the usage Dale has mentioned, one VG is
best. If for no other reason that multiple VGs reduce the flexibility of
LVM.


   


And I wouldn't put another distro on here anyway.  I wuv my Gentoo. < 
dale hugs the Gentoo bytes on the drive platters >  lol  I think for me, 
just one would be enough.


One more question.  When I buy another drive, I use pvcreate to get the 
new drive ready for LVM.  What command adds it to the VG?  Is it 
vgcreate with some option?  I was sort of looking for something like 
vgadd or something but no luck finding that.  Maybe I am missing it on 
the howtos.


Dale

:-)  :-)



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Dale wrote:

Neil Bothwick wrote:

On Sat, 9 Apr 2011 10:43:12 +0100, Peter Humphrey wrote:


No matter how many drives you have, I doubt you'll need more than one
volume group.

...although I did find not long ago that a second VG for another,
temporary distro kept things tidy.. This is not to contradict you
though.

Oh yes, and I have two VGs on my desktop, because I want to keep backups
completely separate. But for the usage Dale has mentioned, one VG is
best. If for no other reason that multiple VGs reduce the flexibility of
LVM.




And I wouldn't put another distro on here anyway.  I wuv my Gentoo. < 
dale hugs the Gentoo bytes on the drive platters >  lol  I think for 
me, just one would be enough.


One more question.  When I buy another drive, I use pvcreate to get 
the new drive ready for LVM.  What command adds it to the VG?  Is it 
vgcreate with some option?  I was sort of looking for something like 
vgadd or something but no luck finding that.  Maybe I am missing it on 
the howtos.


Dale

:-)  :-)



That would be vgextend wouldn't it?  I just read another bit in another 
howto.


Dale

:-)  :-)



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Alan McKinnon
Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale did 
opine thusly:

> > the new drive ready for LVM.  What command adds it to the VG?  Is it 
> > vgcreate with some option?  I was sort of looking for something like 
> > vgadd or something but no luck finding that.  Maybe I am missing it on 
> > the howtos.
> > 
> > Dale
> > 
> > :-)  :-)
> 
> That would be vgextend wouldn't it?  I just read another bit in another 
> howto.

Yes.

PVs, VGs, LVs all have a concept of extend|resize|reduce. What that means 
depends on what you are working with, but they all make the thing bigger or 
smaller.

For a PV it means the underlying device's size changed, so the PV must change 
to match. Take a 500G drive, create 1 partition on it of 100G and make it a 
PV. Now enlarge the partition to 200G, you must extend the PV to match.

A VG isn't a single thing, it's a collection of things. Extending it means to 
add more PVs, reducing it means to take PVs out of the VG. Hopefully you will 
always remember to migrate the data off a PV before removing it from a VG :-)

Extend/Reduce an LV means to make the device larger/smaller. It is exactly the 
same thing as changing a partition size using fdisk. Obviously, you need to 
tweak the filesystem at the same time

-- 
alan dot mckinnon at gmail dot com



[gentoo-user] Re: FEATURE: fixlafiles

2011-04-09 Thread Allan Gottlieb
On Sat, Apr 09 2011, Neil Bothwick wrote:

> On Fri, 08 Apr 2011 21:02:06 -0400, Allan Gottlieb wrote:
>
>> > The last one is now an option in /etc/make.conf under FEATURES:
>> > fixlafiles  
>> 
>> This sounds great!  Outside of some extra time in emerging is there any
>> reason *not* to add fixlafiles to FEATURES?
>
> Yes, it's already in FEATURES by default :)

I was think of suggesting that :-).

So is the recommended policy to do one last lafilefixer --justfixit
for any la files effected before the FEATURE was made standard and then
strike it off the list of "first responders" for problems involving .la
files?

thanks,
allan



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Alan McKinnon wrote:

Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale did
opine thusly:
Yes.

PVs, VGs, LVs all have a concept of extend|resize|reduce. What that means
depends on what you are working with, but they all make the thing bigger or
smaller.

For a PV it means the underlying device's size changed, so the PV must change
to match. Take a 500G drive, create 1 partition on it of 100G and make it a
PV. Now enlarge the partition to 200G, you must extend the PV to match.

A VG isn't a single thing, it's a collection of things. Extending it means to
add more PVs, reducing it means to take PVs out of the VG. Hopefully you will
always remember to migrate the data off a PV before removing it from a VG :-)

Extend/Reduce an LV means to make the device larger/smaller. It is exactly the
same thing as changing a partition size using fdisk. Obviously, you need to
tweak the filesystem at the same time

   



So, when I get me a new drive, I use pvcreate to get it ready for LVM, 
then use vgextend to add it to the VG, then it is available for whatever 
LV I want to extend or to make a new LV?


I think I am catching on here.  It was just difficult for me to grasp 
how things are layered for some reason.  Some of the pictures I found 
helped a good bit tho.  Just helped me picture what the commands are 
doing exactly.


I did learn the hard way to resize the file system tho.  I forgot that 
earlier.  Sort of had me scratching my head for a bit.  lol


Dale

:-)  :-)



[gentoo-user] Re: FEATURE: fixlafiles

2011-04-09 Thread Dale

Neil Bothwick wrote:

On Fri, 08 Apr 2011 21:02:06 -0400, Allan Gottlieb wrote:

   

The last one is now an option in /etc/make.conf under FEATURES:
fixlafiles
   

This sounds great!  Outside of some extra time in emerging is there any
reason *not* to add fixlafiles to FEATURES?
 

Yes, it's already in FEATURES by default :)

[nelz@yooden ~ 0]% grep fixlafiles /etc/make.conf
[nelz@yooden ~ 1]% emerge --info | grep fixlafiles
FEATURES="assume-digests binpkg-logs buildpkg distlocks fixlafiles
fixpackages news parallel-fetch preserve-libs protect-owned sandbox
sfperms strict unknown-features-warn unmerge-logs unmerge-orphans
userfetch"
[nelz@yooden ~ 0]%


   


Mine is set in features too.  Thing is, I don't have lafilefixer 
installed.  I guess portage would say something about broken links if it 
was needed.  Right?


root@fireball / # eix lafilefixer
* dev-util/lafilefixer
 Available versions:  ~0.0.1 0.5
 Homepage:http://www.gentoo.org/
 Description: Utility to fix your .la files

root@fireball / #

Dale

:-)  :-)



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Joost Roeleveld
On Friday 08 April 2011 16:30:03 Dale wrote:
> J. Roeleveld wrote:
> > On Fri, April 8, 2011 11:01 pm, Dale wrote:
> >> root@fireball / #
> >> 
> >> I'm still trying to figure out how the naming part works tho.  Now to
> >> mount it and put something on it.  See if it works.
> > 
> > Naming part, there are 2 ways of finding it.
> > 1: /dev//
> > 2: /dev/mapper/-
> > 
> > You included a "-" in your VG-name, this is replaced with "--" under
> > /dev/mapper/
> > 
> >> Let me know if something doesn't look right.  Otherwise, I'll keep
> >> playing around with it.
> > 
> > Looks fine so far, don't forget to put a filesystem on
> > "/dev/sdb-vg/test"
> > to be able to mount it somewhere :)
> > 
> > --
> > Joost
> 
> The naming I was talking about was sort of like a label.  I wanted to
> use test, where I might use say data in real use, but ended up with this:
> 
> root@fireball / # df
> Filesystem   1K-blocks  Used Available Use% Mounted on
> << SNIP >>
> /dev/mapper/sdb--vg-test
>51606140184268  48800432   1% /mnt/temp
> root@fireball / #
> 
> I don't mind the sdb--vg part tho.  I guess that sort of points to what
> all is needed to get to that point.  Might come in handy if I needed to
> remove something tho.  Sort of tells me what is what.

True :)
I tend to start my VGs with "vg_". That way I know what they're 
for.
Also, it's a good idea to not name them "vg" as then you can get naming 
conflicts if you ever put the drive into another machine that also has a VG 
called that.

As example for the way I name them:
vg_.
On my server, I actually have 2 Volume Groups. One for the OS-parts (including 
VMs) and the other for the data.

> I did try to mount it before putting a file system on it.  I sort of
> missed that part somewhere.  I knew it needed it, just forgot to do it.
> Mount sort of puked on my keyboard to remind me.  lol

Hehe :)
I forget as well sometimes.

> Whew !!  Progress.  Oh, someone posted a link to a site that had
> pictures.  That helped a good bit.  It needed more detail tho.  I'm
> going to do some google image searches and see what I can find.

I think I posted more then 1 link, actually :)

> Thanks much.

You're welcome

--
Joost



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Joost Roeleveld
On Saturday 09 April 2011 00:28:20 Dale wrote:
> OK.  I learned something.  Check this out:
> 
> root@fireball / # df
> Filesystem   1K-blocks  Used Available Use% Mounted on
> << SNIP >>
> /dev/mapper/sdb--vg-test
>51606140  48910048 74652 100% /mnt/temp
> root@fireball / #
> 
> This is what I am doing here.  As I posted a while ago, I created a 50Gb
> LV.  I attempted to copy about 75Gbs to it which filled it up but I
> wanted to make sure it would.  lol  Then I used lvextend -L100G
> /dev/mapper/sdb--vg-test to make it larger.  I read I could do the same
> thing with lvresize but the example I was reading showed lvextend.  This
> is what I got now:
> 
> root@fireball / # lvdisplay
>--- Logical volume ---
>LV Name/dev/sdb-vg/test
>VG Namesdb-vg
>LV UUIDmixhOb-La6D-BwG4-Uz3l-P0ci-oGg5-YI3mN8
>LV Write Accessread/write
>LV Status  available
># open 1
>LV Size100.00 GiB
>Current LE 25600
>Segments   1
>Allocation inherit
>Read ahead sectors auto
>- currently set to 256
>Block device   254:0
> 
> root@fireball / #
> 
> So, according to that it is 100Gbs which is what I wanted.  Thing was,
> it didn't work.  So, h.  Light bulb moment.  Resize the file system
> silly.  After that, success.  So, I created something that wasn''t big
> enough, filled it up, made it bigger, fixed the file system and now it
> is working.  All while online too.  That is the weird part.
> 
> Still not comfy putting a OS on it but it is cool so far.

Nice :)

Btw, instead of specifying "final" size after resizing, you can actually tell 
it to "add" 20GB by doing:
lvrextend -L+20G /dev/sdb-vg/test

--
Joost



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Joost Roeleveld
On Saturday 09 April 2011 06:43:25 Dale wrote:
> Alan McKinnon wrote:
> > Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale
> > did
> > opine thusly:
> > Yes.
> > 
> > PVs, VGs, LVs all have a concept of extend|resize|reduce. What that
> > means
> > depends on what you are working with, but they all make the thing bigger
> > or smaller.
> > 
> > For a PV it means the underlying device's size changed, so the PV must
> > change to match. Take a 500G drive, create 1 partition on it of 100G
> > and make it a PV. Now enlarge the partition to 200G, you must extend
> > the PV to match.
> > 
> > A VG isn't a single thing, it's a collection of things. Extending it
> > means to add more PVs, reducing it means to take PVs out of the VG.
> > Hopefully you will always remember to migrate the data off a PV before
> > removing it from a VG :-)
> > 
> > Extend/Reduce an LV means to make the device larger/smaller. It is
> > exactly the same thing as changing a partition size using fdisk.
> > Obviously, you need to tweak the filesystem at the same time
> 
> So, when I get me a new drive, I use pvcreate to get it ready for LVM,
> then use vgextend to add it to the VG, then it is available for whatever
> LV I want to extend or to make a new LV?
> 
> I think I am catching on here.  It was just difficult for me to grasp
> how things are layered for some reason.  Some of the pictures I found
> helped a good bit tho.  Just helped me picture what the commands are
> doing exactly.
> 
> I did learn the hard way to resize the file system tho.  I forgot that
> earlier.  Sort of had me scratching my head for a bit.  lol

That's an easy one to miss :)

You do seem to be catching on quick on this.

--
Joost



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Joost Roeleveld wrote:

On Friday 08 April 2011 16:30:03 Dale wrote:
   


The naming I was talking about was sort of like a label.  I wanted to
use test, where I might use say data in real use, but ended up with this:

root@fireball / # df
Filesystem   1K-blocks  Used Available Use% Mounted on
<<  SNIP>>
/dev/mapper/sdb--vg-test
51606140184268  48800432   1% /mnt/temp
root@fireball / #

I don't mind the sdb--vg part tho.  I guess that sort of points to what
all is needed to get to that point.  Might come in handy if I needed to
remove something tho.  Sort of tells me what is what.
 

True :)
I tend to start my VGs with "vg_". That way I know what they're
for.
Also, it's a good idea to not name them "vg" as then you can get naming
conflicts if you ever put the drive into another machine that also has a VG
called that.

As example for the way I name them:
vg_.
On my server, I actually have 2 Volume Groups. One for the OS-parts (including
VMs) and the other for the data.

   


I wish it was like file system labels but I guess any clues is better 
than nothing.




I did try to mount it before putting a file system on it.  I sort of
missed that part somewhere.  I knew it needed it, just forgot to do it.
Mount sort of puked on my keyboard to remind me.  lol
 

Hehe :)
I forget as well sometimes.

   

Whew !!  Progress.  Oh, someone posted a link to a site that had
pictures.  That helped a good bit.  It needed more detail tho.  I'm
going to do some google image searches and see what I can find.
 

I think I posted more then 1 link, actually :)

   

Thanks much.
 

You're welcome

--
Joost
   


You did.  I think a couple of them had some pictures to but google image 
search found some more that helped.  Of course, reading the commands to 
see how they work helped too.  I just needed a picture to see how this 
was built up.


I learned a lot in the past couple days.  Still don't want my OS on it 
tho.  ;-)


Dale

:-)  :-)



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Joost Roeleveld wrote:


Nice :)

Btw, instead of specifying "final" size after resizing, you can actually tell
it to "add" 20GB by doing:
lvrextend -L+20G /dev/sdb-vg/test

--
Joost


   


So that was what the howto meant.  If I know the total I need then I can 
specify it but if I know the amount of extra space I need, I can just do 
+XX and it adds it.  That's neat.  Some coder had his/her thinking hat 
on that day.


Thanks.

Dale

:-)  :-)



Re: [gentoo-user] Re: FEATURE: fixlafiles

2011-04-09 Thread Neil Bothwick
On Sat, 09 Apr 2011 07:14:52 -0500, Dale wrote:

> Mine is set in features too.  Thing is, I don't have lafilefixer 
> installed.  I guess portage would say something about broken links if
> it was needed.  Right?

You don't need lafilefixer with a recent portage, it does the job itself.


-- 
Neil Bothwick

Energizer Bunny arrested, charged with battery :)


signature.asc
Description: PGP signature


Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Alan McKinnon
Apparently, though unproven, at 13:43 on Saturday 09 April 2011, Dale did 
opine thusly:

> So, when I get me a new drive, I use pvcreate to get it ready for LVM, 
> then use vgextend to add it to the VG, then it is available for whatever 
> LV I want to extend or to make a new LV?

Yup, that's really what it's all about.



LVM will decide for itself what bits of what PV to use for each LV, you should 
just let it go ahead and make it's own decisions. The man page describes 
options where you can control stuff - like striping and mirroring. I find this 
just confuses the issue though and makes stuff needlessly complex.

A much better viewpoint is you deal with your striping and performance issues 
at a lower layer - RAID - and treat LVM as something that creates a gigantic 
storage bucket where you take out how much you need and don't care where it 
is. If two drives have vastly different performance characteristics and you 
find yourself having to dictate to LVM what to do, then they really should not 
be in the same VG at all.

-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Neil Bothwick
On Sat, 09 Apr 2011 08:00:49 -0500, Dale wrote:

> I wish it was like file system labels but I guess any clues is better 
> than nothing.

It is like filesystem labels in that you can give VGs and LVs meaningful
names. You can use filesystem labels too, if you feel the need. A logical
volume is just a block device, like /dev/sda1, you can do the same to
either in terms of filesystems.


-- 
Neil Bothwick

"You know how dumb the average person is? Well, statistically, half of
them are even dumber than that" - Lewton, P.I.


signature.asc
Description: PGP signature


Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Dale

Joost Roeleveld wrote:

On Saturday 09 April 2011 06:43:25 Dale wrote:
   

Alan McKinnon wrote:
 

Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale
did
opine thusly:
Yes.

PVs, VGs, LVs all have a concept of extend|resize|reduce. What that
means
depends on what you are working with, but they all make the thing bigger
or smaller.

For a PV it means the underlying device's size changed, so the PV must
change to match. Take a 500G drive, create 1 partition on it of 100G
and make it a PV. Now enlarge the partition to 200G, you must extend
the PV to match.

A VG isn't a single thing, it's a collection of things. Extending it
means to add more PVs, reducing it means to take PVs out of the VG.
Hopefully you will always remember to migrate the data off a PV before
removing it from a VG :-)

Extend/Reduce an LV means to make the device larger/smaller. It is
exactly the same thing as changing a partition size using fdisk.
Obviously, you need to tweak the filesystem at the same time
   

So, when I get me a new drive, I use pvcreate to get it ready for LVM,
then use vgextend to add it to the VG, then it is available for whatever
LV I want to extend or to make a new LV?

I think I am catching on here.  It was just difficult for me to grasp
how things are layered for some reason.  Some of the pictures I found
helped a good bit tho.  Just helped me picture what the commands are
doing exactly.

I did learn the hard way to resize the file system tho.  I forgot that
earlier.  Sort of had me scratching my head for a bit.  lol
 

That's an easy one to miss :)

You do seem to be catching on quick on this.

--
Joost

   


I think I am too.  Since folks know I am disabled anyway, I went to the 
Dr the other day.  The new meds aren't perfect but it is better.  When I 
go back, he may change it to another med.  He just wanted to try this 
first.  It does sort of help me to get a better grasp on things tho.  
Sort of weird in a way.  That part is like a side effect.  :/


I'm just needing to find me a good LARGE drive to put in here.  I'm 
checking out the reviews but it just seems most have issues.  May just 
have to buy one, work the stuffing out of it with a script or something 
to see if it holds up.


I see some of the large drives spin slower, some a lot slower.  Given 
the density of the data, are they about as fast as a drive that spins at 
7200?  My main drives for my OS and the large drive I already have turn 
at 7200 rpms.  I'm just curious if that would be slower or because of 
the density of the data, it doesn't matter.  I get about 80 to 100Mb/sec 
on my current drives.  I have 3gbs/sec drives which is what my mobo 
maxes out at.  I thought about getting a 6Gb/sec just in case I upgrade 
my mobo later.


My data drive mostly has audio/video stuff but does contain pictures I 
took with my camera and some documents, mostly saved web pages or OOo 
stuff.  My 750Gb drives plays audio/video stuff just fine, even the HD 
stuff.  I just wouldn't want to get a drive that is slow enough to cause 
pauses and such.


I see newegg has 3Tb drives too.  he he he he  O_O

Thoughts?

Dale

:-)  :-)



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Thanasis
on 04/09/2011 04:33 PM Dale wrote the following:
> 
> I'm just needing to find me a good LARGE drive to put in here.  I'm
> checking out the reviews but it just seems most have issues.
> 
> Thoughts?
>
I think you should be safe with WD1002FAEX, WD1502FAEX and WD2002FAEX.



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Mark Knecht
On Sat, Apr 9, 2011 at 6:33 AM, Dale  wrote:

>
> I think I am too.  Since folks know I am disabled anyway, I went to the Dr
> the other day.  The new meds aren't perfect but it is better.  When I go
> back, he may change it to another med.  He just wanted to try this first.
>  It does sort of help me to get a better grasp on things tho.  Sort of weird
> in a way.  That part is like a side effect.  :/
>
> I'm just needing to find me a good LARGE drive to put in here.  I'm checking
> out the reviews but it just seems most have issues.  May just have to buy
> one, work the stuffing out of it with a script or something to see if it
> holds up.
>
> I see some of the large drives spin slower, some a lot slower.  Given the
> density of the data, are they about as fast as a drive that spins at 7200?
>  My main drives for my OS and the large drive I already have turn at 7200
> rpms.  I'm just curious if that would be slower or because of the density of
> the data, it doesn't matter.  I get about 80 to 100Mb/sec on my current
> drives.  I have 3gbs/sec drives which is what my mobo maxes out at.  I
> thought about getting a 6Gb/sec just in case I upgrade my mobo later.
>
> My data drive mostly has audio/video stuff but does contain pictures I took
> with my camera and some documents, mostly saved web pages or OOo stuff.  My
> 750Gb drives plays audio/video stuff just fine, even the HD stuff.  I just
> wouldn't want to get a drive that is slow enough to cause pauses and such.
>
> I see newegg has 3Tb drives too.  he he he he  O_O
>
> Thoughts?
>
> Dale

Good thread Dale. I've been busy this week so I finally read the whole
thing, start to finish, this morning. Good LVM info which I expect
I'll use one of these days myself.

Personally II think one thing you might want to consider, given your
concerns about not losing important personal data, is to investigate
RAID with the same level of focus that you are doing with LVM. Instead
of buying very large drives (3TB) you can build a large RAID6 or RAID5
out of smaller 500GB or 1TB drives. Personally my home compute server,
which runs 4 copies of Windows 7 in VMWare and Virtualbox for trading
in the futures market, is set up this way:

- Five 500GB WD RAID Edition physical drives

- /boot is just a 100MB partition on /dev/sda, but I've saved more
partition space on other drives with various kernel images should
/dev/sda fail.

- Gentoo is on a 50GB 5-drive RAID1. That's a LOT of redundancy. I can
technically lose 4 drives and the system continues to work fine. For
the OS that's essentially unkillable short of someting like a power
supply failure taking out all the drives or the MB.

- /home is on a 5-drive RAID6 using 50GB partitions. That gives me a
total of 150GB storage personally for my pictures, videos, code, etc.,
and allows 2 drives to fail without losing data.

- /VirtualMachines is on a 5-drive RAID6 using the remaining 400GB on
each drive, so that's 1.2TB with redundancy of a 2-drive loss being
protected.

I then have a few external eSATA hard drives that I use for backups.
/home to one pair, /VirtualMachines to another pair.

I think if I was to set up this system from scratch again I might
consider one large RAID6 using 450GB and putting /home in one LV and
/VirtualMachines in another. The advantage would be that over time, if
my personal needs increased, I could resize the LVs more easily than
resizing the RAIDs. (Which is also possible but beyond the scope of
this thread...)

Anyway, it's just another idea about how you can use the same hardware
in a different configuration. Five 1TB drives as a RAID6 gives you
both 3TB of storage as well as far more reliability. One 3TB drive by
itself can die and everything is gone.

Congrats on your learning experience and I hope it continues to be
successful for you.

Cheers,
Mark



Re: [gentoo-user] LVM for data drives but not the OS

2011-04-09 Thread Joost Roeleveld
On Saturday 09 April 2011 08:04:19 Dale wrote:
> Joost Roeleveld wrote:
> > Nice :)
> > 
> > Btw, instead of specifying "final" size after resizing, you can actually
> > tell it to "add" 20GB by doing:
> > lvrextend -L+20G /dev/sdb-vg/test
> > 
> > --
> > Joost
> 
> So that was what the howto meant.  If I know the total I need then I can
> specify it but if I know the amount of extra space I need, I can just do
> +XX and it adds it.  That's neat.  Some coder had his/her thinking hat
> on that day.

For completeness, I just want to add that if there is not sufficient space 
available in the VG. The command will fail with a message telling you there is 
not enough room :)

--
Joost




[gentoo-user] [OT] Disk recommendations?

2011-04-09 Thread Peter Humphrey
Hello list,

I've seen some discussion of hard disks on this list recently, but I didn't 
notice any reference to Samsung Spinpoint F3 disks.

I have two of these in my workstation; if I were thinking of adding 3 more to 
make a more robust system, what advice would I receive?

-- 
Rgds
Peter



Re: [gentoo-user] [OT] Disk recommendations?

2011-04-09 Thread Mark Knecht
On Sat, Apr 9, 2011 at 1:00 PM, Peter Humphrey  wrote:
> Hello list,
>
> I've seen some discussion of hard disks on this list recently, but I didn't
> notice any reference to Samsung Spinpoint F3 disks.
>
> I have two of these in my workstation; if I were thinking of adding 3 more to
> make a more robust system, what advice would I receive?
>
> --
> Rgds
> Peter

Some questions:

Are you running a RAID?

Are you considering going to RAID?

Are you looking for a little redundancy or a lot of redundancy?

What are your future space & drive bandwidth requirements vs today's
requirements?

Sort of hard to give any inputs (not even advice) not knowing what
your usage model is.

Cheers,
Mark



Re: [gentoo-user] .config file for gentoo guest on vmware workstation 7.1.4

2011-04-09 Thread James Wall
On Apr 8, 2011 11:13 PM, "Pandu Poluan"  wrote:
>
> I had a working .config. Unfortunately, I left it at office.
>
> The main 'trap' usually would be the SCSI Driver.
>
> If you're using PVSCSI, go into SCSI & RAID, then SCSI Low Level
> Driver, then select VMware PVSCSI as built-in, not module.
>
> If you're using LSI Logic, select Fusion MPT instead.
>
> Don't forget to emerge grub and edit /boot/grub/menu.lst
>
> (and please excuse my top-posting. Gmail mobile can only top post; it
> hides the message being replied, and automatically appends the message
> after mine)
>
> Rgds,
>
>
> On 2011-04-09, Adam Carter  wrote:
> > Hi All,
> >
> > I'm getting the usual cant boot root device error on my gentoo guest.
AFAICT
> > i've built all the relevant scsi adapter and filesystem drivers into the
> > kernel. Most of the info on the web is a bit old and talks about other
> > vmware versions - can someone share a working .config? The guest is
using
> > 2.6.38,
> >
> > Cheers
> >
>
>
> --
> --
> Pandu E Poluan - IT Optimizer
> My website: http://pandu.poluan.info/
>
I am posting now from Gmail mobile by selecting the respond inline button
towards the bottom of the compose screen. I just get rid of the virtual
keyboard to find it.
James Wall


Re: [gentoo-user] .config file for gentoo guest on vmware workstation 7.1.4

2011-04-09 Thread Pandu Poluan
On 2011-04-10, James Wall  wrote:
> On Apr 8, 2011 11:13 PM, "Pandu Poluan"  wrote:
>>
>> I had a working .config. Unfortunately, I left it at office.
>>
>> The main 'trap' usually would be the SCSI Driver.
>>
>> If you're using PVSCSI, go into SCSI & RAID, then SCSI Low Level
>> Driver, then select VMware PVSCSI as built-in, not module.
>>
>> If you're using LSI Logic, select Fusion MPT instead.
>>
>> Don't forget to emerge grub and edit /boot/grub/menu.lst
>>
>> (and please excuse my top-posting. Gmail mobile can only top post; it
>> hides the message being replied, and automatically appends the message
>> after mine)
>>
>> Rgds,
>>
>>
>> On 2011-04-09, Adam Carter  wrote:
>> > Hi All,
>> >
>> > I'm getting the usual cant boot root device error on my gentoo guest.
> AFAICT
>> > i've built all the relevant scsi adapter and filesystem drivers into the
>> > kernel. Most of the info on the web is a bit old and talks about other
>> > vmware versions - can someone share a working .config? The guest is
> using
>> > 2.6.38,
>> >
>> > Cheers
>> >
>>
>>
>> --
>> --
>> Pandu E Poluan - IT Optimizer
>> My website: http://pandu.poluan.info/
>>
> I am posting now from Gmail mobile by selecting the respond inline button
> towards the bottom of the compose screen. I just get rid of the virtual
> keyboard to find it.
> James Wall
>

No such thing in Gmail Java Mobile Client for Symbian (I'm using a
Nokia E72-1). Neither is an option to reply inline in Gmail's Mobile
website.

I have to browse to Gmail's HTML website if I want to reply inline.
And it's a great inconvenience trying to view Gmail HTML even in Opera
Mobile (320x240)

--
Pandu E Poluan - IT Optimizer
My website: http://pandu.poluan.info/