quick question

quick question

[tim fitz]

Hi everyone,
This is Tim Fitz over at iParadigms (www.turnitin.com). We've been doing
some more playing with reiser and it seems to be running pretty well,
but every now and then our Dell PERC card seems to throw a tantrum and
kill the machine. Well either way, we have been happy for a few months
but now we are in the hole again. The machine is up but on two of our
partitions we have errors. After running reiserfsck we got the messages
below. I was wondering if there was any serious worries about trying to
fix these errors with reiserfsprogs-3.6.10? Anything I should worry
about? I know the --check happened with older utilities, but I just
downloaded the 3.6.10... Anything I should worry about? Or is there any
special thing I should do?

Thanks alot!!!

Tim


--------------------------------------

rep1:~/reiserfsprogs-3.6.5-pre2/fsck # ./reiserfsck --check /dev/sdb1

<-------------reiserfsck, 2002------------->
reiserfsprogs 3.6.5-pre2

  *************************************************************
  ** If you are using the latest reiserfsprogs and  it fails **
  ** please  email bug reports to reiserfs-list@namesys.com, **
  ** providing  as  much  information  as  possible --  your **
  ** hardware,  kernel,  patches,  settings,  all  reiserfsk **
  ** messages  (including version),  the reiserfsck logfile, **
  ** check  the  syslog file  for  any  related information. **
  ** If you would like advice on using this program, support **
  ** is available  for $25 at  www.namesys.com/support.html. **
  *************************************************************

Will read-only check consistency of the filesystem on /dev/sdb1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
###########
reiserfsck --check started at Wed Jul 23 10:18:36 2003
###########
Replaying journal..
0 transactions replayed
Checking internal tree../  1 (of  34)/119 (of 147)/ 80 (of 162)/ 60 (of
136)block 562318: The level of the node (0) is not correct, (1) expected
 the problem in the internal node occured (562318), whole subtree is
skipped
/  2 (of  34)/ 16 (of 133)/ 40 (of 159)/114 (of 152)bad_leaf: block
1429700, items 4 and 5: The wrong order of items: [53184 4693494 0x1
DRCT (2)], [53184 4693495 0x1 DRCT (2)]
/115 (of 152)block 1429701: The level of the node (3) is not correct,
(1) expected
 the problem in the internal node occured (1429701), whole subtree is
skipped
/116 (of 133)/ 52 (of 170)/ 34 (of 167)block 4228346: The level of the
node (0) is not correct, (1) expected
 the problem in the internal node occured (4228346), whole subtree is
skipped
/  3 (of  34)/ 55 (of 133)/ 98 (of 170)/168 (of 169)block 6338838: The
level of the node (0) is not correct, (1) expected
 the problem in the internal node occured (6338838), whole subtree is
skipped
/126 (of 133)/117 (of 170)/ 78 (of 169)block 8449305: The level of the
node (0) is not correct, (1) expected
 the problem in the internal node occured (8449305), whole subtree is
skipped
/  8 (of  34)/ 49 (of  86)/153 (of 170)/109 (of 164)bad_indirect_item:
block 35031784: The item (125113 78494461 0x1 IND (1), len 4, location
2356 entry count 0, fsck need 0, format new) has the bad pointer (0) to
the block (28235501), which is in tree already
/ 60 (of  86)/ 51 (of 170)/152 (of 162)bad_leaf: block 35463068, items 5
and 6: The wrong order of items: [125477 79460671 0x1001 DRCT (2)],
[125477 79460672 0x1 DRCT (2)]
/153 (of 162)block 35463069: The level of the node (30425) is not
correct, (1) expected
 the problem in the internal node occured (35463069), whole subtree is
skipped
/ 12 (of  34)/168 (of 170)/ 86 (of 170)/154 (of 170)block 59632218: The
level of the node (40122) is not correct, (1) expected
 the problem in the internal node occured (59632218), whole subtree is
skipped
/ 13 (of  34)/ 18 (of 170)/ 54 (of 170)/ 80 (of 169)block 60421583: The
level of the node (45664) is not correct, (1) expected
 the problem in the internal node occured (60421583), whole subtree is
skipped
/ 14 (of  34)/153 (of 170)/  6 (of 170)/165 (of 169)bad_indirect_item:
block 72433096: The item [153420 168695575 0x1 IND (1)] has the bad
pointer (0) to the block (4260207410)
bad_indirect_item: block 72433096: The item [153420 168695576 0x1 IND
(1)] has the bad pointer (0) to the block (1133521883)
/ 15 (of  34)/ 10 (of 170)/ 41 (of 170)/ 54 (of 167)block 73505462: The
level of the node (20372) is not correct, (1) expected
 the problem in the internal node occured (73505462), whole subtree is
skipped
/ 13 (of 170)/  4 (of 170)/ 75 (of 167)block 73616595: The level of the
node (19986) is not correct, (1) expected
 the problem in the internal node occured (73616595), whole subtree is
skipped
/ 44 (of 170)/117 (of 170)/150 (of 168)block 74879572: The level of the
node (15017) is not correct, (1) expected
 the problem in the internal node occured (74879572), whole subtree is
skipped
/ 16 (of  34)/ 53 (of 170)/ 55 (of 170)/103 (of 169)block 81849488: The
level of the node (58986) is not correct, (1) expected
 the problem in the internal node occured (81849488), whole subtree is
skipped
/ 18 (of  34)/ 90 (of 170)/ 71 (of 170)/ 14 (of 170)block 96149585: The
level of the node (2079) is not correct, (1) expected
 the problem in the internal node occured (96149585), whole subtree is
skipped
/ 98 (of 170)/ 55 (of 170)/ 90 (of 168)block 96447299: The level of the
node (46106) is not correct, (1) expected
 the problem in the internal node occured (96447299), whole subtree is
skipped
/ 21 (of  34)/ 82 (of 170)/149 (of 170)/ 87 (of 170)block 108707229: The
level of the node (51164) is not correct, (1) expected
 the problem in the internal node occured (108707229), whole subtree is
skipped
/150 (of 170)/ 47 (of 170)/ 36 (of 169)block 111097021: The level of the
node (2850) is not correct, (1) expected
 the problem in the internal node occured (111097021), whole subtree is
skipped
/155 (of 170)/ 14 (of 170)/ 78 (of 170)block 111269980: The level of the
node (35589) is not correct, (1) expected
 the problem in the internal node occured (111269980), whole subtree is
skipped
/ 22 (of  34)/ 29 (of  86)/ 67 (of 170)/ 65 (of 170)block 112942176: The
level of the node (9706) is not correct, (1) expected
 the problem in the internal node occured (112942176), whole subtree is
skipped
/ 24 (of  34)/ 38 (of 170)/ 53 (of 170)/101 (of 170)block 120103820: The
level of the node (30830) is not correct, (1) expected
 the problem in the internal node occured (120103820), whole subtree is
skipped
/137 (of 170)/ 67 (of 170)/ 38 (of 168)block 123964496: The level of the
node (28828) is not correct, (1) expected
 the problem in the internal node occured (123964496), whole subtree is
skipped
/ 25 (of  34)/  2 (of 170)/164 (of 170)/155 (of 170)block 125380199: The
level of the node (8152) is not correct, (1) expected
 the problem in the internal node occured (125380199), whole subtree is
skipped
/ 61 (of 170)/ 14 (of 170)/101 (of 170)block 127605491: The level of the
node (61328) is not correct, (1) expected
 the problem in the internal node occured (127605491), whole subtree is
skipped
/ 32 (of  34)/ 33 (of 170)/ 51 (of 170)/120 (of 170)block 166100880: The
level of the node (59985) is not correct, (1) expected
 the problem in the internal node occured (166100880), whole subtree is
skipped
finished                                            
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps
differs.
Bad nodes were found, Semantic pass skipped
25 found corruptions can be fixed only during --rebuild-tree
###########
reiserfsck finished at Thu Jul 24 11:03:56 2003
###########

And then for the next partition:

rep1:~/reiserfsprogs-3.6.5-pre2/fsck # ./reiserfsck --check /dev/sdb2

<-------------reiserfsck, 2002------------->
reiserfsprogs 3.6.5-pre2

  *************************************************************
  ** If you are using the latest reiserfsprogs and  it fails **
  ** please  email bug reports to reiserfs-list@namesys.com, **
  ** providing  as  much  information  as  possible --  your **
  ** hardware,  kernel,  patches,  settings,  all  reiserfsk **
  ** messages  (including version),  the reiserfsck logfile, **
  ** check  the  syslog file  for  any  related information. **
  ** If you would like advice on using this program, support **
  ** is available  for $25 at  www.namesys.com/support.html. **
  *************************************************************

Will read-only check consistency of the filesystem on /dev/sdb2
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
###########
reiserfsck --check started at Thu Jul 24 12:50:31 2003
###########
Replaying journal..
0 transactions replayed
Checking internal tree../  1 (of  38)/  1 (of 134)/ 14 (of 170)/122 (of
170)block 12586: The level of the node (0) is not correct, (1) expected
 the problem in the internal node occured (12586), whole subtree is
skipped
/ 16 (of 170)/149 (of 170)block 12955: The level of the node (0) is not
correct, (1) expected
 the problem in the internal node occured (12955), whole subtree is
skipped
/ 19 (of 170)/ 13 (of 170)block 13333: The level of the node (0) is not
correct, (1) expected
 the problem in the internal node occured (13333), whole subtree is
skipped
/ 27 (of 134)/136 (of 170)/ 10 (of 170)block 38189287: The level of the
node (33416) is not correct, (1) expected
 the problem in the internal node occured (38189287), whole subtree is
