Back in February, I asked a question about problems I was having with
the hard disks sequence flip-flopping when I would boot: disk #1
would be hda and disk #2 would be hdc; or disk #1 would be hde and
disk #2 would be hda.

I receive answers about using labels with the partitions so, I
labeled the partitions and updated /etc/fstab. This is how things now look:

IDE #1 Partition Label Mount Point
1 / /
2 swap1 swap file
3 /usr /usr
4
5 /usr/local /usr/local
6 /var /var

IDE #2 Partition Label Mount Point
1 /var/poptemp /var/poptemp
2 /var/mail /var/mail

The /etc/fstab:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
LABEL=/ / ext3 defaults,errors=remount-ro 0 1
LABEL=/usr /usr ext3 defaults 0 2
LABEL=/usr/local /usr/local ext3 defaults 0 2
LABEL=/var /var ext3 defaults 0 2
LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
LABEL=/var/mail /var/mail ext3 defaults 0 2
LABEL=swap1 none swap sw 0 0

Now the partitions and mount points get assigned correctly no matter
which order the drives are assigned.

The remaining problem is with the GRUB and the kernel. It was
suggested that a LABEL specification be placed in the
/boot/grub/menu.1st entry so that:

# kopt=root=/dev/hda1 becomes
# kopt=root=LABEL=/

Using a LABEL in the Grub menu does not work because the kernel get confused:

1. If kopt=root=/dev/hda1 and the disk order changes to make
the boot disk be /dev/hde, the boot process stops and drops
into a prompt. I can unmount /boot, mount /boot on the
correct drive, give a CTL-D to the prompt, and the system
would continue to boot.

2. If kopt=root=LABEL=/, the boot process will stop and drop
into a prompt WITHOUT /boot being mounted. I can mount
/boot on the correct drive, give a CTL-D to the prompt,
and the system will continue to boot.

No where have I been able to find any documentation that shows that
the Kernel boot command root= can have a LABEL specified.

So, how do I make the kernel consistently detect and assign the disks
in the correct order? Someone suggested the problem lies with UDEV
and the parallel hardware detection process.

Thanks for any suggestions.

Butch


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> Back in February, I asked a question about problems I was having with
> the hard disks sequence flip-flopping when I would boot: disk #1 would be
> hda and disk #2 would be hdc; or disk #1 would be hde and disk #2 would
> be hda.
>
> I receive answers about using labels with the partitions so, I labeled
> the partitions and updated /etc/fstab. This is how things now look:
>
> IDE #1 Partition Label Mount Point
> 1 / /
> 2 swap1 swap file
> 3 /usr /usr
> 4
> 5 /usr/local /usr/local
> 6 /var /var
>
> IDE #2 Partition Label Mount Point
> 1 /var/poptemp /var/poptemp
> 2 /var/mail /var/mail
>
> The /etc/fstab:
>
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> LABEL=/ / ext3 defaults,errors=remount-ro 0 1
> LABEL=/usr /usr ext3 defaults 0 2
> LABEL=/usr/local /usr/local ext3 defaults 0 2
> LABEL=/var /var ext3 defaults 0 2
> LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
> LABEL=/var/mail /var/mail ext3 defaults 0 2
> LABEL=swap1 none swap sw 0 0
>
> Now the partitions and mount points get assigned correctly no matter
> which order the drives are assigned.
>
> The remaining problem is with the GRUB and the kernel. It was suggested
> that a LABEL specification be placed in the /boot/grub/menu.1st entry so
> that:
>
> # kopt=root=/dev/hda1 becomes
> # kopt=root=LABEL=/
did you do an update-initramfs to build a new initrd ?

>
> Using a LABEL in the Grub menu does not work because the kernel get confused:
>
> 1. If kopt=root=/dev/hda1 and the disk order changes to make
> the boot disk be /dev/hde, the boot process stops and drops
> into a prompt. I can unmount /boot, mount /boot on the
> correct drive, give a CTL-D to the prompt, and the system
> would continue to boot.
>
> 2. If kopt=root=LABEL=/, the boot process will stop and drop
> into a prompt WITHOUT /boot being mounted. I can mount
> /boot on the correct drive, give a CTL-D to the prompt,
> and the system will continue to boot.
>
> No where have I been able to find any documentation that shows that the
> Kernel boot command root= can have a LABEL specified.
>
> So, how do I make the kernel consistently detect and assign the disks in
> the correct order? Someone suggested the problem lies with UDEV and the
> parallel hardware detection process.
>
> Thanks for any suggestions.
>
> Butch
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

