Board index Freebsd

Installation Glitches

Installation Glitches

Post by chris31 » Tue, 29 Apr 2003 16:09:44



I'm having some issues while doing a post-install configuration while logged in
as root. I decided to use the RTFM approach and here are the results:

Trying to configure the XFree86 server using the "Fully graphical XFree86
configuration tool" -- I decide to accept the default settings for now. On page
71 of "The FreeBSD Handbook", 2nd ed., item 7 says "Testing the Server -- Verify
all the settings once again and select Done ...". "Done" -- right -- there's
"Configure Layout", "Expert Mode", "Layout", "Help" and "Quit", but no "Done".
For lack of a "Done" I click "Quit" and instead of the promised server test I am
greeted with two offers to write the configuration file, to which I click "Yes".
We exit the GUI and are greeted with the cheery message, "The XFree86
configuration process seems to have failed. Would you like to try again?" WTF?
The same message greets me after using the ncurses tool. After three or four
go-rounds we get the idea that this isn't working.

OK let's leave the XFree86 server alone for now, perhaps the defaults will see
us through. How about setting KDE as the default desktop. How challenging can
this be -- after all, computers have been booting into GUIs for 20 years now?
RTFM tells us on page 139, "After KDE2 has been installed, the X server must be
told to launch this application instead of the default window manager. This is
acomplished by editing the .xinitrc file: # echo "/usr/X11R6/bin/startkde" >
-/.xinitrc". The response: "-/.xinitrc: No such file or directory".

Other than the above issues, FreeBSD is a terrific OS and the RTFM approach
works every time.

 
 
 
Top

Installation Glitches

Post by Erik Nygre » Tue, 29 Apr 2003 17:13:17


...
Quote:> acomplished by editing the .xinitrc file: # echo "/usr/X11R6/bin/startkde" >
> -/.xinitrc". The response: "-/.xinitrc: No such file or directory".

you mistake ~ (tilde) to a - (minus). Try this instead:
  cd
  echo "/usr/X11R6/bin/startkde" > .xinitrc
And I'm sure startx will run kde for you.

Quote:> Other than the above issues, FreeBSD is a terrific OS and the RTFM approach
> works every time.

Well, not perfect, but very good.

--
Erik Nygren
e r i k { a t } s w i p { d o t } n e t
Linux - If you hate Microsoft, FreeBSD - If you love Unix

 
 
 
Top

Installation Glitches

Post by chris31 » Tue, 29 Apr 2003 17:55:04


Quote:>you mistake ~ (tilde) to a - (minus). Try this instead:
>  cd
>  echo "/usr/X11R6/bin/startkde" > .xinitrc
>And I'm sure startx will run kde for you.

That's one helluva small tilde. I'll try that.

Quote:> Other than the above issues, FreeBSD is a terrific OS and the RTFM approach
> works every time.

>Well, not perfect, but very good.

Erik - turn on your sarcasm detector :-)
 
 
 
Top

Installation Glitches

Post by Helmut Schellon » Tue, 29 Apr 2003 19:07:56



> We exit the GUI and are greeted with the cheery message, "The XFree86
> configuration process seems to have failed. Would you like to try again?" WTF?
> The same message greets me after using the ncurses tool. After three or four
> go-rounds we get the idea that this isn't working.

You can safely ignore these messages.

sysinstall:
-----------
BUGS
      This utility is a prototype which lasted several years past its expira-
      tion date and is greatly in need of death.

AUTHORS

HISTORY
      This version of sysinstall first appeared in FreeBSD 2.0.

--
Mit freundlichen Gr?en


http://www.wikiservice.at/dse/wiki.cgi?FreeBSD

 
 
 
Top

Installation Glitches

Post by chris31 » Tue, 29 Apr 2003 20:57:20


Quote:> -/.xinitrc". The response: "-/.xinitrc: No such file or directory".
>you mistake ~ (tilde) to a - (minus). Try this instead:
>  cd
>  echo "/usr/X11R6/bin/startkde" > .xinitrc
>And I'm sure startx will run kde for you.

I tried it. I was able to start KDE before with startx but now it won't start at
all. I get:

cat: /root/.Xauthority: No such file or directory
/root/.xinitrc: /usr/X11R6/bin/startkde: not found

 
 
 
Top

Installation Glitches

Post by Us » Tue, 29 Apr 2003 23:17:47


On Mon, 28 Apr 2003 04:57:20 -0700


> > -/.xinitrc". The response: "-/.xinitrc: No such file or directory".

> >you mistake ~ (tilde) to a - (minus). Try this instead:
> >  cd
> >  echo "/usr/X11R6/bin/startkde" > .xinitrc
> >And I'm sure startx will run kde for you.

> I tried it. I was able to start KDE before with startx but now it
> won't start at all. I get:

> cat: /root/.Xauthority: No such file or directory
> /root/.xinitrc: /usr/X11R6/bin/startkde: not found

I think you were misinformed. It should read "exec startkde". That is
all I have in my .xinitrc and .xsessionrc (one is a ln -s of another)

--
Us
-----
All trespassers will be shot,
survivers will be shot again.

 
 
 
Top

Installation Glitches

Post by Lowell Gilber » Tue, 29 Apr 2003 23:25:45



> > -/.xinitrc". The response: "-/.xinitrc: No such file or directory".

> >you mistake ~ (tilde) to a - (minus). Try this instead:
> >  cd
> >  echo "/usr/X11R6/bin/startkde" > .xinitrc
> >And I'm sure startx will run kde for you.

> I tried it. I was able to start KDE before with startx but now it won't start at
> all. I get:

> cat: /root/.Xauthority: No such file or directory
> /root/.xinitrc: /usr/X11R6/bin/startkde: not found

Start with the obvious: is the executable there?

("ls /usr/X11R6/bin/startkde")

 
 
 
Top

Installation Glitches

Post by chris31 » Wed, 30 Apr 2003 02:03:42


Quote:>sysinstall:
>-----------
>BUGS
>      This utility is a prototype which lasted several years past its expira-
>      tion date and is greatly in need of death.

Let's just say I haven't thrown away my Mandrake CDs.
 
 
 
Top

Installation Glitches

Post by Us » Wed, 30 Apr 2003 17:52:50


On Mon, 28 Apr 2003 14:25:45 GMT



> > > -/.xinitrc". The response: "-/.xinitrc: No such file or
> > > directory".

> > >you mistake ~ (tilde) to a - (minus). Try this instead:
> > >  cd
> > >  echo "/usr/X11R6/bin/startkde" > .xinitrc
> > >And I'm sure startx will run kde for you.

> > I tried it. I was able to start KDE before with startx but now it
> > won't start at all. I get:

> > cat: /root/.Xauthority: No such file or directory
> > /root/.xinitrc: /usr/X11R6/bin/startkde: not found

> Start with the obvious: is the executable there?

> ("ls /usr/X11R6/bin/startkde")

I have it in /usr/local/bin/startkde
 
 
 
Top

Installation Glitches

Post by Lowell Gilber » Fri, 02 May 2003 03:45:23



> On Mon, 28 Apr 2003 14:25:45 GMT


> > > > -/.xinitrc". The response: "-/.xinitrc: No such file or
> > > > directory".

> > > >you mistake ~ (tilde) to a - (minus). Try this instead:
> > > >  cd
> > > >  echo "/usr/X11R6/bin/startkde" > .xinitrc
> > > >And I'm sure startx will run kde for you.

> > > I tried it. I was able to start KDE before with startx but now it
> > > won't start at all. I get:

> > > cat: /root/.Xauthority: No such file or directory
> > > /root/.xinitrc: /usr/X11R6/bin/startkde: not found

> > Start with the obvious: is the executable there?

> > ("ls /usr/X11R6/bin/startkde")

> I have it in /usr/local/bin/startkde

Then obviously your startfile will have to specify that path instead
of /usr/X11R6...
 
 
 
Top

Installation Glitches

Post by Us » Tue, 06 May 2003 17:43:58


On Wed, 30 Apr 2003 18:45:23 GMT



> > On Mon, 28 Apr 2003 14:25:45 GMT


