Search Results for 'xinitrc'

Again folks, this is subjective, just the way I do things. 🙂

After installing antiX, the first thing I configure is sudo.

# visudo

Put this line at the bottom of the file:

<your_user_name>  ALL=NOPASSWD:ALL

save/exit/reboot

If you use nano,

# nano /etc/sudoers

ditto as above.

Next, aliases make my life easier,

$ nano .bash_aliases

Paste this:

alias adu="sudo apt-get update && sudo apt-get dist-upgrade"
alias agi="sudo apt-get install"
alias as="apt-cache search"
alias ash="apt-cache show"

logout/login and test it as USER:

$ adu

Go to .nanorc and type this:

set smooth

UFW (Uncomplicated Firewall)

# apt-get install ufw
# ufw enable
# ufw status
# reboot

After coming back do another ‘ufw status’ to find out if the firewall
is working.

To avoid pinging: go to:

# nano /etc/ufw/before.rules

And leave this section looking like this:

# ok icmp codes
-A ufw-before-input -p icmp --icmp-type destination-unreachable -j DROP
-A ufw-before-input -p icmp --icmp-type source-quench -j DROP
-A ufw-before-input -p icmp --icmp-type time-exceeded -j DROP
-A ufw-before-input -p icmp --icmp-type parameter-problem -j DROP
-A ufw-before-input -p icmp --icmp-type echo-request -j DROP

Next, go to http://www.grc.com and click on ShieldsUp, next screen scroll down to Hot
Spots, and click on ShieldsUp again, next screen click on Proceed, next screen
click on All Service Ports and let it check the ports, gives an ok result, the
ports are neon green, and gives you this veredict:

“Your system has achieved a perfect “TruStealth” rating. Not a single packet —
solicited or otherwise — was received from your system as a result of our
security probing tests. Your system ignored and refused to reply to repeated
Pings (ICMP Echo Requests). From the standpoint of the passing probes of any
hacker, this machine does not exist on the Internet. Some questionable personal
security systems expose their users by attempting to “counter-probe the prober”,
thus revealing themselves. But your system wisely remained silent in every way.
Very nice.”

Startup
To start your apps and window manager: go to .xinitrc as USER,

$ nano .xinitrc

Put this:

#!/bin/sh

setxkbmap -option terminate:ctrl_alt_bksp
xsetroot -solid black
unclutter -idle 2 &
numlockx &

exec window manager

I think this is about it, thanks for your patience.

Happy trails,
macondo

antiX Core 64 Bit Runit IceWM

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

Again folks, this is very subjective, just the way I do things, it’s not written on stone 🙂

After installing antiX, the first thing I configure is sudo.

# visudo

Put this line at the bottom of the file:

<your_user_name> ALL=NOPASSWD:ALL

save/exit/reboot

If you use nano,

# nano /etc/sudoers

ditto as above.

Next, aliases make my life easier,

$ nano .bash_aliases

Paste this:

alias adu="sudo apt-get update && sudo apt-get dist-upgrade"
alias agi="sudo apt-get install"
alias as="apt-cache search"
alias ash="apt-cache show"

logout/login and test it as USER:

$ adu

Go to .nanorc and type this:

set smooth

UFW (Uncomplicated Firewall)

# apt-get install ufw
# ufw enable
# ufw status
# reboot

After coming back do another ‘ufw status’ to find out if the firewall
is working.

To avoid pinging: go to:

# nano /etc/ufw/before.rules

And leave this section looking like this:

# ok icmp codes
-A ufw-before-input -p icmp --icmp-type destination-unreachable -j DROP
-A ufw-before-input -p icmp --icmp-type source-quench -j DROP
-A ufw-before-input -p icmp --icmp-type time-exceeded -j DROP
-A ufw-before-input -p icmp --icmp-type parameter-problem -j DROP
-A ufw-before-input -p icmp --icmp-type echo-request -j DROP

Next, go to http://www.grc.com and click on ShieldsUp, next screen scroll down to Hot
Spots, and click on ShieldsUp again, next screen click on Proceed, next screen
click on All Service Ports and let it check the ports, gives an ok result, the
ports are neon green, and gives you this veredict:

“Your system has achieved a perfect “TruStealth” rating. Not a single packet —
solicited or otherwise — was received from your system as a result of our
security probing tests. Your system ignored and refused to reply to repeated
Pings (ICMP Echo Requests). From the standpoint of the passing probes of any
hacker, this machine does not exist on the Internet. Some questionable personal
security systems expose their users by attempting to “counter-probe the prober”,
thus revealing themselves. But your system wisely remained silent in every way.
Very nice.”