--
birth, n:
The first and direst of all disasters.
-- Ambrose Bierce, "The Devil's Dictionary"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH99HAkZz88chpJ2MRAvLVAJ4xF3bn2/Gz6gldTX3s1qdsVJVtCgCg7IY9
tnDVBQsCcDf/+NZVpV4zQYk=
=Lijz
-----END PGP SIGNATURE-----

On Sun Apr 06, 2008 at 05:23:45 +1000, Alex Samad wrote:

> did you do an update-initramfs to build a new initrd ?

If you *must* reply to a post with only a single line
of new text please have the decency to trim the message,
rather than quoting it in its entirety.

Steve
--
http://www.steve.org.uk/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> Back in February, I asked a question about problems I was having with
> the hard disks sequence flip-flopping when I would boot: disk #1 would be
> hda and disk #2 would be hdc; or disk #1 would be hde and disk #2 would
> be hda.
>
> I receive answers about using labels with the partitions so, I labeled
> the partitions and updated /etc/fstab. This is how things now look:
>
> IDE #1 Partition Label Mount Point
> 1 / /
> 2 swap1 swap file
> 3 /usr /usr
> 4
> 5 /usr/local /usr/local
> 6 /var /var
>
> IDE #2 Partition Label Mount Point
> 1 /var/poptemp /var/poptemp
> 2 /var/mail /var/mail
>
> The /etc/fstab:
>
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> LABEL=/ / ext3 defaults,errors=remount-ro 0 1


>
> # kopt=root=/dev/hda1 becomes
> # kopt=root=LABEL=/

I think Alex is right, that you should rebuild the initrd. But the
other thought that occurs to me is perhaps using "/" as a label
is a problem.

.02

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH9/fQaIeIEqwil4YRAjSdAKCeR5sjMgWS7RShBf8KcSmKGWq9vQCg u1bh
moxfaCkgPdjuXV9RZU7lP0I=
=wjCE
-----END PGP SIGNATURE-----

On Sat, Apr 05, 2008 at 03:06:09PM -0700, Andrew Sackville-West wrote:
> On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
[snip]>
> >
> > # kopt=root=/dev/hda1 becomes
> > # kopt=root=LABEL=/
>
> I think Alex is right, that you should rebuild the initrd. But the
> other thought that occurs to me is perhaps using "/" as a label
> is a problem.
I have been using / as a label for a while with no problems
>
> .02
>
> A



--
An apple a day makes 365 apples a year.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH9/0AkZz88chpJ2MRAnfJAJ0ZMpdU+z8sYt9mnzlrvSWkBa1PiQCc CTPp
7wLRrDPEpdlIfuW+u263bJg=
=Zpya
-----END PGP SIGNATURE-----

On Sun, Apr 06, 2008 at 08:28:16AM +1000, Alex Samad wrote:
> On Sat, Apr 05, 2008 at 03:06:09PM -0700, Andrew Sackville-West wrote:
> > On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> [snip]>
> > >
> > > # kopt=root=/dev/hda1 becomes
> > > # kopt=root=LABEL=/
> >
> > I think Alex is right, that you should rebuild the initrd. But the
> > other thought that occurs to me is perhaps using "/" as a label
> > is a problem.

> I have been using / as a label for a while with no problems

Fair enough. just a thought. BTW, it's darn hard to find your
responses with no whitespace around them...

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH9//waIeIEqwil4YRAmgbAKC81Ki6gYuzWjiwaP1l9KGpWv0QvgCgw wVE
GGMeVbHfn3BG9McyL1LDW9A=
=xMYG
-----END PGP SIGNATURE-----

On Sat, Apr 05, 2008 at 03:40:48PM -0700, Andrew Sackville-West wrote:
> On Sun, Apr 06, 2008 at 08:28:16AM +1000, Alex Samad wrote:
> > On Sat, Apr 05, 2008 at 03:06:09PM -0700, Andrew Sackville-West wrote:
> > > On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> > [snip]>
> > > >
> > > > # kopt=root=/dev/hda1 becomes
> > > > # kopt=root=LABEL=/
> > >
> > > I think Alex is right, that you should rebuild the initrd. But the
> > > other thought that occurs to me is perhaps using "/" as a label
> > > is a problem.
>
> > I have been using / as a label for a while with no problems
>
> Fair enough. just a thought. BTW, it's darn hard to find your
> responses with no whitespace around them...

Someting like:

color quoted blue white
color quoted1 green white
color quoted3 yellow white
color signature red cyan

Put them in a file, say colours (ok, probably colors if you insist. :-)
Then something like