skipped
/110 (of 134)/ 82 (of 170)/ 25 (of 170)bad_indirect_item: block 344764:
The item (6856 1140155 0x1 IND (1), len 4, location 2096 entry count 0,
fsck need 0, format new) has the bad pointer (0) to the block
(19768492), which is in tree already
/ 30 (of  38)/132 (of 150)/ 35 (of 170)/ 20 (of 170)block 137322975: The
level of the node (2978) is not correct, (1) expected
 the problem in the internal node occured (137322975), whole subtree is
skipped
/ 31 (of  38)/ 93 (of 151)/ 85 (of 170)/ 40 (of 170)block 141041249: The
level of the node (18584) is not correct, (1) expected
 the problem in the internal node occured (141041249), whole subtree is
skipped
/ 36 (of  38)/ 83 (of 170)/167 (of 170)/168 (of 170)block 168706380: The
level of the node (7700) is not correct, (1) expected
 the problem in the internal node occured (168706380), whole subtree is
skipped
/ 37 (of  38)/ 64 (of  86)/ 51 (of 170)/ 63 (of 170)block 173878258: The
level of the node (0) is not correct, (1) expected
 the problem in the internal node occured (173878258), whole subtree is
skipped
/ 38 (of  38)/ 43 (of  85)/ 17 (of 170)/  5 (of 170)block 176139253: The
level of the node (14589) is not correct, (1) expected
 the problem in the internal node occured (176139253), whole subtree is
skipped
/ 44 (of  85)/ 37 (of 170)/ 81 (of 170)block 176178623: The level of the
node (19543) is not correct, (1) expected
 the problem in the internal node occured (176178623), whole subtree is
skipped
finished                               
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps
differs.
Bad nodes were found, Semantic pass skipped
10 found corruptions can be fixed only during --rebuild-tree
###########
reiserfsck finished at Thu Jul 24 22:37:40 2003
###########
rep1:~/reiserfsprogs-3.6.5-pre2/fsck # 

Re: quick question

[Yury Umanets]

On Fri, 2003-07-25 at 23:08, tim fitz wrote:
> Hi everyone,
> This is Tim Fitz over at iParadigms (www.turnitin.com). We've been doing
> some more playing with reiser and it seems to be running pretty well,
> but every now and then our Dell PERC card seems to throw a tantrum and
> kill the machine. Well either way, we have been happy for a few months
> but now we are in the hole again. The machine is up but on two of our
> partitions we have errors. 

> After running reiserfsck we got the messages
> below. I was wondering if there was any serious worries about trying to
> fix these errors with reiserfsprogs-3.6.10? Anything I should worry
> about? I know the --check happened with older utilities, but I just
> downloaded the 3.6.10... Anything I should worry about? Or is there any
> special thing I should do?

Hello,

I propose you make a backup first. Do you have spare drive of
partrition?

Then run lats fsck on backup in maner like the following:

reiserfsck --rebuild-tree /dev/sdb1

This should fix everything. And let us know the result.


-- 
We're flying high, we're watching the world passes by...

Quick Question

[Eliza via Containers]

www.tinyurl.com/ntxqn6e

Hi,

I don't want to take up too much of your time but I'm looking for people to
join me in a unique,
100% online based business opportunity that is totally FREE of charge to
check out.

If you are tired of working hard for pennies this might be what you've been
looking for.
You can actually start making money just by signing up.

All you need to do is to register, check it out and decide if you want to
join.
Please use my link below to check out the videos about the business and get
going and you can thank me later.

www.tinyurl.com/ntxqn6e

There's also this amazing competition that started right now on november
1st where you can get amazing prizes just by participating.
They're also giving away iPad PRO's to 10 lucky people if you check out
their facebook page for more information.

DO NOT MISS this opportunity to check this out for FREE. NO strings
attached.

Yours truly,

Eliza

www.tinyurl.com/ntxqn6e

Quick Question

[Larry]

Hey there,

Not sure if you got my last email but wanted to touch base again.
I was wondering if you wanted to try our email marketing and lead
generation solutions.
We can help to grow your business fast by using our services.
We have worked on a number of projects and campaigns, all our packages are
tailor made and designed
according to your requirements.

If you are interested, I would be more than happy to reach out with more
information
and develop a plan that works with your business type.

Thanks,
Larry
Contact: moriny@tom.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Quick Question

[Larry North]

Hey there,

Not sure if you got my last email but wanted to touch base again.
I was wondering if you wanted to try our email marketing and lead
generation solutions.
We can help to grow your business fast by using our services.
We have worked on a number of projects and campaigns, all our packages are
tailor made and designed
according to your requirements.

If you are interested, I would be more than happy to reach out with more
information
and develop a plan that works with your business type.

Thanks,
Larry
Contact: moriny-WVlzvzqoTvw@public.gmane.org

Quick Question

[Larry North]

Hey there,

Not sure if you got my last email but wanted to touch base again.
I was wondering if you wanted to try our email marketing and lead
generation solutions.
We can help to grow your business fast by using our services.
We have worked on a number of projects and campaigns, all our packages are
tailor made and designed
according to your requirements.

If you are interested, I would be more than happy to reach out with more
information
and develop a plan that works with your business type.

Thanks,
Larry
Contact: moriny@tom.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Quick Question

[Zach]

Hello,

I work for a leading digital marketing agency in Southern California that
focuses on helping small businesses advertise online.

 Our full service small business agency offers the following services and
products:

   1. Geography-Targeted Digital Advertising in the area(s) of your choice

   2. High-End Website Design and Development

   3. Banner Ads, Mobile Advertising

   4. Search Engine Optimization (SEO)

   5. Search Engine Advertising

   6. E-Commerce Solutions, iPhone, Android Apps Development.

If you are interested, I would be more than happy to reach out with more
information
and develop a plan that works with your business type.

PROFESSIONAL    TRUSTWORTHY    RELIABLE    QUALITY   SERVICE

Thanks & Regards,

Zach
Business Development Manager
Contact: maymay01@aliyun.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Quick Question

[Max Lucchetti]

I wanted to confirm that your product "Git" is free for the US government to use? If you cannot answer this question, would you know who could?

Thank you very much for your time,
Max Lucchetti

Re: Quick Question

[Junio C Hamano]

Max Lucchetti <mlucchetti@its.bldrdoc.gov> writes:

> I wanted to confirm that your product "Git" is free for the US
> government to use?

As far as _we_ are concerned, anybody should be able to use it for free
(as both in "libre" and in "gratis" sense); it is licensed under GPLv2 and
the copy of the license is found in COPYING file. Some part is licensed
under BSD license, but that shouldn't change the picture.

Having said that we are in no position of knowing if the branch of the US
goverment you work for has its own restriction regarding its software
procurement process (e.g. "It has to be produced by an ISO 14000 certified
facility").  So...

> If you cannot answer this question, would you know who could?

...if this is a legal inquiry, only _your_ lawyer can answer it.

RE: Quick Question

[Max Lucchetti]

Got it! Thanks again for your time.

-Max

-----Original Message-----
From: Junio C Hamano [mailto:gitster@pobox.com] 
Sent: Thursday, March 01, 2012 12:36 PM
To: Max Lucchetti
Cc: git@vger.kernel.org
Subject: Re: Quick Question

Max Lucchetti <mlucchetti@its.bldrdoc.gov> writes:

> I wanted to confirm that your product "Git" is free for the US 
> government to use?

As far as _we_ are concerned, anybody should be able to use it for free (as both in "libre" and in "gratis" sense); it is licensed under GPLv2 and the copy of the license is found in COPYING file. Some part is licensed under BSD license, but that shouldn't change the picture.

Having said that we are in no position of knowing if the branch of the US goverment you work for has its own restriction regarding its software procurement process (e.g. "It has to be produced by an ISO 14000 certified facility").  So...

> If you cannot answer this question, would you know who could?

...if this is a legal inquiry, only _your_ lawyer can answer it.

quick question...

[Evert Vorster]

Hi there.

Has anybody got a btrfs root filesystem that is running on a bare
block device? Would lilo be able to boot an initramfs that is living
on such a filesystem?

What I intend to do is to erase all the partitions off my system, make
a btrfs volume on /dev/sda, and then just use subvolumes in stead of
partitions.

Is this folly?

Would having an initramfs be a boon or a bane in this endeavour?

Would lilo writing to the mbr of a device that is claimed by btrfs
break the file system?

Do you need to have a partition table to have an MBR?

Thanks for any answers...

-Evert-

-- 
http://magnatune.com - Music shared the way it should be.

Re: quick question...

[C Anthony Risinger]

i'm not an expert, but ill do my best to answer.  replies interspersed below.

On Sun, Aug 8, 2010 at 8:57 PM, Evert Vorster <evorster@gmail.com> wrote:
> Hi there.
>
> Has anybody got a btrfs root filesystem that is running on a bare
> block device? Would lilo be able to boot an initramfs that is living
> on such a filesystem?

i haven't [ever] used lilo, but AFIAK no bootloader, with the
exception of maybe syslinux (extlinux), can boot from a btrfs device;
you won't have to worry about the initramfs, because the loader won't
even be able to find the kernel.  you'll need a boot partition with a
filesystem supported by the loader.

> What I intend to do is to erase all the partitions off my system, make
> a btrfs volume on /dev/sda, and then just use subvolumes in stead of
> partitions.
>
> Is this folly?

not at all.  this is what many of us would like to do, but we run into
the bootloader issues above.

> Would having an initramfs be a boon or a bane in this endeavour?

a non-issue, as the bootloader cannot even get the kernel (unless your
booting the kernel/initramfs from a different device...)

> Would lilo writing to the mbr of a device that is claimed by btrfs
> break the file system?

i don't think so, but i'm not sure.

> Do you need to have a partition table to have an MBR?

i just read about this recently.  IIRC, the partition table is within
the 512 byte MBR; it's a 64 byte section starting at byte 446.  so...
no :-)

