[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Unsubscribe



In message <20021005215828.7AAAB1F67B@murphy.debian.org>, debian-user-
digest-request@lists.debian.org writes
>Content-Type: text/plain
>
>debian-user-digest Digest                              Volume 2002 : Issue 2
>
>Today's Topics:
>  Re: Woody and miscellaneous issues    [ Osamu Aoki <debian@aokiconsulting.c ]
>  Re: Building distributions based upo  [ Simon Law <sfllaw@engmail.uwaterloo ]
>  Re: viewcvs + py2html ?               [ Simon Law <sfllaw@engmail.uwaterloo ]
>  RE: OT: mass installation on XBox     [ "Josh Rehman" <java.josh@verizon.ne ]
>  Re: SquirrelMail installation diffic  [ Steve Waterman <steve@yurmail.com> ]
>  unsubscribe                           [ thebubster <bubba@localhost> ]
>  Re: Performance needed for an Intern  [ "Jamin W. Collins" <jcollins@asgard ]
>  Re: OT: mass installation on XBox     [ Klaus Imgrund <claus.imgrund@terra. ]
>  knoppix                               [ el <nntps2net@t-online.de> ]
>  Re: Installing a SCSI Tape-Drive to   [ Frank Gevaerts <frank@gevaerts.be> ]
>  Re: VIA KT8266A + VIA VT8233A w/ AC9  [ Kent West <westk@acu.edu> ]
>  e2fsck and fsck.ext2                  [ "Brenda J. Butler" <brenda.butler@z ]
>  java debs, where?                     [ Jaye Inabnit ke6sls <ke6sls@cox.net ]
>  Re: e2fsck and fsck.ext2              [ Patrick Wiseman <pwiseman@mindsprin ]
>  Re: knoppix                           [ Bob Nielsen <nielsen@oz.net> ]
>  Re: e2fsck and fsck.ext2              [ bob@proulx.com (Bob Proulx) ]
>  Re: e2fsck and fsck.ext2              [ Frank Gevaerts <frank@gevaerts.be> ]
>  unsubscribe                           [ "Jorge A. Arrieta N." <jarrieta@ic- ]
>Date: Sat, 5 Oct 2002 11:56:55 -0700
>From: Osamu Aoki <debian@aokiconsulting.com>
>To: Paul Lewis <paul.lewis@karachi.freeuk.com>
>Cc: debian-user@lists.debian.org
>Subject: Re: Woody and miscellaneous issues
>Message-ID: <[🔎] 20021005185655.GB18231@aokiconsulting.com>
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Sat, Oct 05, 2002 at 07:36:59PM +0100, Paul Lewis wrote:
>> Hi,
>> 
>>      I have just installed Woody, and I have a few issues I would 
>> like to resolve. The first is my first is my printer is on another 
>> machine, where/what is the utility on Debian that allows me to setup 
>> the print queues?
>
>If you use lpr type spoolers (lpr, lpr-ppd, lprng), edit /etc/printcap
>Just point it to remote printer.  For lpr-ppd, installing gnulpr package
>will pull in printtool GUI configuration utility which should help you.
>
>I bet others will give you suggestions to use CUPS.
>
>>      Next, on my old machine I was able to access a remote drive 
>> (NFS) on a redhat machine, how can I get this working again before 
>> upgrading to Woody I backed up my files to the server, I would like to 
>> get them back onto this machine.
>
>First
>
> # apt-get install nfs-kernel-server
>
>Set up /etc/exports. Also possibly play with /etc/hosts.allow and
>/etc/hosts.deny
>
>>      Then when I installed Woody it put the 2.2 kernel on the 
>> system. I had previously been running the 2.4.9 kernel. How do I 
>> upgrade the kernel on Woody?
>
>Install 2.4 kernel-image package.
>  # apt-get install initrd-tools
>  # apt-get install kernel-image-2.4.19-386
>     (or -686, -686-smp, -k6, -k7, -586tsc variants)
>
>More of these basics in my document below.
>-- 
>~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
>        Osamu Aoki @ Cupertino CA USA, GPG-key: A8061F32
> .''`.  Debian Reference: post-installation user's guide for non-developers
> : :' : http://www.debian.org/doc/manuals/reference/ also http://qref.sf.net
> `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract
>Date: Sat, 5 Oct 2002 15:12:59 -0400
>From: Simon Law <sfllaw@engmail.uwaterloo.ca>
>To: Debian-User <debian-user@lists.debian.org>
>Subject: Re: Building distributions based upon Debian
>Message-ID: <[🔎] 20021005191259.GG7107@engmail.uwaterloo.ca>
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Sat, Oct 05, 2002 at 06:17:13AM -0500, Ron Johnson wrote:
>> On Sat, 2002-10-05 at 05:47, Alan Chandler wrote:
>> > On Friday 04 October 2002 2:41 pm, jurgen.defurne@philips.com wrote:
>> > > Thanks,
>> [snip]
>> > 
>> > I know you don't need all 7 - I just made isos of all 7 and blew them on to 
>> > CDs.  Then went and install my system and only used the first CD (of course 
>I 
>> > am now loading new packages from the net - particularly since I then 
>> > dist-upgraded to unstable.
>> 
>> Which CDs are source-only for Woody?
>
>       Those would be the 7 CDs in the source CD distribution.  The
>source is not distributed with each architecture's ISOs.
>
>Simon
>Date: Sat, 5 Oct 2002 15:14:04 -0400
>From: Simon Law <sfllaw@engmail.uwaterloo.ca>
>To: debian-user@lists.debian.org
>Subject: Re: viewcvs + py2html ?
>Message-ID: <[🔎] 20021005191404.GH7107@engmail.uwaterloo.ca>
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Sat, Oct 05, 2002 at 06:18:07AM -0500, Justin Ryan wrote:
>> Anyone using ViewCVS with py2html to highlight syntax in python code? 
>> Howabout enscript?
>
>       See bugs.debian.org for Bug#140354 and Bug#141642.
>
>Simon
>Date: Sat, 5 Oct 2002 12:22:46 -0700
>From: "Josh Rehman" <java.josh@verizon.net>
>To: <debian-user@lists.debian.org>
>Subject: RE: OT: mass installation on XBox
>Message-ID: <[🔎] 061501c26ca4$963d20a0$6401a8c0@sumi>
>Content-Type: text/plain;
>       charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>
>Klaus wrote:
>> That should be interesting!
>> If that thing ever gets put together and M$ thinks it is illegal I
>would
>> love to see a court battle over that in an european court. Who in the
>> hell are those people that think they can tell me I can't construct a
>> marslander out of a ford taurus? Or use a piece of hardware I bought
>and
>> paid for to what I want it to do? This is ridiculous.
>
>The key here is to give the lawyers an alternative. If backed into a
>corner, they will do the ridiculous thing in order to protect corporate
>profits. However, I believe that if an alternative is provided, then
>this move would not be taken.
>
>The issue is not the modification of the hardware, per se, but rather
>the data that can then be pirated after the modification is made.
>Therefore, the one alternative is to limit piracy. In order to do that,
>strict policing of data streams is necessary.
>
>So that is your choice: give up freedom to modify hardware, or submit
>all data moving in and out of your control to public scrutiny. Since the
>former is both distasteful and fundamentally impossible to enforce, the
>later is inevitable, IMHO.
>
>Encryption makes subjecting data to scrutiny difficult. So it is likely
>that anti-encryption, anti-obfuscation laws would be passed along side
>any scrutiny laws.
>
>Pick your poison: inability to modify the container, or have every bit
>of information you generate or consume scrutinized. Personally, I think
>that the former is the lesser of two evils, by far. From an enforcement
>point of view, I think that corporate America would agree. (E.g. it is
>much less expensive to enforce hardware modification laws than police
>all data conduits).
>
>(I will mention the third option, which is to not worry about enforcing
>data ownership at all. This policy simply will not, and cannot fly in
>this economic, legal or political environment. There is a small class of
>data which can still be sold in this context, namely that which the
>buyer has no incentive to share, or cannot share effectively. Three
>examples that come to mind are data that describes the buyer, data that
>is expensive to share, and data that is time-sensitive. (Of course, the
>seller never has an incentive to share))
>Date: Sat, 5 Oct 2002 14:20:29 -0500
>From: Steve Waterman <steve@yurmail.com>
>To: Stephen Gran <steve@lobefin.net>, debian-user@lists.debian.org
>Subject: Re: SquirrelMail installation difficulties
>Message-Id: <[🔎] 200210051420.29881.steve@yurmail.com>
>Content-Type: text/plain;
>  charset="iso-8859-1"
>Content-Transfer-Encoding: 8bit
>
>Just a second opinion backup Stephen Gran's.  Not the prettiest, but it is 
>straight cgi/html output and needs a bit of tweaking. 
>
>www.inter7.com/sqwebmail
>
>
>On 05 October 2002 01:55 am, Stephen Gran wrote:
>> This one time, at band camp, Forrest L Norvell said:
>> > On Fri, Oct 04, 2002 at 11:33:43AM -0700, nate wrote:
>> > > Forrest L Norvell said:
>> > > > "You must be logged in to view this page" error. Thinking that I
>> > > > might be
>> > >
>> > > I read in the PHP docs that something to do with session management
>> > > was broken on powerPC:
>> > >
>> > > "Sessions do NOT work on hppa, m68k, mips, powerpc, sparc, s390
>> > > Sorry about that. :("
>> > >
>> > > from README.Debian.gz on the php package.
>> >
>> > Well, that just sucks. I didn't see that in the Readme; thanks for
>> > pointing it out to me. Anyone got a webmail package they like that isn't
>> > dependent upon PHP sessions? Does imp work on PPC?
>> >
>> > Forrest
>>
>> steve@mercury:~$ apt-cache show sqwebmail
>> Package: sqwebmail
>> Priority: optional
>> Section: mail
>> Installed-Size: 883
>> Maintainer: Stefan Hornburg (Racke) <racke@linuxia.de>
>> Architecture: i386
>> Source: courier
>> Version: 0.37.3-2.1
>> Depends: libc6 (>= 2.2.4-4), libgdbmg1, exim | mail-transport-agent,
>> courier-base (>= 0.37.3), courier-authdaemon (>= 0.37.3), ispell, iamerican
>> | ispell-dictionary, apache | httpd, cron, expect, courier-maildrop (>=
>> 0.37.3) Suggests: gnupg, courier-pcp
>> Filename: pool/updates/main/c/courier/sqwebmail_0.37.3-2.1_i386.deb
>> Size: 285110
>> MD5sum: 552cfb82cef0e7ae20485175a9c0fcb3
>> Description: Webmail Server
>>  This package contains the SqWebMail webmail server.
>>  This CGI is used by the Courier mail server to provide
>>  webmail access to local mailboxes. SqWebMail is provided
>>  here as a separate package that can be used with other
>>  mail servers as well.
>>
>> Works quite well for me (x86, but I assume it works on PPC, or it
>> shouldn't be in stable.)  No PHP, just cgi/perl.  The default template
>> is kind of ugly, but it shoudn't be too hard to rewrite when I get a
>> little more time.
>>
>> HTH,
>> Steve
>Date: Sat, 5 Oct 2002 15:38:41 -0400
>From: thebubster <bubba@localhost>
>To: debian-user@lists.debian.org
>Subject: unsubscribe
>Message-Id: <[🔎] 200210051538.41348.bubba@localhost>
>Content-Type: text/plain;
>  charset="us-ascii"
>Content-Transfer-Encoding: quoted-printable
>
>Date: Sat, 5 Oct 2002 15:01:44 -0500
>From: "Jamin W. Collins" <jcollins@asgardsrealm.net>
>To: Debian Users <debian-user@lists.debian.org>
>Subject: Re: Performance needed for an Internet gateway
>Message-ID: <[🔎] 20021005200144.GB4374@jamin-mini>
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Sat, Oct 05, 2002 at 06:09:10PM +0200, Elimar Riesebieter wrote:
>> On Sat, 05 Oct 2002 the mental interface of 
>> Balazs Javor told:
>> 
>> > NAT / port forwarding
>> > packet filtering
>
>This can be done quite easily with iptables.
>
>> > bandwidth management / trafic shaping
>
>You'll probably want to check out this site:
>  http://lartc.org/
>
>in particular:
>  http://lartc.org/wondershaper/
>
>> > some sort of secure access for my laptop through wireless network
>
>IPSEC or PPTP work well for this sort of thing.
>
>> > I was wondering what sort of processing power is needed for such a 
>> > computer?
>> 
>> You can also set up an at least
>> 200MHz box with ipchains and ipmasq. 
>
>I doubt the OP would need anything remotely near a 200Mhz system.  I've
>done all of the above (with the single exception of traffic shaping) on
>a 486SX25 with a mere 16 Megs of RAM.  The system is running Debian
>woody with a 2.4.18 kernel.  It provides an iptables based firewall
>along with PPTP and IPSEC VPN access along with SSH connectivity for
>remote administration.
>
>-- 
>Jamin W. Collins
>Date: Sat, 5 Oct 2002 17:05:46 -0300
>From: Klaus Imgrund <claus.imgrund@terra.com.br>
>To: debian-user@lists.debian.org
>Subject: Re: OT: mass installation on XBox
>Message-Id: <[🔎] 20021005170546.7d9e1874.claus.imgrund@terra.com.br>
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: 7bit
>
>On Sat, 05 Oct 2002 12:22:46 -0700
>"Josh Rehman" <java.josh@verizon.net> wrote:
>
>> Klaus wrote:
>> > That should be interesting!
>> > If that thing ever gets put together and M$ thinks it is illegal I
>> would
>> > love to see a court battle over that in an european court. Who in
>> > the hell are those people that think they can tell me I can't
>> > construct a marslander out of a ford taurus? Or use a piece of
>> > hardware I bought and
>> > paid for to what I want it to do? This is ridiculous.
>> 
>> The key here is to give the lawyers an alternative. If backed into a
>> corner, they will do the ridiculous thing in order to protect
>> corporate profits. However, I believe that if an alternative is
>> provided, then this move would not be taken.
>> 
>> The issue is not the modification of the hardware, per se, but rather
>> the data that can then be pirated after the modification is made.
>> Therefore, the one alternative is to limit piracy. In order to do
>> that, strict policing of data streams is necessary.
>> 
>> So that is your choice: give up freedom to modify hardware, or submit
>> all data moving in and out of your control to public scrutiny. Since
>> the former is both distasteful and fundamentally impossible to
>> enforce, the later is inevitable, IMHO.
>> 
>> Encryption makes subjecting data to scrutiny difficult. So it is
>> likely that anti-encryption, anti-obfuscation laws would be passed
>> along side any scrutiny laws.
>> 
>> Pick your poison: inability to modify the container, or have every bit
>> of information you generate or consume scrutinized. Personally, I
>> think that the former is the lesser of two evils, by far. From an
>> enforcement point of view, I think that corporate America would agree.
>> (E.g. it is much less expensive to enforce hardware modification laws
>> than police all data conduits).
>> 
>> (I will mention the third option, which is to not worry about
>> enforcing data ownership at all. This policy simply will not, and
>> cannot fly in this economic, legal or political environment. There is
>> a small class of data which can still be sold in this context, namely
>> that which the buyer has no incentive to share, or cannot share
>> effectively. Three examples that come to mind are data that describes
>> the buyer, data that is expensive to share, and data that is
>> time-sensitive. (Of course, the seller never has an incentive to
>> share))
>> 
>Good points,
>
>the only problem I have with that whole stuff is that the industry
>should play with open cards here. If you buy a piece of hardware and you
>are not allowed to tailor it to your needs you don't really own it in
>the classical sense of ownership. For example with the xbox they should
>then give you a leasing contract and be done with it. This would be a
>completely honest solution so that even the dumbest customer out there
>can understand what he is in for. Of course that would put a little dent
>in the cash flow generated by the product and cause even heavier losses.
>So basically the industry gets it both ways.They 'sell' a product that
>you don't really own and get the money. I don't care what is in the law
>books about this issues - that's how I feel about it.I think it is fraud
>and no stinkin' law can change that.
>
>Prost,
>
>Klaus
>Date: Sat, 05 Oct 2002 22:36:57 +0200
>From: el <nntps2net@t-online.de>
>To: debian-user@lists.debian.org
>Subject: knoppix
>Message-ID: <[🔎] 3D9F4D69.7030305@t-online.de>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>does anybody here know of a downloadable, STABLE version of knoppix?
>
>i searched all resources i could think of.
>the knoppix-forum (http://www.linuxtag.org/forum/) is not reachable.
>all i found were beta-versions, switching from
>
>?
>05/02 = vers. 2.1b
>to
>08/02 = vers. 3.1b
>10/02 =   "    "
>
>for my rescue tasks i could really need a stable version,
>if available ...
>
>thanks
>Date: Sat, 5 Oct 2002 22:41:25 +0200
>From: Frank Gevaerts <frank@gevaerts.be>
>To: Doug MacFarlane <madmac@covad.net>
>Cc: debian-user@lists.debian.org
>Subject: Re: Installing a SCSI Tape-Drive to an Existing Woody System
>Message-ID: <[🔎] 20021005204125.GA12110@gevaerts.be>
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Sat, Oct 05, 2002 at 06:18:19PM +0000, Doug MacFarlane wrote:
>> 
>> Team:
>> 
>> I installed an HP DDS-4 SCSI tape-drive to my existing Woody system.  Upon
>> the reboot, the startup messages showed that it was detected, but I guess
>> the base install doesn't include support for it because:
>> 
>> boulion:/cdrom# tar cvf /dev/st0 /home
>> tar: Removing leading `/' from member names
>> home/
>> home/lost+found/
>> home/madmac/
>> home/madmac/.bashrc
>> home/madmac/.bash_profile
>> home/madmac/.xsession-errors
>> tar: /dev/st0: Wrote only 0 of 10240 bytes
>> tar: Error is not recoverable: exiting now
>> boulion:/cdrom# 
>> 
>> So I assume I need to install a module for this.  My questions:
>
>I think that is not the problem. If I try this on a machine without a
>tapedrive, I get a 'no such device' error.
>What does 'mt -f /dev/st0 status' report ?
>
>Maybe you should try 'mt -f /dev/st0 setblk 10240' before the tar
>command (the default tar blocksize is 10240 bytes)
>
>> 1.  How do I find out what modules support what devices?
>> 
>> 2.  Where are the instructions for adding/installing a module?
>> 
>> All the stuff I found via google and linuxhelp.org was centered around what
>> to do when installing linux, or using kudzu with Red Hat . . .
>> 
>> TIA
>> 
>> mamdac
>> 
>> -- 
>> Doug MacFarlane
>> madmac@covad.net
>> 
>> 
>> -- 
>> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>Date: Sat, 05 Oct 2002 16:03:50 -0500
>From: Kent West <westk@acu.edu>
>To: debian-user@lists.debian.org
>Subject: Re: VIA KT8266A + VIA VT8233A w/ AC97 sound
>Message-ID: <[🔎] 3D9F53B6.40402@acu.edu>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>Alan Chandler wrote:
>
>>On Wednesday 02 October 2002 11:04 am, Robert Ian Smit wrote:
>>  
>>
>>>* D. Nathan Cookson <dorzak@earthlink.net> [02-10-2002 07:20]:
>>>    
>>>
>>>>1 - Does anybody know from definitive experience the status of support
>>>>for the Via VT8233A southbridge in Debian kernels?
>>>>      
>>>>
>>>Compile a 2.4.19 kernel of your own. I had to do it bacause of a new
>>>motherboard, was scared, but can recommend it. The reference manual,
>>>chapter 7, has all the details. Getting .config right might be
>>>tricky, so if you need more help on that, ask.
>>>
>>>    
>>>
>>
>>I am quite puzzled why a lot of people seem to think they need to compile 
>>their own kernels rather than use the debian standard ones.  Debian kernels 
>>have nearly everything compiled as a module - so provided you get the modules 
>>loaded everything works - and you don't need to keep rebooting either
>>
>>  
>>
>Because:
>
>    1) A lot of the documentation out there says to recompile the kernel 
>in order to get X piece of hardware working, etc, so we dutifully follow 
>the FM so we won't get flamed for not RTFM (in other words, 
>documentation for Debian (Linux in general) is still spotty/immature),
>
>and
>
>    2) When we try to install a new kernel using dselect, etc, we're 
>warned that this is the "initrd" version and that we need to make sure 
>we have done some prior step before using this kernel  (or something 
>similar) which actually sounds scarier than recompiling a kernel to some 
>(in other words, documentation for Debian (Linux in general) is still 
>spotty/immature).
>
>
>In other words, "people seem to think they need to compile their own 
>kernels rather than use the debian standard ones" for the simple reason 
>that they don't know any better, and even if the correct information is 
>"out there", it's mixed in with a lot of old, out-dated, 
>other-distro-oriented, and simply wrong, info. There's not a whole lot 
>that anyone can do about it; the developers are too busy writing code to 
>write documentation for newbies, and the middle-grounders who could 
>write the documentation don't have the understanding of the code to 
>write authoritative documentation, and even if they do write it, the 
>code changes so quickly in the Free Software world that that 
>documenation quickly becomes dated.
>
>Ideally, every package would have three persons/groups assigned to it: 
>one to write the code, one to package it for Debian, and one to write 
>very clear , multiply-expressed, example-filled, Debian-oriented 
>documentation. But in a Bazaar (sp?) paradigm, that ain't likely to 
>happen. And that's okay; that's the world we choose to live in when we 
>came over to the Forces of Goodness :-)
>
>And of course, I could be totally wrong. But that's why I've always 
>compiled my own kernels. I started out because the documentation I was 
>reading indicated that I needed to. Then later, when I decided to go 
>with a stock Debian kernel, I got that warning something about the 
>kernel being an initrd version (which could simply be the result of me 
>being too ignorant to pick the correct stock Debian kernel, etc), so I 
>figured I better stick with what I know works, which was compilation. So 
>the two reasons given above actually boil down to one: ignorance on the 
>part of the user. (Bummer, I seem to have just proven that I'm ignorant 
>. . . . ) Until users stop being ignorant, they'll (we'll) keep 
>sometimes making the less-than-best choices.
>
>Kent
>Date: Sat, 5 Oct 2002 17:05:55 -0400
>From: "Brenda J. Butler" <brenda.butler@zarlink.com>
>To: debian-user@lists.debian.org
>Subject: e2fsck and fsck.ext2
>Message-ID: <[🔎] 15775.21555.211617.643178@butlerbpc.ottawa.zarlink.com>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>What is the difference between e2fsck and fsck.ext2?
>I'm about to try (one of) them without a net...
>
>I didn't see any comparisons when I Googled, except
>maybe e2fsck can handle the situation where you have
>to specify an alternate superblock and (perhaps)
>fsck.ext2 can't.
>
>Please copy me at this address on the reply.  My
>subscribed email account is also broken :-(
>
>-- 
>bjb
>brenda dot butler at zarlink dot com
>Date: Sat, 5 Oct 2002 14:06:24 -0700
>From: Jaye Inabnit ke6sls <ke6sls@cox.net>
>To: debian help <debian-user@lists.debian.org>
>Subject: java debs, where?
>Message-Id: <[🔎] 20021005211012.RUJE12156.fed1mtao03.cox.net@there>
>Content-Type: text/plain;
>  charset="iso-8859-1"
>Content-Transfer-Encoding: 8bit
>
>Hash: SHA1
>
>deb ftp://ftp.tux.org/pub/java/debian woody non-free
>
>Hello:
>
>I have been getting errors from this server for the last week or so.  Each 
>time I attempt an update, the server reports that it is full.  Is there 
>alternate site for these debs?
>
>tia
>-- 
>
>Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls
>If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN.
>Free software, in a free world, for a free spirit. Please Support freedom!
>
>Date: Sat, 5 Oct 2002 17:16:53 -0400 (EDT)
>From: Patrick Wiseman <pwiseman@mindspring.com>
>To: "Brenda J. Butler" <brenda.butler@zarlink.com>
>Cc: debian-user@lists.debian.org
>Subject: Re: e2fsck and fsck.ext2
>Message-ID: <[🔎] Pine.LNX.4.21.0210051714130.2220-100000@watson>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>On Sat, 5 Oct 2002 at 5:05pm, Brenda J. Butler wrote:
>
>:What is the difference between e2fsck and fsck.ext2?
>:I'm about to try (one of) them without a net...
>
>I think they're the same thing, linked:
>
>watson:/home/pwiseman# ls -l /sbin/e2fsck
>-rwxr-xr-x    2 root     root       101224 Mar 21  2002 /sbin/e2fsck
>watson:/home/pwiseman# which fsck.ext2
>/sbin/fsck.ext2
>watson:/home/pwiseman# ls -l /sbin/fsck.ext2
>-rwxr-xr-x    2 root     root       101224 Mar 21  2002 /sbin/fsck.ext2
>
>And 'man fsck.ext2' brings up the e2fsck man page.
>
>Patrick
>

-- 
Richard Pinch



Reply to: