On Tue, Aug 26, 2008 at 12:27, Martin Michlmayr <[EMAIL PROTECTED]> wrote:
> * Gordon Farquharson <[EMAIL PROTECTED]> [2008-08-26 11:50]:
>> I also see this behaviour on ixp4xx, but I haven't looked into the
>> cause yet. I don't see it on iop32x or orion5x.
>
> I see it on orion5x.
My mistake. I
On Mon, Aug 25, 2008 at 10:43:05PM +0300, Riku Voipio wrote:
>* Xan <[EMAIL PROTECTED]> [2008-08-25 16:32]:
>>Can you confirmed that pidentd is installed by default in debian armel?
>>Why? Is not ident protocol anachronic? (see wikipedia entry)
>
>pidentd is installed on all debian installs by defa
Hello,
I have an usb ethernet adapter in my nslu2. I wanted to keep the network
interfaces persistent with udev:
nslu2:~# cat /etc/udev/rules.d/z25_persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generato
En/na Xan ha escrit:
En/na Xan ha escrit:
Hi,
I have slug with debian armel installed.
ext3 in / (see /etc/fstab I attached).
If I put in fstab: *barrier=1 or commit=30 or data=journal* *in /, *I
can't connect to slug via ssh (ssh: connect to host 172.26.0.2 port
22: No route to host). Is it
En/na Xan ha escrit:
Hi,
I have slug with debian armel installed.
ext3 in / (see /etc/fstab I attached).
If I put in fstab: *barrier=1 or commit=30 or data=journal* *in /, *I
can't connect to slug via ssh (ssh: connect to host 172.26.0.2 port
22: No route to host). Is it possible? 8-|
What
Hi,
I have slug with debian armel installed.
ext3 in / (see /etc/fstab I attached).
If I put in fstab: *barrier=1 or commit=30 or data=journal* *in /, *I
can't connect to slug via ssh (ssh: connect to host 172.26.0.2 port 22:
No route to host). Is it possible? 8-|
What happens?
Can anyone he
* Gordon Farquharson <[EMAIL PROTECTED]> [2008-08-26 11:50]:
> > I have always assumed they were timestamps, but now that i'm seeing
> > odd behavior in them on my NSLU2 running 2.6.26-1-ixp4xx from sid, i
> > don't know what they're supposed to mean. Here's the example from a
> > recent reboot.
>
On Tue 2008-08-26 13:50:32 -0400, Gordon Farquharson wrote:
> I also see this behaviour on ixp4xx, but I haven't looked into the
> cause yet. I don't see it on iop32x or orion5x.
Thanks for the confirmation, Gordon.
FWIW, it does not seem to be present in 2.6.25 (at least not at the
same point i
Hi Daniel
On Tue, Aug 26, 2008 at 11:10, Daniel Kahn Gillmor
<[EMAIL PROTECTED]> wrote:
> I have always assumed they were timestamps, but now that i'm seeing
> odd behavior in them on my NSLU2 running 2.6.26-1-ixp4xx from sid, i
> don't know what they're supposed to mean. Here's the example from
Hey folks--
what are the numbers at the start of the kernel console logs supposed
to represent?
I have always assumed they were timestamps, but now that i'm seeing
odd behavior in them on my NSLU2 running 2.6.26-1-ixp4xx from sid, i
don't know what they're supposed to mean. Here's the example fr
Hi,
I test my jfs and it seems all OK.
I test by doing the following:
- I download kernel source from kernel.org and uncompress it
- copy / from my slug to /arxius/prova (my jfs partition)
- download ubuntu into /arxius
- download ltp
- cp /arxius/prova /arxius/prova2 -r
umount and fsck the part
En/na Tobias Frost ha escrit:
So, part copied and did some testing... I'll attach a transcipt.
Abstract: This time xfs_repair did not fail, but the corruption
reoccured immediatly.
I will prepare a test-image of the partition, if someone is interested.
(I just have to nullify the swap before.
On Tue, Aug 26, 2008 at 11:19:47AM +0200, Tobias Frost wrote:
> So, part copied and did some testing... I'll attach a transcipt.
>
> Abstract: This time xfs_repair did not fail, but the corruption
> reoccured immediatly.
>
> I will prepare a test-image of the partition, if someone is interested.
So, part copied and did some testing... I'll attach a transcipt.
Abstract: This time xfs_repair did not fail, but the corruption
reoccured immediatly.
I will prepare a test-image of the partition, if someone is interested.
(I just have to nullify the swap before.)
thecus:~#xfs_check /dev/md1 2
After making some test off-list together with Xan, I decided to get back on the
list,
after I got my first results.
Here's a snippet from the conversation off-list, to help everyone
understanding what we were doing.
>> Thanks Tobias for the intro:
>> * The mounting process was OK.
>> *
En/na Riku Voipio ha escrit:
* Xan <[EMAIL PROTECTED]> [2008-08-25 16:32]:
Can you confirmed that pidentd is installed by default in debian armel?
Why? Is not ident protocol anachronic? (see wikipedia entry)
pidentd is installed on all debian installs by default,
since the "priority" s
16 matches
Mail list logo
