Search Results for 'startx'

antiX Core Plus Just Enough X – a recipe

A step-by-step tutorial of my way of building an antiX system from a core-ISO install with just the programs I find “essential” — including the X Window System. I thought it would be good to compile a complete basic setup “recipe” in one post. (Note that many of these directions were gleaned from others on this forum.) If desired, one can use this as a guide to begin a similar project. My entire used hard disk space is 2.12 GB.

1. Preparation:
I chose an antiX 17.4.1 core-ISO installation (the latest core version as of this writing), because my target computer is a quite old 32-bit netbook, and I wanted to squeeze every little bit of performance out of it. After installing, I set up the WIFI through Ceni, then upgraded the software through apt-get upgrade. If you are playing with core, I assume you know how to do this. (If not, then please check out the fantastic antiX FAQs. 🙂 )

2. Installing the software:
The list, and the “why:”

xserver-xorg-legacy
# base x package for antiX

xserver-xorg-video-intel
# my netbook’s specific video server

xserver-xorg-video-vesa
# generic fall-back video server

xserver-xorg-input-all
# input for all mouse, keyboard, etc

conky-legacy-all
# I need conky to enjoy my system!

pmount
# mounts usb drives, etc by normal user

jwm
# minimalistic window manager

file-roller
# handles compressed archive files

rox-filer
# file manager & launcher panel

xinit
# starts X window system

lxterminal
# terminal for X

geany
# text editor

ufw
# firewall – set it & forget it

gexec gksu
# easy way to start apps as root

lxappearance
# change the desktop theme

firefox-esr
# my favorite web browser

qpdfview
# pdf reader for my books

dosbox pysolfc
# my bare-essential games

smtube mpv
# view you tube videos without ads

volumeicon-alsa-legacy
# tray icon to easily control sound volume

blackbird-gtk-theme
# the only theme I want, to make my system enjoyable

mirage
# simple image viewer, to chose icons & wallpaper

So run the following command (with a space separating each package):
sudo apt install xserver-xorg-legacy xserver-xorg-video-intel xserver-xorg-video-vesa xserver-xorg-input-all conky-legacy-all pmount jwm file-roller rox-filer xinit lxterminal geany ufw gexec gksu lxappearance firefox-esr qpdfview dosbox pysolfc smtube mpv blackbird-gtk-theme volumeicon-alsa-legacy mirage

This takes about 1 GB of space.

3. Editing the configuration (text) files, preparing the system:
For each of these first two files, start up the nano editor as root.

a. This gives your normal user privilages to run X:
sudo nano /etc/X11/Xwrapper.config
1. Add the following line at the bottom of the file:
needs_root_rights=yes
2. Save (Ctrl+O),then exit (Ctrl+X)