Startup
To start your apps and window manager: go to .xinitrc as USER,

$ nano .xinitrc

Put this:

#!/bin/sh

firefox &
setxkbmap -option terminate:ctrl_alt_bksp
xsetroot -solid black
unclutter -idle 2 &
numlockx &

exec <window manager>

I think this is about it, thanks for your patience.

Happy trails,
macondo

• This topic was modified 2 years, 10 months ago by macondo.
• This topic was modified 2 years, 10 months ago by Brian Masinick.

antiX Core 64 Bit Runit IceWM

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

Again folks, this is subjective, just how I do things, it’s not written anywhere. 🙂

After installing antiX, the first thing I configure is sudo. I like it with no passwords.

# visudo

Put this line at the bottom of the file:

<your_user_name> ALL=NOPASSWD:ALL

save/exit/reboot

If you use nano,

# nano /etc/sudoers

ditto as above.

Next, aliases make my life easier,

$ nano .bash_aliases

Paste this:

alias adu="sudo apt-get update && sudo apt-get dist-upgrade"
alias agi="sudo apt-get install"
alias as="apt-cache search"
alias ash="apt-cache show"

logout/login and test it as USER:

$ adu

Go to .nanorc and type this:

set smooth

UFW (Uncomplicated Firewall)

# apt-get install ufw
# ufw ena
ble
# ufw status
# reboot`

After coming back do another ‘ufw status’ to find out if the firewall
is working.

Startup
To start your apps and window manager: go to .xinitrc as USER,

$ nano .xinitrc

I put this:

#!/bin/sh

firefox &
setxkbmap -option terminate:ctrl_alt_bksp
xsetroot -solid black
unclutter -idle 2 &
numlockx &

exec (window manager)

I think this is about it, thanks for your patience.

Happy trails,
macondo

• This topic was modified 2 years, 10 months ago by macondo.
• This topic was modified 2 years, 10 months ago by Brian Masinick.

antiX Core 64 Bit Runit IceWM

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

[Member Thalassius]

Here it is:

# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
#
default_path        /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver     /usr/bin/X11/X
xserver_arguments   -nolisten tcp -background none

# Commands for halt, login, etc. on live antiX
halt_cmd            /usr/local/bin/persist-config --shutdown --command halt 
reboot_cmd          /usr/local/bin/persist-config --shutdown --command reboot 
# Commands for halt, login, etc. on installed antiX
halt_cmd            sudo halt 
reboot_cmd        sudo reboot 
#console_cmd         /usr/bin/urxvt -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue.net; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/X11/xauth

# Xauth file for server
authfile           /var/run/slim.auth

# Activate numlock when slim starts. Valid values: on|off
numlock             on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. not using desktop-session-antix:
#login_cmd         exec /bin/bash -login /etc/X11/Xsession %session 
#################OLD COMMAND####################
# login_cmd         exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1
################################################
#LOGIN COMMAND FOR DESKTOP SESSION BELOW#
#############################################################################################
login_cmd   setsid /usr/local/bin/desktop-session %session
#############################################################################################

# login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd	some command
# sessionstop_cmd	some command

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon	yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
#sessions rox-fluxbox,space-fluxbox,fluxbox,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm,herbstluftwm
sessiondir /usr/share/xsessions

# Executed when pressing F11 (requires scrot)
screenshot_cmd      scrot /root/slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         (Press F1 to toggle sessions)

# Session message. Prepended to the session name when pressing F1
# session_msg         Session: 

# shutdown / reboot messages
shutdown_msg 	The system is shutting down...
reboot_msg 		The system is rebooting...

# Focus the password field on start when #default_user is set
# Set to "yes" to enable this feature
focus_password      yes

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        giorgos

# current theme, use comma separated list to specify a set to 
# randomly choose from
#current_theme 	BlueLines
#current_theme 	BlueLinesLight
current_theme 	antiXIce
#current_theme 	DarkCity#current_theme 	PrettyPink
#current_theme 	SunnyDay

# Lock file
lockfile            /var/run/slim.lock

# Log file
logfile             /var/log/slim.log

For the glorious men, every land is a grave.
Pericles' "Funeral Oration".

I’ve encountered exactly the problem described in this topic. I tried switching to other WM’s, figured that i can’t go back to IceWM and while clicking sporadically to other menu options i switched accidentally to herbsluftwm tile manager which i have zero idea of how to use. Now i’m stuck with it and feel like a clueless 5yo. Can you please help me to set up Ice back as a default?

I managed to run Terminal and Rox and edited “exec icewm” in /etc/X11/xinit/xinitrc. That didn’t help.

