9:58 a.m.
Hi,
Why doesn't .bash_profile work in Fedora Core 1?
When I log into a console, neither .bash_profile or .bashrc works.
How can I enable this?
best regards,
Bart
==============================================================================
NOTICE - This communication may contain confidential and privileged
information that is for the sole use of the intended recipient. Any viewing,
copying or distribution of, or reliance on this message by unintended
recipients is strictly prohibited. If you have received this message in
error, please notify us immediately by replying to the message and deleting
it from your computer.
==============================================================================
11:56 a.m.
On Thursday 11 December 2003 15:58, Bart.Wille(a)jacobs.com wrote:
Hi,
Why doesn't .bash_profile work in Fedora Core 1?
When I log into a console, neither .bash_profile or .bashrc works.
How can I enable this?
best regards,
Bart
Bart,
I just tried a quick test here and it seems to work both logging into a
new console via <ctrl><alt><f1> or simply opening up a new new KDE
konsole session in a current login. I simply added a new alias:
alias less='le'
to .bashrc as a test while logged in as root and the new alias was
working in either of the methods used above. Perhaps we need to know
more about your setup and what you're doing?
Regards, Mike Klinke
11:56 a.m.
El jue, 11-12-2003 a las 16:58, Bart.Wille(a)jacobs.com escribió:
I don't know it works on my Laptop?.... What you want to do?
Hi,
Why doesn't .bash_profile work in Fedora Core 1?
When I log into a console, neither .bash_profile or .bashrc works.
How can I enable this?
best regards,
Bart
==============================================================================
NOTICE - This communication may contain confidential and privileged
information that is for the sole use of the intended recipient. Any viewing,
copying or distribution of, or reliance on this message by unintended
recipients is strictly prohibited. If you have received this message in
error, please notify us immediately by replying to the message and deleting
it from your computer.
==============================================================================
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
________________________________________________________________________
José Salgado
http://www.saladelfrio.com
Una web que ya no se ni porque la hice, pero ahí está.
3:48 a.m.
New subject: Old kernel loads instead of updated one
After installing new kernel, kernel-2.4.22-1.2129.nptl.athlon Fedora is
still booting the kernel-ntfs-2.4.22-1.2115.nptl kernel. After reboot
the up2date still says I need to reboot. I have uninstalled the new
kernel and reinstalled it several times all with the same results. The
new kernel is not even given as an option during boot.
Using MSI K7N2G w/ Athlon 2600, 512 SDRAM, Adaptec 2940UW and 2 WD
Enterprise drives.
6:33 a.m.
New subject: Old kernel loads instead of updated one
On Saturday 13 December 2003 09:48, Tom Gibbs wrote:
After installing new kernel, kernel-2.4.22-1.2129.nptl.athlon Fedora
is
still booting the kernel-ntfs-2.4.22-1.2115.nptl kernel.
You probably should edit /etc/grub.conf .
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
10:22 a.m.
New subject: Old kernel loads instead of updated one
On Sat, 2003-12-13 at 12:33, Timothy Murphy wrote:
On Saturday 13 December 2003 09:48, Tom Gibbs wrote:
> After installing new kernel, kernel-2.4.22-1.2129.nptl.athlon Fedora is
> still booting the kernel-ntfs-2.4.22-1.2115.nptl kernel.
You probably should edit /etc/grub.conf .
That should be /boot/grub/grub.conf
Look for the line near the top:
default=0 (or whatever)
Underneath this you'll see a section beginning something like:
title Fedora Core 1 (kernel-xxx.xx....)
root (hdx,x)
kernel ....
initrd ....
title Fedora Core 1 (kernel-yyy.yy...)
etc
etc
The first title section will be loaded automatically if you have
default=0, the second if you have default=1, etc.
You'll probably find the new kernel has inserted itself into first
place, so you just need to set default=0
Hope this helps,
Andy
10:54 a.m.
New subject: Old kernel loads instead of updated one
On Saturday 13 December 2003 16:22, Andy Wallace wrote:
On Sat, 2003-12-13 at 12:33, Timothy Murphy wrote:
> On Saturday 13 December 2003 09:48, Tom Gibbs wrote:
> > After installing new kernel, kernel-2.4.22-1.2129.nptl.athlon
> > Fedora is still booting the kernel-ntfs-2.4.22-1.2115.nptl
> > kernel.
> >
> >The new kernel is not even given as an option
> >during boot.
>
> You probably should edit /etc/grub.conf .
That should be /boot/grub/grub.conf
Either will work as it's they're linked:
16:27:55 # ll /etc/grub.conf
lrwxrwxrwx /etc/grub.conf -> ../boot/grub/grub.conf
You'll probably find the new kernel has inserted
itself into first place, so you just need to set
default=0
This isn't likely to help since Tom noted above that the new kernel
wasn't even listed as an option when he rebooted.
Tom, when you updated did you "update", "freshen", or
"install" the
new kenel? Only the last, "install" will give you an additional entry
in your boot loader, as the other two will simply replace your running
kernel with the new one.
What is the output of "uname -a"?
What is the output of "rpm -qa | grep kernel"?
What does the listing of /boot look like?
Regards, Mike Klinke
11:56 p.m.
New subject: Old kernel loads instead of updated one
Guys,
In my impatience, I thought maybe there was some connection between the
kernel and the nvidia drivers. So I installed all the .2129 nvidia
stuff. This effectively killed the system with a half dozen errors on
boot up.
Now get this, since I also have 2 IDE drives attached with an old
install of Fedora, I set the BIOS to boot off the IDE drive instead of
the SCSI I was working on. Amazingly (explain this if you can) the
system still booted on the SCSI drive but the update was now intact and
it loaded everything beautifully and everything works.
I can mount the IDE drives but the system insists on booting from the
SCSI, even though BIOS tells it to do otherwise.
So now, /boot (on the SCSI) has all the .2129 files the way it's
supposed to. Before, /boot had all .2115 files. And /boot on the IDE
drive is now totally empty.
I suppose there is reason the IDE /boot dir is empty but why the SCSI
miraculously fixed itself is a mystery to me.
Thanks for replies.
5:02 a.m.
On Thu, 11 Dec 2003 Bart.Wille(a)jacobs.com wrote:
Why doesn't .bash_profile work in Fedora Core 1?
When I log into a console, neither .bash_profile or .bashrc works.
How can I enable this?
As other have stated 'it works for us'.
How do you log into a console?
First make sure that bash is the shell invoked for you. It will
be in your passwd line, or you can see it with ps. Other shells
might be sh, ksh, csh, zsh, tcsh. The text file /etc/shells
contains a list of shell that tools will install or you as a user
can switch too with the "chsh" (change shell) command. Root can
make anything your shell.
The command 'ps' should tell you which shell you have active.
Looks like:
$ ps
PID TTY TIME CMD
21497 pts/0 00:00:00 bash
21795 pts/0 00:00:00 ps
Next if you are running bash read the man page (man bash) and
look at the the INVOCATION section and note the difference
between a login shell, interactive shell, non-interactive shell.
One key to understanding is that subshells inherit variables and
state from the parent so the reading of 'dot' files is altered.
Next note that in an X window system the way a terminal emulator
is launched is different than if you login without X or use ssh,
telnet or another way in.
Also pay attention to the 'terminal' you use. There are multiple
choices, xterm, kterm, gnome-terminal, bsod, konsole and more.
Each has different invocations that might interact with your
chosen shell.
--
T o m M i t c h e l l
mitch48 -a*t- yahoo-dot-com
8:51 a.m.
On Sun, 2003-12-14 at 05:02, Tom Mitchell wrote:
The command 'ps' should tell you which shell you have active.
Looks like:
$ ps
PID TTY TIME CMD
21497 pts/0 00:00:00 bash
21795 pts/0 00:00:00 ps
ps shows all your active shells, so it could show bash, csh, and more if
you're running multiples.
Check your current shell by entering `echo $0` at a console.
You might try placing some echo commands in your .bash_profile and
.bashrc files then re-sourcing them (`source ~/.bashrc`) to double-check
for typos.
Also double-check to see whether /etc/bashrc is overriding something you
put into ~/.bashrc. This assumes that the last thing your ~/.bashrc does
is to source /etc/bashrc.
HTH,
Paul
7478
days inactive
7481
days old
9 comments
8 participants
participants (8)
-
Andy Wallace -
Bart.Wille＠jacobs.com -
Listas -
Mike Klinke -
Paul Morgan -
Timothy Murphy -
Tom Gibbs -
Tom Mitchell