Re: RTC Timezone

In article <[EMAIL PROTECTED]> you wrote: > My RTC clock is set to the local timezone. However, when I boot linux using > the -b option, to stop by a shell before the bootscripts begin, the clock is > exaclty two hours ahead. The problem is that the clock is correct, but the timezone of your

Re: RTC Timezone

In article [EMAIL PROTECTED] you wrote: My RTC clock is set to the local timezone. However, when I boot linux using the -b option, to stop by a shell before the bootscripts begin, the clock is exaclty two hours ahead. The problem is that the clock is correct, but the timezone of your system

Re: a 15 GB file on tmpfs

On Fri, Jul 22, 2005 at 01:00:18PM +0200, Stefan Smietanowski wrote: > > You cant have 16GB of Memory with 32bit CPUs. > PAE > CONFIG_HIGMEM64G > Supports a 36bit address space, which Xeons do support. Yes right, I was just not aware recent hardware (still) supports that. I mean even mit 2MB

Re: a 15 GB file on tmpfs

In article <[EMAIL PROTECTED]> you wrote: > The machine we plan to buy is a HP Proliant Xeon machine and I want to run a > 32 bit linux kernel on it (the xeon we want doesn't have the 64-bit stuff > yet) You cant have 16GB of Memory with 32bit CPUs. Bernd - To unsubscribe from this list: send

Re: a 15 GB file on tmpfs

In article [EMAIL PROTECTED] you wrote: The machine we plan to buy is a HP Proliant Xeon machine and I want to run a 32 bit linux kernel on it (the xeon we want doesn't have the 64-bit stuff yet) You cant have 16GB of Memory with 32bit CPUs. Bernd - To unsubscribe from this list: send the

Re: a 15 GB file on tmpfs

On Fri, Jul 22, 2005 at 01:00:18PM +0200, Stefan Smietanowski wrote: You cant have 16GB of Memory with 32bit CPUs. PAE CONFIG_HIGMEM64G Supports a 36bit address space, which Xeons do support. Yes right, I was just not aware recent hardware (still) supports that. I mean even mit 2MB modules

Re: Swap partition vs swap file

In article <[EMAIL PROTECTED]> you wrote: > So are you saying that if I create a swap partition it's best to use dd to > zero it out before mkswap? Nope I did not. However I dont know of any other shell tool which can do it that easyly. > As far as portable, we're talking about linux,

Re: Swap partition vs swap file

In article [EMAIL PROTECTED] you wrote: So are you saying that if I create a swap partition it's best to use dd to zero it out before mkswap? Nope I did not. However I dont know of any other shell tool which can do it that easyly. As far as portable, we're talking about linux, portability is

Re: Swap partition vs swap file

In article <[EMAIL PROTECTED]> you wrote: > You misunderstood entirely what I said. There is no portable/documented way to grow a file without having the file system null its content. However why is that a problem, you dont create those files very often. Besides it is better for the OS to be able

Re: Swap partition vs swap file

In article [EMAIL PROTECTED] you wrote: You misunderstood entirely what I said. There is no portable/documented way to grow a file without having the file system null its content. However why is that a problem, you dont create those files very often. Besides it is better for the OS to be able to

Re: Swap partition vs swap file

In article <[EMAIL PROTECTED]> you wrote: > I guess/hope dd always makes it contiguously. No, it is creating files by appending just like any other file write. One could think about a call to create unfragmented files however since this is not always working best is to create those files young or

Re: Swap partition vs swap file

In article [EMAIL PROTECTED] you wrote: I guess/hope dd always makes it contiguously. No, it is creating files by appending just like any other file write. One could think about a call to create unfragmented files however since this is not always working best is to create those files young or

Re: ia64 git pull

In article <[EMAIL PROTECTED]> you wrote: > Why? Because I'm still using the stupid "get all objects" thing when I > pull. one could do a symlink/hardlink parallel tree for a specific snapshot with GIT tools, and then only poll that with git-unaware copy tools. I guess this would make sense for

Re: ia64 git pull

In article [EMAIL PROTECTED] you wrote: Why? Because I'm still using the stupid get all objects thing when I pull. one could do a symlink/hardlink parallel tree for a specific snapshot with GIT tools, and then only poll that with git-unaware copy tools. I guess this would make sense for the

Re: Why Ext2/3 needs immutable attribute?

On Sun, Apr 17, 2005 at 07:48:50PM -0400, Xin Zhao wrote: > any kernel level protection, including > SELinux, could be disabled after the kernel is compromised. Am I > missing some points here? No, Immutable bit is an application of capabilities (or securelevel), you are right. If the kernel is

Re: Why Ext2/3 needs immutable attribute?

In article <[EMAIL PROTECTED]> you wrote: > Yes. I know, with immutable, even root cannot modify sensitive > files. What I am curious is if an intruder has root access, he may > have many ways to turn off the immutable protection and modify files. If you secure your system correctly (i.e make

Re: Why Ext2/3 needs immutable attribute?

In article <[EMAIL PROTECTED]> you wrote: > Why not simply unset the write bit for all three groups of users? > That seems to be enough to prevent file modification. # touch test # chmod a-w test # echo test > test # cat test test Because this does not protect against writes from root and it

Re: More performance for the TCP stack by using additional hardware chip on NIC

In article <[EMAIL PROTECTED]> you wrote: > maybe one day you would be able to offload your firewall and policy > router too :) There are quite a few filtering NICs out there. Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: More performance for the TCP stack by using additional hardware chip on NIC

In article [EMAIL PROTECTED] you wrote: maybe one day you would be able to offload your firewall and policy router too :) There are quite a few filtering NICs out there. Greetings Bernd - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL

Re: Why Ext2/3 needs immutable attribute?

In article [EMAIL PROTECTED] you wrote: Why not simply unset the write bit for all three groups of users? That seems to be enough to prevent file modification. # touch test # chmod a-w test # echo test test # cat test test Because this does not protect against writes from root and it does

Re: Why Ext2/3 needs immutable attribute?

In article [EMAIL PROTECTED] you wrote: Yes. I know, with immutable, even root cannot modify sensitive files. What I am curious is if an intruder has root access, he may have many ways to turn off the immutable protection and modify files. If you secure your system correctly (i.e make

Re: Why Ext2/3 needs immutable attribute?

On Sun, Apr 17, 2005 at 07:48:50PM -0400, Xin Zhao wrote: any kernel level protection, including SELinux, could be disabled after the kernel is compromised. Am I missing some points here? No, Immutable bit is an application of capabilities (or securelevel), you are right. If the kernel is

Re: [PATCH encrypted swsusp 1/3] core functionality

In article <[EMAIL PROTECTED]> you wrote: > The dmcrypt swap can only be unlocked by the user with a passphrase, > which is analogous to how you unlock your ssh private key stored > on the disk using a passphrase. We talk about the unlocked system getting hacked. However I am not why the hacker

Re: [PATCH encrypted swsusp 1/3] core functionality

In article <[EMAIL PROTECTED]> you wrote: > The ssh keys are *encrypted* in the swap when dmcrypt is used. > When the swap runs over dmcrypt all writes including those from > swsusp are encrypted. The problem is that after an resume the running system has access to the swap, because the key is

Re: [PATCH encrypted swsusp 1/3] core functionality

In article [EMAIL PROTECTED] you wrote: The ssh keys are *encrypted* in the swap when dmcrypt is used. When the swap runs over dmcrypt all writes including those from swsusp are encrypted. The problem is that after an resume the running system has access to the swap, because the key is

Re: [PATCH encrypted swsusp 1/3] core functionality

In article [EMAIL PROTECTED] you wrote: The dmcrypt swap can only be unlocked by the user with a passphrase, which is analogous to how you unlock your ssh private key stored on the disk using a passphrase. We talk about the unlocked system getting hacked. However I am not why the hacker would

Re: more git updates..

In article <[EMAIL PROTECTED]> you wrote: > (I repeat the xxx in the leaf name - easier to code.) It is a bit OT, but just a note: there are file systems (hash functions) out there who dont like a lot of files named the same way. For example NTFS with the 8.3 short names. Greetings Bernd - To

Re: more git updates..

In article [EMAIL PROTECTED] you wrote: (I repeat the xxx in the leaf name - easier to code.) It is a bit OT, but just a note: there are file systems (hash functions) out there who dont like a lot of files named the same way. For example NTFS with the 8.3 short names. Greetings Bernd - To

Re: more git updates..

In article <[EMAIL PROTECTED]> you wrote: > Ralph wrote: >> Watch out for when xargs invokes do_something more than once and the `<' >> is parsed by a different one than the `>'. > It will take a pretty long list to do that. It seems that > GNU xargs on top of a Linux kernel has a 128 KByte

Re: more git updates..

In article [EMAIL PROTECTED] you wrote: Ralph wrote: Watch out for when xargs invokes do_something more than once and the `' is parsed by a different one than the `'. It will take a pretty long list to do that. It seems that GNU xargs on top of a Linux kernel has a 128 KByte ARG_MAX. In the

Re: Aligning file system data

In article <[EMAIL PROTECTED]> you wrote: > How likely is it that I can actually align stuff to 31.5KiB on the > physical disk, i.e. have each block be a track? It is not that easy to allign on tracks, even on raw partition. Some disks have different length of tracks (of course because the inner

Re: Aligning file system data

In article [EMAIL PROTECTED] you wrote: How likely is it that I can actually align stuff to 31.5KiB on the physical disk, i.e. have each block be a track? It is not that easy to allign on tracks, even on raw partition. Some disks have different length of tracks (of course because the inner

Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)

Hello Ted, In article <[EMAIL PROTECTED]> you wrote: > Should we fix it today? Given that we have ext3, I'd probably answer > no. It's a known property of ext2; we've lived with it for over ten > years, and to add this would just slow down ext2 (which gets used > often as benchmark standard to

Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)

Hello Ted, In article [EMAIL PROTECTED] you wrote: Should we fix it today? Given that we have ext3, I'd probably answer no. It's a known property of ext2; we've lived with it for over ten years, and to add this would just slow down ext2 (which gets used often as benchmark standard to aspire

Re: Devices/Partitions over 2TB

In article <[EMAIL PROTECTED]> you wrote: > You have to ignore the partition table contents for ending cylinder. Why use MSDOS partition tables at all? What about LVM or GUID Partitions? Gruss Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: Devices/Partitions over 2TB

In article [EMAIL PROTECTED] you wrote: You have to ignore the partition table contents for ending cylinder. Why use MSDOS partition tables at all? What about LVM or GUID Partitions? Gruss Bernd - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to

Re: [MC] [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option?

In article <[EMAIL PROTECTED]> you wrote: > 3. I open a file w/o O_SYNC, issue a bunch of writes, then call > ioctl(FIOASYNC) to set the fd sync, then issure a second set of writes. > Only the second set of writes are synchronous? I also am curious if one can open a file, write to it, close it,

Re: [MC] [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option?

In article [EMAIL PROTECTED] you wrote: 3. I open a file w/o O_SYNC, issue a bunch of writes, then call ioctl(FIOASYNC) to set the fd sync, then issure a second set of writes. Only the second set of writes are synchronous? I also am curious if one can open a file, write to it, close it, open

Re: Huge unreliability - does Linux have something to do with it?

In article <[EMAIL PROTECTED]> you wrote: > I halted the machine correctly yesterday night. I never dropped the > box in 3 years. Am I just being unlucky? Or could the fact that I am > using Linux on the box affect the reliability in some ways on that > particular hardware (Dell Inspiron 8100)? I

Re: Huge unreliability - does Linux have something to do with it?

In article [EMAIL PROTECTED] you wrote: I halted the machine correctly yesterday night. I never dropped the box in 3 years. Am I just being unlucky? Or could the fact that I am using Linux on the box affect the reliability in some ways on that particular hardware (Dell Inspiron 8100)? I run

Re: Drive performance bottleneck

In article <[EMAIL PROTECTED]> you wrote: > Below is an oprofile (truncated) of (the same) dd running on /dev/sdb. do you also have the oprofile of the sg_dd handy? Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: Drive performance bottleneck

In article [EMAIL PROTECTED] you wrote: Below is an oprofile (truncated) of (the same) dd running on /dev/sdb. do you also have the oprofile of the sg_dd handy? Greetings Bernd - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL

Re: [RFC] "biological parent" pid

In article <[EMAIL PROTECTED]> you wrote: > I am not aware of concepts in Linux or other unices that apply to this > case. Normal process accounting. If you want to keep the pid of the bio-parent, you also need to keep the start-time to make it unique. Better would be to have a all-time-unqiue

Re: [RFC] biological parent pid

In article [EMAIL PROTECTED] you wrote: I am not aware of concepts in Linux or other unices that apply to this case. Normal process accounting. If you want to keep the pid of the bio-parent, you also need to keep the start-time to make it unique. Better would be to have a all-time-unqiue

Re: [Bug 4081] New: OpenOffice crashes while starting due to a threading error

In article <[EMAIL PROTECTED]> you wrote: > stat64("/dev/dri/card14", 0xbff9c8bc) = -1 ENOENT (No such file or > directory) > What is at fault? Certainly oo shouldn't just seg-fault, but should the > permissions on /dev/dri/card* be crw-rw or crw-rw-rw-? it is not a permission thing, it

Re: [Bug 4081] New: OpenOffice crashes while starting due to a threading error

In article [EMAIL PROTECTED] you wrote: stat64(/dev/dri/card14, 0xbff9c8bc) = -1 ENOENT (No such file or directory) What is at fault? Certainly oo shouldn't just seg-fault, but should the permissions on /dev/dri/card* be crw-rw or crw-rw-rw-? it is not a permission thing, it tells

Re: Linux and system area networks

In article <[EMAIL PROTECTED]> you wrote: > We seem to have come full circle. My original question was about > providing a better way for sockets applications to take advantage of > SAN hardware. W2K Datacenter introduces "Winsock Direct," which will > bypass the protocol stack when

Re: Linux and system area networks

In article [EMAIL PROTECTED] you wrote: We seem to have come full circle. My original question was about providing a better way for sockets applications to take advantage of SAN hardware. W2K Datacenter introduces Winsock Direct, which will bypass the protocol stack when appropriate. The

Re: harddisk support

In article <[EMAIL PROTECTED]> you wrote: > How can I access more than 16 harddisks? Create the Device File with: cd /dev ; MAKEDEV sdq -or- cd /dev ; mknod sdq b 65 0 mknod sdq1 b 65 1 ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: how to display proxy arp addresses using "ip neigh" from iproute2

In article <[EMAIL PROTECTED]> you wrote: > 47.129.82.116 * * MPeth0 the asteriks simply show you, that the new linuix kernel will not be able to remeber any mac address for a proxy arp entry. It will always respond with the device' own MAC address. Can't

Re: how to display proxy arp addresses using ip neigh from iproute2

In article [EMAIL PROTECTED] you wrote: 47.129.82.116 * * MPeth0 the asteriks simply show you, that the new linuix kernel will not be able to remeber any mac address for a proxy arp entry. It will always respond with the device' own MAC address. Can't

Re: harddisk support

In article [EMAIL PROTECTED] you wrote: How can I access more than 16 harddisks? Create the Device File with: cd /dev ; MAKEDEV sdq -or- cd /dev ; mknod sdq b 65 0 mknod sdq1 b 65 1 ... - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL

Re: missing sysrq

In article <[EMAIL PROTECTED]> you wrote: > However, if I go to /proc/sys/kernel/sysrq does not exist. It is a compile time option, so the person who compiled your kernel left it out. > vm.freepages = 383 766 1149 tat feature is removed in recent VM Systems. Greetings Bernd - To unsubscribe

Re: missing sysrq

In article [EMAIL PROTECTED] you wrote: However, if I go to /proc/sys/kernel/sysrq does not exist. It is a compile time option, so the person who compiled your kernel left it out. vm.freepages = 383 766 1149 tat feature is removed in recent VM Systems. Greetings Bernd - To unsubscribe from

Re: light weight user level semaphores

In article <[EMAIL PROTECTED]> you wrote: > So FS_create() starts out by allocating the backing store for the > semaphore. This can basically be done in user space, although the > kernel does need to get involved for the second part of it, which > is to (a) allocate a kernel "backing

Re: light weight user level semaphores

In article [EMAIL PROTECTED] you wrote: So FS_create() starts out by allocating the backing store for the semaphore. This can basically be done in user space, although the kernel does need to get involved for the second part of it, which is to (a) allocate a kernel "backing store"

Re: ARP responses broken!

> but why would you want it to reply for the IP of the other interface even if > it was NOT on the same subnet? Because Linux is always answering to all its local IP addresses, regardless of the Network interface. Even if you tun off the IP Forwarding. This is by Designs, there are situation

Re: ARP responses broken!

but why would you want it to reply for the IP of the other interface even if it was NOT on the same subnet? Because Linux is always answering to all its local IP addresses, regardless of the Network interface. Even if you tun off the IP Forwarding. This is by Designs, there are situation

Re: ARP responses broken!

In article <[EMAIL PROTECTED]> you wrote: > The second one is the valid one, but both interfaces seem to answer to the > broadcasted packet with their own ARP addresses. it is because the kernel does not know if both interfaces are on one subnet, or not. The easisets thing to solve this is t use

Re: ARP responses broken!

In article [EMAIL PROTECTED] you wrote: The second one is the valid one, but both interfaces seem to answer to the broadcasted packet with their own ARP addresses. it is because the kernel does not know if both interfaces are on one subnet, or not. The easisets thing to solve this is t use the

Re: fsck, raid reconstruction & bad bad 2.4.3

In article <[EMAIL PROTECTED]> you wrote: > Is this a pathological case because of the way fsck does business, or does the RAID >re-sync affect any disk-bound process that severely? i gues the seeks are the problem. fsck will quite heavyly reposition, so does the rebuild, most likely on

Re: fsck, raid reconstruction & bad bad 2.4.3

In article <01041521302600.15046@tabby> you wrote: >>a) stop rebuild until fsck is fixed > And let fsck read bad data because the raid doesn't yet recognize the correct > one a degraded raid will not deliver broken data. and even if it does, one more reason not to check a degraded raid. >

Re: fsck, raid reconstruction & bad bad 2.4.3

In article <[EMAIL PROTECTED]> you wrote: >>(There is no config file to disable/alter this .. no work-around that I >>know of ..) > You can't be serious. Go sit down and think about what's going on. Well, there are two potential solutions: a) stop rebuild until fsck is fixed b) wait with fsck

Re: fsck, raid reconstruction bad bad 2.4.3

In article [EMAIL PROTECTED] you wrote: (There is no config file to disable/alter this .. no work-around that I know of ..) You can't be serious. Go sit down and think about what's going on. Well, there are two potential solutions: a) stop rebuild until fsck is fixed b) wait with fsck until