Needless to say my experience with linux systems is close to none.

• This topic was modified 3 years ago by MatroskinTheCat.

[Moderator BobC]

I got almost there… Can’t get X-windows to start. a few errors in starting…

xf86EnableIOPorts: failed to set IOPL for I/O (Operaation not pernmitted)
resize called 1440 900

then in .xinitrc

slstatus not found
exec: dwm: Exec format error

If I knew what I was doing I would be dangerous, LOL

[Moderator christophe]

THAT DID THE TRICK!!
Thank you very very much.

So, to reiterate, from antiX 19 core:
1.) installed slim.
1.5) I already DID have xserver-xorg-legacy installed, so that may be necessary…
2.) made sure login_cmd exec /bin/bash -login /etc/X11/Xsession %session is the uncommented line. (line 36)
3.) frugal = only disabling “l” in the boot codes. (not d or 3)
4.) no other strange lines added to /etc/slim.conf
5.) no ~/.xinitrc added (by an over-zealous, struggling antiXer).

and slim works.

(Seems like “antiX magic” to me…)

confirmed antiX frugaler, since 2019

[Member stroudmw]

Here you go!

# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
#
default_path        /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver     /usr/bin/X11/X
xserver_arguments   -nolisten tcp

# Commands for halt, login, etc. on antiX
halt_cmd            /usr/local/bin/persist-config --shutdown --command halt 
reboot_cmd          /usr/local/bin/persist-config --shutdown --command reboot 
console_cmd         /usr/bin/urxvt -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue.net; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/X11/xauth

# Xauth file for server
authfile           /var/run/slim.auth

# Activate numlock when slim starts. Valid values: on|off
# numlock             on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd         exec /bin/bash -login /etc/X11/Xsession %session 
#################OLD COMMAND####################
# login_cmd         exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1
################################################
#LOGIN COMMAND FOR DESKTOP SESSION BELOW#
#############################################################################################
login_cmd   setsid /usr/local/bin/desktop-session %session
#############################################################################################

# login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd	some command
# sessionstop_cmd	some command

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon	yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
#sessions rox-fluxbox,space-fluxbox,fluxbox,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm,herbstluftwm
sessiondir /usr/share/xsessions

# Executed when pressing F11 (requires scrot)
screenshot_cmd      scrot /root/slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         (Press F1 to toggle sessions)

# Session message. Prepended to the session name when pressing F1
# session_msg         Session: 

# shutdown / reboot messages
shutdown_msg 	The system is shutting down...
reboot_msg 		The system is rebooting...

# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password      yes

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login          no

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        demo

# current theme, use comma separated list to specify a set to 
# randomly choose from
current_theme       antiX

# Lock file
lockfile            /var/run/slim.lock

# Log file
logfile             /var/log/slim.log
default_user        
auto_login          yes
lockfile            /var/run/slim.lock
logfile             /var/log/slim.log

[Forum Admin anticapitalista]

You don’t need a .xinitrc file.
You might need to install xserver-xorg-legacy as well as making the edits I mentioned above.

Aha- core plus frugal — remove the ‘d’ and probably ‘3’ in disable=lxd boot menu

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

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator christophe]

anticapitalista wrote:

Do you have ~/.xinitrc file?

No. I don’t.
After I edited my slim.conf as you suggested, I found (something like) this in the xinitrc.sample in “fatso” on gitlab. Do I want something like this in the ~/.xinitrc?

DEFAULT_SESSION=jwm
case $1 in
fluxbox)
	exec fluxbox
	;;
*)
	exec jwm
	exec $DEFAULT_SESSION
	;;
esac

By the way, to everyone, I really appreciate the help & suggestions.

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

confirmed antiX frugaler, since 2019

[Anonymous]

maybe #31725 is intended as “instruction, specific to this case, to get it working”.
I drafted a long post prior to reading that, and my post recommends a cmd_login line which matches that seen in default antiX 19 full.
Here, I’m prefacing the long post by mentioning that I am not contradicting the instruction provided in #31725 ~~ I’m just covering how the dots are connected to work in the as-shipped antiX full.
___________________________

