Linpus anyone?

wonder if 9.6 is installable... distrowatch says it should be?

http://distrowatch.com/table.php?distribution=linpus

Quote:

---

Anyone with better linux experience please teach me how to add a custom resolution.

---

I installed Dream Linux for someone that wanted a carputer (or rather sold my old HD w/ DreamLinux preinstalled)... had the same question... not sure if this will work in Linpus though

Quote:

---

You can try to edit the xorg.conf including the correct resolution screen.

For safe, first do a backup of original configuration, open terminal and:
Code:

sudo cp /etc/X11/xorg.conf /etc/X11/xorg-backup.conf


Then, edit the screen section of your xorg.conf:
If you are on Xfce, open it with:

Code:
gksu mousepad /etc/X11/xorg.conf


If you are on Gnome:

Code:
gksu gedit /etc/X11/xorg.conf


Now only include the appropriate resolution (below you see an example of my screen section running fine on 1280x1024, if I had the problem you are, I had only to write and keep the resolution I would like).

Example original

Quote:

---

Section "Screen"
Identifier "Default Screen"
Device "UniChrome Pro IGP"
Monitor "SAMSUNG SyncMaster"
DefaultDepth 24
SubSection "Display"
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

---

Example modified

Quote:

---

Section "Screen"
Identifier "Default Screen"
Device "UniChrome Pro IGP"
Monitor "SAMSUNG SyncMaster"
DefaultDepth 24
SubSection "Display"
Modes "800x480" "640x480"
EndSubSection
EndSection

---

After you modify the file according your computer specs (not mine, please), save, close it and Quit > Logout.

If not works, you can restore the original configuration with the command:

Code:
sudo cp /etc/X11/xorg-backup.conf /etc/X11/xorg.conf

---

followed the exact procedure, and many other similar, but still no luck.
I have no problem editing the file, no problem saving the file, but it always revert back to the original setting somehow. Starting to give up.

Quote:

---

Originally Posted by Punky

followed the exact procedure, and many other similar, but still no luck.
I have no problem editing the file, no problem saving the file, but it always revert back to the original setting somehow. Starting to give up.

---

Try setting the immutable flag with chattr on your xorg.conf and check your logs for errors, that should help pin down what's wiping out your config.

could you explain more detail, sorry i'm totally noob in linux.

Quote:

---

followed the exact procedure, and many other similar, but still no luck.

---

Wasn't sure if it would work, but seemed to be the best option I knew of

As for the immutable thing, here's the best I could find that explains it, maybe someone else could fill in the gaps

http://linuxhelp.blogspot.com/2005/1...hich-even.html

Quote:

---

Originally Posted by Punky

could you explain more detail, sorry i'm totally noob in linux.

---

Kardain's link is a pretty good write-up. Basically, if you make a file "immutable", even root can't delete the file (without turning it off anyway), so whatever is overwriting your xorg.conf, won't be able to, and hopefully, you see an error message stating such in the log, then you should be able to figure out what exactly is trying to configure X for you and make the change in the right place so it won't be overwritten.

i have the following error when i try using that command
"chattr: Inappropriate ioctl for device while reading flags on xorg.conf"

Quote:

---

Originally Posted by Punky

i have the following error when i try using that command
"chattr: Inappropriate ioctl for device while reading flags on xorg.conf"

---

Weird, what type of file system is it? You can look in "/etc/fstab" to find out. Maybe it's not ext3, I googled a bit but could not find out. I did see some people with the same complaint (that xorg.conf is overwritten on boot).

It would probably be easier to just look through the boot scripts (in /etc/init.d) and find when it overwrites it, and from where, and either modify it, or change the one it generates so your changes stay permanent.

Another possibility would be to save your changes as xorg.conf.mine or something and before xstarts, add a startup script to copy it to xorg.conf right before X starts

The file system is definitely ext3 from the fstab file.
I searched every file in the init.d folder for the string xorg, and the only file i found which this string was: xfs file
here is the content:

Quote:

---

#!/bin/bash
#
# $Id:$
#
# xfs: Starts the X Font Server
#
# Version: @(#) /etc/init.d/xfs 2.0
#
# chkconfig: 2345 90 10
# description: Starts and stops the X Font Server at boot time and shutdown. \
# It also takes care of (re-)generating font lists.
#
# processname: xfs
# config: /etc/X11/fs/config
# hide: true