source ~/configs/colors

in your .muttrc

I have attached my color file which is set up for black on white. I
think it could have a better regexp for picking up urls though.

--
Chris.
======

Butch Kemper wrote:
> Back in February, I asked a question about problems I was having with
> the hard disks sequence flip-flopping when I would boot: disk #1 would
> be hda and disk #2 would be hdc; or disk #1 would be hde and disk #2
> would be hda.
>
> I receive answers about using labels with the partitions so, I labeled
> the partitions and updated /etc/fstab. This is how things now look:
>
> IDE #1 Partition Label Mount Point
> 1 / /
> 2 swap1 swap file
> 3 /usr /usr
> 4
> 5 /usr/local /usr/local
> 6 /var /var
>
> IDE #2 Partition Label Mount Point
> 1 /var/poptemp /var/poptemp
> 2 /var/mail /var/mail
>
> The /etc/fstab:
>
> # <file system> <mount point> <type> <options> <dump>
> <pass>
> proc /proc proc defaults 0 0
> LABEL=/ / ext3 defaults,errors=remount-ro 0 1
> LABEL=/usr /usr ext3 defaults 0 2
> LABEL=/usr/local /usr/local ext3 defaults 0 2
> LABEL=/var /var ext3 defaults 0 2
> LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
> LABEL=/var/mail /var/mail ext3 defaults 0 2
> LABEL=swap1 none swap sw 0 0
>
> Now the partitions and mount points get assigned correctly no matter
> which order the drives are assigned.
>
> The remaining problem is with the GRUB and the kernel. It was suggested
> that a LABEL specification be placed in the /boot/grub/menu.1st entry so
> that:
>
> # kopt=root=/dev/hda1 becomes
> # kopt=root=LABEL=/
>
> Using a LABEL in the Grub menu does not work because the kernel get
> confused:
>
> 1. If kopt=root=/dev/hda1 and the disk order changes to make
> the boot disk be /dev/hde, the boot process stops and drops
> into a prompt. I can unmount /boot, mount /boot on the
> correct drive, give a CTL-D to the prompt, and the system
> would continue to boot.
>
> 2. If kopt=root=LABEL=/, the boot process will stop and drop
> into a prompt WITHOUT /boot being mounted. I can mount
> /boot on the correct drive, give a CTL-D to the prompt,
> and the system will continue to boot.
>
> No where have I been able to find any documentation that shows that the
> Kernel boot command root= can have a LABEL specified.
>


# kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
network quiet

WFM

but you are still stuck with the GRUB root command, which does not
accept a label.
So I changed grub (0.97-29) to accept this:


find /ST380011A.03
root FILE=/ST380011A.03


and then where he finds file ST380011A.03 that is where the root will be.

Now I have a truly LABEL driven system and the drive devices can be
wherever they are and I don't care...

Hugo


> So, how do I make the kernel consistently detect and assign the disks in
> the correct order? Someone suggested the problem lies with UDEV and the
> parallel hardware detection process.
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Apr 07, 2008 at 02:44:44AM +1200, Chris Bannister wrote:
> On Sat, Apr 05, 2008 at 03:40:48PM -0700, Andrew Sackville-West wrote:

> > Fair enough. just a thought. BTW, it's darn hard to find your
> > responses with no whitespace around them...
>
> Someting like:
>
> color quoted blue white
> color quoted1 green white
> color quoted3 yellow white
> color signature red cyan
>
> Put them in a file, say colours (ok, probably colors if you insist. :-)
> Then something like
>
> source ~/configs/colors
>
> in your .muttrc
>
> I have attached my color file which is set up for black on white. I
> think it could have a better regexp for picking up urls though.

Still doesn't on my white-on-black VT520. A bit of white-space
(well, actually black-space) does .

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Apr 07, 2008 at 02:44:44AM +1200, Chris Bannister wrote:
> On Sat, Apr 05, 2008 at 03:40:48PM -0700, Andrew Sackville-West wrote:
> > On Sun, Apr 06, 2008 at 08:28:16AM +1000, Alex Samad wrote:
> > > On Sat, Apr 05, 2008 at 03:06:09PM -0700, Andrew Sackville-West wrote:
> > > > On Sat, Apr 05, 2008 at 02:14:17PM -0500, Butch Kemper wrote:
> > > [snip]>
> > > > >
> > > > > # kopt=root=/dev/hda1 becomes
> > > > > # kopt=root=LABEL=/
> > > >
> > > > I think Alex is right, that you should rebuild the initrd. But the
> > > > other thought that occurs to me is perhaps using "/" as a label
> > > > is a problem.
> >
> > > I have been using / as a label for a while with no problems
> >
> > Fair enough. just a thought. BTW, it's darn hard to find your
> > responses with no whitespace around them...
>
> Someting like:
>
> color quoted blue white
> color quoted1 green white
> color quoted3 yellow white
> color signature red cyan
>
> Put them in a file, say colours (ok, probably colors if you insist. :-)
> Then something like
>
> source ~/configs/colors
>
> in your .muttrc