The topic linked from post #1 discusses antix19core-LXDE —} lightDM + lxdm + (presumably) lxsession.
That line (in post #1 here) is suitable only for use with a full-blown DE (desktop environment, e.g. LXDE, Xfce, Mate) .

lightDM and SLiM serve only as “display manager” aka “login manager”.
— starts Xorg server
— checks user+password login credentials
— uses a PAM (kernel pluggable authentication module) mechanism to register a “seat”
(your tty, er console, input {–} output display hardware marshalled by xserver)
— invokes the “session manager of choice” component… and then it just waits, serving as a idle wrapper
(idle until logout/login is requested, or exit/shutdown)

Upon installation of any display manager package, the DM is registered with rc.d to be automatically started for runlevels 2 and 5.
If, during installation, another DM is found already present on the system, you are asked to choose which of the DMs will be enabled.
^—v
During a session, if you logout (or you kill the DM process, or it crashes) the rc.d will automatically*** restart the DM.

*** a sysadmin is free to install multiple DMs and manually change which one (or none) is started for each runlevel.

The “startx” command is supposed to be (provide) a convenience… but, as an abstraction, it muddies the water.
Users are resigned to not knowing / caring which display manager and auth mechanism and session manager components will be invoked in order to create their “desktop session”.

We probably cannot put much weight in the terms “standard” vs NON-standard”.
— some distros do not use, nor provide, a “startx” command
— some distros are configured to only start a DM when entering runlevel 5
— some distros replace rc.d with systemd
— some distros ship only one DesktopEnvironment or WM
— the sessionmanager component of a given DesktopEnvironment may demand use of its own WM
____________________________________________

login_cmd setsid /usr/local/bin/desktop-session %session
https://gitlab.com/antiX-Linux/Build-iso/blob/master/Themes/full/misc/slim.conf

This SLiM login_cmd line (as seen in antiX full) calls a “session manager” utility named desktop-session which, in turn,
invokes whichever “session” has been chosen via F1, e.g. “rox-icewm” (and passed as a commandline argument).
Additionally, and in place of (instead of) sourcing ~/.Xsession, the utility sources both an “all cases” .startup file
and (depending on which WM has been requested for this session) ~/.fluxbox/startup or ~/icewm/startup or…

rox desktop manager (and spacefm -d) are windowmanager agnostic.
Further, either of them can be manually invoked (and killed), at will during the course of a “desktop session”.

When the antiX “session manager” utility (the desktop-session command) parses the commandline args for a given session request, it selectively starts the requested “desktop manager” (or none) along with the requested “window manager”… and each of those can be (and typically are) configured to autostart additional processes. Along the way, ~/.xinitrc is never sourced. (IIRC, by default, on an antiX full system that file isn’t even present)

____________________________________________

re: “startx [..] error message & restarting”

https://www.antixforum.com/forums/topic/antix-19-1-based-on-debian-sid-available/

It seems that if you use startx, you need to also install xserver-xorg-legacy, but it is not needed if you use slim.
If user does chooses slim login manager, you MUST edit /etc/slim.conf as shown above otherwise you get the error reported by Koo.

[Forum Admin anticapitalista]

Looking at slim.conf, remove the line you added (line 44) and instead uncomment line 36

login_cmd exec /bin/bash -login /etc/X11/Xsession %session

Also remove line 65 (sessions jwm,fluxbox)

Do you have ~/.xinitrc file?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin anticapitalista]

edit /etc/slim.conf as I posted to you here:

https://www.antixforum.com/forums/topic/how-do-i-modify-slim-conf-on-a-netbooks-ssd-from-the-live-environment/

You need changes like this:

login_cmd         exec /bin/bash -login /etc/X11/Xsession %session
#################OLD COMMAND####################
# login_cmd         exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1
################################################
#LOGIN COMMAND FOR DESKTOP SESSION BELOW#
#############################################################################################
#login_cmd   setsid /usr/local/bin/desktop-session %session 
#############################################################################################

auto_login          yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        anticap

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

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin anticapitalista]

Have you edited /etc/slim.conf?

You need changes like this:

login_cmd         exec /bin/bash -login /etc/X11/Xsession %session  <strong>(uncomment)</strong>
#################OLD COMMAND####################
# login_cmd         exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1
################################################
#LOGIN COMMAND FOR DESKTOP SESSION BELOW#
#############################################################################################
#login_cmd   setsid /usr/local/bin/desktop-session %session <strong>(comment)</strong>
#############################################################################################

auto_login          yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        anticap

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin anticapitalista]

Have you edited /etc/slim.conf?

You need changes like this:

login_cmd exec /bin/bash -login /etc/X11/Xsession %session (uncomment)
#################OLD COMMAND####################
# login_cmd exec /bin/bash -login ~/.xinitrc %session >~/.xsession-errors$DISPLAY 2>&1
################################################
#LOGIN COMMAND FOR DESKTOP SESSION BELOW#
#############################################################################################
#login_cmd setsid /usr/local/bin/desktop-session %session (comment)
#############################################################################################

auto_login yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user anticap

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.