Re: fsck, raid reconstruction bad bad 2.4.3

In article [EMAIL PROTECTED] you wrote: Is this a pathological case because of the way fsck does business, or does the RAID re-sync affect any disk-bound process that severely? i gues the seeks are the problem. fsck will quite heavyly reposition, so does the rebuild, most likely on different

Re: fsck, raid reconstruction bad bad 2.4.3

In article 01041521302600.15046@tabby you wrote: a) stop rebuild until fsck is fixed And let fsck read bad data because the raid doesn't yet recognize the correct one a degraded raid will not deliver broken data. and even if it does, one more reason not to check a degraded raid. There

Re: [BUG] tmpfs and loop

In article <01041321112600.23961@oscar> you wrote: > oscar% sudo mount /tmp/disk /snap -oloop -text2 > ioctl: LOOP_SET_FD: Invalid argument are you sure you have a working loop device? Try to verify it in a non tmpfs filesystem. > stat64("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7,

Re: [BUG] tmpfs and loop

In article 01041321112600.23961@oscar you wrote: oscar% sudo mount /tmp/disk /snap -oloop -text2 ioctl: LOOP_SET_FD: Invalid argument are you sure you have a working loop device? Try to verify it in a non tmpfs filesystem. stat64("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 0),

Re: race condition on looking up inodes

In article <000201c0c0a4$eb5c7b10$321ea8c0@saturn> you wrote: >rename("/usr/hybrid/cfg/data","/usr/mytemp/data1"); /*for process 1*/ > rename("/usr/mytemp/data1","/usr/test");/* for process 2*/ Rename syscall is expected to be atomic on unixoid systems. And I dont know of a case where a

Re: race condition on looking up inodes

In article 000201c0c0a4$eb5c7b10$321ea8c0@saturn you wrote: rename("/usr/hybrid/cfg/data","/usr/mytemp/data1"); /*for process 1*/ rename("/usr/mytemp/data1","/usr/test");/* for process 2*/ Rename syscall is expected to be atomic on unixoid systems. And I dont know of a case where a problem

Re: pivot_root & linuxrc problem

In article <[EMAIL PROTECTED]> you wrote: > Aha.. so that's it. I've never been able to get /linuxrc to execute > automagically. I wonder why /linuxrc executes on Art's system, but > not on mine. I can call it whatever I want and it doesn't run unless > I explicitly start it with

Re: kernel 2.4.2 network performances

In article <[EMAIL PROTECTED]> you wrote: > Yesterday I discovered that the load I can throw out to network seems to > depend on other activities running on machine. I was able to get > throughput of 33M/s with ATM when machine was idle, while I compiled > kernel at same time, the throughput was

Re: kernel 2.4.2 network performances

In article [EMAIL PROTECTED] you wrote: Yesterday I discovered that the load I can throw out to network seems to depend on other activities running on machine. I was able to get throughput of 33M/s with ATM when machine was idle, while I compiled kernel at same time, the throughput was

Re: pivot_root linuxrc problem

In article [EMAIL PROTECTED] you wrote: Aha.. so that's it. I've never been able to get /linuxrc to execute automagically. I wonder why /linuxrc executes on Art's system, but not on mine. I can call it whatever I want and it doesn't run unless I explicitly start it with init=whatever.

Re: Alert on LAN for Linux?

In article <[EMAIL PROTECTED]> you wrote: > Alert on LAN makes the system up from power management type sleep when > there are packets to be processed. Why you would ever have sleep mode on > a server is beyond me. Most professional UPS with Network Management Cards can go a sever to sleep mode

Re: Alert on LAN for Linux?

In article [EMAIL PROTECTED] you wrote: Alert on LAN makes the system up from power management type sleep when there are packets to be processed. Why you would ever have sleep mode on a server is beyond me. Most professional UPS with Network Management Cards can go a sever to sleep mode if

Re: Status of posix-ACL's

In article you wrote: > What are the biggest problems? (i know that many userland-tools must be > changed for this). AFAIK there is no Support in User Land Programs required. You just have additional tools for managing the ACLs . The main problem

Re: Status of posix-ACL's

In article F1457AD86AB6D311A6F200105AD9FB0219E251@EPCNETIN you wrote: What are the biggest problems? (i know that many userland-tools must be changed for this). AFAIK there is no Support in User Land Programs required. You just have additional tools for managing the ACLs . The main problem

Re: ide / usb problem

In article <20010225060326.K127@pervalidus> you wrote: > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hda: dma_intr: error=0x84 { DriveStatusError BadCRC } I think I saw that with broken Drives, too. Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe

Re: ide / usb problem

In article 20010225060326.K127@pervalidus you wrote: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } I think I saw that with broken Drives, too. Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe

Re: reiserfs: still problems with tail conversion

In article <87861.983061717@tiny> you wrote: > Exactly. The tail conversion code depends heavily on the page up to date > bit being set right. It is more than possible that I've screwed up > something there, and the code thinks a page is valid when it really isn't. I have seen null byte

Re: reiserfs: still problems with tail conversion

In article 87861.983061717@tiny you wrote: Exactly. The tail conversion code depends heavily on the page up to date bit being set right. It is more than possible that I've screwed up something there, and the code thinks a page is valid when it really isn't. I have seen null byte

Re: [rfc] Near-constant time directory index for Ext2

In article <01022100361408.18944@gimli> you wrote: > But actually, rm is not problem, it's open and create. To do a > create you have to make sure the file doesn't already exist, and > without an index you have to scan on average half the directory file. Unless you use a File System which is

Re: [rfc] Near-constant time directory index for Ext2

In article 01022100361408.18944@gimli you wrote: But actually, rm is not problem, it's open and create. To do a create you have to make sure the file doesn't already exist, and without an index you have to scan on average half the directory file. Unless you use a File System which is better

Re: ip_conntrack error under 2.4.1-ac18

In article <[EMAIL PROTECTED]> you wrote: > Feb 18 23:05:50 rhino kernel: ip_conntrack: maximum limit of 8184 entries exceed > ed > while running nessus, with 100 simultaneous connections set, against a > company machine. This is the first time I've observed this error. It is not an error, you

Re: Kernel executation from ROM

In article <01e701c09a2a$21e789a0$bba6b3d0@Toshiba> you wrote: > I see . The biggest negative point of running kernel from ROM is that ROM > speed is slow :( Well, normally you use the ROM only as a "boot device". You copy the Kernel into RAM and run it. Ram is not more expensive than ROM :)

Re: Kernel executation from ROM

In article 01e701c09a2a$21e789a0$bba6b3d0@Toshiba you wrote: I see . The biggest negative point of running kernel from ROM is that ROM speed is slow :( Well, normally you use the ROM only as a "boot device". You copy the Kernel into RAM and run it. Ram is not more expensive than ROM :) What

Re: ip_conntrack error under 2.4.1-ac18

In article [EMAIL PROTECTED] you wrote: Feb 18 23:05:50 rhino kernel: ip_conntrack: maximum limit of 8184 entries exceed ed while running nessus, with 100 simultaneous connections set, against a company machine. This is the first time I've observed this error. It is not an error, you just

Re: reiserfs min size (was: [2.4.1] mkreiserfs on loopdevice freezes kernel)

On Wed, Jan 31, 2001 at 11:15:56PM +, James Sutherland wrote: > > dd if=/dev/zero of=/var/loop.img count=32768 size=4096 > > That just creates a 128Mb file of zeros... This sounds a bit small. Why > "size=4096"?? because i am too tired to calculate. mkreiserfs wants 32768 (32*1024) blocks

reiserfs min size (was: [2.4.1] mkreiserfs on loopdevice freezes kernel)

On Wed, Jan 31, 2001 at 09:24:39AM +, James Sutherland wrote: > 32 megaBLOCK?? How big is it in Mbytes? Blocksize is 4k, mkreiserfs in my version is telling me it can not generate partitions smaller than 32M but it is not true, i have to do dd if=/dev/zero of=/var/loop.img count=32768

Re: reiserfs min size (was: [2.4.1] mkreiserfs on loopdevice freezes kernel)

On Wed, Jan 31, 2001 at 11:15:56PM +, James Sutherland wrote: dd if=/dev/zero of=/var/loop.img count=32768 size=4096 That just creates a 128Mb file of zeros... This sounds a bit small. Why "size=4096"?? because i am too tired to calculate. mkreiserfs wants 32768 (32*1024) blocks with a

[2.4.1] mkreiserfs on loopdevice freezes kernel

Hello, if I run mkreiserfs on a 32megablocks /dev/loop0 it will lock up while generating the journaling information. Sometimes at 20% sometimes at 60%. Since mkreiserfs is not using the kernel module i guess this is a loop device problem in 2.4.1 kernels. There is no dmesg message at the

Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN)