yeah I use colou.rs in my mutt all the time, but like Doug says, a
little (white|black) space does wonders.
>
> I have attached my color file which is set up for black on white. I
> think it could have a better regexp for picking up urls though.
>
> --
> Chris.
> ======
>

> ## MUTT COLORS
> # valid colors : white, black, green, magenta,
> # blue, cyan, yellow, red,
> # Each color comes in plain (red) and bright (brightred)
> # color thisthing foreground background [arguments]
> color normal black white
> color attachment black cyan
its certainly better than doing this, even with colors...
> color hdrdefault cyan white
> color indicator black green
> color markers red white
> color index green white ~N # New
> color index magenta yellow ~T # Tagged
> color index black white ~D # Deleted
> color index blue white ~O # Old
> color index red white '~f cron'
> color index red white '~f Anacron'
> color index brightyellow black "~b '\ name.{0,9}\=.{2,30}\.zip'"
> color index red yellow '~f root'
> color quoted blue white
> color quoted1 green white
> color quoted2 magenta white
> color quoted3 yellow white

but I didn't know about the multiple levels of quoted coloring so
thanks for that!

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH+Xm1aIeIEqwil4YRAqX4AJ4+FZaIpEvRedH6be8WGW 85sHJIGwCg4MS+
DS0vVpi5Dd/MabOERTFq4kg=
=1tox
-----END PGP SIGNATURE-----

On Sun, Apr 06, 2008 at 01:54:24PM -0400, Douglas A. Tutty wrote:
> On Mon, Apr 07, 2008 at 02:44:44AM +1200, Chris Bannister wrote:
> > On Sat, Apr 05, 2008 at 03:40:48PM -0700, Andrew Sackville-West wrote:
>
> > > Fair enough. just a thought. BTW, it's darn hard to find your
> > > responses with no whitespace around them...
> >
> > Someting like:
> >
> > color quoted blue white
> > color quoted1 green white
> > color quoted3 yellow white
> > color signature red cyan
> >
> > Put them in a file, say colours (ok, probably colors if you insist. :-)
> > Then something like
> >
> > source ~/configs/colors
> >
> > in your .muttrc
> >
> > I have attached my color file which is set up for black on white. I
> > think it could have a better regexp for picking up urls though.
>
> Still doesn't on my white-on-black VT520. A bit of white-space
> (well, actually black-space) does .

you can use "mono" inplace of color and select underline, bold,
etc... man muttrc (just learned that myself).

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH+XrJaIeIEqwil4YRAgruAKDAiTLuG7MJk+Aox4zrmJ h3VAfeogCeI3ba
UYIPa/4fLVcx+SmNYTHkD14=
=e0xj
-----END PGP SIGNATURE-----

On Sun, Apr 06, 2008 at 06:37:14PM -0700, Andrew Sackville-West wrote:
> On Sun, Apr 06, 2008 at 01:54:24PM -0400, Douglas A. Tutty wrote:
>
> > Still doesn't on my white-on-black VT520. A bit of white-space
> > (well, actually black-space) does .
>
> you can use "mono" inplace of color and select underline, bold,
> etc... man muttrc (just learned that myself).
>

Yeah, I still haven't finished tweaking my .bashrc (or is it
..bash_profile) to get things tweaked based on TERM, since the VT is
connected to a P-II from whense I ssh into the AMD to run mutt.

