2012/3/2 Matthew Finkel :
>
> It's definitely an interesting dilemma, but one that was expected to happen
> eventually. Lucky Gentoo doesn't have to worry about release cycles. MariaDB
> is in portage so, in theory, it shouldn't be too difficult for any of us to
> make the switch.
Seeing how succe
On 2012-03-03 7:26 PM, Michael Orlitzky wrote:
On 03/03/2012 03:21 PM, Tanstaafl wrote:
No one has a template they can use to simply clone me a ready to go
hardened VM?
Or interested in earning a little money?
It's probably the "Microsoft Hyper-V" part that's scaring people away.
Ahh... g
Hi. In my last update, the system wanted to emerge
x11-libs/cairo-1.10.2-r2, but the file EGL/egl.h is missing. Now that file
used to be provided by media-libs/mesa, but it seems the file is no
longer there.
I am running gentoo unstable 64-bit.
Any ideas as to how to solve this problem?
Thanks
Jarry wrote:
> On 01-Mar-12 21:29, walt wrote:
> > On 03/01/2012 09:55 AM, Jarry wrote:
> >> What could be the problem? I remember just yesterday I updated
> >> bind from 9.7.4_p1 to 9.8.1_p1, but today recompilation simply
> >> failed...
> >
> > I'm getting exactly the same error, so I'd say the
On 2012-03-03 10:55 PM, Pandu Poluan wrote:
On Mar 4, 2012 8:13 AM, "Francisco Blas Izquierdo Riera (klondike)"
mailto:klond...@gentoo.org>> wrote:
El 04/03/12 01:26, Michael Orlitzky escribió:
It's probably the "Microsoft Hyper-V" part that's scaring people away.
Or maybe he should just
On Sun, Mar 4, 2012 at 8:30 AM, wrote:
> Hi. In my last update, the system wanted to emerge
> x11-libs/cairo-1.10.2-r2, but the file EGL/egl.h is missing. Now that file
> used to be provided by media-libs/mesa, but it seems the file is no
> longer there.
> I am running gentoo unstable 64-bit.
>
On Sun, 04 Mar 2012 11:34:54 -0500
cov...@ccs.covici.com wrote:
> Jarry wrote:
>
> > On 01-Mar-12 21:29, walt wrote:
> > > On 03/01/2012 09:55 AM, Jarry wrote:
> > >> What could be the problem? I remember just yesterday I updated
> > >> bind from 9.7.4_p1 to 9.8.1_p1, but today recompilation sim
On Mar 4, 2012 11:17 PM, "Tanstaafl" wrote:
>
>
> What are peoples opinions of ESXi? The guys I'm considering using are
perfect for everything else, but they only have experience with Microsoft
Hyper-V and ESXi. I don't think they have *any* experience with Xen on
Linux, but I dunno about XenServe
>> [snip]
>> > I've been using xautolock for years and years. What's good about it is you
>> > can have any 'locker' you want. For now, I'm using feh in slideshow mode.
>> > For another, you can specify another program as a 'killer' such as a
>> > suspend
>> > or hibernate script. However, for a t
anyone?
On Thu, Mar 1, 2012 at 3:17 PM, trevor donahue wrote:
> http://www.lua.org/manual/5.1/manual.html#5.7
> the doc
> also found on other resources scripts using IO not io, that still aint
> working...
>
>
> On Thu, Mar 1, 2012 at 3:14 PM, trevor donahue
> wrote:
>
>> Hi folks,
>> is anyone
I use AwesomeWM, but I haven't messed with the Lua side of things. You
might try in #awesome on Freenode.
On Sun, Mar 4, 2012 at 2:13 PM, trevor donahue wrote:
> anyone?
>
> On Thu, Mar 1, 2012 at 3:17 PM, trevor donahue
> wrote:
>>
>> http://www.lua.org/manual/5.1/manual.html#5.7
>> the doc
>>
Er. #awesome on OFTC apparently has more users.
On Sun, Mar 4, 2012 at 2:28 PM, Michael Mol wrote:
> I use AwesomeWM, but I haven't messed with the Lua side of things. You
> might try in #awesome on Freenode.
>
> On Sun, Mar 4, 2012 at 2:13 PM, trevor donahue
> wrote:
>> anyone?
>>
>> On Thu, M
[snip]
>> I enabled some more kernel options under USB Network Adapters and it's
>> working now. The install is about done but there were a few
>> peculiarities:
>>
>> 1. fdisk won't let me specify a start block before 2048 even though I
>> deleted all partitions.
>>
>
> That's normal. It's a long
> [snip]
>>> I enabled some more kernel options under USB Network Adapters and it's
>>> working now. The install is about done but there were a few
>>> peculiarities:
>>>
>>> 1. fdisk won't let me specify a start block before 2048 even though I
>>> deleted all partitions.
>>>
>>
>> That's normal.
So I take a lot of pictures. A *lot* of pictures. Sometimes around
500/month, sometimes twice that if I manage to get out more. I've got
a large number of 'DCIM' directories from different cameras, different
camera models, etc, going back ten years. Sometimes in JPG, sometimes
RAW, sometimes both.
[snip]
>> HOWEVER, make sure that all partitions begin at multiples of 8 (e.g., 64,
>> 72, 80, and so on); this will save you a lot of grief if it happens that the
>> hard disk you're using has 4KiB-sectors. [1]
>
>
>
> From what I recall of looking at that toy's specs, it's running on an
> SSD, s
Grant writes:
> Just to confirm, starting at block 2048 is OK?
Yes, if it's divisible by 8, it's okay. That's because 512 * 8 = 4096, so
every 8th 512-byte block starts on a 4096 block boundary.
Now I have a related question: My new seagate Barracuda
Green 2TB ST2000DL003-9VT166 drive has 4096 b
Michael Mol wrote:
> So I take a lot of pictures. A *lot* of pictures. Sometimes around
> 500/month, sometimes twice that if I manage to get out more. I've got
> a large number of 'DCIM' directories from different cameras, different
> camera models, etc, going back ten years. Sometimes in JPG, some
I have two hardware-identical laptops exhibiting different behavior
WRT xdm. xdm doesn't try to start automatically on one of the laptops
but does on the other. On the one that does not start xdm, I get this
on startup:
# rc-update -s | grep xdm
xdm | default
# /etc/init.d/xdm status
* status: s
[snip]
>> 1. fdisk won't let me specify a start block before 2048 even though I
>> deleted all partitions.
>>
>
> That's normal. It's a long story, but Windows Vista and Windows 7 expects
> the first partition to start at sector 2048.
>
> You can force a lower number by toggling "DOS compatibility"
On my just-released Dell XPS 13 Ultrabook, I can control the backlight
with 'xbacklight -set 0' and 'xbacklight -set 100'. Any other values
cause the screen to blink and flash. The keyboard backlight shortcuts
don't work unless I map them to xbacklight 0 and 100. Also xbacklight
doesn't work at
On Sun, Mar 4, 2012 at 1:09 PM, Grant wrote:
> [snip]
>>> 1. fdisk won't let me specify a start block before 2048 even though I
>>> deleted all partitions.
>>>
>>
>> That's normal. It's a long story, but Windows Vista and Windows 7 expects
>> the first partition to start at sector 2048.
>>
>> You
>> [snip]
1. fdisk won't let me specify a start block before 2048 even though I
deleted all partitions.
>>>
>>> That's normal. It's a long story, but Windows Vista and Windows 7 expects
>>> the first partition to start at sector 2048.
>>>
>>> You can force a lower number by toggling
On Sun, 4 Mar 2012 13:56:23 -0800
Grant wrote:
> >> [snip]
> 1. fdisk won't let me specify a start block before 2048 even
> though I deleted all partitions.
>
> >>>
> >>> That's normal. It's a long story, but Windows Vista and Windows 7
> >>> expects the first partition to start at
Mark Knecht wrote:
> On Sun, Mar 4, 2012 at 8:30 AM, wrote:
> > Hi. In my last update, the system wanted to emerge
> > x11-libs/cairo-1.10.2-r2, but the file EGL/egl.h is missing. Now that file
> > used to be provided by media-libs/mesa, but it seems the file is no
> > longer there.
> > I am
>> >> [snip]
>> 1. fdisk won't let me specify a start block before 2048 even
>> though I deleted all partitions.
>>
>> >>>
>> >>> That's normal. It's a long story, but Windows Vista and Windows 7
>> >>> expects the first partition to start at sector 2048.
>> >>>
>> >>> You can force
On 03/04/2012 01:02 PM, Grant wrote:
> I have two hardware-identical laptops exhibiting different behavior
> WRT xdm. xdm doesn't try to start automatically on one of the laptops
> but does on the other. On the one that does not start xdm, I get this
> on startup:
>
> # rc-update -s | grep xdm
>
On 03/04/2012 01:16 PM, Grant wrote:
> On my just-released Dell XPS 13 Ultrabook, I can control the backlight
> with 'xbacklight -set 0' and 'xbacklight -set 100'. Any other values
> cause the screen to blink and flash. The keyboard backlight shortcuts
> don't work unless I map them to xbacklight
Grant writes:
> I have two hardware-identical laptops exhibiting different behavior
> WRT xdm. xdm doesn't try to start automatically on one of the laptops
> but does on the other. On the one that does not start xdm, I get this
> on startup:
>
> # rc-update -s | grep xdm
> xdm | default
> # /et
>> On my just-released Dell XPS 13 Ultrabook, I can control the backlight
>> with 'xbacklight -set 0' and 'xbacklight -set 100'. Any other values
>> cause the screen to blink and flash. The keyboard backlight shortcuts
>> don't work unless I map them to xbacklight 0 and 100. Also xbacklight
>> d
El 04/03/12 17:35, Tanstaafl escribió:
> Hmmm... I used to be subscribed, but I seem to recall unsubscribing
> because it seemed essentially dead...
We tend to be shy and not very active since we have many things to focus
on, but this also means posts hardly go by unread, so please don't
confuse la
On Mar 5, 2012 3:37 AM, "Alex Schuster" wrote:
>
> Grant writes:
>
> > Just to confirm, starting at block 2048 is OK?
>
> Yes, if it's divisible by 8, it's okay. That's because 512 * 8 = 4096, so
> every 8th 512-byte block starts on a 4096 block boundary.
>
> Now I have a related question: My new
On Mar 5, 2012 3:15 AM, "Grant" wrote:
>
> [snip]
> >> HOWEVER, make sure that all partitions begin at multiples of 8 (e.g.,
64,
> >> 72, 80, and so on); this will save you a lot of grief if it happens
that the
> >> hard disk you're using has 4KiB-sectors. [1]
> >
> >
> >
> > From what I recall o
On Mar 5, 2012 4:59 AM, "Grant" wrote:
>
>
> All my drives says this from fdisk:
>
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> So it doesn't matter where the first partition starts?
>
Olde
On Mar 5, 2012 5:10 AM, "Alan McKinnon" wrote:
>
>
> Correct. Those drives are all the same style as you've
> been using for years. If partitions start at 63, that's just an msdos
> convention. For reasons I've never understood, Windows liked to reserve
> the first 32k for some purpose or other.
>
On Mar 5, 2012 5:39 AM, "Grant" wrote:
>
>
> So fdisk used to enforce a block 63 start point and now it enforces a
> 2048 start point? fdisk is the one doing this?
>
> - Grant
>
Yes. Like I posted before (and explained in the article I linked), if you
turn off the compatibility mode, you can pus
On Sun, Mar 4, 2012 at 2:08 PM, Michael Mol wrote:
> So I take a lot of pictures. A *lot* of pictures. Sometimes around
> 500/month, sometimes twice that if I manage to get out more. I've got
> a large number of 'DCIM' directories from different cameras, different
> camera models, etc, going back
Dale wrote:
>
> As someone who also takes a LOT of pictures at times, I don't use
> software, I just use directories. Mine starts out like this: Camera
> directory > Year > subject matter > image That works for me. I used to
> not have the year but that ends up with a LOT of pictures in a
> d
38 matches
Mail list logo