b. This logs you in automatically (without any desktop manager), so bootup to your X desktop is hassle-free, light & quick:
sudo nano /etc/inittab
1. find this line & comment it out (put a # in front of the line):
1:2345:respawn:/sbin/getty --noclear 38400 tty1
2. add this line directly after it (substituting “demo” with your user name):
1:2345:respawn:/bin/login -f demo tty1 </dev/tty1 >/dev/tty1 2>&1
3. Save (Ctrl+O),then exit (Ctrl+X)

For each of these last two files, start up the nano editor as your regular user.

c. This starts X automatically
nano ~/.profile
1. at the bottom of file, add a new line with this command:
startx
2. Save (Ctrl+O),then exit (Ctrl+X)
(NOTE: doing this does not allow for loging into a different virtual terminal without running X if you use ctl+alt+Fx, unless you first comment-out this addition.)

d. Copy the window manager configuration file to your home directory for editing:
cp /etc/jwm/system.jwmrc ~/.jwmrc
Edit the ~/.jwmrc file:
nano ~/.jwmrc
NOTE: The .jwmrc file is kind of hard to follow, but hopefully this will serve the purpose if I mention the editing highlights:

1. Comment-out this line with the “arrows” <!-- & --> like this:

<!-- <Include>/etc/jwm/debian-menu</Include> -->

2. Fix the terminal launcher by changing xterm to lxterminal:
<Program icon="terminal.png" label="Terminal">lxterminal</Program>

3. I erased the other default launchers but added shutdown options after the logout command. I’ll use the
ROX panel to launch my apps:

			<Program label="Reboot">sudo reboot</Program>
			<Program label="Poweroff">sudo poweroff</Program>

4. Add startup commands – these start automatically with Jwm: the ROX panel to launch programs, conky
system monitor, and the volume icon to adjust sound volume:

		    <!-- StartupCommands -->
			<StartupCommand>rox --top=PANEL</StartupCommand>
			<StartupCommand>conky</StartupCommand>
			<StartupCommand>volumeicon</StartupCommand>

5. Backgrounds & desktops – different background for each desktop
example:

		<Desktops width="2" height="1">
			<Desktop><Background type="image">/home/demo/wallpaper/black.jpg</Background> 1</Desktop>
			<Desktop><Background type="image">/home/demo/wallpaper/blue.jpg</Background> 2</Desktop>
		</Desktops>

6. Save (Ctrl+O),then exit (Ctrl+X)
[You’ll have to add your wallpaper files later; you’ll have a plain black background until you do.]

4. Reboot the system (ctrl+alt+del) or type at the console: sudo reboot. This will bring up the system directly to your X Window Jwm desktop. Ready for tweaking.

5. Further steps – playing with your desktop environment:
1. Set up ROX panel — drag & drop files ending in .desktop from /usr/share/applications to the panel.

2. Set up geany to open text files by default — in rox, right click “Set Run Action…” & drag a “.txt” file to the window that opens – or type geany in at the beginning of the bottom text field.

3. Edit conky to display what you like to see on your desktop (use geany to edit ~/.conkyrc — remember that files starting with “.” are hidden).

4. Make “.desktop” files (for the ROX panel) for apps that don’t already have them — copy a file ending in .desktop from /usr/share/applications to ~/.local/share/applications – & edit it with geany to make launchers for them — that is, edit & save-as gexec.desktop, pmrp.desktop, etc.

5. To give certain folders their own distinctive icon, copy your choice of icon (& rename) to “.DirIcon” in a rox folder to change the display icon in ROX panel & rox-filer for that folder.

6. Mount removeable devices with pmount – mounts removable drives to /media – to add your documents, media files, wallpapers, etc.
Use terminal (or gexec.dektop from ROX panel) as your normal user:
a. pmount /dev/sdb1 #mounts drive to /media/sdb1
b. pumount /dev/sdb1 #unmounts drive from /media/sdb1 (& removes /media/sdb1 folder)

7. Execute lxappearance.desktop in /usr/share/applications to use that blackbird theme. 😉

Enjoy the adventure!

• This topic was modified 3 years, 7 months ago by christophe.
• This topic was modified 3 years, 7 months ago by christophe.
• This topic was modified 3 years, 7 months ago by christophe. Reason: added code notations

Attachments:

1. 

   2019-09-29-113831_1024x600_scrot.png
   

1. conky.txt
2. desktop.txt

confirmed antiX frugaler, since 2019

[Member eugen-b]

A good solution and it worked with btrfs-lzo: https://hastebin.com/ubuxunayud.php (complete output after finished installation https://hastebin.com/pedicomulo.php )
(Maybe you can break up (or even parallelize) the long cp command at the end of the pastebin smaller, because it is filling up RAM quite a bit.)
But the mount option compress-force=lzo doesn’t get applied during installation:

demo@antix1:~                                                                                                                                      
$ mount | grep btrfs
/dev/sdc1 on /mnt/antiX type btrfs (rw,noatime,space_cache,subvolid=5,subvol=/)

Are mount options meant to be written only to fstab? I think not looking at the source code. EDIT: The compress-force=lzo doesn’t even get written to the target /etc/fstab only defaults,noatime so there must be another bug in the code.

I would recommend against compress-force, because it takes longer on slow machines and gains little, just use compress=lzo or zlib.

A dirrefent issue @anticapitalista: Line 20 in ~/.config/herbstluftwm/autostart should better be xrdb merge ~/.Xresources because I observed an error printed in TTY when I hit Mod+Shift+q. Correction: I think I got the error message when starting herbstluftwm with startx.

• This reply was modified 3 years, 8 months ago by eugen-b.
• This reply was modified 3 years, 8 months ago by eugen-b.
• This reply was modified 3 years, 8 months ago by eugen-b.

[Member VW]

As root user, startx gives the following:

As root user you shouldn’t even be trying to run ‘startx’.

You run startx as a a normal user. Just to help you out:

The startx script is a front end to xinit that provides a somewhat nicer user interface for running a single session of the X Window System. It is often run with no arguments.

Arguments immediately following the startx command are used to start a client in the same manner as xinit. The special argument “–” marks the end of client arguments and the beginning of server options. You may need to specify server options with startx to change the color depth, dots-per-inch, or a different server layout, as permitted by the Xorg server and xorg.conf.

To determine the client to run, startx first looks for a file called .xinitrc in the user’s home directory. If that is not found, it uses the file xinitrc in the xinit library directory. If command line client options are given, they override this behavior and revert to the xinit behavior. To determine the server to run, startx first looks for a file called .xserverrc in the user’s home directory. If that is not found, it uses the file xserverrc in the xinit library directory. If command line server options are given, they override this behavior and revert to the xinit behavior. Users rarely need to provide a .xserverrc file.

The system-wide xinitrc and xserverrc files are found in the /etc/X11/xinit directory.

H.T.H.

“These are the times that try men's souls" - Thomas Paine

After changing a monitor and removing a unused video card that was giving me problems, I cannot start Xwindows.
As root user, startx gives the following:

/etc/X11/xinit/xserverrc: 3: exec: /usr/bin/X: not found
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

I cannot see a X in /usr/bin

If I edit /etc/X11/xinit/xserverrc file to show /usr/bin/X11

I get Permission denied.

Is there a less drastic way of correcting this, without re-installing xserver and xorg?

• This topic was modified 3 years, 9 months ago by oldman.

Hi,

I had to install AntiX 17.4 in failsafe mode because when installing AntiX in normal mode, the first prompt that is shown during the installation on my computer (with the instructions how to login for an installation with the credentials root/root) is cut horizontally through the first line at the bottom of the screen, so one does not see what one has to do and what to enter to properly execute the installation.

Now AntiX starts, and I can login into AntiX, but no window manager is shown. I am not able to start X, neither with the command “startx”, nor with “init 5”.

During one installation attempt I also manually activated X11 as a service for runlevel 5, but X11 is not automatically started at the end of the boot process, only the console prompt is shown.

So among other things I thought “let me install a window manager using the programme cli-aptiX, maybe with the installation of such a window manager my system gets changed in a way that AntiX automatically starts that window manager at the end of the boot process”, but this also failed. I think I installed icewm using cli-aptiX, I cannot exactly remember. The boot process ends with giving me the possibility to login to AntiX on the console.

So how do I make AntiX boot with the effect that a window manager automatically gets displayed at the end of the boot process?

Regards,

prox

PS: I am running an old NVIDIA card in my machine (machine not this one which I used to create this forum post).

[Member seaken64]

Thank you skidoo. I’ve got some reading to do and my understanding of how all of this works is far from where it needs to be if I’m going to be trying to make any changes to the already fantastic system you guys have created. If I am understanding anything on the subject of why antiX uses Slim (which is highly questionable) I guess it’s because Slim can be scripted to do a lot of things that I would otherwise have to handle myself if just starting with startx. Thanks for the clues and links to some reading material.

Seaken64

[Anonymous]

I always wondered why antiX uses Slim.
I still don’t understand it and I am also curious if I can remove it.
I always used startx when learning with Slackware.

Have you ever read the code for startx? If not, go check it out (it’s just a shell script):
leafpad /usr/bin/startx
or, maybe better, for the moment just
head -12 /usr/bin/startx

So, imagine you have been tasked with writing a “nicer version” of startx, toward architecting a desktop linux distribution in which users will have multiple window managers available to choose from. Additionally, must (per specs) provide users an opportunity to elect use of a desktop manager (or not) and, because some users are running resource-strapped machines, must provide an opportunity to forego loading of any autostarted niceties enumerated within the default ~/.xinitrc

Umm, oops, sorry… forgot to mention that your “nicer version” actually needs to accommodate user choice to elect use of {multiple available} desktop managers (or not). Also, the “nicer version” must provide a way for us to setup, and users to edit later, differing sets of “global” items to be autostarted regardless which window manager has been selected for the current session. Oh, and one more thing ~~ that ROX thing, it doesn’t parlayvoo XDG. We need to provide a way for users to assign preferred handlers for mail, for html documents, for text documents, and probably several additional mimetypes.

Time passes and… and a (confusingly similarly named) XDG “desktop session manager” spec becomes prevalent, and it becomes necessary for your “nicer version” to swing by and talk to PAM and pickup an authkey for the session manager, in case users wish to sideload additional WMs/DEs which actually provide a session manager module.

quick-like, skimread these if you’re wondering “Who’s PAM, and does she have a sister?”
pam-easy-guide/#Linux-PAM-Benefit
linuxjournal.com/article/5940

Together, the SLiM + desktop-session-antix package serve as the “nicer version” to provide that functionality, and more.
(splitting hairs, it’d be more accurate to also credit desktop-session-*-antix, desktop-defaults-antix)
If you prefer to remove SLiM from the flow and, instead “startx desktop-session {sessionname plus options}”, your alternative nicer solution might not suffer from failing to visit PAM, considering that the gnomes have have stolen her auth keyring. If you care to replace (or skip the step of invoking) desktop-session, you may need to rewire the logout and/or shutdown buttons and menu commands.

If you want to keep (I’m accustomed to paring down, vs building up from core) use antix ControlCenter in the absence of desktop-{defaults,session}-antix, need to edit its script and search/replace “desktop-defaults -t” with a suitable launchstring for your terminal emulator of choice. Similarly, need to replace “desktop-defaults -e” with your chosen text editor. Hmm, the ds-mouse cc item (encompasses multiple scripts in /usr/local/bin)(and …/lib/) and the set-dpi(?) script and probably a few others would need to be amended.

[Moderator BobC]

ok, not sure if this is actually what was being asked for, but I found a way to disable slim and run from startx after logging into the console in antiX19b1 32 bit.

Obviously, this would void your warranty, which doesn’t exist anyway, lol.

Open terminal
sudo mc
cd /etc/rc5.d
point to S04slim
F6 and rename to K04slim
the README file there says to run “update-rc.d script defaults” but that doesn’t seem to work
Logout – reboot (you can just type reboot as root from mc I am pretty sure)
When you reboot it will come up to a login prompt in console. Log in as your normal user, then type startx

I tested this on my 32 bit instal of antiX19b1, but obviously it might or might not work for you. I am on a test system having done it typing this. Here is my memory print…

bobc@m2400:~
$ su
Password:
root@m2400:/home/bobc# ps_mem.py
Private + Shared = RAM used Program

192.0 KiB + 42.0 KiB = 234.0 KiB gpm
204.0 KiB + 46.5 KiB = 250.5 KiB startx
240.0 KiB + 57.5 KiB = 297.5 KiB acpid
228.0 KiB + 98.5 KiB = 326.5 KiB cron
244.0 KiB + 91.0 KiB = 335.0 KiB init
224.0 KiB + 197.5 KiB = 421.5 KiB xinit
188.0 KiB + 256.5 KiB = 444.5 KiB x-session-manag
452.0 KiB + 58.0 KiB = 510.0 KiB rpc.idmapd
340.0 KiB + 183.5 KiB = 523.5 KiB dbus-launch
368.0 KiB + 173.0 KiB = 541.0 KiB irqbalance
304.0 KiB + 282.0 KiB = 586.0 KiB unclutter
540.0 KiB + 58.0 KiB = 598.0 KiB ssh-agent
388.0 KiB + 232.0 KiB = 620.0 KiB rpcbind
520.0 KiB + 407.5 KiB = 927.5 KiB getty (5)
332.0 KiB + 616.0 KiB = 948.0 KiB avahi-daemon (2)
472.0 KiB + 536.5 KiB = 1.0 MiB su
844.0 KiB + 245.5 KiB = 1.1 MiB rpc.statd
480.0 KiB + 625.0 KiB = 1.1 MiB saned (2)
636.0 KiB + 498.5 KiB = 1.1 MiB login
524.0 KiB + 674.5 KiB = 1.2 MiB gconfd-2
960.0 KiB + 242.0 KiB = 1.2 MiB sshd
628.0 KiB + 677.5 KiB = 1.3 MiB dbus-daemon (2)
1.4 MiB + 97.5 KiB = 1.4 MiB elogind-daemon
1.6 MiB + 265.0 KiB = 1.9 MiB connmand
1.8 MiB + 135.0 KiB = 1.9 MiB rsyslogd
2.3 MiB + 446.5 KiB = 2.7 MiB wpa_supplicant
2.4 MiB + 432.5 KiB = 2.8 MiB udevd
3.1 MiB + 38.0 KiB = 3.2 MiB haveged
1.4 MiB + 2.4 MiB = 3.7 MiB gksu
2.6 MiB + 1.5 MiB = 4.1 MiB bash (3)
5.5 MiB + 5.0 MiB = 10.6 MiB icewm
7.0 MiB + 6.0 MiB = 13.0 MiB roxterm
37.0 MiB + 1.5 MiB = 38.5 MiB Xorg
———————————
99.1 MiB
=================================

PS: so to prove how much I saved, I put slim back and rebooted again with slim set for min-icewm. The moral of the story is that I LOST 1 mb using startx on this machine because slim isn’t using 34 mb on this one.

bobc@m2400:~
$ su
Password:
root@m2400:/home/bobc# ps_mem.py
Private + Shared = RAM used Program

192.0 KiB + 42.0 KiB = 234.0 KiB gpm
244.0 KiB + 53.5 KiB = 297.5 KiB acpid
224.0 KiB + 97.5 KiB = 321.5 KiB cron
256.0 KiB + 75.0 KiB = 331.0 KiB init
188.0 KiB + 229.5 KiB = 417.5 KiB icewm-session
368.0 KiB + 173.0 KiB = 541.0 KiB irqbalance
332.0 KiB + 220.0 KiB = 552.0 KiB dbus-launch
508.0 KiB + 61.0 KiB = 569.0 KiB rpc.idmapd
392.0 KiB + 253.0 KiB = 645.0 KiB rpcbind
464.0 KiB + 420.0 KiB = 884.0 KiB desktop-session
332.0 KiB + 620.0 KiB = 952.0 KiB avahi-daemon (2)
536.0 KiB + 481.5 KiB = 1.0 MiB su
824.0 KiB + 255.5 KiB = 1.1 MiB rpc.statd
420.0 KiB + 666.0 KiB = 1.1 MiB saned (2)
508.0 KiB + 616.5 KiB = 1.1 MiB gconfd-2
624.0 KiB + 558.0 KiB = 1.2 MiB getty (6)
1.0 MiB + 257.0 KiB = 1.3 MiB sshd
676.0 KiB + 651.0 KiB = 1.3 MiB dbus-daemon (2)
1.4 MiB + 103.0 KiB = 1.5 MiB elogind-daemon
1.6 MiB + 307.0 KiB = 1.9 MiB connmand
1.8 MiB + 136.0 KiB = 1.9 MiB rsyslogd
1.5 MiB + 547.5 KiB = 2.1 MiB gnome-keyring-daemon
2.3 MiB + 424.5 KiB = 2.7 MiB wpa_supplicant
1.7 MiB + 1.1 MiB = 2.8 MiB bash (2)
2.4 MiB + 422.5 KiB = 2.8 MiB udevd
3.1 MiB + 42.0 KiB = 3.2 MiB haveged
1.4 MiB + 2.5 MiB = 3.9 MiB gksu
3.4 MiB + 1.5 MiB = 5.0 MiB slim
3.8 MiB + 2.0 MiB = 5.7 MiB icewm
12.0 MiB + 3.5 MiB = 15.5 MiB roxterm
34.2 MiB + 1.6 MiB = 35.8 MiB Xorg
———————————
98.3 MiB
=================================

• This reply was modified 3 years, 10 months ago by BobC.

[Member seaken64]

I will revisit this thread when v19 goes to release. I have two P-III’s I use antiX-17 on. One with 512MB and one with 256MB. I am curious if I will be able to get the memory use similar to what I have in v17. The tips here look promising.

I always wondered why antiX uses Slim. I still don’t understand it and I am also curious if I can remove it. I always used startx when learning with Slackware. But I’m still a newbie in setting up X and a DM. I’ll live with whatever works with antiX.

Seaken64

[Member aledosim]

Hello everyone. Thanks for all the replies.

ex_Koo wrote:

Going by what I see in your post about i3 and startx do you relies that you have installed the core version their is no X installed with the core version to start with, and dbus has nothing to do with your problem. Just install the full version then install i3 if you wish. Core version is mostly used by people who wish to use the command line or by people who wish to build their own system and they know what their doing in the first place.

Starting a new post about this will not help you at all..

If you are feeling geeky and would like to continue with the core version Dolphin has done it for you have a look that these great videos about installing the core version of antiX..

Video 1

Video 2

Video 3

and so on..

I’m aware that core version doesn’t have X. My intention is to build my own system, just started another topic because I thought that was the simplest way to organize the discussion. Furthermore, I think this is a step in my studies that I can handle based on the tutorials like the Dolphin one.

Anonymous wrote:

Koo, in post#3 aledosim acknowledged Dolphin’s video(s)

Similar to macondo’s recent adventure (start with core, add ratpoison WM), SLiM may not be necessary.
Different from the case of macondo’s success, aledosim’s system is probably still missing some requisite packages.
dbus-x11? Dunno, aledosim hasn’t mentioned whatall packages have been installed atop core so far.

I’ve installed this packages:
– i3
– i3status
– stterm
– slim
– xorg
– suckless-tools

Will try installing dbus-x11.
Thank very much you all.

EDIT: Just tried with dbus-x11 and the problem persists.

• This reply was modified 3 years, 10 months ago by aledosim.

[Anonymous]

requires clarification?

Similar to macondo’s recent adventure (start with core
add ratpoison WM), SLiM
inclusion of a graphical login manager may not be necessary ^or desirable.

https://gitlab.com/skidoo/slim-antix
Demonstrably, skidoo is among SLiM’s most enthusiastic proponents. Given a context of “building up from antiX Base Edition”, across various prior topics I have explained how/why SLiM represents a “lesser evil” compared to LightDM and other available graphical login managers.

…you might find bspwm very similar in look
[..]
don’t get rid of Slim; installs of desktops will complain if you do.
[..]
Also be aware that lightdm-gtk-greeter-settings has a problem in antiX19

^— faff, and such distraction is disrectpectful of the OP’s clearly expressed goal.

.
re: “don’t get rid of Slim; installs of desktops will complain if you do.”
We should expect that only JWM, fluxbox, iceWM — the 3 window managers whose packages and settings are tampered by antiX — would “complain”, and presence/absence of SLiM isn’t the deciding factor. For jwm/fluxbox/icewm sessions launched via startx or SLiM or otherwise, if launch is not chained via /usr/local/bin/desktop-session, you must be prepared to accept responsibility for manually (tailoring and/or) maintaining a suitable keys file, startup file, menu file {ellipsis}…

package: “desktop-session-antix”
package “desktop-defaults-antix”
package: “desktop-defaults-*-antix”
macondo’s recent post accurately described the antiX desktop-session stuff as being “endemic”.
A decision to forego inclusion of these will have broad (sweeping) consequences.
Vis macondo’s case, it’s absolutely “do-able”. Unfortunately, a gap exists, in terms of supporting such cases.

[Member ex_Koo]

Going by what I see in your post about i3 and startx do you relies that you have installed the core version their is no X installed with the core version to start with, and dbus has nothing to do with your problem. Just install the full version then install i3 if you wish. Core version is mostly used by people who wish to use the command line or by people who wish to build their own system and they know what their doing in the first place.

Starting a new post about this will not help you at all..

If you are feeling geeky and would like to continue with the core version Dolphin has done it for you have a look that these great videos about installing the core version of antiX..

Video 1

Video 2

Video 3

and so on..

Hey everyone,
A feel days ago I posted this: https://www.antixforum.com/forums/topic/trying-to-use-i3wm/
After some more investigation, I’ve discovered that the problem is related to dbus. Found this error at slim log:

slim: open_session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Looking at htop I’ve noted that dbus isn’t running when I enter “sudo slim” to start slim (it crash in this way). When I run “sudo /etc/init.d/dbus start” before starting slim, it shows up this message:

Failed to execute login command

I tried “sudo startx” and it opens the i3wm, but dbus still not running.

And all this happens after the “apt upgrade” in which dbus is updated to version 1.10.28. Before this it worked fine.

Is this a misconfiguration? Is this problem related to the minimalism of core version?

• This topic was modified 3 years, 10 months ago by aledosim.

After having tried the Net install, the Core install was wonderful, with the exception of a couple of ambiguous questions, “Core” was a pleasant surprise, I installed it in one of my 3 ssd and booted fine, when I got to startx, I could not get in as user, only as Root.

Gave me the following error:

[code]
xauth: file /home/bobo/.Xauthority does not exist. server error
[/code]

Been ddg’ing and checking the irc…

any ideas?

antiX Core 64 Bit Runit IceWM

"Sometimes a man finds his destiny on the road he took to avoid it."

[Member fatmac]

Providing that you installed the X window system, you should be able to use startx at the command line.

If I add a GUI, that’s the way I prefer to start it, but you will likely need to do some setup to slim to use it.

Linux (& BSD) since 1999