Doug.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:
>Butch Kemper wrote:
>>Back in February, I asked a question about problems I was having
>>with the hard disks sequence flip-flopping when I would boot: disk
>>#1 would be hda and disk #2 would be hdc; or disk #1 would be hde
>>and disk #2 would be hda.
>>I receive answers about using labels with the partitions so, I
>>labeled the partitions and updated /etc/fstab. This is how things now look:
>> IDE #1 Partition Label Mount Point
>> 1 / /
>> 2 swap1 swap file
>> 3 /usr /usr
>> 4
>> 5 /usr/local /usr/local
>> 6 /var /var
>> IDE #2 Partition Label Mount Point
>> 1 /var/poptemp /var/poptemp
>> 2 /var/mail /var/mail
>>The /etc/fstab:
>># <file system> <mount point> <type> <options> <dump>
>><pass>
>>proc /proc proc defaults 0 0
>>LABEL=/ / ext3 defaults,errors=remount-ro 0 1
>>LABEL=/usr /usr ext3 defaults 0 2
>>LABEL=/usr/local /usr/local ext3 defaults 0 2
>>LABEL=/var /var ext3 defaults 0 2
>>LABEL=/var/poptemp /var/poptemp ext3 defaults 0 2
>>LABEL=/var/mail /var/mail ext3 defaults 0 2
>>LABEL=swap1 none swap sw 0 0
>>Now the partitions and mount points get assigned correctly no
>>matter which order the drives are assigned.
>>The remaining problem is with the GRUB and the kernel. It was
>>suggested that a LABEL specification be placed in the
>>/boot/grub/menu.1st entry so that:
>> # kopt=root=/dev/hda1 becomes
>> # kopt=root=LABEL=/
>>Using a LABEL in the Grub menu does not work because the kernel get confused:
>> 1. If kopt=root=/dev/hda1 and the disk order changes to make
>> the boot disk be /dev/hde, the boot process stops and drops
>> into a prompt. I can unmount /boot, mount /boot on the
>> correct drive, give a CTL-D to the prompt, and the system
>> would continue to boot.
>> 2. If kopt=root=LABEL=/, the boot process will stop and drop
>> into a prompt WITHOUT /boot being mounted. I can mount
>> /boot on the correct drive, give a CTL-D to the prompt,
>> and the system will continue to boot.
>>No where have I been able to find any documentation that shows that
>>the Kernel boot command root= can have a LABEL specified.
>
>
># kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
>network quiet
>
>WFM
>
>but you are still stuck with the GRUB root command, which does not
>accept a label.
>So I changed grub (0.97-29) to accept this:
>
>
>find /ST380011A.03
>root FILE=/ST380011A.03
>
>
>and then where he finds file ST380011A.03 that is where the root will be.
>
>Now I have a truly LABEL driven system and the drive devices can be
>wherever they are and I don't care...
>
>Hugo
>
>
>>So, how do I make the kernel consistently detect and assign the
>>disks in the correct order? Someone suggested the problem lies
>>with UDEV and the parallel hardware detection process.

Hugo,

I understand the "find" command and the results that it returns. But
I am unable to locate any mention of the "root" command having a
"FILE=" option.

So, did you modify Grub to make the "root" command have a FILE= parameter?

Butch


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Apr 06, 2008 at 09:50:24PM -0400, Douglas A. Tutty wrote:
> On Sun, Apr 06, 2008 at 06:37:14PM -0700, Andrew Sackville-West wrote:
> > On Sun, Apr 06, 2008 at 01:54:24PM -0400, Douglas A. Tutty wrote:
> >
> > > Still doesn't on my white-on-black VT520. A bit of white-space
> > > (well, actually black-space) does .
> >
> > you can use "mono" inplace of color and select underline, bold,
> > etc... man muttrc (just learned that myself).
> >
>
> Yeah, I still haven't finished tweaking my .bashrc (or is it
> .bash_profile) to get things tweaked based on TERM, since the VT is
> connected to a P-II from whense I ssh into the AMD to run mutt.

<cough>Rube<cough-cough>Goldberg<cough-cough-cough>



A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH+YUFaIeIEqwil4YRAsksAJ9p75Jtjl/QnE+DkRCFQ2yK8VJdfQCeMuSS
WO1c9lfzd9oAKt7kcsNmjjQ=
=2G1B
-----END PGP SIGNATURE-----

On Sun, Apr 06, 2008 at 07:20:53PM -0700, Andrew Sackville-West wrote:
> On Sun, Apr 06, 2008 at 09:50:24PM -0400, Douglas A. Tutty wrote:
> > On Sun, Apr 06, 2008 at 06:37:14PM -0700, Andrew Sackville-West wrote:
> > > On Sun, Apr 06, 2008 at 01:54:24PM -0400, Douglas A. Tutty wrote:
> > >
> > > > Still doesn't on my white-on-black VT520. A bit of white-space
> > > > (well, actually black-space) does .
> > >
> > > you can use "mono" inplace of color and select underline, bold,
> > > etc... man muttrc (just learned that myself).
> >
> > Yeah, I still haven't finished tweaking my .bashrc (or is it
> > .bash_profile) to get things tweaked based on TERM, since the VT is
> > connected to a P-II from whense I ssh into the AMD to run mutt.
>
> <cough>Rube<cough-cough>Goldberg<cough-cough-cough>