C Anthony

Quick question

[Ioannis Aslanidis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I do not know if this is the proper place for this; however, neither on
IRC in #selinux on freenode nor in other places related to SELinux I was
able to get the appropriate help. I have also spent over a month reading
through documentation and googling around to find something similar to
what I needed, but to no avail.

I would like to know how to create a module or policy or modify the
current policy so that users of the system are:
1. Unable to list the /home directory
2. Unable to get into other users directory using SELinux rules
3. (optional) Be able to list /home, but be unable to see anything apart
from his home.

I have specific needs in my production environment which require these
specifications. Normal permissions are not an option in my environment,
because of shared permissions of nfs mounts.

Getting a template and working over it or converting deny rules to allow
rules is not an option for me, as I need to be able to understand and
allow others to understand the text and be able to easily maintainy and
modify it.

In order to prevent the users from getting any data in /etc/passwd I
plan to use PAM + LDAP or a similar solution.

I hope you can give me a hand with this.

Regards,

Ioannis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFIPEb6Fq+8w76sCAARArB0AKCTYt7EWWnjnhvx86wJDHj/NuUTLgCgrex7
RoyVndANCtwStrM+7+WsX5E=
=vSb3
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Quick question

[Stephen Smalley]

On Tue, 2008-05-27 at 19:38 +0200, Ioannis Aslanidis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> I do not know if this is the proper place for this; however, neither on
> IRC in #selinux on freenode nor in other places related to SELinux I was
> able to get the appropriate help. I have also spent over a month reading
> through documentation and googling around to find something similar to
> what I needed, but to no avail.
> 
> I would like to know how to create a module or policy or modify the
> current policy so that users of the system are:
> 1. Unable to list the /home directory
> 2. Unable to get into other users directory using SELinux rules
> 3. (optional) Be able to list /home, but be unable to see anything apart
> from his home.
> 
> I have specific needs in my production environment which require these
> specifications. Normal permissions are not an option in my environment,
> because of shared permissions of nfs mounts.
> 
> Getting a template and working over it or converting deny rules to allow
> rules is not an option for me, as I need to be able to understand and
> allow others to understand the text and be able to easily maintainy and
> modify it.
> 
> In order to prevent the users from getting any data in /etc/passwd I
> plan to use PAM + LDAP or a similar solution.
> 
> I hope you can give me a hand with this.

If I understand correctly, you want to provide separation on a per-user
basis (not just per-role) for NFS-mounted home directories.  I don't
think that is realistically supportable by SELinux today, as 1) SELinux
distinguishes based on security context/label, not uid, and 2) NFS
doesn't support file labeling yet.  Sounds more like a job for 'normal
permissions' i.e. discretionary access modes and/or ACLs.  There is
ongoing work to support file labeling in NFSv4, but it is still in
development, and even then, instantiating a separate role for every user
is going to be problematic for any large number of users.

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Quick question

[Ioannis Aslanidis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephen Smalley wrote:
> 
> If I understand correctly, you want to provide separation on a per-user
> basis (not just per-role) for NFS-mounted home directories.  I don't
> think that is realistically supportable by SELinux today, as 1) SELinux
> distinguishes based on security context/label, not uid, and 2) NFS
> doesn't support file labeling yet.  Sounds more like a job for 'normal
> permissions' i.e. discretionary access modes and/or ACLs.  There is
> ongoing work to support file labeling in NFSv4, but it is still in
> development, and even then, instantiating a separate role for every user
> is going to be problematic for any large number of users.
> 


And would there be a way to do something so that each user has a
different context? That is to say, I can assign a different context to
each user and have something easily maintained. Do you see that viable?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFIPE4SFq+8w76sCAARAjn1AJ9WOkv51PzZTueUkD8jCYAN1z/U8wCcDsyj
r2FnoXXpA0la49+Li2jAuK4=
=h8RH
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Quick question

[Stephen Smalley]

On Tue, 2008-05-27 at 20:08 +0200, Ioannis Aslanidis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Stephen Smalley wrote:
> > 
> > If I understand correctly, you want to provide separation on a per-user
> > basis (not just per-role) for NFS-mounted home directories.  I don't
> > think that is realistically supportable by SELinux today, as 1) SELinux
> > distinguishes based on security context/label, not uid, and 2) NFS
> > doesn't support file labeling yet.  Sounds more like a job for 'normal
> > permissions' i.e. discretionary access modes and/or ACLs.  There is
> > ongoing work to support file labeling in NFSv4, but it is still in
> > development, and even then, instantiating a separate role for every user
> > is going to be problematic for any large number of users.
> > 
> 
> 
> And would there be a way to do something so that each user has a
> different context? That is to say, I can assign a different context to
> each user and have something easily maintained. Do you see that viable?

It can be done (e.g. you can define a SELinux user in policy for each of
your users and then use a policy constraint on the user identity field
to enforce the separation, or you can define per-user roles in policy
and use the RBAC support), but I'm not sure how practical it is.  But
even if it were done, without labeling support in NFS, you can't use it
for NFS-mounted home directories (you are limited to a single context
per filesystem there at present).

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Quick question

[Ioannis Aslanidis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Understood. That changes a little the policy, but I could still create
one mount point per user inside his own home. That still leaves me with
the possibility of listing /home, which could be achieved by removing
the read flag on the directory on normal permission mode and so on, so I
guess SELinux wouldn't be needed in that case.

Thanks for your help. If you have any comments or proposals I am open to
them.

Thanks once again,

Ioannis

Stephen Smalley wrote:
> On Tue, 2008-05-27 at 20:08 +0200, Ioannis Aslanidis wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Stephen Smalley wrote:
>>> If I understand correctly, you want to provide separation on a per-user
>>> basis (not just per-role) for NFS-mounted home directories.  I don't
>>> think that is realistically supportable by SELinux today, as 1) SELinux
>>> distinguishes based on security context/label, not uid, and 2) NFS
>>> doesn't support file labeling yet.  Sounds more like a job for 'normal
>>> permissions' i.e. discretionary access modes and/or ACLs.  There is
>>> ongoing work to support file labeling in NFSv4, but it is still in
>>> development, and even then, instantiating a separate role for every user
>>> is going to be problematic for any large number of users.
>>>
>>
>> And would there be a way to do something so that each user has a
>> different context? That is to say, I can assign a different context to
>> each user and have something easily maintained. Do you see that viable?
> 
> It can be done (e.g. you can define a SELinux user in policy for each of
> your users and then use a policy constraint on the user identity field
> to enforce the separation, or you can define per-user roles in policy
> and use the RBAC support), but I'm not sure how practical it is.  But
> even if it were done, without labeling support in NFS, you can't use it
> for NFS-mounted home directories (you are limited to a single context
> per filesystem there at present).
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFIPF0zFq+8w76sCAARAmICAJ9BzLJdQv1f9tWKt9SbCXAES89FvACgswzB
GV7yhgfJEZCmxUlgpq/0U4g=
=CwtZ
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: Quick question

[Stephen Smalley]

On Tue, 2008-05-27 at 21:12 +0200, Ioannis Aslanidis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Understood. That changes a little the policy, but I could still create
> one mount point per user inside his own home.

I don't think so; you are limited to per-filesystem/superblock
granularity at present, not per-mount.  If you make multiple mounts from
the same filesystem on the server, they'll be labeled identically.
You'd need genuine labeled NFS support, which is yet to come (in
progress).

>  That still leaves me with
> the possibility of listing /home, which could be achieved by removing
> the read flag on the directory on normal permission mode and so on, so I
> guess SELinux wouldn't be needed in that case.
> 
> Thanks for your help. If you have any comments or proposals I am open to
> them.

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Quick question

