On Wed, May 21, 2014 at 3:02 AM, Richard Hector wrote:
> On 20/05/14 23:50, Richard Owlett wrote:
>> I read the man pages for all the commands others referenced but didn't
>> come with any extrapolation to improve my skills at retrieving
>> information on my own.
>> Any suggestions?
>
> Experience
On 20/05/14 23:50, Richard Owlett wrote:
> I read the man pages for all the commands others referenced but didn't
> come with any extrapolation to improve my skills at retrieving
> information on my own.
> Any suggestions?
Experience, I think :-(
Richard
--
To UNSUBSCRIBE, email to debian-user
On Tue 20 May 2014 at 06:50:58 -0500, Richard Owlett wrote:
> My config file did include "CONFIG_BLK_DEV_LOOP=m" and the two lines
> acted as desired.
> Thank you.
>
> However no one addressed the more general question posed in my first
> paragraph.
>
> I read the man pages for all the commands
Tom H wrote:
On Sun, May 18, 2014 at 9:07 AM, Richard Owlett wrote:
My general question is "How to search for a particular particle of
information that you've seen SOMEWHERE in the reams of information available
as formal documentation, web pages, mailing lists, etc."
My current instance is a
On Mon, May 19, 2014 at 3:33 AM, Curt wrote:
> On 2014-05-18, Tom H wrote:
You'll have to run "chown root:disk /dev/loop8" too.
>>>
>>> Nobody mentioned that in my reading!
>>
>> ls -l /dev/loop*
>
> Yes, I did that after you mentioned the chown and remarked that all my
> loopy devices
On 2014-05-18, Tom H wrote:
>>>
>>> You'll have to run "chown root:disk /dev/loop8" too.
>>
>> Nobody mentioned that in my reading!
>
> ls -l /dev/loop*
>
Yes, I did that after you mentioned the chown and remarked that all my
loopy devices (0-7) have root:disk ownership.
Thank you for all the go
On Sun, May 18, 2014 at 11:41 AM, Curt wrote:
> On 2014-05-18, Tom H wrote:
>>>
>>> I'm reading you can *add* another loop device on the fly
>>> with the mknod command:
>>>
>>> mknod -m 660 /dev/loop8 b 7 8
>>
>> You'll have to run "chown root:disk /dev/loop8" too.
>
> Nobody mentioned that in my
On Sun, May 18, 2014 at 11:35 AM, Filip wrote:
> On Sun, 18 May 2014 15:15:34 + (UTC)
> Curt wrote:
>> On 2014-05-18, Richard Owlett wrote:
>>>
>>> My current instance is attempting to modify the max number of
>>> loop devices. One pellet of Google buckshot reminded me that it
>>> can be res
On 2014-05-18, Brian wrote:
>
> You really should try Tom H's advice. Two minutes out of your life. :)
>
So if loop is compiled as a module (as it is here) you can change the
max number of devices without rebooting (but this requires removing the
module from the running kernel, which might be dif
On Sun 18 May 2014 at 16:01:08 +, Curt wrote:
> But all seriousness aside it appears that the max number of loop devices
> cannot be altered on the fly and requires a reboot, if I'm understanding
> correctly.
You really should try Tom H's advice. Two minutes out of your life. :)
--
To UNSU
On 2014-05-18, Filip wrote:
>>
>> mknod -m 660 /dev/loop8 b 7 8
>>
>> But I guess that covers only half of the word "modify."
>
> You can create devices nodes with that in the filesystem, but they will
> not work unless they also exist in the kernel.
Yes, but "work" was not part of the problem
On Sun 18 May 2014 at 11:23:56 -0400, Tom H wrote:
> On Sun, May 18, 2014 at 11:14 AM, Brian wrote:
> > On Sun 18 May 2014 at 09:40:29 -0400, Tom H wrote:
> >>
> >> If you have loop compiled in to the kernel, as I do below, you can
> >> only change the number of loop devices at boot by using
> >>
On 2014-05-18, Tom H wrote:
>>
>> I'm reading you can *add* another loop device on the fly
>> with the mknod command:
>>
>> mknod -m 660 /dev/loop8 b 7 8
>
> You'll have to run "chown root:disk /dev/loop8" too.
>
Nobody mentioned that in my reading!
--
To UNSUBSCRIBE, email to debian-user-re
On Sun, 18 May 2014 15:15:34 + (UTC)
Curt wrote:
> On 2014-05-18, Richard Owlett wrote:
> >
> > My current instance is attempting to modify the max number of
> > loop devices. One pellet of Google buckshot reminded me that it
> > can be reset for the next re-boot under /etc/modprobe.d . Bu
On Sun, May 18, 2014 at 11:15 AM, Curt wrote:
> On 2014-05-18, Richard Owlett wrote:
>>
>> My current instance is attempting to modify the max number of
>> loop devices. One pellet of Google buckshot reminded me that it
>> can be reset for the next re-boot under /etc/modprobe.d . But I
>> want to
On Sun, May 18, 2014 at 11:14 AM, Brian wrote:
> On Sun 18 May 2014 at 09:40:29 -0400, Tom H wrote:
>>
>> If you have loop compiled in to the kernel, as I do below, you can
>> only change the number of loop devices at boot by using
>> "max_loop=>
>> # grep BLK_DEV_LOOP /boot/config-3.15-rc5
>> CON
The Wanderer a écrit :
>
> What does 'modprobe -r loop' do to any active loop devices?
Nothing.
> I would expect it to either error out without removing the module if any
> loop devices are in use,
As usual when the module is in use.
> or automatically shut the loop devices down.
That would b
On 2014-05-18, Richard Owlett wrote:
>
> My current instance is attempting to modify the max number of
> loop devices. One pellet of Google buckshot reminded me that it
> can be reset for the next re-boot under /etc/modprobe.d . But I
> want to reset it on the fly.
I'm reading you can *add* an
On Sun 18 May 2014 at 09:40:29 -0400, Tom H wrote:
> If you have loop compiled in to the kernel, as I do below, you can
> only change the number of loop devices at boot by using
> "max_loop=
> # grep BLK_DEV_LOOP /boot/config-3.15-rc5
> CONFIG_BLK_DEV_LOOP=y
> CONFIG_BLK_DEV_LOOP_MIN_COUNT=16
>
On Sun, May 18, 2014 at 10:20 AM, The Wanderer wrote:
> On 05/18/2014 09:52 AM, Pascal Hambourg wrote:
>> Tom H a écrit :
>>>
>>> If you have loop compiled in to the kernel, as I do below, you can
>>> only change the number of loop devices at boot by using
>>> "max_loop=>>
>>> But if loop is compi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/18/2014 09:52 AM, Pascal Hambourg wrote:
> Tom H a écrit :
>> If you have loop compiled in to the kernel, as I do below, you can
>> only change the number of loop devices at boot by using
>> "max_loop=>
>> But if loop is compiled as module
>
Tom H a écrit :
>>
>> My current instance is attempting to modify the max number of loop devices.
>> One pellet of Google buckshot reminded me that it can be reset for the next
>> re-boot under /etc/modprobe.d . But I want to reset it on the fly.
>
> If you have loop compiled in to the kernel, as
On Sun, May 18, 2014 at 9:07 AM, Richard Owlett wrote:
>
> My general question is "How to search for a particular particle of
> information that you've seen SOMEWHERE in the reams of information available
> as formal documentation, web pages, mailing lists, etc."
>
> My current instance is attempt
My general question is "How to search for a particular particle
of information that you've seen SOMEWHERE in the reams of
information available as formal documentation, web pages, mailing
lists, etc."
My current instance is attempting to modify the max number of
loop devices. One pellet of Go
24 matches
Mail list logo