What, the Athlon doesn't have a spare serial port or a paralell port. I
need a backup box anyway, so it acts as a print server when I need to
print, and a terminal server when I need to access stuff from upstairs.
Saves me buying a USB/paralell and a USB/serial adapter. The Athlon's
one serial port is used to connect to my 3Com (USR) Courier V.Everything
external modem. The P-II is also located in the basement (since it
makes a lot of noise) while the VT520 is upstairs.

Unix terminal handling grew up where an individual user would have one
type of terminal, it doesn't have inherent abilities to adjust features
(e.g. colours) based on TERM. The only exceptions seem to be Lynx, Vim,
and partially mc (e.g. learn-keys gets save with TERM type).

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Butch Kemper wrote:
> At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:
>> Butch Kemper wrote:
>>> Back in February, I asked a question about problems I was having with
>>> the hard disks sequence flip-flopping when I would boot: disk #1
>>> would be hda and disk #2 would be hdc; or disk #1 would be hde and
>>> disk #2 would be hda.
>>> I receive answers about using labels with the partitions so, I
>>> labeled the partitions and updated /etc/fstab. This is how things
>>> now look:
>>> IDE #1 Partition Label Mount Point
>>> 1 / /
>>> 2 swap1 swap file
>>> 3 /usr /usr
>>> 4
>>> 5 /usr/local /usr/local
>>> 6 /var /var
>>> IDE #2 Partition Label Mount Point
>>> 1 /var/poptemp /var/poptemp
>>> 2 /var/mail /var/mail
>>> The /etc/fstab:
>>> # <file system> <mount point> <type> <options> <dump>
>>> <pass>
>>> proc /proc proc defaults
>>> 0 0
>>> LABEL=/ / ext3 defaults,errors=remount-ro
>>> 0 1
>>> LABEL=/usr /usr ext3 defaults
>>> 0 2
>>> LABEL=/usr/local /usr/local ext3 defaults
>>> 0 2
>>> LABEL=/var /var ext3 defaults
>>> 0 2
>>> LABEL=/var/poptemp /var/poptemp ext3 defaults
>>> 0 2
>>> LABEL=/var/mail /var/mail ext3 defaults
>>> 0 2
>>> LABEL=swap1 none swap sw
>>> 0 0
>>> Now the partitions and mount points get assigned correctly no matter
>>> which order the drives are assigned.
>>> The remaining problem is with the GRUB and the kernel. It was
>>> suggested that a LABEL specification be placed in the
>>> /boot/grub/menu.1st entry so that:
>>> # kopt=root=/dev/hda1 becomes
>>> # kopt=root=LABEL=/
>>> Using a LABEL in the Grub menu does not work because the kernel get
>>> confused:
>>> 1. If kopt=root=/dev/hda1 and the disk order changes to make
>>> the boot disk be /dev/hde, the boot process stops and drops
>>> into a prompt. I can unmount /boot, mount /boot on the
>>> correct drive, give a CTL-D to the prompt, and the system
>>> would continue to boot.
>>> 2. If kopt=root=LABEL=/, the boot process will stop and drop
>>> into a prompt WITHOUT /boot being mounted. I can mount
>>> /boot on the correct drive, give a CTL-D to the prompt,
>>> and the system will continue to boot.
>>> No where have I been able to find any documentation that shows that
>>> the Kernel boot command root= can have a LABEL specified.
>>
>>
>> # kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
>> network quiet
>>
>> WFM
>>
>> but you are still stuck with the GRUB root command, which does not
>> accept a label.
>> So I changed grub (0.97-29) to accept this:
>>
>>
>> find /ST380011A.03
>> root FILE=/ST380011A.03
>>
>>
>> and then where he finds file ST380011A.03 that is where the root will be.
>>
>> Now I have a truly LABEL driven system and the drive devices can be
>> wherever they are and I don't care...
>>
>> Hugo
>>
>>
>>> So, how do I make the kernel consistently detect and assign the disks
>>> in the correct order? Someone suggested the problem lies with UDEV
>>> and the parallel hardware detection process.
>
> Hugo,
>
> I understand the "find" command and the results that it returns. But I
> am unable to locate any mention of the "root" command having a "FILE="
> option.
>
> So, did you modify Grub to make the "root" command have a FILE= parameter?
>

Right. FIND saves where it found the file and root with FILE= uses that
saved info. So I don't have to specify absolute locations. I can send
the diff if you tell me where.

Hugo






