On Tue, Jun 19, 2007 at 08:51:25PM +0200, Karel Zak wrote:
> > > I don't think that mtab is a good place for this shared subtree
> > > stuff. The mtab needs to die.
> >
> > Perhaps. Perhaps not.
> >
> > On the one hand I think there is a place for arbitrary user-space info
> > about mounted
On Tue, Jun 19, 2007 at 04:15:28PM +0200, Karel Zak wrote:
> We use GIT for development, the utils/util-linux-ng is for releases.
Aha - and there have not been any releases yet.
> > Anyway, Dirk Gerrits, Ren?? Gabri??l and Peter Kooijmans sent me
I meant Dirk Gerrits, Ren?? Gabri??ls and
On Tue, Jun 19, 2007 at 04:15:28PM +0200, Karel Zak wrote:
We use GIT for development, the utils/util-linux-ng is for releases.
Aha - and there have not been any releases yet.
Anyway, Dirk Gerrits, Ren?? Gabri??l and Peter Kooijmans sent me
I meant Dirk Gerrits, Ren?? Gabri??ls and Peter
On Tue, Jun 19, 2007 at 08:51:25PM +0200, Karel Zak wrote:
I don't think that mtab is a good place for this shared subtree
stuff. The mtab needs to die.
Perhaps. Perhaps not.
On the one hand I think there is a place for arbitrary user-space info
about mounted filesystems. With
On Sat, Jun 02, 2007 at 08:55:13PM +0200, Jonathan Schleifer wrote:
> This patch adds a new kernel parameter (ignore_partitions=device) to
> the kernel. It is useful when using a fake RAID with dmraid so that
> Linux won't complain about attemps to access the drive beyond its
> boundaries when
On Sat, Jun 02, 2007 at 08:55:13PM +0200, Jonathan Schleifer wrote:
This patch adds a new kernel parameter (ignore_partitions=device) to
the kernel. It is useful when using a fake RAID with dmraid so that
Linux won't complain about attemps to access the drive beyond its
boundaries when udev
On Fri, May 04, 2007 at 11:18:37PM +0400, Sergei Shtylyov wrote:
> HPT36x chip don't seem to have the channel enable bits,
> so prevent the IDE core from checking them...
>
> Signed-off-by: Sergei Shtylyov <[EMAIL PROTECTED]>
Earlier this evening I reported that HPT366 was broken in 2.6.21.
I
On Fri, May 04, 2007 at 11:18:37PM +0400, Sergei Shtylyov wrote:
HPT36x chip don't seem to have the channel enable bits,
so prevent the IDE core from checking them...
Signed-off-by: Sergei Shtylyov [EMAIL PROTECTED]
Earlier this evening I reported that HPT366 was broken in 2.6.21.
I confirm
On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
> I'm having problems with a font I just created. It's a rather big one,
> intended for a framebuffer console in UTF-8 mode. The strace program
> reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
> In reading the kernel
On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
I'm having problems with a font I just created. It's a rather big one,
intended for a framebuffer console in UTF-8 mode. The strace program
reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
In reading the kernel
On Sat, Apr 07, 2007 at 01:27:09PM -0400, John Anthony Kazos Jr. wrote:
> From: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
>
> improves help text for MSDOS_PARTITION in fs/partitions/Kconfig.
> @@ -108,7 +112,11 @@ config MSDOS_PARTITION
> bool "PC BIOS (MSDOS partition tables) support" if
On Sat, Apr 07, 2007 at 01:27:09PM -0400, John Anthony Kazos Jr. wrote:
From: John Anthony Kazos Jr. [EMAIL PROTECTED]
improves help text for MSDOS_PARTITION in fs/partitions/Kconfig.
@@ -108,7 +112,11 @@ config MSDOS_PARTITION
bool PC BIOS (MSDOS partition tables) support if
On Sat, Jan 20, 2007 at 09:08:47AM +0100, Michał Kudła wrote:
> Hello,
> after
> ...
> hdb: max request size: 512KiB
> hdb: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63,
>
> Should be everywere KiB, MiB, GiB, ... according to IEC 60027-2
You are mistaken. The MB here are
On Sat, Jan 20, 2007 at 09:08:47AM +0100, Michał Kudła wrote:
Hello,
after
...
hdb: max request size: 512KiB
hdb: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63,
Should be everywere KiB, MiB, GiB, ... according to IEC 60027-2
You are mistaken. The MB here are actual
>> You were right, even after making the changes, it seems to be
>> telling lies:
>>
>> # mount
>> /dev/hda2 on / type ext2 (rw,usrquota)
Roughly speaking:
/etc/mtab shows you what you said to mount.
/proc/mounts shows what the current kernel state is.
These may differ greatly.
For all
You were right, even after making the changes, it seems to be
telling lies:
# mount
/dev/hda2 on / type ext2 (rw,usrquota)
Roughly speaking:
/etc/mtab shows you what you said to mount.
/proc/mounts shows what the current kernel state is.
These may differ greatly.
For all filesystems
On Fri, Jan 12, 2007 at 06:18:00PM -0500, Kris Karas wrote:
> Hello Andries,
>
> I noticed you're listed as the maintainer for the disk
> geometry/partitioning logic in the 2.6 kernel, so I'm sending this to
> you, as I think this bug is most likely in that part of the code, ...
>
> I've been
On Fri, Jan 12, 2007 at 06:18:00PM -0500, Kris Karas wrote:
Hello Andries,
I noticed you're listed as the maintainer for the disk
geometry/partitioning logic in the 2.6 kernel, so I'm sending this to
you, as I think this bug is most likely in that part of the code, ...
I've been
On Mon, Jan 08, 2007 at 04:06:53PM -0800, Andrew Morton wrote:
> Daniel, it'd be good if you could review and test these changes please.
>
> Also, a signed-off-by from yourself and from Andries, please...
Signed-off-by: Andries Brouwer <[EMAIL PROTECTED]>
Andries
-
To u
On Mon, Jan 08, 2007 at 04:06:53PM -0800, Andrew Morton wrote:
Daniel, it'd be good if you could review and test these changes please.
Also, a signed-off-by from yourself and from Andries, please...
Signed-off-by: Andries Brouwer [EMAIL PROTECTED]
Andries
-
To unsubscribe from this list
On Fri, Apr 01, 2005 at 07:18:52PM +0200, Uwe Zybell wrote:
> There is a line in fs/partitions/msdos.c that lets extended partitions
> be max 1k (..."==1 ? 1 : 2"...). The comment explains it to protect
> sysadmins from themselves. But now I have found a legitimate use
> for extended partitions
On Fri, Apr 01, 2005 at 07:18:52PM +0200, Uwe Zybell wrote:
There is a line in fs/partitions/msdos.c that lets extended partitions
be max 1k (...==1 ? 1 : 2...). The comment explains it to protect
sysadmins from themselves. But now I have found a legitimate use
for extended partitions in
On Mon, Mar 28, 2005 at 12:02:52PM -0800, Chris Wright wrote:
> * Pekka Enberg ([EMAIL PROTECTED]) wrote:
> > This patch removes macro obfuscation from fs/isofs/rock.c and cleans it up
> > a bit to make it more readable and maintainable. There are no functional
> > changes, only cleanups. I have
On Mon, Mar 28, 2005 at 12:02:52PM -0800, Chris Wright wrote:
* Pekka Enberg ([EMAIL PROTECTED]) wrote:
This patch removes macro obfuscation from fs/isofs/rock.c and cleans it up
a bit to make it more readable and maintainable. There are no functional
changes, only cleanups. I have only
On Wed, Mar 23, 2005 at 03:20:55PM -0800, Andrew Morton wrote:
> Nothing beats poking around in a dead machine's guts with kgdb though.
Everyone his taste.
But I was surprised by
> SwapTotal: 1052216 kB
> SwapFree: 1045984 kB
Strange that processes are killed while lots of swap is
> "Alan Curry" <[EMAIL PROTECTED]> wrote:
>>
>> With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously,
>> a block cursor could be selected by
>> echo Cursor 0-31 >> /etc/TextConfig ; SVGATextMode
>> and the cursor would be a block. On all consoles. Forever.
>>
>> To
Alan Curry [EMAIL PROTECTED] wrote:
With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously,
a block cursor could be selected by
echo Cursor 0-31 /etc/TextConfig ; SVGATextMode
and the cursor would be a block. On all consoles. Forever.
To accomplish the same thing
On Mon, Mar 14, 2005 at 10:44:31AM -0600, Berkley Shands wrote:
> With a Broadcom BC4852 and suitable Sata drives, it is easy to create
> functional devices with well in excess of 2TB raw space. This presents a
> severe
> problem to partitioning tools, such as fdisk/cfdisk and the like as
On Mon, Mar 14, 2005 at 10:44:31AM -0600, Berkley Shands wrote:
With a Broadcom BC4852 and suitable Sata drives, it is easy to create
functional devices with well in excess of 2TB raw space. This presents a
severe
problem to partitioning tools, such as fdisk/cfdisk and the like as the
On Wed, Mar 09, 2005 at 03:14:36PM -0800, Nick Stoughton wrote:
> On Linux, the link() system call does not dereference symbolic links
>
> This behavior does not conform to POSIX
>
> Most Unix implementations behave in the manner specified by POSIX. One
> notable exception is Solaris 8 (I don't
On Wed, Mar 09, 2005 at 04:55:27PM +, Alan Cox wrote:
> > [PATCH] remove dead cyrix/centaur mtrr init code
>
> This patch was discussed previously and declared incorrect. The ->init
> method call is missing in the base mtrr code.
>
> Should be reverted and/or fixed properly.
Hi Alan -
On Wed, Mar 09, 2005 at 04:55:27PM +, Alan Cox wrote:
[PATCH] remove dead cyrix/centaur mtrr init code
This patch was discussed previously and declared incorrect. The -init
method call is missing in the base mtrr code.
Should be reverted and/or fixed properly.
Hi Alan - a
On Wed, Mar 09, 2005 at 03:14:36PM -0800, Nick Stoughton wrote:
On Linux, the link() system call does not dereference symbolic links
This behavior does not conform to POSIX
Most Unix implementations behave in the manner specified by POSIX. One
notable exception is Solaris 8 (I don't know
On Sat, Mar 05, 2005 at 10:35:24PM +0100, Alexander Nyberg wrote:
> 2.6.3-mm1 'dm-crypt vs. cryptoloop' discussion was some time ago, it is
> time to bring this up again:
> http://kerneltrap.org/node/2433
Are you a troll?
This is not something to be quoted by anybody serious.
Andrew referred
On Fri, Mar 04, 2005 at 02:21:46PM -0800, Greg KH wrote:
> Anything else anyone can think of? Any objections to any of these?
> I based them off of Linus's original list.
>
> thanks,
>
> greg k-h
>
> --
>
> Rules on what kind of patches are accepted, and what ones are not, into
> the
On Fri, Mar 04, 2005 at 02:21:46PM -0800, Greg KH wrote:
Anything else anyone can think of? Any objections to any of these?
I based them off of Linus's original list.
thanks,
greg k-h
--
Rules on what kind of patches are accepted, and what ones are not, into
the linux-release
On Sat, Mar 05, 2005 at 10:35:24PM +0100, Alexander Nyberg wrote:
2.6.3-mm1 'dm-crypt vs. cryptoloop' discussion was some time ago, it is
time to bring this up again:
http://kerneltrap.org/node/2433
Are you a troll?
This is not something to be quoted by anybody serious.
Andrew referred to
On Fri, Mar 04, 2005 at 12:44:31PM -0800, Andrew Morton wrote:
> Here's the list of things which we might choose to put into 2.6.11.2.
...
> nfsd--exportfs-reduce-stack-usage.patch
...
Different people want different things with our 2.6.x.y.
I would hope that criteria include (i) patch is
On Fri, Mar 04, 2005 at 12:44:31PM -0800, Andrew Morton wrote:
Here's the list of things which we might choose to put into 2.6.11.2.
...
nfsd--exportfs-reduce-stack-usage.patch
...
Different people want different things with our 2.6.x.y.
I would hope that criteria include (i) patch is obvious,
Ha - a nice big thread. Issues include trivial fixes, testing,
and API stability.
-
About trivial fixes:
davem: the day Linus releases we always get a pile of "missing MODULE_EXPORT()"
type bug reports that are one liner fixes.
davej: So what was broken with the 2.6.8.1 type of release
Ha - a nice big thread. Issues include trivial fixes, testing,
and API stability.
-
About trivial fixes:
davem: the day Linus releases we always get a pile of missing MODULE_EXPORT()
type bug reports that are one liner fixes.
davej: So what was broken with the 2.6.8.1 type of release ?
On Wed, Mar 02, 2005 at 01:45:43PM +, Alan Cox wrote:
> On Mer, 2005-03-02 at 08:02, Dave Jones wrote:
> > If there are any of them still being used out there, I'd be even
> > more surprised if they're running 2.6. Then again, there are
> > probably loonies out there running it on 386/486's.
On Wed, Mar 02, 2005 at 01:45:43PM +, Alan Cox wrote:
On Mer, 2005-03-02 at 08:02, Dave Jones wrote:
If there are any of them still being used out there, I'd be even
more surprised if they're running 2.6. Then again, there are
probably loonies out there running it on 386/486's. 8-)
On Tue, Mar 01, 2005 at 11:52:44PM +, Alan Cox wrote:
> On Llu, 2005-02-28 at 19:20, Andries Brouwer wrote:
> > One such case is the mtrr code, where struct mtrr_ops has an
> > init field pointing at __init functions. Unless I overlook
> > something, this case may be
On Tue, Mar 01, 2005 at 11:52:44PM +, Alan Cox wrote:
On Llu, 2005-02-28 at 19:20, Andries Brouwer wrote:
One such case is the mtrr code, where struct mtrr_ops has an
init field pointing at __init functions. Unless I overlook
something, this case may be easy to settle, since the .init
On Mon, Feb 28, 2005 at 08:35:29PM +0100, Adrian Bunk wrote:
> Hi Andries,
>
> your patch has many overlappings with a patch of mine aleady in -mm
> (both none of the two patches is a subset of the other one).
>
> Nowadays, working against -mm often avoids duplicate work.
>
> cu
> Adrian
As
There are several cases where __init function pointers are
stored in a general purpose struct. For example, a SCSI
template may contain a __init detect function.
Have not yet thought of an elegant way to avoid this.
One such case is the mtrr code, where struct mtrr_ops has an
init field pointing
On Mon, Feb 28, 2005 at 01:55:28PM +0100, [EMAIL PROTECTED] wrote:
> Avoid changing the state of the console two times in some cases.
A bad change for several reasons.
(i) more object code is generated
(ii) the code is slower
(iii) you change something
Straight line code is cheap, jumps are
On Mon, Feb 28, 2005 at 01:55:28PM +0100, [EMAIL PROTECTED] wrote:
Avoid changing the state of the console two times in some cases.
A bad change for several reasons.
(i) more object code is generated
(ii) the code is slower
(iii) you change something
Straight line code is cheap, jumps are
There are several cases where __init function pointers are
stored in a general purpose struct. For example, a SCSI
template may contain a __init detect function.
Have not yet thought of an elegant way to avoid this.
One such case is the mtrr code, where struct mtrr_ops has an
init field pointing
On Mon, Feb 28, 2005 at 08:35:29PM +0100, Adrian Bunk wrote:
Hi Andries,
your patch has many overlappings with a patch of mine aleady in -mm
(both none of the two patches is a subset of the other one).
Nowadays, working against -mm often avoids duplicate work.
cu
Adrian
As far as I
The file include/sound/yss225.h is unused.
It is more or less identical to sound/oss/yss225.h,
used by sound/oss/wavfront.c.
# rm include/sound/yss225.h
Andries
(Maybe this file is a remains from an attempt to consolidate
sound/oss/yss225.c and sound/isa/wavefront/wavefront_fx.c -
it is true
The file include/sound/yss225.h is unused.
It is more or less identical to sound/oss/yss225.h,
used by sound/oss/wavfront.c.
# rm include/sound/yss225.h
Andries
(Maybe this file is a remains from an attempt to consolidate
sound/oss/yss225.c and sound/isa/wavefront/wavefront_fx.c -
it is true
On Sun, Feb 27, 2005 at 03:04:31AM +0100, Matthias Kunze wrote:
+config DEFAULT_CONSOLE_LOGLEVEL
You do not want to add yet another config option.
Config options are used to select or deselect major subsystems,
or support for specific hardware.
Not to tweak variables.
Adding more config
On Sun, Feb 27, 2005 at 01:47:43AM +0100, Uwe Bonnes wrote:
> on a Suse 9.2 System with Suse Hotplug, the phantom partition was somehow
> recognized as Reiserfs, and then the Hotplug mechanism trying to mount the
> bogus partition as a Reiser Filesystem ended in an Oops...
Always report the
On Sat, Feb 26, 2005 at 03:46:03PM -0800, Linus Torvalds wrote:
> We should probably do the same for the
> extended partition case, just to be consistent.
True.
diff -uprN -X /linux/dontdiff a/fs/partitions/msdos.c b/fs/partitions/msdos.c
--- a/fs/partitions/msdos.c 2004-12-29
On Sat, Feb 26, 2005 at 03:12:28PM -0800, Linus Torvalds wrote:
> > The default fdisk will assign type 83 to a newly created partition.
>
> Ok. Is that a "it has done so for the last 5 years" thing?
The last twelve years.
> > (About type 0: DOS has used type 0 as definition of unused. It is
On Sat, Feb 26, 2005 at 02:28:45PM -0800, Linus Torvalds wrote:
> Would it not make more sense to just sanity-check the size itself, and
> throw it out if the partition size (plus start) is bigger than the disk
> size?
I don't mind.
> There might well be people use use partition type 0, just
A well-known kernel bug is that it guesses at the partition type
and the partitions on any disk it encounters. This is bad because
needless I/O is done, slowing down the boot, sometimes quite a lot,
especially when I/O errors occur. And it is bad because sometimes
we guess wrong.
In other words,
setup_APIC_timer is only called in __init context and uses __initdata
Andries
diff -uprN -X /linux/dontdiff a/arch/i386/kernel/apic.c
b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c 2005-02-26 12:13:28.0 +0100
+++ b/arch/i386/kernel/apic.c 2005-02-26 16:13:21.0 +0100
wait_timer_tick refers to the __init functions wait_8254_wraparound
or wait_hpet_tick, hence must be __initdata.
Andries
diff -uprN -X /linux/dontdiff a/arch/i386/kernel/apic.c
b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c 2005-02-26 12:13:28.0 +0100
+++
scsi_dev_flags is referred to in
module_param_string(dev_flags, scsi_dev_flags, sizeof(scsi_dev_flags), 0);
Andries
diff -uprN -X /linux/dontdiff a/drivers/scsi/scsi_devinfo.c
b/drivers/scsi/scsi_devinfo.c
--- a/drivers/scsi/scsi_devinfo.c 2004-12-29 03:39:47.0 +0100
+++
cfq_init() calls __init cfq_slab_setup and hence must be __init itself
also made it static
Andries
diff -uprN -X /linux/dontdiff a/drivers/block/cfq-iosched.c
b/drivers/block/cfq-iosched.c
--- a/drivers/block/cfq-iosched.c 2005-02-26 12:13:29.0 +0100
+++
parport_init_mode is referred to in int __devinit sio_via_probe().
Andries
diff -uprN -X /linux/dontdiff a/drivers/parport/parport_pc.c
b/drivers/parport/parport_pc.c
--- a/drivers/parport/parport_pc.c 2005-02-26 12:13:30.0 +0100
+++ b/drivers/parport/parport_pc.c 2005-02-26
parport_init_mode is referred to in int __devinit sio_via_probe().
Andries
diff -uprN -X /linux/dontdiff a/drivers/parport/parport_pc.c
b/drivers/parport/parport_pc.c
--- a/drivers/parport/parport_pc.c 2005-02-26 12:13:30.0 +0100
+++ b/drivers/parport/parport_pc.c 2005-02-26
cfq_init() calls __init cfq_slab_setup and hence must be __init itself
also made it static
Andries
diff -uprN -X /linux/dontdiff a/drivers/block/cfq-iosched.c
b/drivers/block/cfq-iosched.c
--- a/drivers/block/cfq-iosched.c 2005-02-26 12:13:29.0 +0100
+++
scsi_dev_flags is referred to in
module_param_string(dev_flags, scsi_dev_flags, sizeof(scsi_dev_flags), 0);
Andries
diff -uprN -X /linux/dontdiff a/drivers/scsi/scsi_devinfo.c
b/drivers/scsi/scsi_devinfo.c
--- a/drivers/scsi/scsi_devinfo.c 2004-12-29 03:39:47.0 +0100
+++
wait_timer_tick refers to the __init functions wait_8254_wraparound
or wait_hpet_tick, hence must be __initdata.
Andries
diff -uprN -X /linux/dontdiff a/arch/i386/kernel/apic.c
b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c 2005-02-26 12:13:28.0 +0100
+++
setup_APIC_timer is only called in __init context and uses __initdata
Andries
diff -uprN -X /linux/dontdiff a/arch/i386/kernel/apic.c
b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c 2005-02-26 12:13:28.0 +0100
+++ b/arch/i386/kernel/apic.c 2005-02-26 16:13:21.0 +0100
A well-known kernel bug is that it guesses at the partition type
and the partitions on any disk it encounters. This is bad because
needless I/O is done, slowing down the boot, sometimes quite a lot,
especially when I/O errors occur. And it is bad because sometimes
we guess wrong.
In other words,
On Sat, Feb 26, 2005 at 02:28:45PM -0800, Linus Torvalds wrote:
Would it not make more sense to just sanity-check the size itself, and
throw it out if the partition size (plus start) is bigger than the disk
size?
I don't mind.
There might well be people use use partition type 0, just
On Sat, Feb 26, 2005 at 03:12:28PM -0800, Linus Torvalds wrote:
The default fdisk will assign type 83 to a newly created partition.
Ok. Is that a it has done so for the last 5 years thing?
The last twelve years.
(About type 0: DOS has used type 0 as definition of unused. It is not
bad
On Sat, Feb 26, 2005 at 03:46:03PM -0800, Linus Torvalds wrote:
We should probably do the same for the
extended partition case, just to be consistent.
True.
diff -uprN -X /linux/dontdiff a/fs/partitions/msdos.c b/fs/partitions/msdos.c
--- a/fs/partitions/msdos.c 2004-12-29
On Sun, Feb 27, 2005 at 01:47:43AM +0100, Uwe Bonnes wrote:
on a Suse 9.2 System with Suse Hotplug, the phantom partition was somehow
recognized as Reiserfs, and then the Hotplug mechanism trying to mount the
bogus partition as a Reiser Filesystem ended in an Oops...
Always report the oops.
On Sun, Feb 27, 2005 at 03:04:31AM +0100, Matthias Kunze wrote:
+config DEFAULT_CONSOLE_LOGLEVEL
You do not want to add yet another config option.
Config options are used to select or deselect major subsystems,
or support for specific hardware.
Not to tweak variables.
Adding more config
On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote:
> > SuSE 9.1
> > Vendor: easyRAID Model: X16 Rev: 0001
> > Type: Direct-Access ANSI SCSI revision: 03
> > scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than
> > currently supported.
>
> Looks like random
On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote:
SuSE 9.1
Vendor: easyRAID Model: X16 Rev: 0001
Type: Direct-Access ANSI SCSI revision: 03
scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than
currently supported.
Looks like random garbage.
I read e
On Wed, Feb 16, 2005 at 07:20:35PM +0100, Jirka Bohac wrote:
> Now ... are there any more suggestions for any of the patches?
For the time being I look only at the diacr for unicode part.
The fragment below looks like a strange kludge.
> - if (diacr)
> - value = handle_diacr(vc,
On Wed, Feb 16, 2005 at 07:20:35PM +0100, Jirka Bohac wrote:
Now ... are there any more suggestions for any of the patches?
For the time being I look only at the diacr for unicode part.
The fragment below looks like a strange kludge.
- if (diacr)
- value = handle_diacr(vc,
On Wed, Feb 09, 2005 at 06:19:21PM +0100, Jirka Bohac wrote:
> There are presently two ways around this, neither of them good enough
> 1) assigning one of the other modifier keysyms to the CapsLock key
>-- the LED will not work
True.
> But by adding two modifiers to almost every keyboard
On Wed, Feb 09, 2005 at 05:55:00PM +0100, Vojtech Pavlik wrote:
> On Wed, Feb 09, 2005 at 05:38:56PM +0100, Andries Brouwer wrote:
>> On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
>>
>>>> It seems very unlikely that you cannot handle Czech with all
On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
> > It seems very unlikely that you cannot handle Czech with all
> > combinations of 8 keys pressed, and need 9.
>
> A czech keyboard has the letters 'escrzyaie' with accents on the number
> row of keys. With a Shift, they are
On Wed, Feb 09, 2005 at 02:26:54PM +0100, Jirka Bohac wrote:
> Hi folks,
>
> find attached a patch that improves the keycode to keysym mapping in the
> kernel. The current system has its limits, not allowing to implement keyboard
> maps that people in different countries are used to. This patch
On Wed, Feb 09, 2005 at 02:26:54PM +0100, Jirka Bohac wrote:
Hi folks,
find attached a patch that improves the keycode to keysym mapping in the
kernel. The current system has its limits, not allowing to implement keyboard
maps that people in different countries are used to. This patch tries
On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
It seems very unlikely that you cannot handle Czech with all
combinations of 8 keys pressed, and need 9.
A czech keyboard has the letters 'escrzyaie' with accents on the number
row of keys. With a Shift, they are supposed to
On Wed, Feb 09, 2005 at 05:55:00PM +0100, Vojtech Pavlik wrote:
On Wed, Feb 09, 2005 at 05:38:56PM +0100, Andries Brouwer wrote:
On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
It seems very unlikely that you cannot handle Czech with all
combinations of 8 keys pressed
On Wed, Feb 09, 2005 at 06:19:21PM +0100, Jirka Bohac wrote:
There are presently two ways around this, neither of them good enough
1) assigning one of the other modifier keysyms to the CapsLock key
-- the LED will not work
True.
But by adding two modifiers to almost every keyboard map,
On Tue, Feb 08, 2005 at 02:57:07PM -0800, cliff white wrote:
> Running 2.6.10-ac10 on the STP 1-CPU machines, we don't seem to be able to
> complete
> a kernbench run without hitting the OOM-killer. ( kernbench is multiple
> kernel compiles,
> of course ) Machine is 800 mhz PIII with 1GB
On Tue, Feb 08, 2005 at 02:57:07PM -0800, cliff white wrote:
Running 2.6.10-ac10 on the STP 1-CPU machines, we don't seem to be able to
complete
a kernbench run without hitting the OOM-killer. ( kernbench is multiple
kernel compiles,
of course ) Machine is 800 mhz PIII with 1GB memory. We
On Mon, Feb 07, 2005 at 03:53:00PM +0900, Clemens Schwaighofer wrote:
> >>Yeah, but the link order could be changed... Patch inlined.
> >
> > And just what does the link order (or changes thereof) have to do with that?
>
> because some distributions (eg gentoo) make a symlink to
On Mon, Feb 07, 2005 at 09:10:38AM -0500, Pavel Fedin wrote:
> Nobody answered so i repeat the question.
> I think i found a way to make use of NLS table for HFS filesystem and
> i'm going to try to implement it. But first i need to create NLS module
> for codepage 10007 (Mac cyrillic). In the
On Mon, Feb 07, 2005 at 09:10:38AM -0500, Pavel Fedin wrote:
Nobody answered so i repeat the question.
I think i found a way to make use of NLS table for HFS filesystem and
i'm going to try to implement it. But first i need to create NLS module
for codepage 10007 (Mac cyrillic). In the
On Mon, Feb 07, 2005 at 03:53:00PM +0900, Clemens Schwaighofer wrote:
Yeah, but the link order could be changed... Patch inlined.
And just what does the link order (or changes thereof) have to do with that?
because some distributions (eg gentoo) make a symlink to /proc/filesystems
On Thu, Feb 03, 2005 at 03:18:20PM +0100, Fruhwirth Clemens wrote:
> (Actually it's a Multi Time Pad.)
And you call this "crypto"?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
> I ran badblocks (all night). There were none. It's a SCSI disk
> and it requires chunks of DMA RAM for each write. The machine
> just croaks when it gets low on RAM and tries to write to
> SCSI swap which requires RAM.
In some other
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
I ran badblocks (all night). There were none. It's a SCSI disk
and it requires chunks of DMA RAM for each write. The machine
just croaks when it gets low on RAM and tries to write to
SCSI swap which requires RAM.
In some other post
On Thu, Feb 03, 2005 at 03:18:20PM +0100, Fruhwirth Clemens wrote:
(Actually it's a Multi Time Pad.)
And you call this crypto?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Wed, Feb 02, 2005 at 01:23:43PM -0500, linux-os wrote:
>
> When I compile and run the following program:
>
> #include
> int main(int x, char **y)
> {
> pause();
> }
> ... as:
>
> ./xxx `yes`
>
> ... the following occurs after about 30 seconds (your mileage
> may vary):
>
> Additional
On Wed, Feb 02, 2005 at 01:23:43PM -0500, linux-os wrote:
When I compile and run the following program:
#include stdio.h
int main(int x, char **y)
{
pause();
}
... as:
./xxx `yes`
... the following occurs after about 30 seconds (your mileage
may vary):
Additional sense:
On Tue, Feb 01, 2005 at 01:14:39AM +0900, OGAWA Hirofumi wrote:
> Andries Brouwer <[EMAIL PROTECTED]> writes:
> > On Sun, Jan 30, 2005 at 09:25:33PM -0800, Andrew Morton wrote:
> >
> >> The nls_cp936.c is not synchronized with MS's translation table, there are
1 - 100 of 737 matches
Mail list logo