[Radoslaw Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

How to display ignored files of the whole project using only core git?

I've tried:

git-ls-files -o -i -X .git/info/exclude

and it only showed me the excluded files in the current directory...

-- 
GPG Key id:  0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2

AstralStorm


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: Quick question

[Linus Torvalds]

On Mon, 13 Feb 2006, Radoslaw Szkodzinski wrote:
>
> How to display ignored files of the whole project using only core git?
> 
> I've tried:
> 
> git-ls-files -o -i -X .git/info/exclude
> 
> and it only showed me the excluded files in the current directory...

Well, since you're telling it to only show excluded files, it will also 
only show excluded directories.

Which is admittedly insane. You don't want to exclude directories. Or 
maybe you do, but then we should add the "/" to the end before we do the 
exclusion.

This patch (untested) will never exclude directories. Which may or may not 
be the right thing. 

Junio? Others? Comments?

		Linus

---
diff --git a/ls-files.c b/ls-files.c
index 7024cf1..b923f92 100644
--- a/ls-files.c
+++ b/ls-files.c
@@ -276,8 +276,6 @@ static void read_directory(const char *p
 				continue;
 			len = strlen(de->d_name);
 			memcpy(fullname + baselen, de->d_name, len+1);
-			if (excluded(fullname) != show_ignored)
-				continue;
 
 			switch (DTYPE(de)) {
 			struct stat st;
@@ -304,6 +302,8 @@ static void read_directory(const char *p
 			case DT_LNK:
 				break;
 			}
+			if (excluded(fullname) != show_ignored)
+				continue;
 			add_name(fullname, baselen + len);
 		}
 		closedir(dir);

Re: Quick question

[Radoslaw Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

Linus Torvalds wrote:
> 
> Well, since you're telling it to only show excluded files, it will also 
> only show excluded directories.
> 
> Which is admittedly insane. You don't want to exclude directories. Or 
> maybe you do, but then we should add the "/" to the end before we do the 
> exclusion.
> 
> This patch (untested) will never exclude directories. Which may or may not 
> be the right thing. 
> 
> Junio? Others? Comments?
> 

For me it seems to do the right thing, although I have no need to exclude directories.
If I really needed to, I'd say something like:

/excluded_dir/*

in .git/info/exclude, and it would show the files as being excluded.

-- 
GPG Key id:  0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2

AstralStorm


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: Quick question

[Alex Riesen]

Radoslaw Szkodzinski, Mon, Feb 13, 2006 19:26:03 +0100:
> Linus Torvalds wrote:
> > 
> > Well, since you're telling it to only show excluded files, it will also 
> > only show excluded directories.
> > 
> > Which is admittedly insane. You don't want to exclude directories. Or 
> > maybe you do, but then we should add the "/" to the end before we do the 
> > exclusion.
> > 
> > This patch (untested) will never exclude directories. Which may or may not 
> > be the right thing. 

I actually quiet like it how it is.

> > Junio? Others? Comments?
> > 
> 
> For me it seems to do the right thing, although I have no need to exclude directories.
> If I really needed to, I'd say something like:
> 
> /excluded_dir/*
> 
> in .git/info/exclude, and it would show the files as being excluded.
> 

What's wrong with .gitignore in the excluded_dir containing everything
you don't want to see, or even just "*"?

Re: Quick question

[Junio C Hamano]

Linus Torvalds <torvalds@osdl.org> writes:

> Which is admittedly insane. You don't want to exclude directories. Or 
> maybe you do, but then we should add the "/" to the end before we do the 
> exclusion.
>
> This patch (untested) will never exclude directories. Which may or may not 
> be the right thing. 
>
> Junio? Others? Comments?
>
> 		Linus

I might have sounded negative or happy with status quo in my
earlier messages but that was not intended.  I am swamped and
have not formed an opinion.

Re: Quick question

[Junio C Hamano]

Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl> writes:

> How to display ignored files of the whole project using only core git?
>
> I've tried:
>
> git-ls-files -o -i -X .git/info/exclude
>
> and it only showed me the excluded files in the current directory...

With the git.git repository itself, I tried:

$ cat /var/tmp/i
*.c
$ git ls-files -i -X /var/tmp/i | head -n 6
apply.c
arm/sha1.c
blob.c
cat-file.c
check-ref-format.c
checkout-index.c

So I am not sure what you mean.  You wanted to "display ignored
files of the whole project", right?  I am getting arm/sha1.c
here in my output, so I do not understand the issue here...

Re: Quick question

[Radoslaw Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Junio C Hamano wrote:
> With the git.git repository itself, I tried:
> 
> $ cat /var/tmp/i
> *.c
> $ git ls-files -i -X /var/tmp/i | head -n 6
> apply.c
> arm/sha1.c
> blob.c
> cat-file.c
> check-ref-format.c
> checkout-index.c
> 
> So I am not sure what you mean.  You wanted to "display ignored
> files of the whole project", right?  I am getting arm/sha1.c
> here in my output, so I do not understand the issue here...
> 

Wrong. I wanted to display files that are ignored and not checked in.
(unlike your example)

That's why I used the -o (--others).

Try your example with git repo's .gitignore and any .o file.
I would like to use it for backup~ hunting purposes in a script
and not have to worry about find and other less portable tools.

-- 
GPG Key id:  0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2

AstralStorm


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: Quick question

[Junio C Hamano]

Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl> writes:

> Wrong. I wanted to display files that are ignored and not checked in.
> (unlike your example)

Wow, you have a strong voice.

> That's why I used the -o (--others).

You asked it to show either ignored or others.


> I would like to use it for backup~ hunting purposes in a script
> and not have to worry about find and other less portable tools.

I usually do this for that:

	git ls-files -o '*~'

Re: Quick question

[Radoslaw Szkodzinski]

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

Junio C Hamano wrote:
> Wow, you have a strong voice.
>
I didn't want to sound rude at all, of course.

>> That's why I used the -o (--others).
> 
> You asked it to show either ignored or others.
> 

So here's the catch? I don't think so.
But the manpage isn't totally clear in this matter.

When I specify just -o, it gives me files which weren't ignored too.
-o -i gives me only ignored files.
Plain -i returns nothing.

With git directory, compare:
git-ls-files -o -i -X .gitignore

with:
git-ls-files -o

The remainder is:
git-ls-files -o -X .gitignore

I have the documentation built.
(Yes, I'm not including its .gitignore on purpose)

> 
>> I would like to use it for backup~ hunting purposes in a script
>> and not have to worry about find and other less portable tools.
> 
> I usually do this for that:
> 
> 	git ls-files -o '*~'
> 

Also good. I have *~ in ignored too, so I think -o -i will suffice.

-- 
GPG Key id:  0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2

AstralStorm


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Quick question.

[vlobanov]

Hi,

I have a quick question about a supposed scenario.

Suppose you have two pthreads - a main pthread and a utility pthread -
both running in the same application. The utility pthread is currently
in the middle of doing a recv() call on a network socket. At the same time,
the main pthread decides that it's time to exit, and either returns or
does a series of fork()/execv() calls. Is the behavior of the utility
pthread in such a case deterministic, and if so, what is it?

Thanks in advance for the help.

-Vadim Lobanov

Re: Quick question.

[John Richard Moser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I believe that terminating the thread executing main() terminates the
program.

vlobanov wrote:
| Hi,
|
| I have a quick question about a supposed scenario.
|
| Suppose you have two pthreads - a main pthread and a utility pthread -
| both running in the same application. The utility pthread is currently
| in the middle of doing a recv() call on a network socket. At the same
time,
| the main pthread decides that it's time to exit, and either returns or
| does a series of fork()/execv() calls. Is the behavior of the utility
| pthread in such a case deterministic, and if so, what is it?
|
| Thanks in advance for the help.
|
| -Vadim Lobanov
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at  http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at  http://www.tux.org/lkml/
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA8KFkhDd4aOud5P8RAgr6AJ9wxIQzbxQfsuucbVT/362Mjaz+NgCgjYYd
VCJKlbnXyAAjQhOlZeqypwM=
=Ys+h
-----END PGP SIGNATURE-----

Quick question

[Anand Eswaran]

Hi :

   Are there any particular flags for a page that I can use to check if a
given page is used by the slab-allocator or not.

Thanks a lot,
Anand.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

Re: Quick question

[Dave Hansen]

On Mon, 2004-02-23 at 19:14, Anand Eswaran wrote:
>    Are there any particular flags for a page that I can use to check if a
> given page is used by the slab-allocator or not.

#define PageSlab(page)          test_bit(PG_slab, &(page)->flags)
#define SetPageSlab(page)       set_bit(PG_slab, &(page)->flags)
#define ClearPageSlab(page)     clear_bit(PG_slab, &(page)->flags)
#define TestClearPageSlab(page) test_and_clear_bit(PG_slab, &(page)->flags)
#define TestSetPageSlab(page)   test_and_set_bit(PG_slab, &(page)->flags)

-- dave

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

quick question

[Stephen Brown]

Hi all,

what do you all think about this:

http://www.m-sys.com/content/products/product.asp?PID=17&FILE=DOCIdePro&FAM=
doc

if I used this as a standard IDE device does this mean that I wouldn't
require any MTD drivers for linux and just use the standard IDE?

if so could I format this as EXT2 fs and contain my ROOT file system on it?
or would I still run the risk of power failure disk error etc?

 I mean I can load my ROOT fs into memory so thats not a problem, see the
thing is at the moment I can't get the MTD drivers to work with the onboard
'Msys D-O-C' on an Ampro p5e module, reason being is Ampro use part of the
FLASH to store the bios for the ampro board and have specific tools for
formatting etc, so I boot from a dos partition using 'LoadLin' or I can boot
from a Harddrive connected to the IDE, so in my case maybe the 'IDE PRO' is
an alternative , also to save recompiling the kernel for the p5e maybe..

anyways let me know what you think,

kind regards

stephen


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Re: quick question

[David Woodhouse]

On Thu, 2003-06-26 at 12:00, Stephen Brown wrote:
> Hi all,
> 
> what do you all think about this:
> 
> http://www.m-sys.com/content/products/product.asp?PID=17&FILE=DOCIdePro&FAM=
> doc
> 
> if I used this as a standard IDE device does this mean that I wouldn't
> require any MTD drivers for linux and just use the standard IDE?
> 
> if so could I format this as EXT2 fs and contain my ROOT file system on it?
> or would I still run the risk of power failure disk error etc?

You'd want EXT3 not EXT2, presumably, but yes -- it should just work. 

You still have the same fundamental problem that you're running a
journalling file system atop a journalling pseudo-filesystem which
emulates a block device, but unlike the reports I've heard about most
CompactFlash devices, I'd expect that M-Systems have at least managed to
make the firmware within the device itself reliable w.r.t.
power-failure.

>  I mean I can load my ROOT fs into memory so thats not a problem, see the
> thing is at the moment I can't get the MTD drivers to work with the onboard
> 'Msys D-O-C' on an Ampro p5e module, reason being is Ampro use part of the
> FLASH to store the bios for the ampro board and have specific tools for
> formatting etc,

That's interesting... can you describe the problems? Precisely what type
of DiskOnChip is it, is it detected correctly by the hardware driver? Is
it only the NFTL code which is unhappy? etc. 

-- 
dwmw2

Re: quick question

[Stephen Brown]

hi,

its a DOC 2000 , onboard 8 MB, it resides on the p5e module, Ampro have
specifically changed the hardware to suit their SBC, which includes a bios
copy from eprom, they provide utility tools similar to the 'm-sys' ones,
except are specifically designed for Ampro, if you use the 'm-sys' tools the
SBC won't boot as 'im assuming' the bios cannot be copied from eprom as the
first bios screen wont load, this creates a DOS partition as well as a bios
area stored close to the boot sector.

1st problem is, compiling the kernel for the Ampro p5e module takes a good
half day!!
2nd problem, the preparation for a standard 'm-sys DOC' is not the same as
in the specific tools that are written for the p5e module.

I tried quite a few different kernel compiles ( include MTD - etc etc - also
tried the ones default with kernel 2.4.4 and the latest ones from web ) to
try and make the DOC compatible with the real-time linux kernel, recompiled
with RTLinux pre-1, but couldnt get it to work, this takes up a lot of time!
so.. i opted to load the RTLinux kernel and root filesystem from the DOS
partition, that resides on the p5e module, using 'loadlin' , this loads into
memory using initrd as the p5e module has 32 MB sdram,

the system is finished and I am happy with its performance but ...  looking
ahead into the future 'if' the hardware has to stay the same it would be
nice to have a non-volatile area so to store network information etc,
instead at the moment I can change on the fly, until I power down, or... I
can create a new ROOT filesystem (*.gz) , change a few scripts etc, for
permanent changes.

I cannot recompile the kernel for Red Hat 7.2 and RTLinux to include ext3
fs, so I have learned to live with it as ext2.

This is why I have an interest in the 'IDE PRO' if maybe it can provide a
solution via the IDE bus, without a lot more time consuming kernel
compiling, the other option was a seperate DOC from 'm-sys' that could
interface with our pc-104 stack which Im assuming would require me to
recompile the kernel, which in turn would have a knock on effect to my
development PC and all modules compiled for the target p5e etc etc... blah
blah...    i dont mind doing it but obviously an alternative would be better
, while we are tied with the current hardware..

kind regards

stephen
----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Stephen Brown" <sbrown@stirling-dynamics.com>
Cc: <linux-mtd@lists.infradead.org>
Sent: Thursday, June 26, 2003 12:06 PM
Subject: Re: quick question


> On Thu, 2003-06-26 at 12:00, Stephen Brown wrote:
> > Hi all,
> >
> > what do you all think about this:
> >
> >
http://www.m-sys.com/content/products/product.asp?PID=17&FILE=DOCIdePro&FAM=
> > doc
> >
> > if I used this as a standard IDE device does this mean that I wouldn't
> > require any MTD drivers for linux and just use the standard IDE?
> >
> > if so could I format this as EXT2 fs and contain my ROOT file system on
it?
> > or would I still run the risk of power failure disk error etc?
>
> You'd want EXT3 not EXT2, presumably, but yes -- it should just work.
>
> You still have the same fundamental problem that you're running a
> journalling file system atop a journalling pseudo-filesystem which
> emulates a block device, but unlike the reports I've heard about most
> CompactFlash devices, I'd expect that M-Systems have at least managed to
> make the firmware within the device itself reliable w.r.t.
> power-failure.
>
> >  I mean I can load my ROOT fs into memory so thats not a problem, see
the
> > thing is at the moment I can't get the MTD drivers to work with the
onboard
> > 'Msys D-O-C' on an Ampro p5e module, reason being is Ampro use part of
the
> > FLASH to store the bios for the ampro board and have specific tools for
> > formatting etc,
>
> That's interesting... can you describe the problems? Precisely what type
> of DiskOnChip is it, is it detected correctly by the hardware driver? Is
> it only the NFTL code which is unhappy? etc.
>
> --
> dwmw2
>
>
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star Internet. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________
>

----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Stephen Brown" <sbrown@stirling-dynamics.com>
Cc: <linux-mtd@lists.infradead.org>
Sent: Thursday, June 26, 2003 12:06 PM
Subject: Re: quick question


> On Thu, 2003-06-26 at 12:00, Stephen Brown wrote:
> > Hi all,
> >
> > what do you all think about this:
> >
> >
http://www.m-sys.com/content/products/product.asp?PID=17&FILE=DOCIdePro&FAM=
> > doc
> >
> > if I used this as a standard IDE device does this mean that I wouldn't
> > require any MTD drivers for linux and just use the standard IDE?
> >
> > if so could I format this as EXT2 fs and contain my ROOT file system on
it?
> > or would I still run the risk of power failure disk error etc?
>
> You'd want EXT3 not EXT2, presumably, but yes -- it should just work.
>
> You still have the same fundamental problem that you're running a
> journalling file system atop a journalling pseudo-filesystem which
> emulates a block device, but unlike the reports I've heard about most
> CompactFlash devices, I'd expect that M-Systems have at least managed to
> make the firmware within the device itself reliable w.r.t.
> power-failure.
>
> >  I mean I can load my ROOT fs into memory so thats not a problem, see
the
> > thing is at the moment I can't get the MTD drivers to work with the
onboard
> > 'Msys D-O-C' on an Ampro p5e module, reason being is Ampro use part of
the
> > FLASH to store the bios for the ampro board and have specific tools for
> > formatting etc,
>
> That's interesting... can you describe the problems? Precisely what type
> of DiskOnChip is it, is it detected correctly by the hardware driver? Is
> it only the NFTL code which is unhappy? etc.
>
> --
> dwmw2
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star Internet. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________
>


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Re: quick question

[David Woodhouse]

Weird -- what did you do different between your reply directly to me
(which had correct References: headers) and your reply to the list
(which didn't, hence got rejected)? 

(... and then what did you do differently in your _second_ reply to the
list, which worked?)

Had you deleted the mail to which you're replying, or changed folders
and were no longer looking at the same folder, or something?

You're using Outlook and Exchange, right?

On Thu, 2003-06-26 at 13:01, Stephen Brown wrote:
> hi,
> 
> its a DOC 2000 , onboard 8 MB, it resides on the p5e module, Ampro have
> specifically changed the hardware to suit their SBC, which includes a bios
> copy from eprom, they provide utility tools similar to the 'm-sys' ones,
> except are specifically designed for Ampro, if you use the 'm-sys' tools the
> SBC won't boot as 'im assuming' the bios cannot be copied from eprom as the
> first bios screen wont load, this creates a DOS partition as well as a bios
> area stored close to the boot sector.
> 
> 1st problem is, compiling the kernel for the Ampro p5e module takes a good
> half day!!

Weird -- why? Are you building on the board itself and starting from
'make clean' each time? 

You ought to be able to make just the MTD and DiskOnChip modules to
match the kernel you're running, and shouldn't even need to reboot to
test them.

> 2nd problem, the preparation for a standard 'm-sys DOC' is not the same as
> in the specific tools that are written for the p5e module.

Interesting. Do you know what _address_ you tell the p5e DFORMAT utility
to find the DiskOnChip at? Or what address it finds it at?

> I tried quite a few different kernel compiles ( include MTD - etc etc - also
> tried the ones default with kernel 2.4.4 and the latest ones from web ) to
> try and make the DOC compatible with the real-time linux kernel, recompiled
> with RTLinux pre-1, but couldnt get it to work, this takes up a lot of time!

Can you remember details? Did the hardware driver manage to detect the
DiskOnChip and report its presence? Was it only a problem with the
_contents_ of the DiskOnChip?

> I cannot recompile the kernel for Red Hat 7.2 and RTLinux to include ext3
> fs, so I have learned to live with it as ext2.

Why so?

-- 
dwmw2

Re: Quick question

[David Stuart]

On Tue, 2003-06-03 at 09:18, Paul Davis wrote:

> its also very unclear what you want help with. there is nothing
> particularly different about capture and playback on 2 devices
> compared to doing it on just 1.

Ah, I think you misunderstand me a little bit.. it's not that I am
trying to do anything different than usual, it's that I'm having trouble
with the basics. Specifically, the HOW-TOs that I have found all seem to
have a different way of writing and reading to/from the hardware buffer.
I have not, as of yet, been able to find a clear description of the core
concepts around writing and reading to the device. Also some recommend
one way, and then another HOWTO says not to do it that way.. it's all
rather confusing.

For instance, I'm really not sure what size my buffer needs to be, if
there is a difference between the "hardware buffer" and the buffer in my
program, How "periods" work into all this, what's the difference between
hw and plughw, etc. Also each of the examples seems to configure the
hardware differently, which I find also odd..

So to sum it up, the problem is not only that I'm new to ALSA, but that
I'm new to sound programming in general. Is there somewhere I can go to
learn the basics (at least enough to do capture and playback, beyond
that I'm not as interested)?


-- 
David Stuart, SIPQuest
phone: 254-8886 x234 web: http://www.sipquest.com/



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Re: Quick question

[Paul Davis]

>Ah, I think you misunderstand me a little bit.. it's not that I am
>trying to do anything different than usual, it's that I'm having trouble
>with the basics. Specifically, the HOW-TOs that I have found all seem to
>have a different way of writing and reading to/from the hardware buffer.

thats because there are multiple ways to do it.

>I have not, as of yet, been able to find a clear description of the core
>concepts around writing and reading to the device. Also some recommend
>one way, and then another HOWTO says not to do it that way.. it's all
>rather confusing.

if you want something that's not confusing, then JACK is your
friend. it was specifically designed to cut away all the complexity
and force you to write a well-designed application (and yes, its me
who gets to define what well-designed means :)

and no, you don't need to modify anything about your stock RH system
to use JACK. the modifications are only needed if you want low
latency, and such modifications would be needed to get this with just
ALSA anyway. a jack client will run just as well as a native ALSA
(better in some senses) when the jack server is run with equivalent
parameters for the audio hardware.

>For instance, I'm really not sure what size my buffer needs to be, if
>there is a difference between the "hardware buffer" and the buffer in my
>program, How "periods" work into all this, what's the difference between
>hw and plughw, etc. Also each of the examples seems to configure the
>hardware differently, which I find also odd..

there are many ways of doing this too.

>So to sum it up, the problem is not only that I'm new to ALSA, but that
>I'm new to sound programming in general. Is there somewhere I can go to
>learn the basics (at least enough to do capture and playback, beyond
>that I'm not as interested)?

if you're trying to learn sound programming, the last thing you want
to be messing with is a hardware abstraction layer that can handle any
audio h/w you can imagine. do yourself a favor and use jack
instead. you can focus on audio programming rather than how to setup
an audio interface. better yet, your application will talk to other
jack-enabled applications if and when you want to.

--p




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Quick question

[Jan Depner]

David,

	I don't know that much about the internals of JACK but I do know this -
all serious Linux sound apps either use or are preparing to use JACK. 
I've gotten to the point where I look for that in an application.  If
it's not JACK enabled I just move on to something else.

Jan


On Tue, 2003-06-03 at 19:38, Paul Davis wrote:
> >Ah, I think you misunderstand me a little bit.. it's not that I am
> >trying to do anything different than usual, it's that I'm having trouble
> >with the basics. Specifically, the HOW-TOs that I have found all seem to
> >have a different way of writing and reading to/from the hardware buffer.
> 
> thats because there are multiple ways to do it.
> 
> >I have not, as of yet, been able to find a clear description of the core
> >concepts around writing and reading to the device. Also some recommend
> >one way, and then another HOWTO says not to do it that way.. it's all
> >rather confusing.
> 
> if you want something that's not confusing, then JACK is your
> friend. it was specifically designed to cut away all the complexity
> and force you to write a well-designed application (and yes, its me
> who gets to define what well-designed means :)
> 
> and no, you don't need to modify anything about your stock RH system
> to use JACK. the modifications are only needed if you want low
> latency, and such modifications would be needed to get this with just
> ALSA anyway. a jack client will run just as well as a native ALSA
> (better in some senses) when the jack server is run with equivalent
> parameters for the audio hardware.
> 
> >For instance, I'm really not sure what size my buffer needs to be, if
> >there is a difference between the "hardware buffer" and the buffer in my
> >program, How "periods" work into all this, what's the difference between
> >hw and plughw, etc. Also each of the examples seems to configure the
> >hardware differently, which I find also odd..
> 
> there are many ways of doing this too.
> 
> >So to sum it up, the problem is not only that I'm new to ALSA, but that
> >I'm new to sound programming in general. Is there somewhere I can go to
> >learn the basics (at least enough to do capture and playback, beyond
> >that I'm not as interested)?
> 
> if you're trying to learn sound programming, the last thing you want
> to be messing with is a hardware abstraction layer that can handle any
> audio h/w you can imagine. do yourself a favor and use jack
> instead. you can focus on audio programming rather than how to setup
> an audio interface. better yet, your application will talk to other
> jack-enabled applications if and when you want to.
> 
> --p
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Quick question

[jfm3]

> and no, you don't need to modify anything about your stock RH system to
> use JACK. the modifications are only needed if you want low
> latency, and such modifications would be needed to get this with just
> ALSA anyway. a jack client will run just as well as a native ALSA
> (better in some senses) when the jack server is run with equivalent
> parameters for the audio hardware.

Not only that, but there's Planet CCRMA, which allows you to make
automated RPM package updates to your stock RH (like up2date or
red-carpet, but cooler) that give you the low latency kernel, precompiled
ALSA drivers, and enough Jack apps to keep you busy for quite some time.

Jack is so great, many developers on this list have named their children
after it. Do the right thing.

(jfm3)




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Quick question

[David Stuart]

jfm3@ouroboros-complex.org wrote:

>Jack is so great, many developers on this list have named their children
>after it. Do the right thing.
>

LOL! That's a good one! David, meet Jack. David, Jack. David, Jack. ... 
"Is your name not Jack?" .. "no" ..."that's going to cause a little 
confusion, mind if we call you Jack, just to keep it clear?"

Well OK, I guess all of the lobbying here (in the ALSA-dev mailing list 
of all places) has convinced me that JACK is indeed the way to go. At 
the very least I could suggest that our customers install the CCRMA on 
top of their RedHat platform..

My only complaint with the CCRMA stuff is that it forces them to install 
apt-get, which is not really sound related, and not packaged with RedHat 
by default. But apart from that (which is indeed a very minor beef) it 
seems like a great idea to have a low-latency pre-packaged solution. 
Certainly this is a lot easier than telling them how to patch their 
kernel, etc.

I guess this means that I will have to start reading JACK documentation 
in earnest. I trust that there is such a thing.. ;)





-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Quick question

[Paul Davis]

>I guess this means that I will have to start reading JACK documentation 
>in earnest. I trust that there is such a thing.. ;)

there is reference documentation generated by docbook using jack.h.
there is also a directory full of working example clients that you can
copy and modify to do whatever you want.


-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Quick question

[David Stuart]

Does anyone have a short example of capturing from one device and doing
a playback (of the captured data) on another?

-- 
David Stuart, SIPQuest
phone: 254-8886 x234 web: http://www.sipquest.com/



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Re: Quick question

[David Stuart]

Apparently the ALSA community is too busy to answer my little questions,
this is the sadly the 3rd or 4th time I has posted to this list with no
answer. :(

I don't think my question is too difficult. All I'm asking for is a
little help! Either a small snippet or a pointer to some other
information.. Maybe my question is too newbie-ish, but you can't develop
new experts without said experts being newbies at one time.


On Mon, 2003-06-02 at 16:01, David Stuart wrote:
> Does anyone have a short example of capturing from one device and doing
> a playback (of the captured data) on another?

-- 
David Stuart, SIPQuest
phone: 254-8886 x234 web: http://www.sipquest.com/



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Re: Quick question

[Patrick Shirkey]

David Stuart wrote:
> Apparently the ALSA community is too busy to answer my little questions,
> this is the sadly the 3rd or 4th time I has posted to this list with no
> answer. :(
> 
> I don't think my question is too difficult. All I'm asking for is a
> little help! Either a small snippet or a pointer to some other
> information.. Maybe my question is too newbie-ish, but you can't develop
> new experts without said experts being newbies at one time.
> 
> 
> On Mon, 2003-06-02 at 16:01, David Stuart wrote:
> 
>>Does anyone have a short example of capturing from one device and doing
>>a playback (of the captured data) on another?
> 
> 

Check out ecasound. It can do this quite easily apparently.



-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Re: Quick question

[Paul Davis]

>I don't think my question is too difficult. All I'm asking for is a
>little help! Either a small snippet or a pointer to some other
>information.. Maybe my question is too newbie-ish, but you can't develop
>new experts without said experts being newbies at one time.

its not a little question. its something that is not done very often
at all. in fact, i don't know of a single piece of code that does it,
although theoretically the most recent version of JACK could do so,
since it allows different PCM device names for playback and
capture. its hardly a "simple example" however.

its also very unclear what you want help with. there is nothing
particularly different about capture and playback on 2 devices
compared to doing it on just 1.







-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Re: Quick question

[David E. Storey]

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

Well, I would have answered your question, but I personally don't have
the answers you seek. For starters, I wouldn't use alsa for doing such
things. I'd use Jack. <http://jackit.sf.net/> It's so much more
flexible, powerful and easier to code for than straight alsa.

Having said that, your question involved using TWO devices, which I
believe jack doesn't really support unless you're "bonding" them a la
your .asoundrc file. (and even then, you'd really want to syncronize
their clocks which most, if not all, consumer products don't support.)
Assuming you don't care about clock synchronization, you could follow
the examples at <http://www.suse.de/~mana/alsa090_howto.html>. Just open
up one device for capture and the other for playback. When you receive
data from one, pass it to the other.

(and reading Paul's recent post on jack, apparently you can do what you
want to do with jack.)

d!

On Tue, 2003-06-03 at 09:05, David Stuart wrote:
> Apparently the ALSA community is too busy to answer my little questions,
> this is the sadly the 3rd or 4th time I has posted to this list with no
> answer. :(
> 
> I don't think my question is too difficult. All I'm asking for is a
> little help! Either a small snippet or a pointer to some other
> information.. Maybe my question is too newbie-ish, but you can't develop
> new experts without said experts being newbies at one time.
> 
> 
> On Mon, 2003-06-02 at 16:01, David Stuart wrote:
> > Does anyone have a short example of capturing from one device and doing
> > a playback (of the captured data) on another?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Quick question

[David Stuart]

Ah! I do exist! :)

Perhaps a better description of what I'm trying to do is in order. I
don't know if anyone here is familiar with JMF (java media framework),
but I would like to create an ALSA capture plugin on Linux very similar
to the "direct sound" one that's available on the Windows platform.

When I said that I would like to capture and then playback on TWO
devices, in reality they will probably be always the SAME device (in
full duplex mode). Hopefully that makes the problem easier. This small
test program was my way of getting started.

I realize that JACK is probably the wave of the future in this respect,
but I was thinking of using ALSA because:

1) It's relatively easy to install (from rpms anyway)
2) One does not have to tinker too much with a default RedHat (our
"tested" distro) installation to use ALSA.
3) It has good full-duplex support, as opposed to the default OSS setup.
4) JACK is the future, but not yet the present (seems to me)

Although I admittedly haven't tried JACK yet, I was suspecting that
using ALSA directly would require our customers to do less customization
of their default RedHat installation than installing ALSA + JACK. I need
to keep the procedure simple because we will have to support them.


On Tue, 2003-06-03 at 09:25, David E. Storey wrote:
> Having said that, your question involved using TWO devices, which I
> believe jack doesn't really support unless you're "bonding" them a la
> your .asoundrc file. (and even then, you'd really want to syncronize
> their clocks which most, if not all, consumer products don't support.)
> Assuming you don't care about clock synchronization, you could follow
> the examples at <http://www.suse.de/~mana/alsa090_howto.html>. Just open
> up one device for capture and the other for playback. When you receive
> data from one, pass it to the other.

Hmm .. I did find this HOWTO once before (and a few others), and tried
to follow them, but I must be doing something wrong because I can't get
more than a few pops out of my playback device. I was hoping that
someone could either tell me what I was doing wrong in my program, or
provide a small working example that I could use to learn from..


-- 
David Stuart, SIPQuest
phone: 254-8886 x234 web: http://www.sipquest.com/



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

RE: Quick question

[Mark Knecht]

> -----Original Message-----
> From: alsa-devel-admin@lists.sourceforge.net
> [mailto:alsa-devel-admin@lists.sourceforge.net]On Behalf Of David Stuart
> Sent: Tuesday, June 03, 2003 6:53 AM
> To: David E. Storey
> Cc: alsa
> Subject: Re: [Alsa-devel] Quick question
>
>
> Ah! I do exist! :)
>
<SNIP>
>
> 1) It's relatively easy to install (from rpms anyway)
> 2) One does not have to tinker too much with a default RedHat (our
> "tested" distro) installation to use ALSA.
> 3) It has good full-duplex support, as opposed to the default OSS setup.
> 4) JACK is the future, but not yet the present (seems to me)
<SNIP>

Hi,
Since you're on Redhat, you can install Alsa and Jack very easily using the
PlanetCCRMA flow in less than an hour. Check it out if you're interested.

Cheers,
Mark




-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Quick question...

[Adam K Kirchhoff]

Can anyone fill me in on what cards support hardware mixing and if it's
supported in the Alsa drivers?

I know, for example, that the SB Live! and Audigy support it, as do the
drivers.  And the ymfpci driver supports it for the Yamaha cards.

Are there others?

Adam



----------------------------------------------------------------------------
                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

Re: Quick question...

[Takashi Iwai]

At Wed, 19 Jun 2002 13:01:22 -0400 (EDT),
Adam K Kirchhoff wrote:
> 
> 
> Can anyone fill me in on what cards support hardware mixing and if it's
> supported in the Alsa drivers?
> 
> I know, for example, that the SB Live! and Audigy support it, as do the
> drivers.  And the ymfpci driver supports it for the Yamaha cards.
> 
> Are there others?

trident
ali5451
es1968
maestro3 (up to 2 streams)
gus (on gf1 pcm stream)


Takashi


-------------------------------------------------------
                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

Quick Question

[Mike Atlas]

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Hello Everyone. I hope you all can help me, I'm sure you can (it seems like
a pretty simple problem).

I am setting up a Squid proxy server to run in transparent mode. To do this,
I need to forward all port 80 and 443 traffic to squids' port, 3128.
Additionally, I would like all other traffic on all other ports to forward
on to the router.

I have found a script to forward port 80 to squid (note: eth1 is my internal
interface, eth0 is external):

iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j
REDIRECT --to-port 3128

I assume I can run the same line for 443:

iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j
REDIRECT --to-port 3128


However, what can I use to forward EVERYTHING that is not port 80 out of the
eth0 interface, to our router (192.168.0.2)?
I know it has something to do with --dport ! 80, but I can't figure it out.

Thanks for your help.
BTW, this is RedHat 72. if that makes any difference. Linux kernel 2.4.9-31.

-mike
______________________________________________
Mike Atlas                          703.385.8362(v)
Senior System Engineer    703.385.3674(f)
Vista Innovation                www.vistainnovation.com


[-- Attachment #2: Type: text/html, Size: 3850 bytes --]

Re: Quick Question

[Antony Stone]

On Thursday 30 May 2002 9:17 pm, Mike Atlas wrote:

> I am setting up a Squid proxy server to run in transparent mode. To do
> this, I need to forward all port 80 and 443 traffic to squids' port, 3128.
> Additionally, I would like all other traffic on all other ports to forward
> on to the router.
>
> I have found a script to forward port 80 to squid (note: eth1 is my
> internal interface, eth0 is external):
>
> iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j
> REDIRECT --to-port 3128

Yes.   REDIRECT is used only when you are not changing the IP address, and 
you are changing the port number (ie the packet remains addressed to the same 
machine).

To change the address of the machine it's going to, you use DNAT:

iptables -A PREROUTING -t nat -i eth1 -d a.b.c.d -j DNAT --to 192.168.0.2

where a.b.c.d is the IP address of eth1 on the firewall.

That rule as I've written it will send *everything* addressed from the 
internal network to the firewall, on to the router on 192.168.0.2 (and it 
will send the replies back again).

No need to specify --dport ! 80; just put this rule after the one you wrote 
above, and the DNAT rule will only get used if the REDIRECT didn't.

You can put a '-p tcp' etc into the rule if you only mean to send TCP packets 
on to the router, or whatever.



Antony.

Re: Quick Question

[Ramin Alidousti]

On Thu, May 30, 2002 at 09:31:47PM +0100, Antony Stone wrote:

> On Thursday 30 May 2002 9:17 pm, Mike Atlas wrote:
> 
> > I am setting up a Squid proxy server to run in transparent mode. To do
> > this, I need to forward all port 80 and 443 traffic to squids' port, 3128.
> > Additionally, I would like all other traffic on all other ports to forward
> > on to the router.
> >
> > I have found a script to forward port 80 to squid (note: eth1 is my
> > internal interface, eth0 is external):
> >
> > iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j
> > REDIRECT --to-port 3128
> 
> Yes.   REDIRECT is used only when you are not changing the IP address, and 
> you are changing the port number (ie the packet remains addressed to the same 
> machine).

Not completely correct, Antony ;-) From the HowTo:

There is a specialized case of Destination NAT called redirection: it is
a simple convenience which is exactly equivalent to doing DNAT to the address
of the incoming interface.

Ramin

> 
> To change the address of the machine it's going to, you use DNAT:
> 
> iptables -A PREROUTING -t nat -i eth1 -d a.b.c.d -j DNAT --to 192.168.0.2
> 
> where a.b.c.d is the IP address of eth1 on the firewall.
> 
> That rule as I've written it will send *everything* addressed from the 
> internal network to the firewall, on to the router on 192.168.0.2 (and it 
> will send the replies back again).
> 
> No need to specify --dport ! 80; just put this rule after the one you wrote 
> above, and the DNAT rule will only get used if the REDIRECT didn't.
> 
> You can put a '-p tcp' etc into the rule if you only mean to send TCP packets 
> on to the router, or whatever.
> 
> 
> 
> Antony.

Re: Quick Question

[Antony Stone]

On Thursday 30 May 2002 9:54 pm, Ramin Alidousti wrote:

> There is a specialized case of Destination NAT called redirection: it is
> a simple convenience which is exactly equivalent to doing DNAT to the
> address of the incoming interface.

Oh.   So REDIRECT is a sort of "grab all packets and make it look like they 
were addressed to me" then ?   Like the opposite of MASQUERADE, really ?

(With an optional change to the port number along the way...)


Antony.

RE: Quick Question

[Joe Patterson]

[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]

One quick note:  This will not work for port 443.  squid can only
transparently proxy for normal http traffic.  If you want to deal with
https, you have two choices: either snat/masq/route the connection,
bypassing squid entirely (which cuts out some squid overhead and can be done
transparently) or tell the browser to use the the squid box on port 3128 to
proxy for https traffic (which I believe gives you somewhat nicer logging
and ACL-ability).  When a browser is configured to use a proxy server for
https it makes the connection to the proxy, issues a command something like
CONNECT server:port (I'm not sure of the syntax) and then treats that like a
tcp connection to the server it's trying to get in touch with (starting up
ssl and such).  If it's not configured to use a proxy, then it just makes
the tcp connection to the destination server on 443, and starts up ssl
immediately.  A proxy can't intercept that transparently.

-Joe
  -----Original Message-----
  From: netfilter-admin@lists.samba.org
[mailto:netfilter-admin@lists.samba.org]On Behalf Of Mike Atlas
  Sent: Thursday, May 30, 2002 4:18 PM
  To: netfilter@lists.samba.org
  Subject: Quick Question


  Hello Everyone. I hope you all can help me, I'm sure you can (it seems
like a pretty simple problem).

  I am setting up a Squid proxy server to run in transparent mode. To do
this, I need to forward all port 80 and 443 traffic to squids' port, 3128.
Additionally, I would like all other traffic on all other ports to forward
on to the router.

  I have found a script to forward port 80 to squid (note: eth1 is my
internal interface, eth0 is external):

  iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j
REDIRECT --to-port 3128

  I assume I can run the same line for 443:

  iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j
REDIRECT --to-port 3128


  However, what can I use to forward EVERYTHING that is not port 80 out of
the eth0 interface, to our router (192.168.0.2)?
  I know it has something to do with --dport ! 80, but I can't figure it
out.

  Thanks for your help.
  BTW, this is RedHat 72. if that makes any difference. Linux kernel
2.4.9-31.

  -mike
  ______________________________________________
  Mike Atlas                          703.385.8362(v)
  Senior System Engineer    703.385.3674(f)
  Vista Innovation                www.vistainnovation.com



[-- Attachment #2: Type: text/html, Size: 5777 bytes --]

RE: Quick Question

[Mike Atlas]

[-- Attachment #1: Type: text/plain, Size: 2734 bytes --]

Okay, cool. I will not add this to the iptables rule, and just have it
connect without going through squid...
-mike
  -----Original Message-----
  From: Joe Patterson [mailto:jpatterson@asgardgroup.com]
  Sent: Thursday, May 30, 2002 5:51 PM
  To: Mike Atlas; netfilter@lists.samba.org
  Subject: RE: Quick Question


  One quick note:  This will not work for port 443.  squid can only
transparently proxy for normal http traffic.  If you want to deal with
https, you have two choices: either snat/masq/route the connection,
bypassing squid entirely (which cuts out some squid overhead and can be done
transparently) or tell the browser to use the the squid box on port 3128 to
proxy for https traffic (which I believe gives you somewhat nicer logging
and ACL-ability).  When a browser is configured to use a proxy server for
https it makes the connection to the proxy, issues a command something like
CONNECT server:port (I'm not sure of the syntax) and then treats that like a
tcp connection to the server it's trying to get in touch with (starting up
ssl and such).  If it's not configured to use a proxy, then it just makes
the tcp connection to the destination server on 443, and starts up ssl
immediately.  A proxy can't intercept that transparently.

  -Joe
    -----Original Message-----
    From: netfilter-admin@lists.samba.org
[mailto:netfilter-admin@lists.samba.org]On Behalf Of Mike Atlas
    Sent: Thursday, May 30, 2002 4:18 PM
    To: netfilter@lists.samba.org
    Subject: Quick Question


    Hello Everyone. I hope you all can help me, I'm sure you can (it seems
like a pretty simple problem).

    I am setting up a Squid proxy server to run in transparent mode. To do
this, I need to forward all port 80 and 443 traffic to squids' port, 3128.
Additionally, I would like all other traffic on all other ports to forward
on to the router.

    I have found a script to forward port 80 to squid (note: eth1 is my
internal interface, eth0 is external):

    iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j
REDIRECT --to-port 3128

    I assume I can run the same line for 443:

    iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j
REDIRECT --to-port 3128


    However, what can I use to forward EVERYTHING that is not port 80 out of
the eth0 interface, to our router (192.168.0.2)?
    I know it has something to do with --dport ! 80, but I can't figure it
out.

    Thanks for your help.
    BTW, this is RedHat 72. if that makes any difference. Linux kernel
2.4.9-31.

    -mike
    ______________________________________________
    Mike Atlas                          703.385.8362(v)
    Senior System Engineer    703.385.3674(f)
    Vista Innovation                www.vistainnovation.com


[-- Attachment #2: Type: text/html, Size: 6676 bytes --]

Quick Question

[Mike Atlas]

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Hello Everyone. I hope you all can help me, I'm sure you can (it seems like
a pretty simple problem).

I am setting up a Squid proxy server to run in transparent mode. To do this,
I need to forward all port 80 and 443 traffic to squids' port, 3128.
Additionally, I would like all other traffic on all other ports to forward
on to the router.

I have found a script to forward port 80 to squid (note: eth1 is my internal
interface, eth0 is external):

iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j
REDIRECT --to-port 3128

I assume I can run the same line for 443:

iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j
REDIRECT --to-port 3128


However, what can I use to forward EVERYTHING that is not port 80 out of the
eth0 interface, to our router (192.168.0.2)?
I know it has something to do with --dport ! 80, but I can't figure it out.

Thanks for your help.
BTW, this is RedHat 72. if that makes any difference. Linux kernel
2.4.9-31.

-mike
______________________________________________
Mike Atlas                          703.385.8362(v)
Senior System Engineer    703.385.3674(f)
Vista Innovation                www.vistainnovation.com


[-- Attachment #2: Type: text/html, Size: 3838 bytes --]

RE: Quick Question

[Aldo S. Lagana]

[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]

It is fairly easy - 
 
The redirect to squid is done in the PREROUTING chain and
SNAT is done in POSTROUTING...
 
so if it is port 80 it will get picked up first, otherwise it will be
SNAT'ted in the POSTROUTING chain:
 
iptables -t nat -A PREROUTING -i $INTERNAL_INTERFACE -p tcp --dport 80
-j REDIRECT --to-port 3128
 
iptables -t nat -A POSTROUTING -o $INTERNET_INTERFACE -j SNAT
--to-source $INTERNET_IP


-----Original Message-----
From: netfilter-admin@lists.samba.org
[mailto:netfilter-admin@lists.samba.org] On Behalf Of Mike Atlas
Sent: Thursday, May 30, 2002 4:10 PM
To: netfilter@lists.samba.org
Subject: Quick Question


Hello Everyone. I hope you all can help me, I'm sure you can (it seems
like a pretty simple problem).
 
I am setting up a Squid proxy server to run in transparent mode. To do
this, I need to forward all port 80 and 443 traffic to squids' port,
3128. Additionally, I would like all other traffic on all other ports to
forward on to the router. 
 
I have found a script to forward port 80 to squid (note: eth1 is my
internal interface, eth0 is external):
 
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j REDIRECT
--to-port 3128
 
I assume I can run the same line for 443:
 
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j REDIRECT
--to-port 3128
 
 
However, what can I use to forward EVERYTHING that is not port 80 out of
the eth0 interface, to our router (192.168.0.2)?
I know it has something to do with --dport ! 80, but I can't figure it
out.
 
Thanks for your help.
BTW, this is RedHat 72. if that makes any difference. Linux kernel
2.4.9-31.
 
-mike

______________________________________________
Mike Atlas                          703.385.8362(v)
Senior System Engineer    703.385.3674(f)
Vista Innovation                www.vistainnovation.com 

 


[-- Attachment #2: Type: text/html, Size: 5940 bytes --]

Quick Question

[rclarke2]

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

TO: linux-mips@oss.sgi.com
I hope I'm contacting the right person here. My name is Randell Clarke and I wanted to ask if you were looking for any equipment, new or used, for either yourself or for your customers that I might help finance. My company, Preferred Lease, does anything from company vehicles, to printing and industrial equipment, to construction equipment and heavy machinery, to computers, software and furniture-- basically anything you can use for your business, and work with the "tough credits" that a lot of banks and financial companies do not want to spend time on, in addition to the "A" credits. Please give me a call or e-mail me if there's anything on the agenda/wishlist in the next couple months or if you had any questions or just wanted a quick quote. I thank you for your time.

Best Regards,

Randell Clarke
Sales Manager
Preferred Lease, A CapitalWerks Company
Direct Line- (949) 270-2170
Direct Fax - (949) 270-2171
rclarke2@preferredlease.com
www.preferredlease.com
www.capitalwerks.com

RE: Quick question.

[Gareth Williams]

Hi David.

Thankyou for the advice you gave me earlier last week.

I wonder if you would take a couple of minutes to look over the following
message the kernel gave me on booting and give your advice.

I managed to finally get the 2.4.12 linux kernel configured & compiled,
after much pratting about with upgrades to gcc & bin utils etc, here is my
kernel config which I specified for the MTD stuff:

(where I have not listed something then I have not included that in the
kernel build)

* Mem tech device support
* NFTL support
* Write support for NFTL (BETA)
NOTE: Mapping drivers for chip access menu has NO SUBMENU!! (pressing enter
on it has no effect).
*	Self contained MTD device drivers>>>>
	*M-Systems DOC & Millennium
	*Advanced detection options for DOC
	*0 - Physical address
	*Probe for 0x55 & 0xAA
	*NAND flash device drivers>>>>>
		*NAND device support
		*Enable ECC

On booting the kernel your stuff correctly detects that I have a DOC2000
with 8MB but fails to create any device special file in /dev, here is a
transcript:

DiskOnChip 2000 found at address 0xD4000
Flash Chip Found: Manufacturer ID: EC, Chip ID: E6 (Samsung KM29U64000)
1 Flash chips found.  Total DiskOnChip size: 8MiB
NFTL Driver: nftlcore.c $ Revision: 1.82 $, nftlmount.c $Revision: 1.23$
ANAND header found @ 0xC000 in mtd0, but ECC read failed (err 1)
ANAND header found @ 0xE000 in mtd0, but ECC read failed (err 1)
Could not find valid boot record.
Could not mount NFTL device.

I hope you can give some advice on this matter, it is probably just a
mistake on my behalf in configuring the kernel.

Thanks in advance.

Gareth Williams.

Re: Quick question.

[David Woodhouse]

gareth@microm-electronics.com said:
> ANAND header found @ 0xC000 in mtd0, but ECC read failed (err 1) 
> ANAND header found @ 0xE000 in mtd0, but ECC read failed (err 1)
> Could not find valid boot record.
> Could not mount NFTL device.

It's being anal and refusing to deal with the Media Header because the ECC 
failed on that block - it seems that some versions of the M-Systems 
firmware don't put ECC on the Media Header blocks.

--- drivers/mtd/nftlmount.c	2001/09/19 21:42:32	1.23
+++ drivers/mtd/nftlmount.c	2001/10/19 12:22:13
@@ -94,7 +94,7 @@
 			continue;
 		}
 
-#if 1 /* Some people seem to have devices without ECC or erase marks
+#if 0 /* Some people seem to have devices without ECC or erase marks
 	 on the Media Header blocks. There are enough other sanity
 	 checks in here that we can probably do without it.
       */



--
dwmw2

Quick Question

[Josh Kindler]

The LiVid GATOS project website (linuxvideo.org/gatos) says that there are
two versions of the Rage Mobility.
Can you tell me which one is in my Pismo Powerbook (2000 model).

Thanks.
--
Josh Kindler

A hen is an egg's way of making another egg.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Quick Question

[Michel Dänzer]

Josh Kindler wrote:
>
> The LiVid GATOS project website (linuxvideo.org/gatos) says that there are
> two versions of the Rage Mobility.
> Can you tell me which one is in my Pismo Powerbook (2000 model).

michdaen@pismo:~> lspci |grep VGA
00:10.0 VGA compatible controller: ATI Technologies Inc Mobility M3 AGP 2x
(rev 02)


This is the Rage128 based one.


--
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Quick Question

[B]

[-- Attachment #1: Type: text/plain, Size: 252 bytes --]

I was just wondering whether LinuxPPC 5.0, will be able to read and write to HFS Plus drives. I have had a look through your sites but could not find any info on this.

Any information you could provide me with would be greatly appreciated.

Brad

[-- Attachment #2: Type: text/html, Size: 733 bytes --]