Newsgroup: it.comp.os.linux.iniziare
Titolo: 2 problemi e una domanda

quando sembrava che la mia slackware stesse funzionando quasi al meglio, 
sono spuntati fuori 2 problemi di cui non capisco la causa...
1) non ho il permesso in scrittura su /dev/hda2
2)ogni volta che provo a lanciare startx ci mette un sacco e mi dice che
xauth va in timeout in locking authority file /home/rent/.Xauthority... 
mi da sto messaggio 3 volte e poi parte x dopo quasi un minuto, ho letto 
il man di xauth ma non ci ho capito niente...
grazie a chi rendera' questa mia mattinata meno nera di ieri sera...
ciao
rent

 1) non ho il permesso in scrittura su /dev/hda2
posta la riga corrispondente in /etc/fstab

redwiz wrote:

/dev/hda1       swap        swap        defaults   0   0
/dev/hda2       /        ext2        defaults   1   1
/dev/hdd1       /fat     vfat        defaults   1   1
none             /dev/pts  devpts     gid=5,mode=620  0   0
none             /proc    proc        defaults   0   0
ahh mi ero scordato la domanda... si puo' passare da slcak 8 a 9 in 
maniera indolore?
thx
rent


This document explains how to upgrade from Slackware 8.1 to Slackware
9.0
Before you begin, I would strongly recommend making a backup of your
system, or, if not the entire system, at least the /etc directory.  You
might find that you need to refer to a few things about the upgrade
process is complete. Back it up, or take your chances.
OK, now that everything is safely backed up, let's proceed. :-)
To do this, you'll need the Slackware 9.0 packages.  If these are on a
CD, create a new directory to mount the CD on so that it doesn't get in
the way during the upgrade:
mkdir /packages
mount /dev/cdrom /packages
The packages don't have to be on a CD-ROM, as an alternative you could
copy the slackware directory (the one with the various package
subdirectories in it, basically the "slackware" directory from the
install CD) to someplace like /root/slackware/.  The important thing is
that you know where the slackware packages directory is.  We'll use
/root/slackware in the following examples.
0.  Put your machine in single-user mode:
    telinit 1
1.  Upgrade your glibc shared libraries.  This is important, or things  
 will go haywire during the first part of the upgrade:
    upgradepkg /root/slackware/a/glibc-solibs-*.tgz
2.  Upgrade your package utilities:
    upgradepkg /root/slackware/a/pkgtools-*.tgz
3.  Upgrade everything else (and install new packages):
    upgradepkg --install-new /root/slackware/*/*.tgz
4.  Make sure your system will boot.  If you use LILO, make sure the
    paths in /etc/lilo.conf point to a valid kernel and then type 'lilo'
    to reinstall LILO.  If you use a bootdisk, you'll need to use
    makebootdisk to make a new bootdisk using the kernel in /boot.
5.  Fix your config files.  Some of the config files in /etc are going
to     need your attention.  You'll find the new incoming config files
on     your system with the ".new" extension.  You may need to fill
these in     with information from your old config files and then move
them over.
6.  Return to multi-user mode:
    telinit 3
Finally, you might want to go into /var/log/packages, and take a look at
the package list:
    ls -l | less
You may spot some old, obsolete, or discontinued packages.  If so, you
can remove these using 'removepkg'.
At this point you should be running Slackware 9.0.  :-)
 I wish everyone good luck with this! 
+--8<-- cut here --8<--+
ciao
- -- 
Try the Linux Live Experience!
Stixx Live! 1.0 released:
http://www.stixx.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
iEYEARECAAYFAj9XErkACgkQLpOZQGVrY42COwCfSVbmbBa+bPYSvGeQtCvFtN61
ORkAnRJPN14nwL6th6lz/+PNsRPqoE5J
=oblK
-----END PGP SIGNATURE-----


grazie... metto a scaricare la 9 allora...
ciao
rent

>> Informazioni e link su 
http://www.softwarelibero.org

 un GROSSO problema di sicurezza...
scusami mi sono espresso male forse... /dev/hda2 e' la partizione 
linux... /dev/hda1 e' la swap
forse ora e' piu' chiaro...
ciao
rent

 linux... /dev/hda1 e' la swap
E` lo stesso.
Gli utenti NON DEVONO poter scrivere sui device dei dischi, altrimenti
i danni potenziali sono enormi.
Neanche root dovrebbe leggere o scrivere _direttamente_ sulle device,
salvo rari casi.


 ciao
ciao e buona fortuna.
Desidio
-- 
questo articolo e` stato inviato via web dal servizio gratuito 
http://www.newsland.it/news
 segnala gli abusi ad 
ab...@newsland.it

 relativa!
si ho un nvidia geforce, ma la 2 penso.. e' vecchiotta.. cmq i driver 
funzionano benissimo.. e che secondo me il problema dei permessi causava 
anche quest'altro di X.. infatti con il nuovo utente funziona tutto, 
quasi tutto... e X parte tranquillamente...
grazie cmq dei consigli :)
ciao
rent