9:13 AM, Huang, Ying wrote:
> Hi, Alex,
>
> Sorry for late, I just notice this email today.
>
> "Alejandro Colomar (mailing lists; readonly)"
> writes:
>
>> Hi Huang Ying,
>>
>> Please see a few fixes below.
>>
>> Michael, as
ed by the process's current cpuset.
> +.TP
> +.BR MPOL_F_NUMA_BALANCING " (since Linux 5.11)"
I'd prefer it to be in alphabetical order (rather than just adding at
the bottom).
That way, when lists grow, it's easier to find things.
> +Enable the Linux kernel NUMA balancing for the ta
Hi Guo,
Thanks for the details!
I'll try to add csky to the man page,
and if I have any doubts I'll ask you.
Anyway, I'll CC you in any change I propose.
Cheers,
Alex
On 11/24/20 1:07 PM, Guo Ren wrote:
> Thx Michael & Alejandro,
>
> Yes, the man page has no csky's.
>
> C-SKY have abiv1 and
HI Michael,
On 11/24/20 10:51 AM, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
>
> On 11/23/20 10:31 PM, Alejandro Colomar (man-pages) wrote:
>> Hi Michael,
>>
>> SYNOPSIS
>>#include
>>
>>#if defined __i386__ || defined __x86_64__
>># include
>>
>>int
On 26.10.20 21:10, Cristian Marussi wrote:
> Add support for new SCMIv3.0 Sensors extensions related to new sensors'
> features, like multiple axis and update intervals, while keeping
> compatibility with SCMIv2.0 features.
> While at that, refactor and simplify all the internal helpers macros and
On 22/07/20 08:45, Johannes Thumshirn wrote:
> On 22/07/2020 08:27, Christoph Hellwig wrote:
>> it is know to support cgroup writeback, or the bdi comes from the block
> knwon ~^
>
Whoops - "known"
> Apart from that,
> Reviewed-by: Johannes Thumshirn
>
Cheers,
Wol
On 17/04/2019 16:30, Mathieu Desnoyers wrote:
> - On Apr 17, 2019, at 10:43 AM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Apr 17, 2019, at 6:37 AM, richard earnshaw richard.earns...@arm.com
>> wrote:
>>
>>> On 16/04/2019 14:39, Mathieu Desnoyers wrote:
On 16/04/2019 14:39, Mathieu Desnoyers wrote:
> - On Apr 15, 2019, at 9:37 AM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Apr 15, 2019, at 9:30 AM, peter maydell peter.mayd...@linaro.org
>> wrote:
>>
>>> On Mon, 15 Apr 2019 at 14:11, Mathieu Desnoyers
>>>
On 14/02/19 01:59, Song Liu wrote:
>> I believe the direction is clear. It needs people to do the work.
>> > We're critically short of reviewers. I got precious little review of
>> > the original XArray work, which made Andrew nervous and delayed its
>> > integration. Now I'm getting little
On 08/08/18 15:12, Mikulas Patocka wrote:
>
>
> On Wed, 8 Aug 2018, Catalin Marinas wrote:
>
>> On Fri, Aug 03, 2018 at 01:09:02PM -0400, Mikulas Patocka wrote:
>>> while (1) {
>>> start = (unsigned)random() % (LEN + 1);
>>> end = (unsigned)random() % (LEN + 1);
>>>
On 08/08/18 15:12, Mikulas Patocka wrote:
>
>
> On Wed, 8 Aug 2018, Catalin Marinas wrote:
>
>> On Fri, Aug 03, 2018 at 01:09:02PM -0400, Mikulas Patocka wrote:
>>> while (1) {
>>> start = (unsigned)random() % (LEN + 1);
>>> end = (unsigned)random() % (LEN + 1);
>>>
On 03/08/18 14:31, Mikulas Patocka wrote:
>
>
> On Fri, 3 Aug 2018, Andrew Pinski wrote:
>
>> On Thu, Aug 2, 2018 at 12:31 PM Mikulas Patocka wrote:
>>>
>>> Hi
>>>
>>> I tried to use a PCIe graphics card on the MacchiatoBIN board and I hit a
>>> strange problem.
>>>
>>> When I use the links
On 03/08/18 14:31, Mikulas Patocka wrote:
>
>
> On Fri, 3 Aug 2018, Andrew Pinski wrote:
>
>> On Thu, Aug 2, 2018 at 12:31 PM Mikulas Patocka wrote:
>>>
>>> Hi
>>>
>>> I tried to use a PCIe graphics card on the MacchiatoBIN board and I hit a
>>> strange problem.
>>>
>>> When I use the links
On 03/08/18 10:29, Ard Biesheuvel wrote:
> On 3 August 2018 at 11:15, Ramana Radhakrishnan
> wrote:
>> On Fri, Aug 3, 2018 at 8:53 AM, Florian Weimer wrote:
>>> On 08/03/2018 09:11 AM, Andrew Pinski wrote:
Yes fix Links not to use memcpy on the framebuffer.
It is undefined
On 03/08/18 10:29, Ard Biesheuvel wrote:
> On 3 August 2018 at 11:15, Ramana Radhakrishnan
> wrote:
>> On Fri, Aug 3, 2018 at 8:53 AM, Florian Weimer wrote:
>>> On 08/03/2018 09:11 AM, Andrew Pinski wrote:
Yes fix Links not to use memcpy on the framebuffer.
It is undefined
On 26/08/17 12:19, Martin Steigerwald wrote:
> Also… when a hang happened the mouse pointer was frozen, Ctrl-Alt-F1 didn´t
> work and so on… so it may easily be a completely different issue.
>
> I did not see much point in reporting it so far… as I have no idea on how to
> reliably pin-point
On 26/08/17 12:19, Martin Steigerwald wrote:
> Also… when a hang happened the mouse pointer was frozen, Ctrl-Alt-F1 didn´t
> work and so on… so it may easily be a completely different issue.
>
> I did not see much point in reporting it so far… as I have no idea on how to
> reliably pin-point
You can add my acked-by (never done it before, not sure how :-)
Cheers,
Wol
On 30/03/17 17:58, Gioh Kim wrote:
> Remove a boolean expression in switch condition
> to prevent compile error of some compilers,
> for example, gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2).
>
> Signed-off-by:
You can add my acked-by (never done it before, not sure how :-)
Cheers,
Wol
On 30/03/17 17:58, Gioh Kim wrote:
> Remove a boolean expression in switch condition
> to prevent compile error of some compilers,
> for example, gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2).
>
> Signed-off-by:
On 28/03/17 16:02, Ming Lei wrote:
>> What I meant is that a future change to the function might cause
>> > another bug to go unnoticed later.
> What is the future change? And what is another bug? Please don't suppose or
> assume anything in future.
What was that about some American General
On 28/03/17 16:02, Ming Lei wrote:
>> What I meant is that a future change to the function might cause
>> > another bug to go unnoticed later.
> What is the future change? And what is another bug? Please don't suppose or
> assume anything in future.
What was that about some American General
I'm running kernel 4.7/stable.
It's installed from Opensuse packages atm.
Using the current kernel causes a crash when booting Xen 4.7 on UEFI.
Referenced in this now ridiculously-long thread
https://lists.xenproject.org/archives/html/xen-devel/2016-07/msg02758.html
In hunting down
I'm running kernel 4.7/stable.
It's installed from Opensuse packages atm.
Using the current kernel causes a crash when booting Xen 4.7 on UEFI.
Referenced in this now ridiculously-long thread
https://lists.xenproject.org/archives/html/xen-devel/2016-07/msg02758.html
In hunting down
On 29/07/16 01:50, Eric Wheeler wrote:
> Hello all,
>
> With the many SSD caching layers being developed (bcache, dm-cache,
> dm-writeboost, etc), how could we flag a bio from userspace to indicate
> whether the bio is preferred to hit spinning disks instead of an SSD?
>
> Unnecessary
On 29/07/16 01:50, Eric Wheeler wrote:
> Hello all,
>
> With the many SSD caching layers being developed (bcache, dm-cache,
> dm-writeboost, etc), how could we flag a bio from userspace to indicate
> whether the bio is preferred to hit spinning disks instead of an SSD?
>
> Unnecessary
Hello,
I'm trying to understand how this value has been chosen.
Was it arbitrary, or did it come up after some rationale?
If alter it to a lower value like 30 (or 60), and a piece of third
party code hung in D state triggers the kernel hung task complain
message, can I still report this as an
Hello,
I'm trying to understand how this value has been chosen.
Was it arbitrary, or did it come up after some rationale?
If alter it to a lower value like 30 (or 60), and a piece of third
party code hung in D state triggers the kernel hung task complain
message, can I still report this as an
On 12/04/16 00:03, Joe Perches wrote:
> I think that's not a particularly good definition.
> MAINTAINERS describes the M: entry as:
>
> M: Mail patches to: FullName
>
> That _person_ is generally responsible for vetting patches
> and bug fixing.
Ahh ... you are ASS U ME
On 12/04/16 00:03, Joe Perches wrote:
> I think that's not a particularly good definition.
> MAINTAINERS describes the M: entry as:
>
> M: Mail patches to: FullName
>
> That _person_ is generally responsible for vetting patches
> and bug fixing.
Ahh ... you are ASS U ME ing that it is a
On 11/04/16 22:08, Joe Perches wrote:
> I'm a native English speaker and I think that's a not
> a good argument.
>
> Having the same entry for M: and L: where M: isn't an
> actual person is not a great idea.
>
> The list is not a maintainer.
>
>
Depends on your definition of maintainer ...
To
On 11/04/16 22:08, Joe Perches wrote:
> I'm a native English speaker and I think that's a not
> a good argument.
>
> Having the same entry for M: and L: where M: isn't an
> actual person is not a great idea.
>
> The list is not a maintainer.
>
>
Depends on your definition of maintainer ...
To
On 11/04/16 17:39, Sudip Mukherjee wrote:
> On Monday 11 April 2016 09:53 PM, Alasdair G Kergon wrote:
>> On Mon, Apr 11, 2016 at 09:45:01PM +0530, Sudip Mukherjee wrote:
>>> L stands for "Mailing list that is relevant to this area", and this is a
>>> mailing list. :)
>>
>> Your proposed patch
On 11/04/16 17:39, Sudip Mukherjee wrote:
> On Monday 11 April 2016 09:53 PM, Alasdair G Kergon wrote:
>> On Mon, Apr 11, 2016 at 09:45:01PM +0530, Sudip Mukherjee wrote:
>>> L stands for "Mailing list that is relevant to this area", and this is a
>>> mailing list. :)
>>
>> Your proposed patch
Just a quick question - will there be any support for enabling booting into
virtualisation mode to run xen and the like?
Cheers
Nick
Just a quick question - will there be any support for enabling booting into
virtualisation mode to run xen and the like?
Cheers
Nick
On 20/03/15 20:31, Matthew Wilcox wrote:
> Ah! I've looked at that a couple of times as well. I asked our database
> performance team what impact freeing up the memmap would have on their
> performance. They told me that doubling the amount of memory generally
> resulted in approximately a 40%
On 19/03/15 19:59, Andrew Morton wrote:
> This is all contingent upon the prevalence of machines which have vast
> amounts of nv memory and relatively small amounts of regular memory.
> How confident are we that this really is the future?
Somewhat off-topic, but it's also the past. I can't help
On 19/03/15 19:59, Andrew Morton wrote:
This is all contingent upon the prevalence of machines which have vast
amounts of nv memory and relatively small amounts of regular memory.
How confident are we that this really is the future?
Somewhat off-topic, but it's also the past. I can't help
On 20/03/15 20:31, Matthew Wilcox wrote:
Ah! I've looked at that a couple of times as well. I asked our database
performance team what impact freeing up the memmap would have on their
performance. They told me that doubling the amount of memory generally
resulted in approximately a 40%
Hi,
I have a rather nasty situation developing on one of the big 24x7
production database servers. It seems that a batch of drives in one of the
servers started to fail.
The file servers are ext3fs on a top of raid-0 over a pair of raid-1 mirrors,
with each of raid-1 mirrors having two
Hi,
I have a rather nasty situation developing on one of the big 24x7
production database servers. It seems that a batch of drives in one of the
servers started to fail.
The file servers are ext3fs on a top of raid-0 over a pair of raid-1 mirrors,
with each of raid-1 mirrors having two
I get this on brand new hardware, 2xHitachi Deathstar 320gb SATA2
(sata_via driver)
I get this a lot, the disk makes some sound after heavy IO and then the
system hangs for a few seconds, then this comes up:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd
I get this on brand new hardware, 2xHitachi Deathstar 320gb SATA2
(sata_via driver)
I get this a lot, the disk makes some sound after heavy IO and then the
system hangs for a few seconds, then this comes up:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd
Hi,
which leads to the question: Why is the "Enable Tablets" entry not
inside the tablets menu. This way it's more obvious that it's disabled
if it's the only entry in the menu. Plus the parent menu gets
cleaned up as well.
Till
Am Dienstag 15 Mai 2007 schrieb Jeremy Roberson:
> LOL. Thanks, I
Hi,
which leads to the question: Why is the Enable Tablets entry not
inside the tablets menu. This way it's more obvious that it's disabled
if it's the only entry in the menu. Plus the parent menu gets
cleaned up as well.
Till
Am Dienstag 15 Mai 2007 schrieb Jeremy Roberson:
LOL. Thanks, I
It is a Samsung HD501LJ SATA drive connected to 631xESB/632xESB controller.
Reading and writing every block of the drive does not generate any other
errors/failures. This is observed in 2.6.20.7 like a clockwork on any
badblocks -v run or rebuild of a MD raid1 array onto the disk.
It, however,
It is a Samsung HD501LJ SATA drive connected to 631xESB/632xESB controller.
Reading and writing every block of the drive does not generate any other
errors/failures. This is observed in 2.6.20.7 like a clockwork on any
badblocks -v run or rebuild of a MD raid1 array onto the disk.
It, however,
On Fri, 2 Sep 2005, John Heffner wrote:
Have you tried increasing the size of the receive buffer yet?
Actually, I just did. I changed rmem_max and rmem_default to 4MB and
tcp_rmem to "64k 4MB 4MB". It did seem to help, but I'm wondering if
that's simply because it has a _lot_ of memory now
Hi David,
On Thu, 1 Sep 2005, David S. Miller wrote:
From: John Heffner <[EMAIL PROTECTED]>
Date: Thu, 1 Sep 2005 22:51:48 -0400
I have an idea why this is going on. Packets are pre-allocated by the
driver to be a max packet size, so when you send small packets, it
wastes a lot of memory.
Hi David,
On Thu, 1 Sep 2005, David S. Miller wrote:
From: John Heffner [EMAIL PROTECTED]
Date: Thu, 1 Sep 2005 22:51:48 -0400
I have an idea why this is going on. Packets are pre-allocated by the
driver to be a max packet size, so when you send small packets, it
wastes a lot of memory.
On Fri, 2 Sep 2005, John Heffner wrote:
Have you tried increasing the size of the receive buffer yet?
Actually, I just did. I changed rmem_max and rmem_default to 4MB and
tcp_rmem to 64k 4MB 4MB. It did seem to help, but I'm wondering if
that's simply because it has a _lot_ of memory now to
>
> You need support of Solaris disklabels.
isn't that what CONFIG_SOLARIS_X86_PARTITION is?
> And UFS patches that are in
> -ac. Then you can get more or less safe r/o mounts. r/w is hopeless
> at that stage.
that's ok, i only need to read.
-Tony
Trying to mount a solaris x86 drive under linux.
kernel 2.4.5, ufs support and x86 partition support compiled in (no
module)
On boot, linux recognizes the drive, but shows no solaris partitions on
it.
Below, linux drive is hda, solaris is hdb.
Jul 2 19:57:56 stevenjude2 kernel: PIIX4: chipset
Trying to mount a solaris x86 drive under linux.
kernel 2.4.5, ufs support and x86 partition support compiled in (no
module)
On boot, linux recognizes the drive, but shows no solaris partitions on
it.
Below, linux drive is hda, solaris is hdb.
Jul 2 19:57:56 stevenjude2 kernel: PIIX4: chipset
You need support of Solaris disklabels.
isn't that what CONFIG_SOLARIS_X86_PARTITION is?
And UFS patches that are in
-ac. Then you can get more or less safe r/o mounts. r/w is hopeless
at that stage.
that's ok, i only need to read.
-Tony
On 27 Jun 2001, David Wagner wrote:
>
> Why is it useless? It sounds useful to me, on first glance. If I want
> to run a user-level network daemon I don't trust (for instance, fingerd),
> isolating it in a chroot area sounds pretty nice: If there is a buffer
> overrun in the daemon, you can
On 27 Jun 2001, David Wagner wrote:
Why is it useless? It sounds useful to me, on first glance. If I want
to run a user-level network daemon I don't trust (for instance, fingerd),
isolating it in a chroot area sounds pretty nice: If there is a buffer
overrun in the daemon, you can get
FYI:
2 small issues:
o make xconfig fails (works ok in ac6) :
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
drivers/net/wireless/Config.in: 5: can't handle dep_bool/dep_mbool/dep_tristate
condition
make[1]: *** [kconfig.tk]
FYI:
2 small issues:
o make xconfig fails (works ok in ac6) :
cat header.tk ./kconfig.tk
./tkparse ../arch/i386/config.in kconfig.tk
drivers/net/wireless/Config.in: 5: can't handle dep_bool/dep_mbool/dep_tristate
condition
make[1]: *** [kconfig.tk] Error 1
I'm running 2.4.2ac23 (can't run 2.4.3, messes up my quota system)
glibc 2.1.3, intel providence PR440FX mobo, intel etherexpress 100B
onboard, RAM is 128MBx3.
Started getting the following errors:
VM: bad swap entry 2000
Unused swap offset entry in swap_dup 2000
memory.c:84: bad pmd
I'm running 2.4.2ac23 (can't run 2.4.3, messes up my quota system)
glibc 2.1.3, intel providence PR440FX mobo, intel etherexpress 100B
onboard, RAM is 128MBx3.
Started getting the following errors:
VM: bad swap entry 2000
Unused swap offset entry in swap_dup 2000
memory.c:84: bad pmd
Hi,
WHen i upgrade from 2.2 to 2.4, my first version was 2.4.1,
in which i upgraded my quota utils to 3.00 and then converted to the new
quota formats for 2.4.
my last 2.4 upgrade was 2.4.2ac23, quotas work fine on that.
but when i run 2.4.3 they dont. quota -v on a user shows just blank space
Hi,
WHen i upgrade from 2.2 to 2.4, my first version was 2.4.1,
in which i upgraded my quota utils to 3.00 and then converted to the new
quota formats for 2.4.
my last 2.4 upgrade was 2.4.2ac23, quotas work fine on that.
but when i run 2.4.3 they dont. quota -v on a user shows just blank space
After all the earlier difficulties booting off scsi disk I am delighted to report
that it worked with ac6.
I must confess I did change one thing and that was to turn off SMP and turn on
IO-APIC for UP. I dont know if this is related or not as I have not tried
going back the other
After all the earlier difficulties booting off scsi disk I am delighted to report
that it worked with ac6.
I must confess I did change one thing and that was to turn off SMP and turn on
IO-APIC for UP. I dont know if this is related or not as I have not tried
going back the other
On Tue, Apr 10, 2001 at 08:00:19AM -0600, Justin T. Gibbs wrote:
> >
> I'm pretty sure you need to be up to at leaset 0005 of
> the firmware to stabilize this drive.
FYI, I contacted seagate and they say the firmware is the latest.
Regards,
Gene/
-
To unsubscribe from this
Justin:
Ya think very buggy? I checked seagate web page and
unfortunately was unable to find any firmware updates
for the barracuda drives.
Curious tho that this has worked flawlessly for well over a
year with all prior version of linux and win2000 as well.
Also a few other folks seem to
Justin:
Ya think very buggy? I checked seagate web page and
unfortunately was unable to find any firmware updates
for the barracuda drives.
Curious tho that this has worked flawlessly for well over a
year with all prior version of linux and win2000 as well.
Also a few other folks seem to
On Tue, Apr 10, 2001 at 08:00:19AM -0600, Justin T. Gibbs wrote:
I'm pretty sure you need to be up to at leaset 0005 of
the firmware to stabilize this drive.
FYI, I contacted seagate and they say the firmware is the latest.
Regards,
Gene/
-
To unsubscribe from this list:
I confirm similar problems (see my message from yesterday).
AIC7XXX_OLD also failed for me. I have tried aic 6.1.8 as well
as 6.1.10.
Both 2.4.0 under redhat 7.0 and 2.4.1 as shipped by redhat
wolverine work. As have all earlier versions going back to 2.3.xx
and 2.2.x
On Mon, Apr 09, 2001
I confirm similar problems (see my message from yesterday).
AIC7XXX_OLD also failed for me. I have tried aic 6.1.8 as well
as 6.1.10.
Both 2.4.0 under redhat 7.0 and 2.4.1 as shipped by redhat
wolverine work. As have all earlier versions going back to 2.3.xx
and 2.2.x
On Mon, Apr 09, 2001
Well my aicxxx problems continue:
I did it again and indeed verified similar error messages as I had
under stock 2.4.3 and 2.4.3+aic 6.1.8. This time it died during boot itself
starting with complaints from ssh/xinet et al - then I started seeing the
scsi errors. (I believe I had also
I used 5000ms. I still freeze up with 2.4.3 + 6.1.10.
Unfortunately i could not see any messages and nothing got logged.
This time an fsck allowed me to boot back to 2.4.1.
The visible symptoms were the same as before (2.4.3 + 6.1.8) but this time I was
unable to flip virtual consoles before
I had tried 6.1.8 + 2.4.3 and had problems which included messages like
'aic7xxx_abort returns 8194' and machine froze up shortly after X started.
This on redhat 7.0. Sorry but since I was unable to even boot back the
prev kernel (2.4.0) I cant provide any more detailed information.
I had tried 6.1.8 + 2.4.3 and had problems which included messages like
'aic7xxx_abort returns 8194' and machine froze up shortly after X started.
This on redhat 7.0. Sorry but since I was unable to even boot back the
prev kernel (2.4.0) I cant provide any more detailed information.
I used 5000ms. I still freeze up with 2.4.3 + 6.1.10.
Unfortunately i could not see any messages and nothing got logged.
This time an fsck allowed me to boot back to 2.4.1.
The visible symptoms were the same as before (2.4.3 + 6.1.8) but this time I was
unable to flip virtual consoles before
Well my aicxxx problems continue:
I did it again and indeed verified similar error messages as I had
under stock 2.4.3 and 2.4.3+aic 6.1.8. This time it died during boot itself
starting with complaints from ssh/xinet et al - then I started seeing the
scsi errors. (I believe I had also
I'm using 2.4.3 vanilla with aic7xxx (aic7880 onboard)
I set the max # of TCQ commands per device setting to 50..what's a really
good setting for this, just the default of 253?
In /proc/scsi/aic7xxx/0 i see for my drives these numbers:
Commands Queued 14
Commands Active 0
I'm using 2.4.3 vanilla with aic7xxx (aic7880 onboard)
I set the max # of TCQ commands per device setting to 50..what's a really
good setting for this, just the default of 253?
In /proc/scsi/aic7xxx/0 i see for my drives these numbers:
Commands Queued 14
Commands Active 0
> >
> >It was causing SMP boxes to crash mysteriously after
> >several hours or days. Quite a lot of them. Nobody
> >was able to explain why, so it was turned off.
>
> I know why it was turned off by default. The annoying this is that now
> the *only* way to activate the watchdog is via a
It was causing SMP boxes to crash mysteriously after
several hours or days. Quite a lot of them. Nobody
was able to explain why, so it was turned off.
I know why it was turned off by default. The annoying this is that now
the *only* way to activate the watchdog is via a boot command.
I got some NMI messages I have never seen before. In fact i've never seen
a NMI message before.
This is kernel 2.4.1-ac13. Got them while running X (4.0.2) and KDE (2.1).
After 15 mins the system froze hard.
PR440FX mobo, dual ppro 200s, 256MB RAM, aic7xxx, no power management at
all.
I've never
I got some NMI messages I have never seen before. In fact i've never seen
a NMI message before.
This is kernel 2.4.1-ac13. Got them while running X (4.0.2) and KDE (2.1).
After 15 mins the system froze hard.
PR440FX mobo, dual ppro 200s, 256MB RAM, aic7xxx, no power management at
all.
I've never
apache documentation states:
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 6;
# don't use Group nobody on these systems!
does this apply to linux in either the 2.2 or 2.4 kernels?
i'd like to use a block of uids from
apache documentation states:
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 6;
# don't use Group nobody on these systems!
does this apply to linux in either the 2.2 or 2.4 kernels?
i'd like to use a block of uids from
got this message spewed on my console this morning:
VFS: dqduplicate(): Locked quota to be duplicated!
SMP 2.4.1-ac9
quota is used on 1 ext2 FS, converted from the old quota format with the
new quota utils quota-3.00
Thanx,
-Tony
got this message spewed on my console this morning:
VFS: dqduplicate(): Locked quota to be duplicated!
SMP 2.4.1-ac9
quota is used on 1 ext2 FS, converted from the old quota format with the
new quota utils quota-3.00
Thanx,
-Tony
Can anyone give testimonials on a journaled FS on software-raid?
I'd like to raid-0 2 SCSI 18Gers, adaptec 2940 u2w controller, kernel
2.4.x.
Also pros and cons for reiser-fs/ext3 on this solution would be
appreciated
Thanx,
-Tony
Can anyone give testimonials on a journaled FS on software-raid?
I'd like to raid-0 2 SCSI 18Gers, adaptec 2940 u2w controller, kernel
2.4.x.
Also pros and cons for reiser-fs/ext3 on this solution would be
appreciated
Thanx,
-Tony
I've been using the 2.2.x series successfully, latest i used
was 2.2.19pre7.
Today i upgraded to 2.4.1-ac9 and noticed that shared memory shows 0.
I searched the list archive briefly and someone said the stats have been
broken since sometime in 2.3, but my system also shows my swap being used
up
I've been using the 2.2.x series successfully, latest i used
was 2.2.19pre7.
Today i upgraded to 2.4.1-ac9 and noticed that shared memory shows 0.
I searched the list archive briefly and someone said the stats have been
broken since sometime in 2.3, but my system also shows my swap being used
up
Would any special hardware besides a multi-cpu system be necessarey to
test this out?
Matthew Fredrickson
On Mon, Feb 05, 2001 at 03:00:40PM +1100, Rusty Russell wrote:
> Hi all,
>
> I did the infrastructure, Anton did the bugfinding and PPC support,
> aka. the hard stuff. Other
http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
On Thu, 1 Feb 2001, Peter Samuelson wrote:
>
> [Admin Mailing Lists]
> > i have no bits directory
>
> Really? What version of libc, and on what Linux distro? I thought all
&
http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
On Thu, 1 Feb 2001, Peter Samuelson wrote:
[Admin Mailing Lists]
i have no bits directory
Really? What version of libc, and on what Linux distro? I thought all
versions of glibc2 had /usr/in
Would any special hardware besides a multi-cpu system be necessarey to
test this out?
Matthew Fredrickson
On Mon, Feb 05, 2001 at 03:00:40PM +1100, Rusty Russell wrote:
Hi all,
I did the infrastructure, Anton did the bugfinding and PPC support,
aka. the hard stuff. Other architectures
Thank goodness, it's about time. :-)
On Sat, Feb 03, 2001 at 07:08:44PM +, Anton Altaparmakov wrote:
> This is to announce the first public release of the Linux-NTFS project
> hosted on sourceforge. The project page, where you can download the source
> code tar ball or rpm as well as
Thank goodness, it's about time. :-)
On Sat, Feb 03, 2001 at 07:08:44PM +, Anton Altaparmakov wrote:
This is to announce the first public release of the Linux-NTFS project
hosted on sourceforge. The project page, where you can download the source
code tar ball or rpm as well as
On Fri, Feb 02, 2001 at 02:51:58PM -0500, Richard B. Johnson wrote:
>
> WARNING!! Messages to linux-kernel are now being intercepted
> (and answered) by this company:
> On Fri, 2 Feb 2001 [EMAIL PROTECTED] wrote:
>
> My message was sent directly to linux-kernel, with no cc address.
> It should
On Wed, Jan 31, 2001 at 06:06:32PM -0200, Rik van Riel wrote:
> On Wed, 31 Jan 2001, Rik van Riel wrote:
>
> > The information page about this bugzilla can be found here:
> >
> > http://www.linux.eu.org/Linux-MM/bugzilla.shtml
>
> OK, I just registered linux-mm.org and changed the
> httpd
On Wed, Jan 31, 2001 at 06:06:32PM -0200, Rik van Riel wrote:
On Wed, 31 Jan 2001, Rik van Riel wrote:
The information page about this bugzilla can be found here:
http://www.linux.eu.org/Linux-MM/bugzilla.shtml
OK, I just registered linux-mm.org and changed the
httpd
1 - 100 of 130 matches
Mail list logo