> > > > > -/.xinitrc". The response: "-/.xinitrc: No such file or
> > > > > directory".

> > > > >you mistake ~ (tilde) to a - (minus). Try this instead:
> > > > >  cd
> > > > >  echo "/usr/X11R6/bin/startkde" > .xinitrc
> > > > >And I'm sure startx will run kde for you.

> > > > I tried it. I was able to start KDE before with startx but now
> > > > it won't start at all. I get:

> > > > cat: /root/.Xauthority: No such file or directory
> > > > /root/.xinitrc: /usr/X11R6/bin/startkde: not found

> > > Start with the obvious: is the executable there?

> > > ("ls /usr/X11R6/bin/startkde")

> > I have it in /usr/local/bin/startkde

> Then obviously your startfile will have to specify that path instead
> of /usr/X11R6...

No problem, mine works from the start. What's with the "exec" in front
of the startkde command? Is that mandatory?
 
 
 
Top

Installation Glitches

Post by Lowell Gilber » Tue, 06 May 2003 23:46:18



> No problem, mine works from the start. What's with the "exec" in front
> of the startkde command? Is that mandatory?

It's a little more efficient, that's all; it replaces the current
process completely, instead of calling the command within the current
environment.  
 
 
 
Top

1. DosLinux installation glitches -- and workarounds

This is about the new Doslinux distribution created by Kent Robotti.

Unlike the UMSDOS version you may have heard about, the latest one uses the
loopback device to access an "image" file.  The image file is a true e2fs
filesystem that appears as a single large file to DOS.  Much cleaner than
the -LINUX---.--- "magic directory" approach taken by UMSDOS, though it does
require you to stake a claim up front for all the space you'll ever want.

I ran into one setup problem, and thought I should share the workaround for
it.

After you run "setup" you'll run a routine called "looplinux" which  will
prompt for "Your DOS or Win95/98 directory".  When it prompted me to enter
/dev/???? I thought that only the four ???? were significant -- wrong! It
wants you to type the complete device name *including* the leading "/dev/"
-- the first time this happened, I entered just the "hda1" and got a kernel
panic.  It was pretty obvious, though, since the kernel was trying to mount
"hda1" and not finding any such device.

I ran "setup" and "looplinux" from my E: drive, but even though I entered
"/dev/hda6" it still reported the free space on my /dev/hda1 (C:) drive --
AND that is where it built the image file.  "This is bad news," I thought.  
Then when I tried to boot it, the kernel panic message told me it WAS trying
to mount /dev/hda6 as I had specified!  So the looplinux routine was using
my input when configuring the initial ramdisk, but it wasn't taking it into
account when building the filesystem image.

Tell looplinux to use the drive you really want, then exit to DOS and use
the MOVE command to move DOSLINUX.IMG from C:\DOSLINUX\SYSTEM to
E:\DOSLINUX\SYSTEM (or whatever drive you really wanted).  Yes, it works!

I was lucky to have enough space on my C: drive to create the image file as
large as I wanted it -- if you were trying to put it onto a system that was
tight for space on its C: drive, you'd be out of luck for now.  But it looks
like a fairly minor tweak to the looplinux routine will fix that.  I hasten
to add, both the kernel and the strange new "loop" filesystem are working
just fine!

I disagree strongly with those who say that Doslinux isn't "worth the
hassle."  If you have a notebook or other system that you've never had the
nerve to reformat for e2fs, you really ought to give Doslinux a try.

ftp://wauug.erols.com/pub/tux/robotti/doslinux

2. where can I customerize the environment variable for root

3. Help - small but annoying glitches in my XFree installation

4. YGGDRASIL Summer 94 - Plug 'n Play my BUTT!

5. Linux - Poster child for security glitches

6. pppoe-1.8 from Roaring Penghin

7. $PATH glitch? -- Gould Powernode

8. HELP: 2.0.4 / PPro ps2 mouse problem

9. Glitches in XF3.2 S3 server

10. EPOX 8RDA+ audio glitches

11. Video glitch with Gnome xterm

12. New: Keyboard glitch detected, ignoring keypress

13. There's a little glitch in the binary of emacs in SLS


All times are UTC
Board index