Date: Fri, 27 Jul 2007 01:38:08 +0100
From: "Hamza Saglam" <hamzasaglam@googlemail.com>
To: debian-user@lists.debian.org
Subject: Weird partition arrangements and broken GRUB
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
After reading dozens of GRUB tutorials for a good few hours and not
getting anywhere, I've decided to post on this mailing list regarding
my problem. If it has been covered before please pardon me, I really
can't see it :(
Now before I start, I'd like to point out that we are both debian
users both due to the nature of our work, we have to have a windows
installation on our machines. Sad but true :(
A friend of mine brought in his laptop after he said he couldn't get
'windows booting', and when I had a look at the partition table using
gparted, I was presented with the following monstrosity:
screenshot:
http://***image.***bayimg.***com/oaeikaabk.jpg
(please get rid of the 9 stars, the mailing list wouldn't accept my
message without these)
(for the text based readers), it looks a bit like:
/dev/sda1 fat32 (boot)
/dev/sda2 extended (lba)
/dev/sda5 ntfs (boot)
/dev/sda6 linux-swap
/dev/sda3 ext3
The first fat32 partition is the recovery files that came with the
laptop, the rest is a bit of mess really :)
Relevant bits from /boot/grub/menu.lst:
title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,2)
kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/sda3 ro
initrd /boot/initrd.img- 2.6.18-4-686
savedefault
title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/sda3 ro single
initrd /boot/initrd.img- 2.6.18-4-686
savedefault
title Microsoft Windows XP
root (hd0,3)
savedefault
makeactive
chainloader +1
title Acer eRecovery Management
root (hd0,0)
savedefault
makeactive
chainloader +1
I've tried all the possible combinations for the root directive of the
Windows section, but it doesn't want to load windows.
Is there any way I can address the ntfs partition within that extended
partition, or do I need to modify the structure. (I'd very much prefer
not changing the structure, even though it is quite messy)
I am stuck so any help would be much appreciated.
Many thanks.
Hamza
Date: Thu, 26 Jul 2007 20:48:40 -0400
From: Mike Robinson <mike@robinsonhome.org>
To: "debian-user@lists.debian.org" <debian-user@lists.debian.org>
Subject: Re: Stability issues
Message-ID: <46A940E8.502@robinsonhome.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
> Mike Robinson wrote:
>> I'm almost to the point of blowing the system away and installing
>> Etch. Anyone with insight would be appreciated.
>
> Well, I've decided to throw in the towel and install Etch. I think I'd
> like to boot with an Etch install CD, keep my partitions, but blow away
> the Debian Testing installation with Etch. I have one large partition
> with all of the data I need to save; the rest can go away. I've never
> done anything like this before, so any warnings/advice is welcome.
Okay, dumb question. It's been a while and I want to get it right. I plan on
downloading the minimal install CD and do a network install. My processor is an
Athlon 64 3200+, but I want the 32-bit distribution with the 'k7' kernel. Which
install image to I burn? I *think* it's the i386 image, and hopefully it'll let
me choose the kernel architecture during the install. Is this correct?
-Mike
Date: Fri, 27 Jul 2007 00:55:52 +0000 (UTC)
From: Oleg Verych <for.gmane@flower.upol.cz>
To: debian-user@lists.debian.org
Subject: adduser
Message-ID: <slrnfaihek.anq.for.gmane@flower.upol.cz>
- Bob Proulx
>
> Oleg Verych wrote:
>> I'm just a user, but developers seem to have some problems in the
>> past: #208848.
>
> But Bug#208848 says that cron needed a dependency upon adduser, which
> it now has because of that bug. Reading that bug this was
> specifically for build daemons with a minimum system without adduser
> otherwise installed. I don't see anything about adduser misbehaving.
> That bug in particular was filed against cron not adduser.
- Bob Proulx
>
>> As i said, i will try to do a simple solution. If i will fail, so be it.
>
> The original poster Rick Spillane seemed to be having trouble with
> /etc/group becoming corrupted. Are you having similar problems?
>
> What are you trying to do?
>
Getting rid of adduser. Misbehaving is one thing, bloated perl code is
another (see below).
>> One thing i can't see so far, why exim4 allocates dynamic UID. E.g. in
>> situation, when i will have same "/etc/", "/var/spool/exim4" but
>> different (re)installation sequence, UID may change, adding unneeded
>> troubles.
>
> What trouble does it cause you when an installation on different
> systems in a different order or on the same system after purging and
> reinstalling system packages in a different order uses different
> system ids?
Ids may change and i will end up with /var/spool/exim4 owned by
different user in case /etc/passwd is new.
> There are a few globally reserved ids. But all of those must be
> between 2 and 99 because traditionally other ids started at uid 100.
> Additionally room must be left for the local admin to create system
> ids. All globally allocated ids for all of Debian must fit between
> 2-99 and are coordinated through the base-passwd maintainer.
If i have /etc/passwd set up, i don't want to install adduser. If there
will be setup option or prompt: "Do you want to add Debian-exim4 (with
random UID)?" I want to say no. I don't want global ID. I want not
random one.
> Most systems, not just Debian, use dynamically assigned ids at package
> installation time. This is a very common practice. It is sometimes
> inconvenient but rarely causes serious enough problems to cause a move
> to globally allocated ids.
>
>> olecom@flower:$ du -hs adduser deluser ../share/perl5/Debian/AdduserCommon.pm
>> 32K adduser
>> 16K deluser
>> 8.0K ../share/perl5/Debian/AdduserCommon.pm
>> olecom@flower:$
>>
>> 56K just for random UID/GID or similar functionality is too much (IMHO,
>> of course). Also it pulls "passwd" anyway.
>
> Hmm... We have completely different ideas of scale. That seems
> pretty small to me. I ran perl-source-stats (from perl monks) on
> those perl scripts and this is what it turned up.
>
> /usr/sbin/adduser
> Found 745 LOC
> Found 142 comment lines
>
> /usr/sbin/deluser
> Found 348 LOC
> Found 63 comment lines
>
> /usr/share/perl5/Debian/AdduserCommon.pm
> Found 166 LOC
> Found 31 comment lines
I have not yet published aggressive cleaner of disk space, and it reports
48K of pure perl, i.e. no comments and redundant whitespace. And i care
about every additional 4097 bytes, actually (for various reasons).
> That is only 1053 lines of perl code in total across all three of
> those files. I consider that quite reasonable. I am against the
> practice of "perl golf" where the smallest number of strokes wins.
> I much prefer verbose over terse if it improves readability.
>
For such functionality it's too much. So we just disagree :)
Date: Thu, 26 Jul 2007 20:59:01 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Stability issues
Message-ID: <20070727005901.GA15317@titan>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Jul 26, 2007 at 08:48:40PM -0400, Mike Robinson wrote:
> >Mike Robinson wrote:
> >>I'm almost to the point of blowing the system away and installing
> >>Etch. Anyone with insight would be appreciated.
> >
> >Well, I've decided to throw in the towel and install Etch. I think
> >I'd like to boot with an Etch install CD, keep my partitions, but
> >blow away the Debian Testing installation with Etch. I have one
> >large partition with all of the data I need to save; the rest can go
> >away. I've never done anything like this before, so any
> >warnings/advice is welcome.
>
> Okay, dumb question. It's been a while and I want to get it right. I
> plan on downloading the minimal install CD and do a network install.
> My processor is an Athlon 64 3200+, but I want the 32-bit distribution
> with the 'k7' kernel. Which install image to I burn? I *think* it's
> the i386 image, and hopefully it'll let me choose the kernel
> architecture during the install. Is this correct?
>
Yes, you want the i386 netinst.iso. The installer will present you with
two sets of kernel choices. One is an actual kernel version the other
is a kernel meta-package that depends on the most recent version.
Other than that, I don't know if it will give you the whole list.
I'm on dialup and I just do a base install (don't have it look to the
net for anything) to get a working system fast. Then I run aptitude and
get the packages that I want. You could do this too since the -486
kernel will run on the athlon, then update to your kernel-of-choice.
Just curious: why not amd64? I'm running it on my Athlon64 3800+. The
_only_ thing I need 32-bit for is adobe flashplayer, for which I run a
chroot for the browser. That problem is fixed in Lenny/Sid but I didn't
want to go that route. After having done it, setting up the chroot was
rather simple and schroot makes running it a breeze.
Good luck with the install.
Doug.
Date: Thu, 26 Jul 2007 18:06:51 -0700
From: PETER EASTHOPE <peasthope@shaw.ca>
To: debian-user@lists.debian.org
Subject: output from nmap
Message-id:
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7bit
Content-disposition: inline
Folk,
I can use a little help to understand the following output
from nmap.
As far as I can discern, IOD = Initial Object Descriptor
and EID = Endpoint Identifier. So does this show that
the UDP packet is getting past IOD #1? What about
IOD #2?
What are EID 8, EID 18 & etc.?
Thanks, ... Peter E.
newton:~# nmap -sU -p1194 --packet-trace peasthope.yi.org
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-07-25 08:18 PDT
SENT (5.1360s) ICMP 137.82.26.91 > 139.142.97.80 Echo request (type=8/code=0) ttl=59 id=24449 iplen=28
SENT (5.1360s) TCP 137.82.26.91:43568 > 139.142.97.80:80 A ttl=43 id=18482 iplen=40 seq=4225371038 win=4096 ack=324668318
RCVD (5.1380s) TCP 139.142.97.80:80 > 137.82.26.91:43568 RA ttl=255 id=54305 iplen=40 seq=324668318 win=4096 ack=4225371038
NSOCK (5.2490s) UDP connection requested to 137.82.1.1:53 (IOD #1) EID 8
NSOCK (5.2490s) Read request from IOD #1 [137.82.1.1:53] (timeout: -1ms) EID 18
NSOCK (5.2500s) UDP connection requested to 137.82.26.240:53 (IOD #2) EID 24
NSOCK (5.2500s) Read request from IOD #2 [137.82.26.240:53] (timeout: -1ms) EID 34
NSOCK (5.2500s) Write request for 44 bytes to IOD #1 EID 43 [137.82.1.1:53]: .............80.97.142.139.in-addr.arpa.....
NSOCK (5.2510s) nsock_loop() started (timeout=500ms). 5 events pending
NSOCK (5.2520s) Callback: CONNECT SUCCESS for EID 24 [137.82.26.240:53]
NSOCK (5.2520s) Callback: CONNECT SUCCESS for EID 8 [137.82.1.1:53]
NSOCK (5.2520s) Callback: WRITE SUCCESS for EID 43 [137.82.1.1:53]
NSOCK (5.7540s) nsock_loop() started (timeout=500ms). 2 events pending
NSOCK (6.2540s) nsock_loop() started (timeout=500ms). 2 events pending
NSOCK (6.7540s) nsock_loop() started (timeout=500ms). 2 events pending
NSOCK (7.2540s) nsock_loop() started (timeout=495ms). 2 events pending
NSOCK (7.7500s) Write request for 44 bytes to IOD #1 EID 51 [137.82.1.1:53]: .............80.97.142.139.in-addr.arpa.....
NSOCK (7.7510s) nsock_loop() started (timeout=500ms). 3 events pending
NSOCK (7.7510s) Callback: WRITE SUCCESS for EID 51 [137.82.1.1:53]
NSOCK (7.8210s) Callback: READ SUCCESS for EID 18 [137.82.1.1:53] (123 bytes)
NSOCK (7.8210s) Read request from IOD #1 [137.82.1.1:53] (timeout: -1ms) EID 58
SENT (7.8390s) UDP 137.82.26.91:43548 > 139.142.97.80:1194 ttl=59 id=39917 iplen=28
SENT (7.9440s) UDP 137.82.26.91:43549 > 139.142.97.80:1194 ttl=42 id=61356 iplen=28
Interesting ports on 139.142.97.80:
PORT STATE SERVICE
1194/udp open|filtered unknown
Nmap finished: 1 IP address (1 host up) scanned in 8.165 seconds
newton:~#
http://carnot.pathology.ubc.ca/
Date: Thu, 26 Jul 2007 21:17:25 -0400
From: Wayne Topa <linuxone@intergate.com>
To: debian-user@lists.debian.org
Subject: Re: Sarge: Lost # of failed logins
Message-ID: <20070727011725.GA26337@buddy.mtntop.home>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Florian Kulzer(florian.kulzer+debian@icfo.es) is reported to have said:
> On Thu, Jul 26, 2007 at 13:51:27 -0600, Bob Proulx wrote:
> > Mumia W.. wrote:
> > > I'm using Sarge. When I log in, I no longer get a message telling me the
> > > # of failed logins.
> > >
> > > For example, if I try to login but use a wrong password, when I try
> > > again using the real password, I should see a message saying "1 failed
> > > login attempts." I no longer get that message.
> >
> > I personally have never seen such a message. You must have previously
> > installed or configured something that added that functionality.
>
> I have been using Debian for about 5 years now. As far as I remember, it
> always had the "n failure(s) since last login" message (if n was greater
> than zero). I never had to do anything to set it up, therefore I
> unfortunately don't know exactly how it works. My best guess is that it
> involves some PAM modules which parse /var/log/faillog and/or use the
> "faillog" command. Maybe this link helps to track it down:
>
> http://linux.sys-con.com/read/49058.htm
>
> (search for "faillog" on that page)
Florian
I still have the results you 'had'. I tried logging in, twice, with
a bad passwd. Got the following.
Last login: Thu Jul 26 21:01:03 2007 on tty6
Linux dj 2.6.18-4-amd64 #1 SMP Fri May 4 00:37:33 UTC 2007 x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
No mail.
1 failure since last login. <<<< BUT I failed twice!
Last was Thu 26 Jul 2007 09:06:23 PM EDT on tty5.
I seems to be coming from something after the motd but before the .bash_profile
and .bashrc. Running etch on a new system and just noticed I had not enabled
the boot log, so can't check that right now. Sorry.
Wayne
--
There were computers in Biblical times. Eve had an Apple.
_______________________________________________________
Date: Thu, 26 Jul 2007 21:30:15 -0400
From: Wayne Topa <linuxone@intergate.com>
To: debian-user@lists.debian.org
Subject: Re: DHCPD giving IP to wrong machine
Message-ID: <20070727013015.GB26337@buddy.mtntop.home>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Clarence W. Robison(robison@kimberly.uidaho.edu) is reported to have said:
Content-Description: Mail message body
> On 26 Jul 2007 at 16:05, Clarence W. Robison wrote:
>
> > I have an entry in my dhcp3 dhcpd.conf which says that host xyz with
> > certain MAC address should receive a fixed ip address. The server does
> > not respect that entry and gives the IP address to another host with a
> > different MAC address. I don't quite understand why it, dhcpd, should do
> > that. Is normal behavior?
> >
>
> OPPS, the message left before I could paste snippets of the conf file.
> ------------ dhcpd.conf ---------------------------------------------- # #
> Global Options pid-file-name "/var/run/dhcpd.pid"; lease-file-name
> "/var/lib/dhcp3/dhcpd.leases"; log-facility local1; ignore client-updates;
> ddns-update-style none; option domain-name-servers XXX.XXX.XXX.3,
> XXX.XXX.XXX.223; default-lease-time 3600; max-lease-time
> 14400; authoritative; subnet XXX.XXX.XXX.0 netmask
> 255.255.255.192 { # Default Options
> option routers XXX.XXX.XXX.1;
> option subnet-mask 255.255.255.192;
> option domain-name "XXXXXXXX.XXXXXX.XXX";
> option time-offset -25200; # Mountain Standard Time
> option ntp-servers XXX.XXX.XXX.3, XXX.XXX.XXX.58;
>
> range dynamic-bootp XXX.XXX.XXX.22 XXX.XXX.XXX.60;
>
> host xxx {
> hardware ethernet 00:13:20:2d:31:d1;
> fixed-address XXX.XXX.XXX.22;
> }
>
No expert here, but as mine works, and differs from your config I'll
show ehat I had to do.
in my /etc/dhcp3/dhcpd.conf (not the /etc/dhcpd.conf) I have
host classy {
hardware ethernet XX:XX:XX:XX:XX:XX;
fixed-address 192.168.1.5;
option host-name "classy.mtntop.home";
}
HTH
Wayne
--
Warning, keyboard not found. Press Enter to continue.
_______________________________________________________
Date: Thu, 26 Jul 2007 18:37:09 -0700 (PDT)
From: Jeff D <fixedored@gmail.com>
To: debian user <debian-user@lists.debian.org>
Subject: Re: output from nmap
Message-ID: <Pine.LNX.4.62.0707261832130.12185@proto.technobounce.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Thu, 26 Jul 2007, PETER EASTHOPE wrote:
> Folk,
>
> I can use a little help to understand the following output
> from nmap.
>
> As far as I can discern, IOD = Initial Object Descriptor
> and EID = Endpoint Identifier. So does this show that
> the UDP packet is getting past IOD #1? What about
> IOD #2?
>
> What are EID 8, EID 18 & etc.?
>
> Thanks, ... Peter E.
>
> newton:~# nmap -sU -p1194 --packet-trace peasthope.yi.org
>
> Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-07-25 08:18 PDT
> SENT (5.1360s) ICMP 137.82.26.91 > 139.142.97.80 Echo request (type=8/code=0) ttl=59 id=24449 iplen=28
> SENT (5.1360s) TCP 137.82.26.91:43568 > 139.142.97.80:80 A ttl=43 id=18482 iplen=40 seq=4225371038 win=4096 ack=324668318
> RCVD (5.1380s) TCP 139.142.97.80:80 > 137.82.26.91:43568 RA ttl=255 id=54305 iplen=40 seq=324668318 win=4096 ack=4225371038
> NSOCK (5.2490s) UDP connection requested to 137.82.1.1:53 (IOD #1) EID 8
> NSOCK (5.2490s) Read request from IOD #1 [137.82.1.1:53] (timeout: -1ms) EID 18
> NSOCK (5.2500s) UDP connection requested to 137.82.26.240:53 (IOD #2) EID 24
> NSOCK (5.2500s) Read request from IOD #2 [137.82.26.240:53] (timeout: -1ms) EID 34
> NSOCK (5.2500s) Write request for 44 bytes to IOD #1 EID 43 [137.82.1.1:53]: .............80.97.142.139.in-addr.arpa.....
> NSOCK (5.2510s) nsock_loop() started (timeout=500ms). 5 events pending
> NSOCK (5.2520s) Callback: CONNECT SUCCESS for EID 24 [137.82.26.240:53]
> NSOCK (5.2520s) Callback: CONNECT SUCCESS for EID 8 [137.82.1.1:53]
> NSOCK (5.2520s) Callback: WRITE SUCCESS for EID 43 [137.82.1.1:53]
> NSOCK (5.7540s) nsock_loop() started (timeout=500ms). 2 events pending
> NSOCK (6.2540s) nsock_loop() started (timeout=500ms). 2 events pending
> NSOCK (6.7540s) nsock_loop() started (timeout=500ms). 2 events pending
> NSOCK (7.2540s) nsock_loop() started (timeout=495ms). 2 events pending
> NSOCK (7.7500s) Write request for 44 bytes to IOD #1 EID 51 [137.82.1.1:53]: .............80.97.142.139.in-addr.arpa.....
> NSOCK (7.7510s) nsock_loop() started (timeout=500ms). 3 events pending
> NSOCK (7.7510s) Callback: WRITE SUCCESS for EID 51 [137.82.1.1:53]
> NSOCK (7.8210s) Callback: READ SUCCESS for EID 18 [137.82.1.1:53] (123 bytes)
> NSOCK (7.8210s) Read request from IOD #1 [137.82.1.1:53] (timeout: -1ms) EID 58
> SENT (7.8390s) UDP 137.82.26.91:43548 > 139.142.97.80:1194 ttl=59 id=39917 iplen=28
> SENT (7.9440s) UDP 137.82.26.91:43549 > 139.142.97.80:1194 ttl=42 id=61356 iplen=28
> Interesting ports on 139.142.97.80:
> PORT STATE SERVICE
> 1194/udp open|filtered unknown
>
> Nmap finished: 1 IP address (1 host up) scanned in 8.165 seconds
> newton:~#
>
>
>
> http://carnot.pathology.ubc.ca/
>
Looks like nmap made a dns request ..
-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.
Date: Thu, 26 Jul 2007 20:45:27 -0500
From: Owen Heisler <owenh000@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: saving package selections (Stability issues)
Message-ID: <20070727014527.GA23095@owenh.hopto.org>
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
On Thu, Jul 26, 2007 at 08:14:23PM -0400, Douglas Allan Tutty wrote:
> On Thu, Jul 26, 2007 at 04:07:59PM -0700, Andrew Sackville-West wrote:
> > if you are only installing the tasksel selections and not adding
> > additional software, then there is no reason to do this. I just know
> > that if I had to reinstall my current machine, I'd want to pull a list
> > of what was installed as I've got a couple years of built-up stuff on
> > here and wouldn't want to hassle with trying to remember it all.
>
> I use aptitude which keeps track of packages that I requested for
> install vs those installed to meet dependancies. In my backups, I keep
> both the dpkg --get-selections but also aptitude search '~i!~M' which
> gives me the names of packages that are installed (~i) that are not (!)
> automatically installed (~M).
I prefer to add a few more steps in order to:
a. save versions, like for mixed stable/testing/unstable systems, yet be
friendly to version changes
b. install exactly the packages I have selected as auto-installed
(recommends makes this a bit more tricky, when used)
c. keep all essential-marked packages
== Saving the package selections ==
1. Save list of all installed packages:
# aptitude -F "%?p" search \~i >| aptitude-installed
2. Same as previous but with versions:
# aptitude -F "%?p=%?V" search \~i | sed 's/ //g' >| aptitude-installed-ver
3. Save list of the packages that have been automatically installed:
# aptitude -F "%?p" search \~i\~M >| aptitude-autoinstalled
== Applying package selections ==
1. Make sure /etc/apt/sources.list and /etc/apt/preferences are correct
and update the lists:
# aptitude update
2. Select essential packages for installation, unmarkauto them, and
markauto non-essential packages:
# aptitude -R --schedule-only install `aptitude -F "%?p" search \~E`
# aptitude -R --schedule-only unmarkauto `aptitude -F "%?p" search \~E`
# aptitude -R --schedule-only markauto `aptitude -F "%?p" search \~i\!\~E`
3. Select packages for installation, then apply versions:
# aptitude -R --schedule-only install `cat aptitude-installed`
# aptitude -R --schedule-only install `cat aptitude-installed-ver`
4. Mark auto-installed packages as such:
# aptitude -R --schedule-only markauto `cat aptitude-autoinstalled`
5. Run aptitude interactively, make sure it is doing what it ought, then
apply either with 'g' or:
# aptitude -y install
There are probably better ways to do some of this. ...Let me know how I
can improve it.
This is obviously overkill for a lot of people.
Date: Fri, 27 Jul 2007 03:29:17 +0200 (CEST)
From: "Agricolae Maximus" <amax@mail15.com>
To: debian-user@lists.debian.org
Subject: Re: dir command
Message-ID: <f8bhpc$50c$1@aioe.org>
Ron Johnson(ron.l.johnson@cox.net) is reported to have said:
> On 07/15/07 09:50, Manon Metten wrote:
> > Hi,
> >
> > Is there a bash command available that shows the contents of the
> > given dir recursively, telling me how many files are in there and
> > the byte size occupied?
<--<snip>-->
>
Hey Ron!
> This is what I wrote to solve a similar problem:
>
> http://members.cox.net/ron.l.johnson/pydir
>
This is pretty slick. Sure saves a few keystrokes - thanks!
~A~
--
Date: Thu, 26 Jul 2007 21:50:02 -0400
From: Mike Robinson <mike@robinsonhome.org>
To: debian-user@lists.debian.org
Subject: Re: Stability issues
Message-ID: <46A94F4A.8090702@robinsonhome.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Douglas Allan Tutty wrote:
> Just curious: why not amd64? I'm running it on my Athlon64 3800+. The
> _only_ thing I need 32-bit for is adobe flashplayer, for which I run a
> chroot for the browser. That problem is fixed in Lenny/Sid but I didn't
> want to go that route. After having done it, setting up the chroot was
> rather simple and schroot makes running it a breeze.
Can the binary nVidia video driver still be used in the 64-bit distribution? If
so, I may try the amd64 route. The only thing I'd have to investigate is if there
are any issues compiling MythTV for 64-bit.
-Mike
End of debian-user-digest Digest V2007 Issue #2033
**************************************************
Received on Thu Jul 26 22:12:52 2007