DebianDog HowTo thread
Firewall from Puppy linux
http://murga-linux.com/puppy/viewtopic. ... 580#777580
The main script is in /opt/bin and it creates $HOME/rc.firewall script which is started from $HOME/Startup/firewall-puppy script after login and can have different setup for each user account.
For user account there will be GUI window to type root password.
Boot DebianDog with systemd
http://www.murga-linux.com/puppy/viewto ... 007#829007
http://www.murga-linux.com/puppy/viewto ... 025#829025
Edit: Systemd workaround from Fred for porteus-boot (for now works only with the default included in the iso kernel 3.2.0-4-486):
http://murga-linux.com/puppy/viewtopic. ... 987#798987
The autologin as root command works also for live-boot-2x and live-boot-3x.fredx181 wrote:Hi Toni, All,
---------------------------------------------
Here's a more solid way to enable systemd for porteus-boot instead of what I wrote here:
http://murga-linux.com/puppy/viewtopic. ... 672#792672
Only for porteus-boot method.
Enable systemd using patched initrd1.xz (kernel 3.2.0-4-486), it's here:
https://googledrive.com/host/0ByBgCDlZZ ... emd.tar.gz
Edit from saintless: this initrd1.xz is included in the iso from October 2014 both DebianDog versions and DebianDog-Squeeze.
by adding "init=/bin/systemd" parameter to your kernel boot line like this:
The steps:Code: Select all
kernel /live/vmlinuz1 noauto from=/ changes=/live/changes.dat init=/bin/systemd
In terminal:Installing also the 'systemd-sysv' package will make it permanent (by not installing it you'll be still able to use the old initscripts when not using 'init=/bin/systemd' parameter)Code: Select all
apt-get update # if needed apt-get install systemd
To enable autologin for user root, run in terminal:Then reboot and systemd should be enabled if you added the 'init=/bin/systemd' parameter.Code: Select all
# Set ExecStart to autologin as root (inittab doesn't work anymore under systemd) EXESTART=`cat /etc/systemd/system/getty.target.wants/getty@tty1.service | grep 'ExecStart='` EXESTARTNEW="ExecStart=-/sbin/agetty --noclear -a root %I 38400" sed -i "s,$EXESTART,$EXESTARTNEW,g" /etc/systemd/system/getty.target.wants/getty@tty1.service
More info about what's changed to make init=/bin/systemd parameter work in the ReadMe-enable-systemd inside initrd1.xz-systemd.tar.gz.
Note: Uninstalling systemd afterwards may give a problem.
If apt-get refuses to uninstall it, best thing to do then is:
Then reboot without 'init=/bin/systemd' parameter added.Code: Select all
apt-get install sysvinit # if it isn't already installed
Then you should be able to uninstall systemd because it's not running anymore.
Fred
Boot DebianDog with systemd: - for live-boot-2x and live-boot-3x.
More information about systemd here:
https://wiki.debian.org/systemd
Only two easy steps needed:
1. Install systemd:
Code: Select all
root@debian:~# apt-get install systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libcryptsetup4 libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0
libwrap0
Suggested packages:
systemd-gui python python-dbus python-cairo
Recommended packages:
tcpd libpam-systemd
The following NEW packages will be installed:
libcryptsetup4 libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0
libwrap0 systemd
0 upgraded, 6 newly installed, 0 to remove and 32 not upgraded.
Need to get 1696 kB of archives.
After this operation, 4310 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
..................................................................................
Unpacking systemd (from .../systemd_44-11+deb7u4_i386.deb) ...
Setting up libwrap0:i386 (7.6.q-24) ...
Setting up libsystemd-daemon0:i386 (44-11+deb7u4) ...
Setting up libsystemd-id128-0:i386 (44-11+deb7u4) ...
Setting up libsystemd-journal0:i386 (44-11+deb7u4) ...
Setting up libcryptsetup4 (2:1.4.3-4) ...
Setting up systemd (44-11+deb7u4) ...
Initializing machine ID from D-Bus machine ID.
root@debian:~#
Example boot code for live-boot-2x:
Code: Select all
title DebianDog Wheezy live-boot-2 Persistent Changes
uuid 25e43216-01b1-43eb-b02d-6350e970da2c
kernel /live/vmlinuz1 boot=live persistent config swapon quickreboot noprompt autologin init=/bin/systemd
initrd /live/initrd1.img
Code: Select all
title DebianDog Wheezy live-boot-3 Persistence Changes
uuid 25e43216-01b1-43eb-b02d-6350e970da2c
kernel /live/vmlinuz1 boot=live config swapon persistence quickreboot noeject autologin init=/bin/systemd
initrd /live/initrd.img
Example boot code for Full install:
Code: Select all
title DebianDog Wheezy Full install
uuid 090712ec-7b56-47de-87a5-be8b1f99534d
kernel /boot/vmlinuz-3.2.0-4-486 root=UUID=090712ec-7b56-47de-87a5-be8b1f99534d init=/bin/systemd rw
initrd /boot/initrd.img-3.2.0-4-486
Removing init=/bin/systemd from your boot code will bring back default sysvinit boot.
============================================
Preventiing default kernel upgrade
Code: Select all
Package: linux-image-3.2.0-4-486
Pin: version 3.2.51-1
Pin-Priority: 1001
If you like to activate default kernel upgrade just remove /etc/apt/preferences and run apt-get update.
Enable touchpad tapping:
Type in terminal tapbutton to enable this option when needed. If you like to keep the changes permanent after reboot symlink the /opt/bin/tapbutton script in /root/Startup.
Install AMD legacy proprietary driver (fglrx-legacy-driver)
Edit3: Some more information how to install fglrx driver in Jessie from Keisha.
Edit2: Instructions how to build ati driver for kernel 3.2.0-4-486 and 3.14-0.bpo.1-686-pae here (thank you, Devil.Dog!):
http://www.murga-linux.com/puppy/viewto ... 674#798674
http://www.murga-linux.com/puppy/viewto ... 838#798838
Maybe no need to read the information below. Devil.Dog's method building ati driver in DebianDog works.
Edit: Read this posts first:
http://www.murga-linux.com/puppy/viewto ... 228#793228
There was a question about this but I can't really tell if it works OK or not on AMD hardware. The install process seems to finish and the system works but testing on proper hardware can confirm if there are problems or not.
I read about problems in google and possible solutions patching amd installer like this one if apt-get install method doesn't work:
http://forums.debian.net/viewtopic.php?f=5&t=94847
Or here:
http://www.debianuserforums.org/viewtop ... f=7&t=2606
http://ftp.debian.org/debian/pool/non-f ... rx-driver/
There are suggestions to use newer kernel above 3.10 so you can test this with separate kernel module for DebianDog from here (026-kernel-3.14-Pae.tar.gz or 024-kernel-3.12.0.bpo.1.zip) :
http://murga-linux.com/puppy/viewtopic. ... 459#774459
How to install AMD legacy proprietary driver (fglrx-legacy-driver) with apt-get:
1. Rename /etc/apt/sources.list to /etc/apt/sources.list-original
2. Create new file /etc/apt/sources.list, add only this one line inside and save it:
Code: Select all
deb http://ftp.de.debian.org/debian wheezy-backports main contrib non-free
4. Install with apt-get fglrx-legacy-driver
Code: Select all
apt-get install fglrx-legacy-driver
Code: Select all
root@debian:~# apt-get install fglrx-legacy-driver
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
glx-alternative-fglrx glx-alternative-mesa glx-diversions libfglrx-legacy
nvidia-installer-cleanup
Suggested packages:
fglrx-legacy-control xvba-va-driver amd-opencl-icd-legacy fglrx-driver
Recommended packages:
fglrx-legacy-modules-dkms fglrx-kernel-8.97.100.7 libgl1-fglrx-legacy-glx
fglrx-legacy-atieventsd libfglrx-legacy-amdxvba1
The following NEW packages will be installed:
fglrx-legacy-driver glx-alternative-fglrx glx-alternative-mesa
glx-diversions libfglrx-legacy nvidia-installer-cleanup
0 upgraded, 6 newly installed, 0 to remove and 16 not upgraded.
Need to get 15.8 MB of archives.
After this operation, 75.5 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://ftp.de.debian.org/debian/ wheezy-backports/contrib nvidia-installer-cleanup i386 20131102+1~bpo70+1 [17.9 kB]
Get:2 http://ftp.de.debian.org/debian/ wheezy-backports/contrib glx-diversions i386 0.4.1~bpo70+1 [9066 B]
Get:3 http://ftp.de.debian.org/debian/ wheezy-backports/non-free libfglrx-legacy i386 8.97.100.7-3~bpo70+1 [9513 kB]
Get:4 http://ftp.de.debian.org/debian/ wheezy-backports/contrib glx-alternative-mesa i386 0.4.1~bpo70+1 [2792 B]
Get:5 http://ftp.de.debian.org/debian/ wheezy-backports/contrib glx-alternative-fglrx i386 0.4.1~bpo70+1 [3658 B]
Get:6 http://ftp.de.debian.org/debian/ wheezy-backports/non-free fglrx-legacy-driver i386 8.97.100.7-3~bpo70+1 [6225 kB]
Fetched 15.8 MB in 1min 49s (144 kB/s)
Preconfiguring packages ...
Selecting previously unselected package nvidia-installer-cleanup.
(Reading database ... 28451 files and directories currently installed.)
Unpacking nvidia-installer-cleanup (from .../nvidia-installer-cleanup_20131102+1~bpo70+1_i386.deb) ...
Setting up nvidia-installer-cleanup (20131102+1~bpo70+1) ...
Selecting previously unselected package glx-diversions.
(Reading database ... 28459 files and directories currently installed.)
Unpacking glx-diversions (from .../glx-diversions_0.4.1~bpo70+1_i386.deb) ...
Selecting previously unselected package libfglrx-legacy:i386.
Unpacking libfglrx-legacy:i386 (from .../libfglrx-legacy_8.97.100.7-3~bpo70+1_i386.deb) ...
Selecting previously unselected package glx-alternative-mesa.
Unpacking glx-alternative-mesa (from .../glx-alternative-mesa_0.4.1~bpo70+1_i386.deb) ...
Selecting previously unselected package glx-alternative-fglrx.
Unpacking glx-alternative-fglrx (from .../glx-alternative-fglrx_0.4.1~bpo70+1_i386.deb) ...
Selecting previously unselected package fglrx-legacy-driver.
Unpacking fglrx-legacy-driver (from .../fglrx-legacy-driver_8.97.100.7-3~bpo70+1_i386.deb) ...
Setting up glx-diversions (0.4.1~bpo70+1) ...
Adding 'diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions'
Adding 'diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions'
Adding 'diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions'
Adding 'diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions'
Adding 'diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions'
Adding 'diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions'
Adding 'diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions'
Adding 'diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions'
Setting up libfglrx-legacy:i386 (8.97.100.7-3~bpo70+1) ...
Setting up glx-alternative-mesa (0.4.1~bpo70+1) ...
update-alternatives: using /usr/lib/mesa-diverted to provide /usr/lib/glx (glx) in auto mode
Setting up glx-alternative-fglrx (0.4.1~bpo70+1) ...
update-alternatives: using /usr/lib/fglrx to provide /usr/lib/glx (glx) in auto mode
I: update-initramfs is disabled (live system is running without media mounted on /lib/live/mount/medium).
Setting up fglrx-legacy-driver (8.97.100.7-3~bpo70+1) ...
root@debian:~#
5. Remove (or rename) /etc/apt/sources.list and rename back /etc/apt/sources.list-original to /etc/apt/sources.list and run apt-get update
I'm not sure if rebuilding initrd files is really needed after installing fglrx-legacy-driver but if it is and someone can give testing details and errors we can add further details in this post. Maybe someone will test this to confirm if it works or not and maybe provide working method if there is a problem with this one.
The best place to post if there is a problem and searching for solution is the development thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=90660
=========================================
DebianDog + Blue Pup Quirky Tahr Dual Boot USB Stick How-To
http://murga-linux.com/puppy/viewtopic.php?t=95139
and
How To Make A Network Storage NAS Appliance With DebianDog and OpenMediaVault
http://murga-linux.com/puppy/viewtopic.php?t=95249
Link added to the first post thread:
http://www.murga-linux.com/puppy/viewto ... 569#771569
Dual boot with Windows UTC - LOCAL time issue
anikin wrote:Hi everyone,This issue will occur on any machine that dual boots with Windows. What's happening is a clash of cultures, two great schools of thought - Microsoft vs nix. Linux uses UTC, while localtime is standard for Windows. The following piece is from antix.Satori wrote:I switch between various puppies, including yours, on a dell E6510 laptop. I'm finding that after rebooting from DebianDog
that the computer's hardware clock is off by a few hours, means I have to go to the bios and muck with it there.
Anyone else have this problem?How to set the correct date and time?
There are 3 possible issues:
1) wrong timezone 2) wrong selection of UTC versus local time 3) BIOS clock set wrong
The first issue is addressed with sudo dpkg-reconfigure tzdata. Do this first. You should also be able to just check the current value with cat /etc/timezone.
Once you are sure the timezone is correct, you can work on setting your BIOS clock. Do this with the hwclock command. First do a man hwclock and then run hwclock --show to see what it is set to. It always reports in localtime which is why you need to first make sure your timezone is set correctly.
Use hwclock --localtime or hwclock --utc depending on whether you want your hardware clock to be set to localtime or utc. Most pure Linux systems use utc. Most dual boot systems use localtime.
Then, after you get your date command working via the sudo command you posted, you can use hwclock --systohc to set the hardware clock so it matches your system time. Again, you need the timezone and localtime/utc choice set correctly first (although if you want to assume they are set correctly already then this is the only command you need to run to get your changes to the date command to stick. If you assumed incorrectly then you will likely get mysteriously screwed by DST a few times per year).
Finally, if you are having problems with hwclock drift or if you are a perfectionist then you can install the ntp package which will use time servers on the net to keep your clock exactly on time. But you have to first go through the steps above before ntp will work correctly.
Allow users to shutdown computer without typing user passwor
In case running DebianDog as normal user instead root.
User account puppy in DebianDog opens password prompt for reboot and shutdown. I think this is safe choice in case you use DebianDog as multiuser system. If other user accounts are active at the same time then shutdown and reboot by accident should be prevented.
Anyway if you like to remove password prompt for shutdown and reboot here is how to do it (the example is for user puppy). Will be included in next DebianDog as menu option.
For older DebianDog versions download and extract the attached archive. Install gsu_1.0.1_i386.deb and copy the included script shutdown-pass-activate_deactivate in /opt/bin
Login as user puppy (or other new created from you user account).
Create group wheel typing in terminal:
Code: Select all
sudo groupadd wheel
Code: Select all
sudo visudo
Code: Select all
# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL
%wheel ALL= NOPASSWD: /sbin/shutdown, /sbin/reboot, /sbin/poweroff, /usr/bin/wmpoweroff, /usr/bin/wmreboot, /usr/bin/save2flash
- Attachments
-
- shutdown-pass-gsu-deb.tar.gz
- (2.69 KiB) Downloaded 736 times
Virtualbox:
Open terminal and type (sudo is not needed for root account):
Code: Select all
sudo apt-get update
sudo apt-get install linux-headers-$(uname -r)
sudo apt-get install virtualbox-dkms
Code: Select all
puppy@debian:~$ sudo apt-get install virtualbox-dkms
...........................................................
Setting up virtualbox-dkms (4.1.18-dfsg-2+deb7u3) ...
Loading new virtualbox-4.1.18 DKMS files...
First Installation: checking all kernels...
Building only for 3.2.0-4-486
Building initial module for 3.2.0-4-486
Done.
vboxdrv:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.2.0-4-486/updates/
vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.2.0-4-486/updates/
vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.2.0-4-486/updates/
vboxpci.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.2.0-4-486/updates/
depmod................
DKMS: install completed.
[ ok ] Stopping VirtualBox kernel modules.
[ ok ] Starting VirtualBox kernel modules.
Code: Select all
sudo apt-get install virtualbox-qt
Code: Select all
virtualbox
http://kazzascorner.com.au/saintless/De ... z.squashfs
Removed linux-headers, virtualbox-dkms and other packages.
Works for me in OpenBox and Jwm version.
Move the module in /live boot folder and reboot.
Or if you prefer not to reboot after loading with sfs-load type:
Code: Select all
start-virtualbox
Code: Select all
/etc/init.d/virtualbox start
wait
virtualbox
Edit: In DebianDog-Squeeze after installing virtualbox-dkms you probably will get this message with the upgraded in squeeze-backports repository virtualbox and virtualbox-dkms ver. 4.1.18:
Code: Select all
DKMS: install Completed.
Stopping VirtualBox kernel modules.
Starting VirtualBox kernel modulesmodprobe vboxdrv failed. Please use 'dmesg' to find out why ... failed!
failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.
Code: Select all
puppy@debian:~$ sudo depmod -a
puppy@debian:~$ sudo /etc/init.d/virtualbox restart
Stopping VirtualBox kernel modules.
Starting VirtualBox kernel modules.
puppy@debian:~$
You need this RTAI kernel module:
027-kernel-3.4.9-rtai-686-pae.tar.gz - (download with right click save link as):
Extract the archive inside /live boot folder.
Included initrd files for live-boot-2.x, live-boot-3.x and porteus-boot.
Change your boot code to point:
initrd.img-rtai - live-boot-3 for linux-image-3.4-9-rtai-686-pae
initrd1.img-rtai - live-boot-2 for linux-image-3.4-9-rtai-686-pae
initrd1.xz-rtai - porteus-boot for linux-image-3.4-9-rtai-686-pae
vmlinuz1-rtai - linux-image-3.4-9-rtai-686-pae
The archive includes also readme text file with this information.
After first boot in 10-20 seconds xmessage window about installed firmware-linux-nonfree will popup. Also information about rtai kernel will be added in dpkg database. We need the kernel information registered because linuxcnc deb package has this kernel as dependency.
Maybe you will have working internet at the moment but if you don't (like I don't have) - after closing xmessage window try to setup the network. It should work now.
Check the new kernel after boot:
Code: Select all
uname -a
Linux debian 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-3linuxcnc i686 GNU/Linux
LinuxCNC 2.6 repository is added in /etc/apt/sources.list
Type in terminal first:
Code: Select all
sudo apt-get update
Code: Select all
sudo apt-get install linuxcnc
Code: Select all
sudo apt-get install libgl1-mesa-swx11 libosmesa6
Read more about this here, and here.
Official linuxcnc cd debian wheezy has much non-free firmware installed.
Maybe it is needed for linuxcnc to work properly. You can install all this firmware by typing in terminal:
Code: Select all
sudo apt-get install firmware-ivtv firmware-realtek firmware-myricom firmware-atheros firmware-bnx2x firmware-netxen firmware-iwlwifi firmware-ipw2x00 firmware-libertas firmware-intelwimax firmware-brcm80211 firmware-qlogic firmware-bnx2
You can download linux-headers for linux-image-3.4-9-rtai-686-pae kernel here (in case you need to install virtualbox by the previous post instruction):
linux-headers-3.4-9-common-rtai_3.4.55-4linuxcnc_i386.deb
linux-headers-3.4-9-rtai-686-pae_3.4.55-4linuxcnc_i386.deb
linux-kbuild-3.4_3.4-linuxcnc2_i386.deb
Download all three deb packages in some-folder-name and install them by typing:
Code: Select all
sudo dpkg -i /path-to/some-folder-name/*.deb
Code: Select all
sudo apt-get -f install
Sound problems and fixes
Problem 1. Cirrus Logic Audio controller - Sound is not working on old Dell OptiPlex Gxa with DebianDog-Wheezy because snd-cs4236 is not loaded on boot.(DebianDog-Squeeze works fine).
Fix 1: Add snd-cs4236 inside /etc/modules and reboot. More modprobe options available here
Usb-headphones problem solution from rufwoof shared here.
====================
Graphic cards problems:
1.Some Intel graphics cards will need this fix for glxgears to work properly (thank you, Darkcity and MrSpike16):
http://www.murga-linux.com/puppy/viewto ... 867#827867
MrSpike16 wrote:Its weird, but Nvidia drivers getting installed too for Intel graphics sometimes happens.
The Nvidia stuff needs to be purged and the Intel drivers, 3D (mesa) and Xorg need to be reinstalled.
These are the commands:
Restart the computer then try glxgears again and it should work.Code: Select all
sudo apt-get purge nvidia* sudo apt-get install --reinstall xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core sudo dpkg-reconfigure xserver-xorg sudo update-alternatives --remove gl_conf /usr/lib/nvidia-current/ld.so.conf
.
autologin & systemd
Here's a nice how to posted by Bro.Tiag on Debian user forum:
http://forums.debian.net/viewtopic.php?p=553954#p553954
which in turn is based on this Manjaro Wiki:
https://wiki.manjaro.org/index.php?titl ... th_Systemd
If you've modified /etc/inittab put it back to it's original.
From the console (as root);
mkdir /etc/systemd/system/getty@tty1.service.d
Edit autologin.conf
vi /etc/systemd/system/getty@tty1.service.d/autologin.conf
with;
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin root --noclear %I 38400 linux
Now update your .bash_profile;
# Following automatically calls - startx when you login:
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
Reboot.
Re: autologin & systemd
Is this relevant to the fact that doing a dist-upgrade from Wheezy to Jessie (in DebianDog) brings the need to log in at boot time, before the desktop comes up?anikin wrote:Autologin and startx without a display manager as implemented in DebianDog Wheezy, doesn't work in Debian Jessie, because systemd handles login quite differently...
If yes, then how is this applicable to DebianDog?--i.e. please give a step-by-step of how I get rid of the login prompt.
Infinality fonts for Debian Wheezy (and DebianDog-Wheezy):
How to install infinality:
Download all 9 deb packages from here in some folder (/tmp/infinality for example):
http://kazzascorner.com.au/saintless/De ... nfinality/
Install them all by typing in terminal:
Code: Select all
sudo dpkg -i /tmp/infinality/*.deb
Code: Select all
sudo apt-mark hold libcairo2 cairo-perf-utils fontconfig-config libcairo-gobject2 libcairo-script-interpreter2 libfreetype6
If you need for compiling or other reason libcairo2-dev install this deb with right click Install option menu:
http://kazzascorner.com.au/saintless/De ... ality/dev/
Or by typing:
Code: Select all
dpkg -i /path-to-package
Code: Select all
apt-get -f install
Code: Select all
sudo apt-mark hold libcairo2-dev
The packages above include infinality patches added from Keisha but separated in official Debian Wheezy packages to prevent dpkg database conflicts after installing infinality in Debian Wheezy.
Configuration changes for xterm and xfce4-terminal after installing infinality packages posted here.
Mirror link for Infinality-Wheezy packages.
===================
For DebianDog-Jessie try:
Infinality-Jessie packages - extract the archive and follow the instruction from Readme.txt
Mirror link for Infinality-Jessie packages.
Some more information about infinality for Jessie read here and here.
===================
configuration information for infinality
The one complaint I have seen so far involves fonting in the Terminal. For myself, I have solved this problem by this procedure:
1. Use Synaptic to install rxvt-unicode-256color.
2. Rename /usr/bin/xterm as /usr/bin/xterm--original and instead made /usr/bin/xterm be a symlink to /usr/bin/urxvtcd.
3. Then I installed (via synaptic) the Luxi fonts including my favorite terminal font, Luxi Mono.
4. Then I imported the configuration file /root/.Xdefaults from my pre-existing install of UnicornPup. It includes the following lines:
Code: Select all
Rxvt.keysym.0xFF50: \033[1~
Rxvt.keysym.0xFF57: \033[4~
Rxvt*saveLines: 1000
urxvt.foreground:#000000000000
urxvt.background:#bbbbbbbbbbbb
urxvt.underlineColor:#ffff00000000
! fonts
! run "fc-list" for a list of available fonts
rxvt.font: xft:Luxi Mono:style=Regular:pixelsize=14,000000
urxvt.font: xft:Luxi Mono:style=Regular:pixelsize=14,000000
urxvt.geometry:80x25
urxvt.scrollBar: True
urxvt.scrollTtyOutput: False
urxvt.scrollTtyKeypress: True
urxvt.secondaryScroll: True
urxvt.saveLines: 1000
urxvt.cursorUnderline:True
urxvt.cursorBlink:True
urxvt.transparent:Off
urxvt.shading:85
urxvt.borderLess:Off
configuration information for infinality, #2
just in case
started DD wireless howto thread
http://murga-linux.com/puppy/viewtopic. ... 212#833212
Didn't want to clutter up the main DD howto thread on what could be a big topic eventually. I needed to get wireless going on a couple of my machines but could only find a few posts about that in existing DD threads, hence my starting the above one. If such a thread already exists though, please let me know and I'll close the above one and move my examples across.
Cheers, William