# Source function library.
export LANG=C
. /etc/init.d/functions
# Set umask to ensure fonts.dir and similar files get created mode 0644
umask 133

prog=xfs

buildfontlist() {
pushd . &> /dev/null
# chkfontpath output filtering, strips all of the junk output by
# chkfontpath that we do not want, including headers, FPE numbers and
# whitespace and other junk. Also filters out FPE's with trailing
# modifiers such as ":unscaled" et al.
for dir in $(/usr/sbin/chkfontpath --list | sed -e '/^Current/d;s#^[0-9]*: ##g;s#:unscaled$##g;/^[[:space:]]*$/d' | sort | uniq) ;do
if [ -d "$dir" ]; then
cd "$dir"
# If fonts.dir does not exist, or if there are files in the
# directory with a newer change time, regenerate fonts.dir, etc.
# Using "-cnewer" here fixes bug #53737
if [ ! -e fonts.dir ] || [ -n "$(find . -maxdepth 1 -type f -cnewer fonts.dir -not -name 'fonts.cache*' 2>/dev/null)" ]; then
rm -f fonts.dir &>/dev/null
if ls | grep -iqs '\.ot[cf]$' ; then
# Opentype fonts found, generate fonts.scale and fonts.dir
mkfontscale . && mkfontdir . &>/dev/null
elif ls | grep -iqs '\.tt[cf]$' ; then
# TrueType fonts found, generate fonts.scale and fonts.dir
ttmkfdir -d . -o fonts.scale && mkfontdir . &>/dev/null
elif ls | grep -Eiqsv '(^fonts\.(scale|alias|cache.*)$|.+(\.[ot]t[cf]|dir)$)' ; then
# This directory contains non-TrueType/non-Opentype fonts
mkfontdir . &>/dev/null
fi
fi
fi
done
popd &> /dev/null
}

start() {
FONT_UNIX_DIR=/tmp/.font-unix
echo -n $"Starting $prog: "
[ -x /usr/sbin/chkfontpath ] && buildfontlist
# Clean out .font-unix dir, and recreate it with the proper ownership and
# permissions.
rm -rf $FONT_UNIX_DIR
mkdir $FONT_UNIX_DIR
chown root:root $FONT_UNIX_DIR
chmod 1777 $FONT_UNIX_DIR
# Fix needed for SELinux for bug (#130421,130969)
[ -x /sbin/restorecon ] && /sbin/restorecon $FONT_UNIX_DIR

daemon xfs -droppriv -daemon
ret=$?
[ $ret -eq 0 ] && touch /var/lock/subsys/xfs
echo
return $ret
}

stop() {
echo -n $"Shutting down $prog: "
killproc xfs
ret=$?
[ $ret -eq 0 ] && rm -f /var/lock/subsys/xfs
echo
return $ret
}

rhstatus() {
status xfs
}

reload() {
if [ -f /var/lock/subsys/xfs ]; then
echo -n $"Reloading $prog: "
[ -x /usr/sbin/chkfontpath ] && buildfontlist
killproc xfs -USR1
ret=$?
echo
return $ret
else
stop
start
fi
}

restart() {
echo $"Restarting $prog:"
stop
start
}

#condrestart() {
# NOTE: We reload normally, to ensure the xfs<->Xserver connection does
# not get broken on xfs upgrades, however we must force a restart on
# upgrades that are migrating from monolithic Xorg (6.8.x or older) to
# modular X, to avoid bug #173271. The modular xfs %preun script will
# now check for the old config file to determine if migration should be
# done, and touch the following migration file if necessary.
# if [ -e /etc/X11/fs/xfs-migrate ] ; then
# restart
# rm -f /etc/X11/fs/xfs-migrate || : &> /dev/null
# else
# reload
# fi
#}

#case "$1" in
# start)
# start
# ;;
# stop)
# stop
# ;;
# restart)
# restart
# ;;
# reload)
# reload
# ;;
# condrestart)
# [ -f /var/lock/subsys/xfs ] && condrestart || :
# ;;
# status)
# rhstatus
# ;;
# *)
# echo $"Usage: $prog {start|stop|status|restart|reload|condrestart}"
# exit 1
#esac

exit $?

---

I tried commenting out the bottom function completely, then edit the xorg.conf file, but after reboot it still reverted back. I have never done scripting in linux, and i'd rather not, because thats another script that'll slow down the startup time.
Any other ideas?

Hmmm, do you have a /mnt/hd/etc/X11/xorg.conf file?