--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hugo Vanwoerkom wrote:
> Butch Kemper wrote:
>> At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:
>>> Butch Kemper wrote:
>>>> Back in February, I asked a question about problems I was having
>>>> with the hard disks sequence flip-flopping when I would boot: disk
>>>> #1 would be hda and disk #2 would be hdc; or disk #1 would be hde
>>>> and disk #2 would be hda.
>>>> I receive answers about using labels with the partitions so, I
>>>> labeled the partitions and updated /etc/fstab. This is how things
>>>> now look:
>>>> IDE #1 Partition Label Mount Point
>>>> 1 / /
>>>> 2 swap1 swap file
>>>> 3 /usr /usr
>>>> 4
>>>> 5 /usr/local /usr/local
>>>> 6 /var /var
>>>> IDE #2 Partition Label Mount Point
>>>> 1 /var/poptemp /var/poptemp
>>>> 2 /var/mail /var/mail
>>>> The /etc/fstab:
>>>> # <file system> <mount point> <type> <options> <dump>
>>>> <pass>
>>>> proc /proc proc defaults
>>>> 0 0
>>>> LABEL=/ / ext3 defaults,errors=remount-ro
>>>> 0 1
>>>> LABEL=/usr /usr ext3 defaults
>>>> 0 2
>>>> LABEL=/usr/local /usr/local ext3 defaults
>>>> 0 2
>>>> LABEL=/var /var ext3 defaults
>>>> 0 2
>>>> LABEL=/var/poptemp /var/poptemp ext3 defaults
>>>> 0 2
>>>> LABEL=/var/mail /var/mail ext3 defaults
>>>> 0 2
>>>> LABEL=swap1 none swap sw
>>>> 0 0
>>>> Now the partitions and mount points get assigned correctly no matter
>>>> which order the drives are assigned.
>>>> The remaining problem is with the GRUB and the kernel. It was
>>>> suggested that a LABEL specification be placed in the
>>>> /boot/grub/menu.1st entry so that:
>>>> # kopt=root=/dev/hda1 becomes
>>>> # kopt=root=LABEL=/
>>>> Using a LABEL in the Grub menu does not work because the kernel get
>>>> confused:
>>>> 1. If kopt=root=/dev/hda1 and the disk order changes to make
>>>> the boot disk be /dev/hde, the boot process stops and drops
>>>> into a prompt. I can unmount /boot, mount /boot on the
>>>> correct drive, give a CTL-D to the prompt, and the system
>>>> would continue to boot.
>>>> 2. If kopt=root=LABEL=/, the boot process will stop and drop
>>>> into a prompt WITHOUT /boot being mounted. I can mount
>>>> /boot on the correct drive, give a CTL-D to the prompt,
>>>> and the system will continue to boot.
>>>> No where have I been able to find any documentation that shows that
>>>> the Kernel boot command root= can have a LABEL specified.
>>>
>>>
>>> # kopt=root=LABEL=wd80_0jd-60.05 ro noapic vga=791 apm=on ddcon=1
>>> network quiet
>>>
>>> WFM
>>>
>>> but you are still stuck with the GRUB root command, which does not
>>> accept a label.
>>> So I changed grub (0.97-29) to accept this:
>>>
>>>
>>> find /ST380011A.03
>>> root FILE=/ST380011A.03
>>>
>>>
>>> and then where he finds file ST380011A.03 that is where the root will
>>> be.
>>>
>>> Now I have a truly LABEL driven system and the drive devices can be
>>> wherever they are and I don't care...
>>>
>>> Hugo
>>>
>>>
>>>> So, how do I make the kernel consistently detect and assign the
>>>> disks in the correct order? Someone suggested the problem lies with
>>>> UDEV and the parallel hardware detection process.
>>
>> Hugo,
>>
>> I understand the "find" command and the results that it returns. But
>> I am unable to locate any mention of the "root" command having a
>> "FILE=" option.
>>
>> So, did you modify Grub to make the "root" command have a FILE=
>> parameter?
>>
>
> Right. FIND saves where it found the file and root with FILE= uses that
> saved info. So I don't have to specify absolute locations. I can send
> the diff if you tell me where.
>

The latest Sid i386 grub is 0.97-35.

I tried the patch and it fits.

Hugo