In article <[EMAIL PROTECTED]> you wrote: > On Tue, Jan 30, 2001 at 02:17:57PM -0800, David S. Miller wrote: > 8.5MB/sec sounds like half-duplex 100baseT. > No; I'm 100% its FD; HD gives 40k/sec TCP because of collisions and > such like. > Positive you are running at full duplex all

Re: Request: increase in PCI bus limit

In article <[EMAIL PROTECTED]> you wrote: > I guess the cleanest solution would be to allow variable setting of the > maximum number of PCI busses in the config file, similar to the > CONFIG_UNIX98_PTY_COUNT setting, so that "exotic" users with 32+ PCI > busses can boost the standard value

Re: Request: increase in PCI bus limit

In article <[EMAIL PROTECTED]> you wrote: > 256, in later 2.4.* kernel releases? That would allow this customer to > work with an unpatched kernel, at the cost of an additional 3.5 kB of > variables in the kernel. Don't think this is fairly common. So especially since I consider that kind of

Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN)

In article [EMAIL PROTECTED] you wrote: On Tue, Jan 30, 2001 at 02:17:57PM -0800, David S. Miller wrote: 8.5MB/sec sounds like half-duplex 100baseT. No; I'm 100% its FD; HD gives 40k/sec TCP because of collisions and such like. Positive you are running at full duplex all the way

[2.4.1] mkreiserfs on loopdevice freezes kernel

Hello, if I run mkreiserfs on a 32megablocks /dev/loop0 it will lock up while generating the journaling information. Sometimes at 20% sometimes at 60%. Since mkreiserfs is not using the kernel module i guess this is a loop device problem in 2.4.1 kernels. There is no dmesg message at the

Re: hotmail not dealing with ECN

In article <[EMAIL PROTECTED]> you wrote: >> Think of yourself as a firewall author now. You come across this, and >> go, "these bits aren't used now; this means noone should be setting >> them. I have no guarantee that anything in the future isn't going to use >> these bits for something that

Re: hotmail not dealing with ECN

In article [EMAIL PROTECTED] you wrote: Think of yourself as a firewall author now. You come across this, and go, "these bits aren't used now; this means noone should be setting them. I have no guarantee that anything in the future isn't going to use these bits for something that isn't

Re: hotmail not dealing with ECN

In article <[EMAIL PROTECTED]> you wrote: > RFC793, where is lists the unused flag bits as "reserved". > That is pretty clear to me. It just has to say that > they are reserved, and that is what it does. Actually I read somehwre "must be 0", but I am afraid dont know where anymore. anyway, it

<    1   2   3   >