Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2245
Today's Topics:
Re: ibm serveraid 7k + amd64 sarge + [ "sfniks sfinks" ]
Re: ibm serveraid 7k + amd64 sarge + [ Neil Watson ]
which fonts config file? [ Jose Rodriguez ]
Re: Good fdisk Practices [ David Brodbeck ]
Re: Good fdisk Practices [ Celejar ]
Re: why is debian coreutils so old? [ bob@proulx.com (Bob Proulx) ]
Re: broken old installer? [ Ken Irving ]
Re: Good fdisk Practices [ bob@proulx.com (Bob Proulx) ]
Re: Good fdisk Practices [ Klein Moebius ]
Date: Fri, 24 Aug 2007 22:08:23 +0300
From: "sfniks sfinks" <sfinks2@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: ibm serveraid 7k + amd64 sarge + ipssend?
Message-ID: <f82af1830708241208r6d97c4a1r6503a0bf84961c4@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_61009_22489023.1187982503117"
------=_Part_61009_22489023.1187982503117
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
ok I ran it from chrooted 32-bit environment, but thats what I get:
# ./ipssend getconfig 1
Found 1 IBM ServeRAID controller(s).
Read configuration has been initiated for controller 1...
Controller information
Firmware version :
Boot block version :
Controller name :
SCSI channel description : 0 parallel SCSI wide
Initiator IDs (Channel/SCSI ID): Maximum physical devices : 0
Defunct disk drive count : 0
Logical drives/Offline/Critical: 0/0/0
Readahead cache setting : Adaptive
Stripe-unit size : Unknown
Hot-swap rebuild : Disabled
Data scrubbing : Enabled
Unattended mode (Yes/No) : No
Concurrent commands supported : 0
Configuration update count : 0
----------------------------------------------------------------------
Logical drive information
None are defined
Physical device information
Command completed successfully.
# cat /proc/scsi/ips/0
IBM ServeRAID General Information:
Controller Type : ServeRAID 7k
Memory region : 0xdafff000 (4096 bytes)
Shared memory address : 0xffffc20000018000
IRQ number : 17
BIOS Version : 7.12.07
Firmware Version : 7.12.07
Boot Block Version : 7.12.07
Driver Version : 7.12.05
Driver Build : 761
Max Physical Devices : 30
Max Active Commands : 64
Current Queued Commands : 0
Current Active Commands : 0
Current Queued PT Commands : 0
Current Active PT Commands : 0
is it driver on ipssend problem?
On 8/24/07, sfniks sfinks <sfinks2@gmail.com> wrote:
>
> Hi,
>
> I'm haveing amd64 sarge installed on ibm server which has serveraid 7k
> controller with scsi disks.
>
> there's ipssend binaries on cd, but
> 1) both are 32 bit:
> /cdrom/linux/scsi/cmdline/ipssend
> /cdrom/linux_x86_64/scsi/cmdline/ipssend
>
> # file /cdrom/linux*/scsi/cmdline/*
> /cdrom/linux/scsi/cmdline/ipssend: ELF 32-bit LSB executable, Intel
> 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses
> shared libs), stripped
> /cdrom/linux_x86_64/scsi/cmdline/ipssend: ELF 32-bit LSB executable, Intel
> 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses
> shared libs), stripped
>
> Anyway, I've searched ibm-s web ang used google but still havent found a
> solution
> how to manage/view raid array (with serveraid 7k) on amd64 sarge..
> Is there statically linked tool by ibm?
> is there source for ipssend by ibm?
> is there any production level opensource tool for this card?
>
> thanks..
>
>
------=_Part_61009_22489023.1187982503117
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
ok I ran it from chrooted 32-bit environment, but thats what I get:
# ./ipssend getconfig 1
Found 1 IBM ServeRAID controller(s).
Read configuration has been initiated for controller 1...
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
Firmware version :
Boot block version :
Controller name :
SCSI channel description : 0 parallel SCSI wide<br> Initiator IDs (Channel/SCSI ID): Maximum physical devices : 0<br> Defunct disk drive count : 0<br> Logical drives/Offline/Critical: 0/0/0<br>
Readahead cache setting : Adaptive<br> Stripe-unit size : Unknown<br> Hot-swap rebuild : Disabled<br> Data scrubbing : Enabled<br> Unattended mode (Yes/No) : No
Concurrent commands supported : 0
Configuration update count : 0
----------------------------------------------------------------------
Logical drive information
----------------------------------------------------------------------
None are defined
----------------------------------------------------------------------
Physical device information
----------------------------------------------------------------------
Command completed successfully.
# cat /proc/scsi/ips/0
IBM ServeRAID General Information:
Controller Type : ServeRAID 7k
Memory region : 0xdafff000 (4096 bytes)
Shared memory address : 0xffffc20000018000
<br> IRQ number : 17<br> BIOS Version : 7.12.07<br> Firmware Version : 7.12.07<br> Boot Block Version : 7.12.07<br> Driver Version :
7.12.05 <br> Driver Build : 761<br> Max Physical Devices : 30<br> Max Active Commands : 64<br> Current Queued Commands : 0<br> Current Active Commands : 0
<br> Current Queued PT Commands : 0<br> Current Active PT Commands : 0<br><br><br>is it driver on ipssend problem?<br><br><br><div><span class="gmail_quote">On 8/24/07, <b class="gmail_sendername">
sfniks sfinks</b> <<a href="mailto:sfinks2@gmail.com">sfinks2@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I'm haveing amd64 sarge installed on ibm server which has serveraid 7k controller with scsi disks.<br><br>there's ipssend binaries on cd, but <br>1) both are 32 bit:<br>/cdrom/linux/scsi/cmdline/ipssend
<br>
/cdrom/linux_x86_64/scsi/cmdline/ipssend<br><br># file /cdrom/linux*/scsi/cmdline/*<br>/cdrom/linux/scsi/cmdline/ipssend: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), stripped
<br>/cdrom/linux_x86_64/scsi/cmdline/ipssend: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), stripped<br><br>Anyway, I've searched ibm-s web ang used google but still havent found a solution
<br>how to manage/view raid array (with serveraid 7k) on amd64 sarge.. <br>Is there statically linked tool by ibm?<br>is there source for ipssend by ibm?<br>is there any production level opensource tool for this card?<br>
<br>thanks..<br><br>
</blockquote></div><br>
------=_Part_61009_22489023.1187982503117--
Date: Fri, 24 Aug 2007 15:11:44 -0400
From: Neil Watson <debian@watson-wilson.ca>
To: debian-user@lists.debian.org
Subject: Re: ibm serveraid 7k + amd64 sarge + ipssend?
Message-ID: <20070824191144.GD19036@watson-wilson.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Call IBM support. When I last worked with IBM gear they fully supported
Linux. They will point you to the correct location to acquire the
latest drivers and management tools.
--
Neil Watson | Debian Linux
System Administrator | Uptime 1 day
http://watson-wilson.ca
Date: Fri, 24 Aug 2007 21:12:05 +0200
From: =?UTF-8?Q?Cs=C3=A1nyi_P=C3=A1l?= <csanyipal@csanyi-pal.info>
To: debian-user@lists.debian.org
Subject: Re: graphics driver issues
Message-ID: <20070824191205.GA4763@csanyi-pal.info>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Aug 24, 2007 at 01:31:49PM -0500, sworoc wrote:
> On 8/24/07, Joe Hart <j.hart@orange.nl> wrote:
> > On Friday 24 August 2007 19:48:31 sworoc wrote:
> > > Hi all,
> > >
> > > I am a college student and am taking a graphics course this fall. I
> > > recently built a PC with an AMD64 CPU and a GeForce 6150 on board
> > > graphics card. I seem to be having trouble getting it to use the
> > > nvidia module, but I'm not sure where I'm going wrong. I installed it
> > > using the module assistant method, and I believe that I have things
> > > set up correctly.
> > >
> > > output:
> > > ----------------------------------------------
> > >
> > > puckett:~# uname -a
> > > Linux puckett 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64
> > > GNU/Linux
> > > puckett:~# lsmod | grep nvidia
> > > nvidia 5434580 0
> > > i2c_core 28288 4 nvidia,it87,i2c_isa,i2c_nforce2
> > > puckett:~# apt-get install nvidia-kernel-common nvidia-glx
> > > nvidia-kernel-2.6.21-2-amd64
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > nvidia-kernel-common is already the newest version.
> > > nvidia-glx is already the newest version.
> > > nvidia-kernel-2.6.21-2-amd64 is already the newest version.
> > > 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
> > >
> > > ---------------------------------------------
> > >
> > > it appears that the nvidia module is running from the output above,
> > > but when I attempt to start X, I get the following:
> > >
> > > ********************************************
> > > xauth: creating new authority file /home/dustin/.serverauth.18757
> > >
> > >
> > > X Window System Version 1.3.0
> > > Release Date: 19 April 2007
> > > X Protocol Version 11, Revision 0, Release 1.3
> > > Build Operating System: Linux Debian (xorg-server 2: 1.3.0.0.dfsg-12)
> > > Current Operating System: Linux puckett 2.6.21-2-amd64 #1 SMP Tue Jul 10
> > > 21:39:38 UTC 2007 x86_64
> > > Build Date: 09 August 2007
> > > Before reporting problems, check http://wiki.x.org <http://wiki.x.org>
> > > to make sure that you have the latest version.
> > > Module Loader present
> > > Markers: (--) probed, (**) from config file, (==) default setting,
> > > (++) from command line, (!!) notice, (II) informational,
> > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > > (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 21 22:12:10 2007
> > > (==) Using config file: "/etc/X11/xorg.conf"
> > > (II) Module already built-in
> > > (II) Module already built-in
> > > (EE) Failed to load module "nvidia" (module does not exist, 0)
> > > (EE) Failed to load module "nvidia" (module does not exist, 0)
> > > (EE) No drivers available.
> > <snip irrelavent portions of xorg.conf>
> >
> > > Section "Module"
> > > Load "i2c"
> > > Load "bitmap"
> > > Load "ddc"
> > > Load "dri"
> > > Load "extmod"
> > > Load "freetype"
> > > Load "nvidia"
> > > Load "glx"
> > > Load "int10"
> > > Load "vbe"
> > > EndSection
> >
> > I'm not an expert, but to me it looks like your problem is with the tabbed
> > line above: Load "nvidia" should not be in this section. Try removing that
> > and see what happens.
Read
/usr/share/doc/nvidia-glx/README.Debian and
/usr/share/doc/nvidia-glx/README.txt.gz
--
Regards, Paul Csanyi
http://www.freewebs.com/csanyi-pal/index.htm
Date: Fri, 24 Aug 2007 14:13:34 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-ID: <46CF2DDE.9030602@cox.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/24/07 12:51, Stefan Monnier wrote:
>>> I'm a big proponent of swap *files*. Once you allocate the whole
>>> disk, there no room left over if you want to add another swap
>>> partition, whereas you can add as many swap files as your heart
>>> desires, whenever you need them.
>
>> I'd always heard that swap files are slower than swap partitions. Is that
>> a myth?
>
>> Also, is there any good reason to have a separate /boot on a modern system?
>> I always thought /boot was just a kludge to get around old BIOSes that
>> couldn't load anything that wasn't on the first part of the disk. I tend
>> to just combine /boot and / on my newer systems --
>> am I taking some kind of risk by doing so?
>
> All my drives have 2 partitions: a /boot (with ext2 or ext3) of about 100MB
> and the rest is an partition dedicated to LVM. The reason for the separate
> /boot is that GRUB does not know how to read files from LVM volumes, so
> I need to load the kernel and initrd files from an ext[23]. Everything else
> (/, /home, swap, etc..) is placed in LVM volumes.
I read recently on this list that LVM is not portable across CPU
architectures, so that you can't just upgrade your mobo to AMD64 and
retain your /home.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGzy3eS9HxQb37XmcRAnDpAJ9KEs2wvyB8i+AeUK1B1oaeivM8FwCgk3nt
iG1Dfg4nC25bBbsFDgMDwNo=
=XxMf
-----END PGP SIGNATURE-----
Date: Fri, 24 Aug 2007 19:56:39 +0100
From: Jose Rodriguez <josec.rodriguez@gmail.com>
To: debian-user@lists.debian.org
Subject: which fonts config file?
Message-ID: <20070824195639.8cdc6f72.josec.rodriguez@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hello
I get different fonts when I start the GUI by issuing startx than
using kdm. I would like to know which configuration files are read
in each case so I can adjust them to my taste.
Thanks
Date: Fri, 24 Aug 2007 12:37:14 -0700
From: J <j1234f@excite.com>
To: debian-user@lists.debian.org
Subject: Getting W: mdadm: /etc/mdadm/mdadm.conf defines no arrays in install of linux-image 2.6.28-5
Message-ID: <1187984234.830312.125460@q5g2000prf.googlegroups.com>
Content-Type: text/plain; charset="iso-8859-1"
Getting W: mdadm: /etc/mdadm/mdadm.conf defines no arrays in install
of linux-image 2.6.28-5
-----------
Getting warning message:
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays
W: mdadm:no array defined in conifuration file.
W: mdadm:falling back to emergency procedure in initramfs.
Added Linux *
during in install of linux-image 2.6.28-5
Will my system reboot if I power off?
thanks
j
Date: Fri, 24 Aug 2007 13:14:42 -0700
From: David Brodbeck <brodbd@u.washington.edu>
To: List Debian User <debian-user@lists.debian.org>
Subject: Re: Good fdisk Practices
Message-Id: <70E55C6D-178F-4427-B5B5-2AC38301E877@u.washington.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
On Aug 24, 2007, at 10:24 AM, Cassiano Bertol Leal wrote:
> If you use LVM you're stuck with a separate, non-LVM /boot partition
> AFAIK. Or is this outated info?
I think that's true. I don't usually make the root filesystem an LVM
volume, anyway. In most distributions it's quite small and making it
a "normal" partition makes some recovery scenarios easier -- it's
just one less thing that has to work for the system to boot into
single user mode.
Date: Fri, 24 Aug 2007 13:18:03 -0700
From: David Brodbeck <brodbd@u.washington.edu>
To: List Debian User <debian-user@lists.debian.org>
Subject: Re: Good fdisk Practices
Message-Id: <1E8B7C13-4848-4AD6-BF1D-AF3AF9293A59@u.washington.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
On Aug 24, 2007, at 12:13 PM, Ron Johnson wrote:
> I read recently on this list that LVM is not portable across CPU
> architectures, so that you can't just upgrade your mobo to AMD64 and
> retain your /home.
Well, now you've got me curious. If so, this is potentially a
serious issue, because most rescue disks are 32-bit. If it's true,
then an LVM created on a 64-bit system wouldn't be readable with a 32-
bit rescue disk. It also might have implications for things like USB
hard disks. (These are getting big enough where it might start to
make sense to LVM them -- I have one USB array that's 1.5 TB.)
I happen to have a spare AMD64 system and a couple of spare IA32
systems, all with hot-swap drive bays that take the same sleds, so I
may try this and see what happens.
Date: Fri, 24 Aug 2007 22:21:22 +0200
From: Michal Krajcirovic <konference@kraja.net>
To: debian-user@lists.debian.org
Subject: graph generate for ip areas
Message-ID: <46CF3DC2.3090301@kraja.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Hello,
i want to generate eth graphs (munin, mrtg, or anything other) in this way:
i have some ip areas. i want to generated 20 areas to first graph, 50
areas to second graph and other to third graph.
How to this?
Thank you.
--
Michal Krajcirovic
Date: Fri, 24 Aug 2007 16:35:24 -0400
From: Celejar <celejar@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-Id: <20070824163524.d42bab1f.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Fri, 24 Aug 2007 13:14:42 -0700
David Brodbeck <brodbd@u.washington.edu> wrote:
>
> On Aug 24, 2007, at 10:24 AM, Cassiano Bertol Leal wrote:
>
> > If you use LVM you're stuck with a separate, non-LVM /boot partition
> > AFAIK. Or is this outated info?
>
> I think that's true. I don't usually make the root filesystem an LVM
> volume, anyway. In most distributions it's quite small and making it
> a "normal" partition makes some recovery scenarios easier -- it's
> just one less thing that has to work for the system to boot into
> single user mode.
I believe it is actually outdated information; GRUB apparently supports
LVM these days:
http://grub.enbug.org/LVMandRAID
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Fri, 24 Aug 2007 16:42:10 -0400
From: Celejar <celejar@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-Id: <20070824164210.7ce639e1.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Fri, 24 Aug 2007 13:51:14 -0400
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> All my drives have 2 partitions: a /boot (with ext2 or ext3) of about 100MB
> and the rest is an partition dedicated to LVM. The reason for the separate
> /boot is that GRUB does not know how to read files from LVM volumes, so
> I need to load the kernel and initrd files from an ext[23]. Everything else
Apparently no longer true, as I pointed out in another message in this
thread.
> Stefan
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Fri, 24 Aug 2007 14:49:00 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: why is debian coreutils so old?
Message-ID: <20070824204900.GA31045@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sven Joachim wrote:
> You should probably ask the package maintainer directly. Some
> information is available at [1].
> [1] http://bugs.debian.org/422279
That particular issue mostly has to do with UTF-8 support. So far all
of the patch suggestions for it (used by other distros) are quite ugly
with a lot of duplicated code and has been rejected by the upstream
maintainer. There really should be a better way to do this.
The inclusion of UTF-8 support and the issues surrounding the upgrade
to a newer coreutils in Debian are mostly independent. However even I
am not aware of the issues the Debian maintainer has with moving to a
newer coreutils. I would like to see it happen too.
Bob
Date: Fri, 24 Aug 2007 12:49:52 -0800
From: Ken Irving <fnkci@uaf.edu>
To: debian-user@lists.debian.org
Subject: Re: broken old installer?
Message-ID: <20070824204952.GA7784@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Aug 24, 2007 at 10:21:17AM -0800, Ken Irving wrote:
> I'm somewhat CD-writing-impaired, and have always installed debian systems
> using outdated installers. For a long time I used a woody net install cd,
> but since mid-2005 I've been using a sarge net install cd, as recently
> as a month ago, without problems. Now I'm seeing the install fail.
> Unfortunately, the first error screen indicating a problem is quickly
> (~ 1 second maybe) replaced with an information-free curses page saying
> that there were errors...
>
> ...
> On thing I haven't tried is to do the install completely off the CD,
> and do the net upgrades later.
... which of course didn't work from the *net install* cd. I was able
to proceed after upgrading aptitude (and related libraries) from another
console.
> Should I not be using my trusty old installer?
I guess not.
--
Ken Irving, fnkci+debianuser@uaf.edu
Date: Fri, 24 Aug 2007 14:55:46 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-ID: <20070824205546.GB31045@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Celejar wrote:
> > Cassiano Bertol Leal wrote:
> > > If you use LVM you're stuck with a separate, non-LVM /boot partition
> > > AFAIK. Or is this outated info?
>
> I believe it is actually outdated information; GRUB apparently supports
> LVM these days:
>
> http://grub.enbug.org/LVMandRAID
Check the version number of grub though. That is only available in
the newer versions. You need "grub2-pc" at the least. I am not sure
how mature grub2-pc is at this time.
Bob
Date: Fri, 24 Aug 2007 16:02:46 -0500
From: Klein Moebius <klein.moebius@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-ID: <20070824210246.GA19404@laphapless.davescrunch.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
* Martin McCormick <martin@dc.cis.okstate.edu> [2007-08-24 08:10:41 -0500]:
> It appears after reading the fdisk manual, that it is
> best to put swap on whats left of the disk after calculating
> one's other partition needs. The boot image should end up in the
> lowest sector numbers. Do I understand this right?
Yep.
>
> I am about to reformat a 20-gig hard disk on a
> 5-year-old Dell laptop that used to run Windows XP. You might
> say, I am giving it a whole new outlook.
>
Got that right.
> The present fdisk report for /dev/hda shows a 32-MB
> partition 1 and a 19-gig partition 2. I think I will probably
> make it 19-gigs for partition 1 and 512 MB for partition2 since
> the system has 256 K of RAM. Partition 1 will be Linux and
> partition2 will be swap.
Hmm. Consider this:
In older machines where hard drive physical speed can be a noticable
factor in machine performance, it makes sense to to place your
partitions that see the most activity in terms of read/write accesses
physically close to each other with swap in between. The head doesn't
have to move as far to accomplish the same task. Hanging the swap out
at the end can be a detriment.
Perhaps a scheme such as this:
50 Mg /boot at the beginning
300 Mg /
5 gig /usr
3 gig /var
384 - 512 Mg swap
480 Mg /tmp
and the balance as /home
--
Regards,
Klein.
One doesn't have a sense of humor. It has you.
-- Larry Gelbart
Date: Fri, 24 Aug 2007 16:40:08 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: Good fdisk Practices
Message-ID: <46CF5038.7080009@cox.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/24/07 16:02, Klein Moebius wrote:
[snip]
> In older machines where hard drive physical speed can be a noticable
> factor in machine performance, it makes sense to to place your
> partitions that see the most activity in terms of read/write accesses
> physically close to each other with swap in between. The head doesn't
Or go out on Ebay and buy some replacement RAM chips. If the chips
on your Hell aren't soldered onto the mobo.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGz1A4S9HxQb37XmcRAmjtAJ4y9FQVcdJpg7a/7cQxiH7QQeyyXQCeNNsE
6AC7lKbX1GvtO4smBy6PZCA=
=r3Tc
-----END PGP SIGNATURE-----
End of debian-user-digest Digest V2007 Issue #2245
**************************************************
Received on Fri Aug 24 18:10:22 2007