I just installed 12.0 and upgraded to current on a thinkpad laptop.
When log in as root, after the mail check and fortune message, the console gives me:

-bash: /bin: is a direcrory
-bash: */: No such file or directory

and then follows PS1.

When as a normal user log in, the console gives me:

-bash: /bin: is a direcrory
-bash: bin/: is a direcrory

and then follows PS1.

All things I did were installation, upgrading(used slackpkg, and overwrite old files), then removed *.orig files.
I also checked /etc/profile, /etc/login.defs, etc. files, and searched the web, found nothing

Could anyone please guide me?
Thanks~

first question: What's the reason for you to upgrade to -Current?
It's a development phase, where things might get broken and you should be prepared to fix things on your own risk

second question: what package did you install? (can you list them?)

My advice: check your .bashrc and .bash_profile (if any)

Hi,

A lot of people just don't read;

It's not called bleeding edge for nothing!

Yeah, I know.
I'd like to keep the newest things, so upgraded to current.

I followed these two guides, exactly.
ftp://ftp.slackware.com/pub/slackwar...nt/UPGRADE.TXT
ftp://ftp.slackware.com/pub/slackwar..._AND_HINTS.TXT

But under /root/ there is neither .bashrc nor .bash_profile, .profile.
I checked the login process scripts, found nothing.
There must be something missing.

There's neither .bashrc nor .bash_profile under /root/ or ~/ ... in a default Slackware install, unless you create them.

Perhaps offering some factual, or technical, help is better than offering unfounded criticism. This is FUD, eh?

There's nothing wrong, IMO, with running -current if you want to test software, and/or help Pat. My test box triple boots Slackware-current, Slackware-stable, and one of those poorly coded OSes from Washington, USA. Some people complain when software isn't updated as soon as they prefer in Slackware, but never do one thing to help debug or build new software.

Cherife, I don't have any answers. I have one Slackware machine running -current. The way I install is to rsync -current from Oregon State University Open Source Lab to my server, then I use the Slackware-stable CD1 to boot the computer and do a network install.

You would need a little less than 4 GB area to save -current. If you have a fileserver you can use, I'll give you a script to rsync -current. If you don't have a server, but have the space available, you can rsync -current and make CD/DVD iso images, then burn whichever one you need. Either way, you're probably better off with a fresh install of -current. For this test box, I don't even use the ~/. files from my previous install.

My present Slackware -current machine is the latest, as of Wed Nov 21 00:11:24 CST 2007. I've not had that issue with BASH -- the only problem is that KDE crashes every time it's shutdown, but that doesn't seem to effect anything else, and is the type of thing I've come to expect from KDE.

Thanks, Bruce.

Finally, I found it is my fault, sorry to post this before completely checking.

I added
to /etc/profile.d/lang.sh and didn't notice "/*","*/"

Sorry guys

me too are running -Current both on my laptop and desktop and i never had this bash problem before and it's quite stable for me (well, up to now)