PS In grub2 you supposedly can do what the patch does with a script. But
I was unsuccessful in my grub2 install attempt so I gave up :-(












--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hugo Vanwoerkom wrote:
> Butch Kemper wrote:
>> At 11:17 AM 4/6/2008, Hugo Vanwoerkom wrote:
>>> Butch Kemper wrote:
>>>
hugo wrote

>>> but you are still stuck with the GRUB root command, which does not
>>> accept a label.
>>> So I changed grub (0.97-29) to accept this:
>>>
>>>
>>> find /ST380011A.03
>>> root FILE=/ST380011A.03
>>>
>>>
>>> and then where he finds file ST380011A.03 that is where the root
>>> will be.
>>>
>>> Now I have a truly LABEL driven system and the drive devices can be
>>> wherever they are and I don't care...
>>>
>>> Hugo
>>>
>>
>> Hugo,
>>
>> I understand the "find" command and the results that it returns. But
>> I am unable to locate any mention of the "root" command having a
>> "FILE=" option.
>>
>> So, did you modify Grub to make the "root" command have a FILE=
>> parameter?
>>
>
> Right. FIND saves where it found the file and root with FILE= uses
> that saved info. So I don't have to specify absolute locations. I can
> send the diff if you tell me where.
>
> Hugo
>

> i'll remember this one! learned something nifty again.
thanks, lads,

steef


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Apr 06, 2008 at 01:54:24PM -0400, Douglas A. Tutty wrote:
> On Mon, Apr 07, 2008 at 02:44:44AM +1200, Chris Bannister wrote:
> > On Sat, Apr 05, 2008 at 03:40:48PM -0700, Andrew Sackville-West wrote:
>
> > > Fair enough. just a thought. BTW, it's darn hard to find your
> > > responses with no whitespace around them...
> >
> > Someting like:
> >
> > color quoted blue white
> > color quoted1 green white
> > color quoted3 yellow white
> > color signature red cyan
> >
> > Put them in a file, say colours (ok, probably colors if you insist. :-)
> > Then something like
> >
> > source ~/configs/colors
> >
> > in your .muttrc
> >
> > I have attached my color file which is set up for black on white. I
> > think it could have a better regexp for picking up urls though.
>
> Still doesn't on my white-on-black VT520. A bit of white-space
> (well, actually black-space) does .

Just change the default colour, if you want white on black, of course be
careful of any existing "black on white" settings.

--
Chris.
======
If you are not subscribed, ask to be CC'd as the Policy of this list is
to reply to the list only.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Douglas A. Tutty <dtutty@porchlight.ca>:
> On Mon, Apr 07, 2008 at 02:44:44AM +1200, Chris Bannister wrote:
> > On Sat, Apr 05, 2008 at 03:40:48PM -0700, Andrew Sackville-West wrote:
> > >
> > > Fair enough. just a thought. BTW, it's darn hard to find your
> > > responses with no whitespace around them...
> >
> > color signature red cyan
> >
> > source ~/configs/colors
> >
> > I have attached my color file which is set up for black on white. I
> > think it could have a better regexp for picking up urls though.
>
> Still doesn't on my white-on-black VT520. A bit of white-space
> (well, actually black-space) does .

# --------------------------------------------------
# my colors ("xterm -fg wheat -bg black -e mutt").
#
color normal white black # pager body
color indicator white red
color status black cyan
color hdrdefault cyan black
color header magenta black ^From:
color header red black ^To:
color header red black ^Reply-To:
color header red black ^Cc:
color header brightred black ^Subject:
color header yellow black ^Received:
# color body brightred black [\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+
# color body brightblue black (http|ftp)://[\-\.\,/%~_:?\#a-zA-Z0-9]+
#
# sbk - from comp.mail.mutt:
# Highlights inside the body of a message.
#
color body brightred default \
"((ftp|http|https)://|(file|mailto|news):|www\\.)[-a-z@0-9_.:]*[a-z0-9](/[^][{} \t\n\r\"<>()]*[^][{} \t\n\r+\"<>().,:])?"
color body magenta black "mailto:[-a-z_0-9.]+@[-a-z_0-9.]+"
color body magenta black "news:[^ \">\t\r\n]*"
color body magenta black "[-a-z_0-9.%$]+@[-a-z_0-9.]+\\.[-a-z][-a-z]+"
#
# Various smilies and the like
#
color body brightgreen black "<[Gg]>" # <g>
color body brightgreen black "<[Bb][Gg]>" # <bg>
color body brightgreen black " [;:]-*[)>(<|]" # :-) etc...
# color body magenta black "\\*[A-Za-z]+\\*" # *Bold* text.
color body brightblue black "\\*[^\*]+\\*" # *Bold* text.
#
color quoted green black
color attachment yellow black
color signature magenta black
color tree brightred black
color tilde magenta black
color markers red black
# --------------------------------------------------



--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org