sto scaricando la versione current di slackware
per avere una roller appunto di slackware da tenere sempre aggiornata
ho sempre usato xfce , ma ho scoperto che anche kde plasma mi piace , e vorrei installarlo appunto sulla current
come devo procedere ?
questi sono i passaggi che farò , dopo non vorrei sbagliare e chiedo un'aiuto
installo slackware normalmente
impostao kde come ambiente predefinito
chiedo come
installare kde plasma
configurare correttamente current per avere la roller di slackware
Meglio se di KDE non installi niente perché comunque poi ti toccherà rimuoverlo.
Ci sono almeno due modi per installare Ktown (kde5): il primo è quello ufficiale, spiegato direttamente da alienbob nel README che accompagna il repo,
lo riporto integralmente:
KDE5
====
Here is KDE 5_17.10 for Slackware, consisting of the KDE Frameworks 5.39.0,
Plasma 5.11.0 and Applications 17.08.2 on top of Qt 5.9.2.
Upgrading from the previous 5_17.09 is straight-forward.
KDE-5_17.10 is meant to be installed on top of Slackware -current.
It will *replace* any version of KDE 4 you might have installed! Plasma 5
has mostly gotten rid of its Qt4 legacy. Applications 17.12 will no longer
ship anything based on kdelibs4.
What is the NEWS in this batch of updates:
- A few updates in the deps section. Most importantly, qt5 was upgraded
to 5.9.2. Two packages were recompiled: ddcutil and gpgme.
- Plasma was updated to 5.11.0, see
https://www.kde.org/announcements/plasma-5.11.0.php .
I compiled plasma5-nm against openconnect so that it picks up support for
it. However I did not add openconnect to the 'deps' section, you need
to install it separately if you need it.
New to Plasma 5.11 is the Vault. It needs an encryption backend (cryfs or
encfs) at runtime but I did not add these to the 'deps'. I might create
packages for those in my regular repository however.
Plasma 5.11 has more improvements, among others it comes with a new design
for systemsettings.
- Frameworks 5.39.0 contains one new framework: qqc2-desktop-style, see
https://www.kde.org/announcements/kde-frameworks-5.39.0.php
- Applications 17.08.2 is a stability update for KDE Applications
17.08 (where the following applications are finally also KF5 based: kmag,
kmousetool, kgoldrunner, kigo, konquest, kreversi, ksnakeduel, kspaceduel,
ksudoku, kubrick, lskat, and umbrello).
See https://www.kde.org/announcements/announce-applications-17.08.2.php .
- In applications-extra I updated kpmcore, partitionmanager, krita and
the kdevelop suite (now finally including kdev-python).
Further points of interest:
- There are a couple of *runtime* dependencies that I did not add to the
ktown repository, but you may want to consider installing them yourself:
* vlc - will give phonon another backend to select from.
* freerdp: access RDP servers through krdc.
* openconnect: support for Cisco's SSL VPN.
All of these can be found in my regular package repository.
- The following kde/kde4-extragear packages should be taken from slackware
itself if you still need them: kaudiocreator, kplayer, kwebkitpart.
- Lots of packages in the 'deps' department are completely new to Slackware.
Since KDE 5 aka Plasma 5 is built on Qt5 (KDE 4 uses Qt4 as its base)
you'll find many Qt5 related packages. Also, in order for Qt4 and GTK based
applications to dock into the Plasma 5 system tray, more dependencies were
needed. So, apart from updates to regular Slackware packages and the
new telepathy support packages (see below), these are the new ones:
OpenAL, PyQT5, accountsservice, cfitsio, cracklib, ddcutil, dvdauthor,
frei0r-plugins, grantlee-qt4, hack-font-ttf, id3lib, json-glib, lensfun,
libappindicator, libburn, libdbusmenu-gtk, libdbusmenu-qt5, libdmtx,
libindicator, libinput, libpwquality, libwacom, libxkbcommon, lmdb, mlt,
ninja, noto-font-ttf, noto-cjk-font-ttf, opencv, polkit-qt5-1, qca-qt5,
qrencode, qt-gstreamer, qt5, qt5-webkit, qtav, sni-qt, vid.stab
and wayland.
As a side note, libinput and libwacom have become part of Slackware-current.
Technically that makes them redundant in the above listing, however I still
compile Plasma5 packages for Slackware 14.2 so I left them in.
The phonon and poppler packages were extended so that they now support
Qt5 as well as Qt4.
Note that the SBo version of 'frei0r-plugins' package is called 'frei0r'.
If you have that SBo package installed, remove it.
- A completely new subset of "deps" packages, contained in their own
"telepathy" subdirectory, needed for KDE Telepathy:
libotr, libnice, farstream, libaccounts-glib, libaccounts-qt5,
signon, signon-plugin-oauth2, signon-ui, libsignon-glib, telegram-qt,
telepathy-glib, telepathy-farstream, telepathy-haze, telepathy-gabble,
telepathy-morse, telepathy-qt5, telepathy-logger, telepathy-logger-qt5,
telepathy-mission-control and telepathy-accounts-signon.
- Telepathy for KDE packages are found in their own subdirectory kde/telepathy .
- The kde/kde4 and kde/kde4-extragear directories contain packages that are
still required to support kdelibs4-based Applications.
- Also worth mentioning: the KF5 ports of calligra, digikam, kile, krita,
ktorrent, partitionmanager, skanlite and the KDE Development Suite
can be found in kde/applications-extra .
Finally, kjots (previously contained in KDEPIM) and kuser (abandoned by its
developer) have been moved into kde/applications-extra as well.
NOTE:
If you install a 32bit program on a 64bit Slackware computer with multilib
and that program needs legacy system tray support (think of Steam for
instance), you will have to grab the 32-bit version of Slackware's
'libdbusmenu-qt' and my ktown-deps package 'sni-qt', and run the
'convertpkg-compat32 -i' command on them to create 'compat32' versions
of these packages. Then install both 'libdbusmenu-qt-compat32' and
'sni-qt-compat32'. Those two are mandatory addons for displaying
system tray icons of 32bit binaries in 64bit multilib Plasma5.
NOTE:
Also explained in more detail below, upgrading to this KDE 5 is non-trivial.
You will have to remove old KDE 4 packages manually. If you do not have KDE
installed at all, you will have to *install* some of Slackware's own KDE 4
packages manually.
NOTE:
If you decide to install these packages on top of a fresh installation of
Slackware 14.2 or -current and have excluded all packages in the 'KDE'
package series during installation, you will be missing several add-on
packages. You can optionally install the following Slackware packages:
* amarok
* kaudiocreator
* kplayer
* kwebkitpart
NOTE:
If you had installed KDE 4 as your default desktop previously, the removal
of KDE 4 packages will break the symbolic link '/etc/X11/xinit/xinitrc'.
An attempt to run 'startx' in a console will fail with a black screen.
After installing Plasma 5 for the first time, you need to run 'xwmconfig'
and select 'xinitrc.plasma' as your desktop session.
-------------------------------------------------------------------------------
Install pre-compiled packages:
-------------------------------------------------------------------------------
In order to install or upgrade KDE 5, follow these steps:
Make sure you are not running KDE or even X ! If you are running an X session,
log out first, and if you are in runlevel 4 (graphical login) you first have to
go back to runlevel 3 (console) by typing "init 3".
If you still have a KDE 4 installed, it must be removed first. No clean
upgrade path can be provided! Do as follows:
If you have Slackware 14.2 or -current's default KDE 4.14.3 installed:
# removepkg /var/log/packages/*-4.14.3-*
# removepkg libkscreen
# removepkg kscreen
# removepkg kactivities
# removepkg kde-workspace
# removepkg libmm-qt
# removepkg libnm-qt
# removepkg plasma-nm
# removepkg polkit-kde-agent-1
# removepkg polkit-kde-kcmodules-1
# removepkg kdeconnect-kde
# removepkg kdepim
# removepkg kdepimlibs
# removepkg kdev-python
# removepkg kdevelop-php
# removepkg kdevelop-php-docs
..or instead of the above, simply '# slackpkg remove kde' and de-select
the packages you want to keep (amarok, etc).
Alternatively, in case you are already using an older release of my KDE 5
packages, you need to look up that particular release in the list right below
(for instance: KDE 5_16.08) and then apply the actions shown for that KDE 5
release *and* all more recent releases, i.e. work your way back up to this
paragraph. Note that some of the old KDE package names were obsoleted along
the way, they were split up, renamed or integrated and that is the reason
for some of the 'removepkg' lines you'll see below.
Here we go:
If you have my 'ktown' set of KDE 5_17.09 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.07 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.06 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.05_02 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.05 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.04 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.03 installed:
- Upgrade to KDE 5_17.04
Remove the packages that no longer exist in KDE 5_17.04:
* removepkg kajongg
* removepkg kommander
* removepkg pim-storage-service-manager
If you have my 'ktown' set of KDE 5_17.02 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.01 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.12 installed:
- Upgrade to KDE 5_17.01
If you are running Slackware-current, manually install or upgrade libinput
and libwacom to the Slackware versions.
Remove the packages that no longer exist in KDE 5_17.01:
* removepkg kactivities
* removepkg nepomuk
* removepkg nepomuk-widgets
* removepkg gpgmepp
* removepkg kdgantt2
* removepkg kde-baseapps kdepim kdewebdev
If you have my 'ktown' set of KDE 5_16.11 installed:
- Upgrade to KDE 5_16.12
Remove the packages that no longer exist in KDE 5_16.12:
* removepkg baloo
* removepkg baloo-widgets
If you have my 'ktown' set of KDE 5_16.08 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.07 installed:
- Upgrade to KDE 5_16.08
Remove the packages that no longer exist in KDE 5_16.07:
* removepkg kdegraphics-strigi-analyzer
* removepkg kdenetwork-strigi-analyzers
* rempovepkg kdesdk-strigi-analyzers
* removepkg kdepimlibs libkdeedu mplayerthumbs
If you have my 'ktown' set of KDE 5_16.06 installed:
- Upgrade to KDE 5_16.07
Remove the packages that no longer exist in KDE 5_16.07:
* removepkg /var/log/packages/noto-font-ttf-2015-09-29-noarch-1alien
If you have my 'ktown' set of KDE 5_16.05 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.04 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.03 installed:
- Upgrade to KDE 5_16.04
Remove the packages that no longer exist in KDE 5_16.04:
* removepkg kactivities-workspace
If you have my 'ktown' set of KDE 5_16.02 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.01 installed:
- No further actions are needed.
Then proceed with installing/upgrading KDE 5 as outlined below.
NOTE:
The example commands below are for Slackware -current but you can use
these commands for Slackware 14.2 as well by replacing the /current/
string with /14.2/ (provided there is a suitable 'ktown' release available
for Slackware 14.2 of course):
NOTE:
Instead of using the mirror host bear.alienbase.nl/mirrors/alien-kde/ ,
you could choose the alternative mirror http://slackware.uk/people/alien-kde/
NOTE:
If you use 'slackpkg' to automate your upgrades, be sure to blacklist my
custom packages or else slackpkg will always try to replace my packages
with the stock Slackware versions if the package names are identical.
As an example, you can add the following lines to the file
"/etc/slackpkg/blacklist" to prevent this unintentional downgrading to KDE4:
# These three lines will blacklist all SBo, alien and multilib packages:
[0-9]+_SBo
[0-9]+alien
[0-9]+compat32
If on the other hand you are using the 'slackpkg+' extension for slackpkg
then your "/etc/slackpkg/blacklist" file should *not* contain the above
lines! The slackpkg+ extension enables the use of 3rd-party repositories
with slackpkg and then Plasma5 package upgrades will be handled properly.
To make it easy for you, here is a one-line command that downloads the whole
'5' directory (excluding the sources), with 32-bit and 64-bit packages.
# rsync -Hav rsync://bear.alienbase.nl/mirrors/alien-kde/current/5/ 5/
Or else, if you want to download packages for just one of the two supported
architectures, you would run one of the following commands instead.
If you want only the 64-bit packages:
# rsync -Hav --exclude=x86 rsync://bear.alienbase.nl/mirrors/alien-kde/current/5/ 5/
If you want only the 32-bit packages:
# rsync -Hav --exclude=x86_64 rsync://bear.alienbase.nl/mirrors/alien-kde/current/5/ 5/
Assuming you just downloaded the bits you want from the directory tree "5",
you must now change your current directory to where you found this README
(which is the directory called '5'). If you used one of the above "rsync"
commands then you can simply do:
# cd 5
From within this directory, you run the following commands as root:
On Slackware 32-bit:
# upgradepkg --reinstall --install-new x86/deps/*.t?z
# upgradepkg --reinstall --install-new x86/deps/telepathy/*.t?z
# upgradepkg --reinstall --install-new x86/kde/*/*.t?z
On Slackware 64-bit:
# upgradepkg --reinstall --install-new x86_64/deps/*.t?z
# upgradepkg --reinstall --install-new x86_64/deps/telepathy/*.t?z
# upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z
If you already have one or more non-english language packs installed:
On Slackware 32-bit:
# upgradepkg x86/kdei/*.t?z
On Slackware 64-bit:
# upgradepkg x86_64/kdei/*.t?z
If you want to have a non-english language pack installed but none is
currently installed, substitute your country code instead of the 'XX'
in the next command:
# upgradepkg --install-new x86_64/kdei/kde-l10n-XX-*.t?z
Note that these separate language packs contain only the localizations for
kdelibs4 based applications. All KDE Frameworks 5 based programs include
localizations in the packages themselves (meaning that you will get all
languages installed always).
Check if any ".new" configuration files have been left behind by
the upgradepkg commands. Compare them to their originals and decide
if you need to use them.
# find /etc/ -name "*.new"
A graphical (ncurses) tool for processing these "*.new" files is slackpkg:
# slackpkg new-config
Then reboot your system.
If all you want is to install the packages I created, then you can skip the
remainder of the README which details how to (re)compile the packages from
their sources; it is not required reading material.
-------------------------------------------------------------------------------
Building it all from source:
-------------------------------------------------------------------------------
Sources and scripts are separated from the packages in my 'ktown' repository.
If you want the sources for KDE 5, run the following command to download them
(downloading from a mirror will usually be much faster):
# rsync -Hav rsync://bear.alienbase.nl/mirrors/alien-kde/source/5/ 5/
There are a lot of 'dependencies' for KDE 5 which you'll have to compile and
install before attempting to compile KDE 5. Compiling and installing these
dependencies on Slackware-current is as easy as:
# cd 5/deps
# ./updates.SlackBuild
# cd -
# cd 5/deps/telepathy
# ./telepathy.SlackBuild
# cd -
Be prepared to wait a *long* time since this will compile a new Qt5 package
among others. The finished packages will be stored in /tmp and will already
have been installed/upgraded automatically.
Then if you want to compile the KDE packages on your computer, run:
# cd 5/kde
# ./KDE.SlackBuild
Wait a long time, and you will find the new packages in /tmp/kde_build .
Note that these packages will already have been installed by KDE.SlackBuild !
Reboot your computer and login to a Plasma session.
==============================================================================
Eric Hameleers / alien at slackware dot com / 13-oct-2017
Il secondo, che io ho sperimentato di recente, è meno laborioso e prevede l'uso di slackpkgplus, ma potresti dover intervenire per dei ritocchi in un secondo momento.
Quale dei due metodi preferisci? (io ti consiglio il primo)
il numero uno :)
ps è la current non la stable
L'hai già fatta l'installazione di base o la devi ancora fare? ...Come l'hai fatta?
allora ho installato la current di slackware
ora hoconfigurato slackpkg e slackpkgplus
sto facendo upgrade all
nella slackpkg/mirror ho decommentatoo it in current
dopo l'upgade all devo disinstallare kde (a farlo prima dell'upgrade :( )
... dovrebbe essere:
slackpkg remove kde kdei
per rimuovere il vecchio kde e i suoi pacchetti delle lingue.
Poi lo inserisci nella blacklist:
slackpkg blacklist kde
e
slackpkg blacklist kdei
fai l'upgrade (se lo avevi fatto prima va bene lo stesso)
A questo punto puoi anche configurare il repo di Ktown (vedi il mio ultimo post del vademecum), metterlo con priorità (...come avevi fatto con multilib).
Solo dopo aver fatto queste operazioni puoi installarlo con:
slackpkg install ktown
Questo è il secondo metodo, ma se stai armeggiando con slackpkg ti può fare solo bene questa esperienza.
NOTA: quando fai modifiche ai repo, come in questo caso, ricordati di dare i comandi di update.
Se invece pensi ancora al primo metodo sappi che le istruzioni sono già tutte nel README che ho postato, e tu dovresti essere in grado di "leggere" e "procedere" senza ulteriore aiuto...
P.S.
Con la current cerca di fare ricorso a SlackBuilds.org (sbopkg) meno che puoi. Cerca invece di farti bastare il repo di alien più che puoi...
EDIT:
Altra cosa molto importante: con la Current DEVI usare anche il comando slackpkg install-new prima di dare l'upgrade-all.
ho dato slackpkg install ktown
ha fatto tutto ma quando ho dato logout e digitato xwmconfig
non ho trovato kdeplasma
Quando si fanno queste cose prima si riavvia il PC poi si avvia il nuovo ambiente. Quindi riavvia e riprova.
Nel caso in cui qualcosa non funzionasse devi vedere quali pacchetti in ktown eventualmente non sono stati installati, per cui dai un:
slackpkg search ktown
Quelli che risultano uninstalled dovrai installarli a mano, con:
slackpkg install pacchetto2 pacchetto1
pacchetto3 ecc.
In alternativa, quando neanche così funzionasse, leggerai quel README e passerai al metodo n.1. Tanto il lavoro con slackpkg dovevi farlo in ogni caso...
Ricordati di riaviare...
EDIT:
Sto provando a fare la stessa installazione ma invece di usare il semplice: slackpkg install ktown, specifico meglio e installo prima:
slackpkg install ktown;deps
poi
slackpkg install ktown;kde
e poi mi cercherò il pacchetto dell'italiano in kdei.
Ti faccio sapere com'è andata.
forese c'è qualcosa che non va nei mirror
provo a installare i pachetti e mi dice che non li trova
bash-4.3# slackpkg install plasma-desktop-5.11.0-x86_64-1alien
Looking for plasma-desktop-5.11.0-x86_64-1alien in package list. Please wait... DONE
No packages match the pattern for install. Try:
/usr/sbin/slackpkg reinstall|upgrade
bash-4.3#
Il mirror o funziona oppure no, se ha funzionato prima, e tu non l'hai manomesso, forse funzionerà ancora...
...Piuttosto il nome non è completo, manca l'estensione. Però, prima di continuare, prova a dare:
slackpkg install ktown;kde
e poi fammi sapere.
...L'ho appena fatto io e non funziona.
con search ktowm mi da questo
senza estensione
(http://i.imgur.com/0wUJ9qZ.png)
Credo di aver trovato la soluzione...
apri la blacklist e per il momento cancella (o commenta) le voci kde e kdei.
leafpad /etc/slackpkg/blacklist
adesso dai slackpkg install ktown
noterai che i pacchetti selezionati per l'installazione sono molti più di prima. Installali tutti. Poi riavvia il PC. Poi fai partire kde.
Una volta installato bisognerà decidere se inserire il vecchio kde nella blacklist o nella greylist. Il README, che alla fine dovrai leggere, contiene anche informazioni interessanti in proposito...
ora dovremmo esserci
(http://i.imgur.com/yA6qUpW.png)
nulla va in crash
(http://i.imgur.com/MXdeSMH.png)
sono entrato con xfce
ho rifatto uodate gpg , update, install-new , upgrade-all
ho pigiato y quando mi ha chiesto del kernel (o giu di li)
e non ho piu riconosciuto piu nessun comando
(http://i.imgur.com/8acEg8r.png)
che faccio reinstallo current e proviamo con il metodo ufficiale senza installare kde?
KDE5
====
Here is KDE 5_17.10 for Slackware, consisting of the KDE Frameworks 5.39.0,
Plasma 5.11.0 and Applications 17.08.2 on top of Qt 5.9.2.
Upgrading from the previous 5_17.09 is straight-forward.
KDE-5_17.10 is meant to be installed on top of Slackware -current.
It will *replace* any version of KDE 4 you might have installed! Plasma 5
has mostly gotten rid of its Qt4 legacy. Applications 17.12 will no longer
ship anything based on kdelibs4.
What is the NEWS in this batch of updates:
- A few updates in the deps section. Most importantly, qt5 was upgraded
to 5.9.2. Two packages were recompiled: ddcutil and gpgme.
- Plasma was updated to 5.11.0, see
https://www.kde.org/announcements/plasma-5.11.0.php .
I compiled plasma5-nm against openconnect so that it picks up support for
it. However I did not add openconnect to the 'deps' section, you need
to install it separately if you need it.
New to Plasma 5.11 is the Vault. It needs an encryption backend (cryfs or
encfs) at runtime but I did not add these to the 'deps'. I might create
packages for those in my regular repository however.
Plasma 5.11 has more improvements, among others it comes with a new design
for systemsettings.
- Frameworks 5.39.0 contains one new framework: qqc2-desktop-style, see
https://www.kde.org/announcements/kde-frameworks-5.39.0.php
- Applications 17.08.2 is a stability update for KDE Applications
17.08 (where the following applications are finally also KF5 based: kmag,
kmousetool, kgoldrunner, kigo, konquest, kreversi, ksnakeduel, kspaceduel,
ksudoku, kubrick, lskat, and umbrello).
See https://www.kde.org/announcements/announce-applications-17.08.2.php .
- In applications-extra I updated kpmcore, partitionmanager, krita and
the kdevelop suite (now finally including kdev-python).
Further points of interest:
- There are a couple of *runtime* dependencies that I did not add to the
ktown repository, but you may want to consider installing them yourself:
* vlc - will give phonon another backend to select from.
* freerdp: access RDP servers through krdc.
* openconnect: support for Cisco's SSL VPN.
All of these can be found in my regular package repository.
- The following kde/kde4-extragear packages should be taken from slackware
itself if you still need them: kaudiocreator, kplayer, kwebkitpart.
- Lots of packages in the 'deps' department are completely new to Slackware.
Since KDE 5 aka Plasma 5 is built on Qt5 (KDE 4 uses Qt4 as its base)
you'll find many Qt5 related packages. Also, in order for Qt4 and GTK based
applications to dock into the Plasma 5 system tray, more dependencies were
needed. So, apart from updates to regular Slackware packages and the
new telepathy support packages (see below), these are the new ones:
OpenAL, PyQT5, accountsservice, cfitsio, cracklib, ddcutil, dvdauthor,
frei0r-plugins, grantlee-qt4, hack-font-ttf, id3lib, json-glib, lensfun,
libappindicator, libburn, libdbusmenu-gtk, libdbusmenu-qt5, libdmtx,
libindicator, libinput, libpwquality, libwacom, libxkbcommon, lmdb, mlt,
ninja, noto-font-ttf, noto-cjk-font-ttf, opencv, polkit-qt5-1, qca-qt5,
qrencode, qt-gstreamer, qt5, qt5-webkit, qtav, sni-qt, vid.stab
and wayland.
As a side note, libinput and libwacom have become part of Slackware-current.
Technically that makes them redundant in the above listing, however I still
compile Plasma5 packages for Slackware 14.2 so I left them in.
The phonon and poppler packages were extended so that they now support
Qt5 as well as Qt4.
Note that the SBo version of 'frei0r-plugins' package is called 'frei0r'.
If you have that SBo package installed, remove it.
- A completely new subset of "deps" packages, contained in their own
"telepathy" subdirectory, needed for KDE Telepathy:
libotr, libnice, farstream, libaccounts-glib, libaccounts-qt5,
signon, signon-plugin-oauth2, signon-ui, libsignon-glib, telegram-qt,
telepathy-glib, telepathy-farstream, telepathy-haze, telepathy-gabble,
telepathy-morse, telepathy-qt5, telepathy-logger, telepathy-logger-qt5,
telepathy-mission-control and telepathy-accounts-signon.
- Telepathy for KDE packages are found in their own subdirectory kde/telepathy .
- The kde/kde4 and kde/kde4-extragear directories contain packages that are
still required to support kdelibs4-based Applications.
- Also worth mentioning: the KF5 ports of calligra, digikam, kile, krita,
ktorrent, partitionmanager, skanlite and the KDE Development Suite
can be found in kde/applications-extra .
Finally, kjots (previously contained in KDEPIM) and kuser (abandoned by its
developer) have been moved into kde/applications-extra as well.
NOTE:
If you install a 32bit program on a 64bit Slackware computer with multilib
and that program needs legacy system tray support (think of Steam for
instance), you will have to grab the 32-bit version of Slackware's
'libdbusmenu-qt' and my ktown-deps package 'sni-qt', and run the
'convertpkg-compat32 -i' command on them to create 'compat32' versions
of these packages. Then install both 'libdbusmenu-qt-compat32' and
'sni-qt-compat32'. Those two are mandatory addons for displaying
system tray icons of 32bit binaries in 64bit multilib Plasma5.
NOTE:
Also explained in more detail below, upgrading to this KDE 5 is non-trivial.
You will have to remove old KDE 4 packages manually. If you do not have KDE
installed at all, you will have to *install* some of Slackware's own KDE 4
packages manually.
NOTE:
If you decide to install these packages on top of a fresh installation of
Slackware 14.2 or -current and have excluded all packages in the 'KDE'
package series during installation, you will be missing several add-on
packages. You can optionally install the following Slackware packages:
* amarok
* kaudiocreator
* kplayer
* kwebkitpart
NOTE:
If you had installed KDE 4 as your default desktop previously, the removal
of KDE 4 packages will break the symbolic link '/etc/X11/xinit/xinitrc'.
An attempt to run 'startx' in a console will fail with a black screen.
After installing Plasma 5 for the first time, you need to run 'xwmconfig'
and select 'xinitrc.plasma' as your desktop session.
-------------------------------------------------------------------------------
Install pre-compiled packages:
-------------------------------------------------------------------------------
In order to install or upgrade KDE 5, follow these steps:
Make sure you are not running KDE or even X ! If you are running an X session,
log out first, and if you are in runlevel 4 (graphical login) you first have to
go back to runlevel 3 (console) by typing "init 3".
If you still have a KDE 4 installed, it must be removed first. No clean
upgrade path can be provided! Do as follows:
If you have Slackware 14.2 or -current's default KDE 4.14.3 installed:
# removepkg /var/log/packages/*-4.14.3-*
# removepkg libkscreen
# removepkg kscreen
# removepkg kactivities
# removepkg kde-workspace
# removepkg libmm-qt
# removepkg libnm-qt
# removepkg plasma-nm
# removepkg polkit-kde-agent-1
# removepkg polkit-kde-kcmodules-1
# removepkg kdeconnect-kde
# removepkg kdepim
# removepkg kdepimlibs
# removepkg kdev-python
# removepkg kdevelop-php
# removepkg kdevelop-php-docs
..or instead of the above, simply '# slackpkg remove kde' and de-select
the packages you want to keep (amarok, etc).
Alternatively, in case you are already using an older release of my KDE 5
packages, you need to look up that particular release in the list right below
(for instance: KDE 5_16.08) and then apply the actions shown for that KDE 5
release *and* all more recent releases, i.e. work your way back up to this
paragraph. Note that some of the old KDE package names were obsoleted along
the way, they were split up, renamed or integrated and that is the reason
for some of the 'removepkg' lines you'll see below.
Here we go:
If you have my 'ktown' set of KDE 5_17.09 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.07 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.06 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.05_02 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.05 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.04 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.03 installed:
- Upgrade to KDE 5_17.04
Remove the packages that no longer exist in KDE 5_17.04:
* removepkg kajongg
* removepkg kommander
* removepkg pim-storage-service-manager
If you have my 'ktown' set of KDE 5_17.02 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_17.01 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.12 installed:
- Upgrade to KDE 5_17.01
If you are running Slackware-current, manually install or upgrade libinput
and libwacom to the Slackware versions.
Remove the packages that no longer exist in KDE 5_17.01:
* removepkg kactivities
* removepkg nepomuk
* removepkg nepomuk-widgets
* removepkg gpgmepp
* removepkg kdgantt2
* removepkg kde-baseapps kdepim kdewebdev
If you have my 'ktown' set of KDE 5_16.11 installed:
- Upgrade to KDE 5_16.12
Remove the packages that no longer exist in KDE 5_16.12:
* removepkg baloo
* removepkg baloo-widgets
If you have my 'ktown' set of KDE 5_16.08 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.07 installed:
- Upgrade to KDE 5_16.08
Remove the packages that no longer exist in KDE 5_16.07:
* removepkg kdegraphics-strigi-analyzer
* removepkg kdenetwork-strigi-analyzers
* rempovepkg kdesdk-strigi-analyzers
* removepkg kdepimlibs libkdeedu mplayerthumbs
If you have my 'ktown' set of KDE 5_16.06 installed:
- Upgrade to KDE 5_16.07
Remove the packages that no longer exist in KDE 5_16.07:
* removepkg /var/log/packages/noto-font-ttf-2015-09-29-noarch-1alien
If you have my 'ktown' set of KDE 5_16.05 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.04 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.03 installed:
- Upgrade to KDE 5_16.04
Remove the packages that no longer exist in KDE 5_16.04:
* removepkg kactivities-workspace
If you have my 'ktown' set of KDE 5_16.02 installed:
- No further actions are needed.
If you have my 'ktown' set of KDE 5_16.01 installed:
- No further actions are needed.
Then proceed with installing/upgrading KDE 5 as outlined below.
NOTE:
The example commands below are for Slackware -current but you can use
these commands for Slackware 14.2 as well by replacing the /current/
string with /14.2/ (provided there is a suitable 'ktown' release available
for Slackware 14.2 of course):
NOTE:
Instead of using the mirror host bear.alienbase.nl/mirrors/alien-kde/ ,
you could choose the alternative mirror http://slackware.uk/people/alien-kde/
NOTE:
If you use 'slackpkg' to automate your upgrades, be sure to blacklist my
custom packages or else slackpkg will always try to replace my packages
with the stock Slackware versions if the package names are identical.
As an example, you can add the following lines to the file
"/etc/slackpkg/blacklist" to prevent this unintentional downgrading to KDE4:
# These three lines will blacklist all SBo, alien and multilib packages:
[0-9]+_SBo
[0-9]+alien
[0-9]+compat32
If on the other hand you are using the 'slackpkg+' extension for slackpkg
then your "/etc/slackpkg/blacklist" file should *not* contain the above
lines! The slackpkg+ extension enables the use of 3rd-party repositories
with slackpkg and then Plasma5 package upgrades will be handled properly.
To make it easy for you, here is a one-line command that downloads the whole
'5' directory (excluding the sources), with 32-bit and 64-bit packages.
# rsync -Hav rsync://bear.alienbase.nl/mirrors/alien-kde/current/5/ 5/
Or else, if you want to download packages for just one of the two supported
architectures, you would run one of the following commands instead.
If you want only the 64-bit packages:
# rsync -Hav --exclude=x86 rsync://bear.alienbase.nl/mirrors/alien-kde/current/5/ 5/
If you want only the 32-bit packages:
# rsync -Hav --exclude=x86_64 rsync://bear.alienbase.nl/mirrors/alien-kde/current/5/ 5/
Assuming you just downloaded the bits you want from the directory tree "5",
you must now change your current directory to where you found this README
(which is the directory called '5'). If you used one of the above "rsync"
commands then you can simply do:
# cd 5
From within this directory, you run the following commands as root:
On Slackware 32-bit:
# upgradepkg --reinstall --install-new x86/deps/*.t?z
# upgradepkg --reinstall --install-new x86/deps/telepathy/*.t?z
# upgradepkg --reinstall --install-new x86/kde/*/*.t?z
On Slackware 64-bit:
# upgradepkg --reinstall --install-new x86_64/deps/*.t?z
# upgradepkg --reinstall --install-new x86_64/deps/telepathy/*.t?z
# upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z
If you already have one or more non-english language packs installed:
On Slackware 32-bit:
# upgradepkg x86/kdei/*.t?z
On Slackware 64-bit:
# upgradepkg x86_64/kdei/*.t?z
If you want to have a non-english language pack installed but none is
currently installed, substitute your country code instead of the 'XX'
in the next command:
# upgradepkg --install-new x86_64/kdei/kde-l10n-XX-*.t?z
Note that these separate language packs contain only the localizations for
kdelibs4 based applications. All KDE Frameworks 5 based programs include
localizations in the packages themselves (meaning that you will get all
languages installed always).
Check if any ".new" configuration files have been left behind by
the upgradepkg commands. Compare them to their originals and decide
if you need to use them.
# find /etc/ -name "*.new"
A graphical (ncurses) tool for processing these "*.new" files is slackpkg:
# slackpkg new-config
Then reboot your system.
If all you want is to install the packages I created, then you can skip the
remainder of the README which details how to (re)compile the packages from
their sources; it is not required reading material.
-------------------------------------------------------------------------------
Building it all from source:
-------------------------------------------------------------------------------
Sources and scripts are separated from the packages in my 'ktown' repository.
If you want the sources for KDE 5, run the following command to download them
(downloading from a mirror will usually be much faster):
# rsync -Hav rsync://bear.alienbase.nl/mirrors/alien-kde/source/5/ 5/
There are a lot of 'dependencies' for KDE 5 which you'll have to compile and
install before attempting to compile KDE 5. Compiling and installing these
dependencies on Slackware-current is as easy as:
# cd 5/deps
# ./updates.SlackBuild
# cd -
# cd 5/deps/telepathy
# ./telepathy.SlackBuild
# cd -
Be prepared to wait a *long* time since this will compile a new Qt5 package
among others. The finished packages will be stored in /tmp and will already
have been installed/upgraded automatically.
Then if you want to compile the KDE packages on your computer, run:
# cd 5/kde
# ./KDE.SlackBuild
Wait a long time, and you will find the new packages in /tmp/kde_build .
Note that these packages will already have been installed by KDE.SlackBuild !
Reboot your computer and login to a Plasma session.
==============================================================================
Eric Hameleers / alien at slackware dot com / 13-oct-2017
Potrebbe essere una buona idea...
Forse non sai che quello che stai cercando di fare esiste già pronto con la Live di Alienbob. Quella live può essere usata con persistenza su una usb e può anche essere installata su HD. Tutto usando gli script di Hameleers.
Il vantaggio è quello di avere una current con KDE5 configurata da AlienBob in persona e quello di sperimentare un tipo di installazione che non conosci.
si l'avevo già notata e scaricata
(http://i.imgur.com/vm63Q78.png)
la passo sul dvd
dopo per l'installazione non so come procedere
Caro trigg,
con questo genere di distribuzioni bisogna imparare, prima o poi, a consultare la documentazione ufficiale. E a cercarsela quando serve.
In questo caso stai entrando nel magnifico mondo di Eric Hameleers, meglio conosciuto come AlienBob, il primo posto in cui andare a cercare è il suo Blog: https://alien.slackbook.org/blog/.
Da qui ottieni informazioni per ktown, i suo repo, le sue live e tutta la documentazione a supporto, che non si trova mai troppo lontana da tutto il resto.
Il secondo posto è tra la documentazione ufficiale di Slackware, è qui infatti che ho trovato questo: https://docs.slackware.com/slackware:liveslak#enduser_documentation , la parte che nell'immediato interesserebbe te è questa:
Citazionesetup2hd
The fourth script:
The "setup2hd" script enables you to install the running Live OS to the computer's local hard disk. The "setup2hd" is a modified Slackware installer, so you will be comfortable with the process. There is no 'SOURCE' selection because the script knows where to find the squashfs modules. After you select the target partition(s), every active module of the Live OS variant (SLACKWARE, PLASMA5, MATE, ...) is extracted to the hard drive. After extraction has completed, the script summarizes how many modules have been extracted. It will also show an example command to extract any remaining inactive or disabled modules manually. The final step in the installation is again the stock Slackware installer which kicks off the Slackware configuration scripts.
Scarica questo file, scompattalo, e nella cartella troverai tutti gli script della collezione, compreso quello per creare una tua personale live... ;D (...quando sarai diventato bravo come alienbob). http://bear.alienbase.nl/cgit/liveslak/snapshot/liveslak-1.1.9.2.tar.gz
Da qui: http://bear.alienbase.nl/cgit/liveslak/ ottieni sempre la versione più aggiornata.
Per il resto non ti so dire molto di più perché io ho usato solo una volta lo script per la persistenza.
... Adesso ne so qualcosa di più. Ci sono un sacco di buone notizie.
Installare la Live su HD è molto semplice, naturalmente prima bisogna installare la LIVE su USB.
La Live su USB si installa eseguendo uno script di quelli contenuti in questo file: http://bear.alienbase.nl/cgit/liveslak/snapshot/liveslak-1.1.9.2.tar.gz
e precisamente questo script:
iso2usb.shla sintassi la trovi nella documentazione ufficiale: https://docs.slackware.com/slackware:liveslak#enduser_documentation
in questo pezzo:
CitazioneTransfering ISO content to USB stick
A script is available which allows you to transfer the ISO image content to a USB stick, making some modifications depending on the script's parameters.
The USB stick will be erased and re-formatted when running this script (except when using the '-r' refresh optoin)! Before inflicting any irreversible damage, the script will show you a prompt at which point you can evaluate whether it is safe to continue.
This script, called 'iso2usb.sh', accepts the following parameters:
-c|--crypt size|perc Add a LUKS encrypted /home ; parameter is the
requested size of the container in kB, MB, GB,
or as a percentage of free space.
Examples: '-c 125M', '-c 1.3G', '-c 20%'.
-d|--devices List removable devices on this computer.
-f|--force Ignore most warnings (except the back-out).
-h|--help This help.
-i|--infile <filename> Full path to the ISO image file.
-o|--outdev <filename> The device name of your USB drive.
-p|--persistence <name> Custom name of the 'persistence' directory/file.
-r|--refresh Refresh the USB stick with the ISO content.
No formatting, do not touch user content.
-s|--scan Scan for insertion of new USB device instead of
providing a devicename (using option '-o').
-u|--unattended Do not ask any questions.
-v|--verbose Show verbose messages.
-w|--wait<number> Add <number> seconds wait time to initialize USB.
-C|--cryptpersistfile size|perc
Use a LUKS-encrypted 'persistence' file instead
of a directory (for use on FAT filesystem).
-P|--persistfile Use an unencrypted 'persistence' file instead
of a directory (for use on FAT filesystem).
Examples:
Create a USB version of Slackware Live, where the USB stick is known to the system as '/dev/sdX. Note - the value for the output parameter is the device name of the stick and not one of its partitions!
# ./iso2usb.sh -i ~/download/slackware64-live-14.2.iso -o /dev/sdX
Create a USB Live like above, but this time adding an encrypted /home filesystem with 750 MB of space, and at the same time increase the wait time on boot to 15 seconds (useful for slow USB media that fail to start the Live OS otherwise):
# ./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 750M -w 15
Create a USB Live with an encrypted /home (allocating 30% of the stick's free space for /home) and where the persistent data will be stored in a container file instead of a directory:
# ./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 30% -P
Una volta avviata la LIVE su USB apri un terminale con i privilegi elevati e fai partire l'installazione con:
setup2hdL'installer è quello classico di Slackware ma solo la parte relativa al setup, per cui le partizioni devono essere già pronte.
La Slackware Live Plasma5 non contiene solo KDE, ci sono anche xfce, lumina, lxqt, i3, openbox...
La mia installazione:
(https://s1.postimg.org/14wwqed39b/Screenshot_20171019_224200.png)
:hmm:
alcune domande a riguardo sulla prassi
1) creo usb normalmente giusto?
2) lo script : iso2usb.sh basta lanciarlo o bisogna copiarlo e incollarlo così com'è per poi lancialrlo ?
3) per due volte con current dopo upgrade-all e l'aggiornamento del kernel pigiando la y , il sistema non ha più riconosciuto alcun comando
(http://i.imgur.com/8acEg8r.png)
4) immagino che la lista dei repo di slackpkg e slackpkgplus è già configurata per la current e bisogna solo scegliere il repo italiano : giusto?
Trigg io riesco a capire poco di ciò di cui parli, per cui cominciamo dalla fine: prima di dare upgrade-all hai usato il comando slackpkg install-new ?
Con la current è assolutamente necessario che install-new preceda upgrade-all, tutte le volte, sempre.
EDIT:
Questa è una cosa che devo assolutamente dire e che forse spiega la mia scarsa disponibilità a dare supporto per la Current di Slackware...
...Mentre penso che Slackware stable sia per "quasi" tutti, soprattutto quelli che non temono di sperimentare e di mettere alla prova il proprio ingegno (certo che Slackware sarà per loro la migliore maestra di Linux).
Penso invece che la sua versione Current sia riservata a chi sa usare perfettamente Slackware.
Per chi capisce come funziona Slackware la Current rappresenta un passaggio naturale, anche se nient'affatto obbligatorio.
Io non uso la Current perché significa rinunciare in parte alla "tranquillità" di Slackware e poi perché non credo di essere tutta questa gran cima... ;D
...Concludendo, l'utente ideale della current secondo me è chi non ha difficoltà a capire come funziona. Tutti gli altri imparassero prima a usare Slackware. Che non è difficile. :)
Detto questo. Le Live di Alien rappresentano una bella scorciatoia per tutta l'installazione. Senza considerare che sono "Magiche" e che con la raccolta di script liveslak di Alien si possono fare un gran numero di belle cose.
Anche in questo caso però è già tutto scritto, a disposizione di chi ha già imparato a leggere...
Chi non ha voglia di imparare a leggere può sempre fare una Live di Mint con unetbootin e la persistenza, che non è affatto la stessa cosa. Ma è sempre qualcosa. ;)
ma ho già letto
il readme.text di liveslack
al punto di iso2usb.sh
=== iso2usb.sh ===
The second script:
The "iso2usb.sh" script's runtime usage is explained in detail in a previous paragraph "Transfering ISO content to USB stick".
This section explains how the script modifies the ISO for the enhanced USB functionality.
c'è scritto questo e non mi dice nulla su cosa fare
mentre a trafering iso to usb mi dice questo
==== Transfering ISO content to USB stick ====
A script is available which allows you to transfer the ISO image content to a USB stick, making some modifications depending on the script's parameters.
The USB stick will be erased and re-formatted when running this script (except when using the '-r' refresh optoin)! Before inflicting any irreversible damage, the script will show you a prompt at which point you can evaluate whether it is safe to continue.
This script, called 'iso2usb.sh', accepts the following parameters: <code>
-c|--crypt size|perc Add a LUKS encrypted /home ; parameter is the
requested size of the container in kB, MB, GB,
or as a percentage of free space.
Examples: '-c 125M', '-c 1.3G', '-c 20%'.
-d|--devices List removable devices on this computer.
-f|--force Ignore most warnings (except the back-out).
-h|--help This help.
-i|--infile <filename> Full path to the ISO image file.
-o|--outdev <filename> The device name of your USB drive.
-p|--persistence <name> Custom name of the 'persistence' directory/file.
-r|--refresh Refresh the USB stick with the ISO content.
No formatting, do not touch user content.
-s|--scan Scan for insertion of new USB device instead of
providing a devicename (using option '-o').
-u|--unattended Do not ask any questions.
-v|--verbose Show verbose messages.
-w|--wait<number> Add <number> seconds wait time to initialize USB.
-C|--cryptpersistfile size|perc
Use a LUKS-encrypted 'persistence' file instead
of a directory (for use on FAT filesystem).
-P|--persistfile Use an unencrypted 'persistence' file instead
of a directory (for use on FAT filesystem).
</code>
Examples:
* Create a USB version of Slackware Live, where the USB stick is known to the system as '/dev/sdX. Note - the value for the output parameter is the device name of the stick and not one of its partitions!
# ./iso2usb.sh -i ~/download/slackware64-live-14.2.iso -o /dev/sdX
* Create a USB Live like above, but this time adding an encrypted /home filesystem with 750 MB of space, and at the same time increase the wait time on boot to 15 seconds (useful for slow USB media that fail to start the Live OS otherwise):
# ./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 750M -w 15
* Create a USB Live with an encrypted /home (allocating 30% of the stick's free space for /home) and where the persistent data will be stored in a container file instead of a directory:
# ./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 30% -P
* Create a USB Live with both the /home and the persistent data encrypted (the persistence filesystem will be 300 MB in size):
# ./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 30% -C 300M
* Refresh the system modules on a USB Live using a Live ISO as the source. Let the script scan for insertion of a USB stick instead of specifying the device name on the commandline. Note that the addons and optional modules will not be touched by this action:
# ./iso2usb.sh -i slackware64-live-current.iso -r -s
You might have noticed that the "-P" parameter does not accept a size parameter. This is because the unencrypted container file is created as a 'sparse' file that starts at zero size and is allowed to grow dynmically to a maximum of 90% of the initial free space on the Linux partition of the USB stick.
non è molto chiaro da quello che vedo dovrò
lanciare lo script make_slackware_live.sh
assegnare hostname e partizioni
dopo lanciare lo script iso2usb.sh e installare
oppure non ho capito se devo creare una iso contenente già lo script iso2usb.sh
e lo lancia in automatico
bha non trovo il bandolo della matassa , se devo rimpiazzare kde stable con cui non mi trovo male solo per il menu di kdeplasma5 prederisco lasciare il mondo come sta , nel dubbio lascio stare le cose così come stanno
Vai nela cartella che contiene gli script e apri un terminale. Supponiamo che la iso della live si trovi nella tua cartella Scaricati.
Supponiamo che la tua USB sia identificata come /dev/sdT (lo sostituirai con quello corretto, sdb, sdc,o sdd che sia).
il comando per installare la chiavetta è:
sh iso2usb.sh -i ~/Scaricati/slackware64-live-plasma5-current.iso -o /dev/sdT -c 30% -P
L'opzione .-c 30% serve per criptare la home e assegnargli una dimensione pari al 30% dello spazio disponibile sulla usb. Puoi cambiarla a tuo piacimento anche in base alle dimensioni della USB e quelle della iso.
Questo è tutto. Alla fine del procedimento avvia la tua LIVE USB e da li, se credi, installa la tua current con Plasma5.
P.S.
Guarda che il vecchio KDE ha a disposizione diversi menu, puoi sempre cambiarlo con uno più agevole per te.
Vedi: https://www.lffl.org/2012/09/i-migliori-menu-per-kde-kubuntu.html
Ciò sovrascriverà i dati in /dev/loop1 in modo irreversibile.
Are you sure? (Type uppercase yes): YES
[color=red]Inserire la passphrase:
Verifica passphrase: [/color]
--- Unlocking the LUKS container requires your passphrase again...
Inserire la passphrase per /mnt/alienusb.etCzxb/slhome.img:
1525760+0 record dentro
1525760+0 record fuori
781189120 bytes (781 MB, 745 MiB) copied, 39,1838 s, 19,9 MB/s
mke2fs 1.43.1 (08-Jun-2016)
Creazione del file system con 190720 4k blocchi e 47712 inode
Etichetta del file system=9f53c005-443a-4d5e-9870-2df2e659c179
Backup del superblocco salvati nei blocchi:
32768, 98304, 163840
Allocating group tables: fatto
Scrittura delle tavole degli inode: fatto
Creating journal (4096 blocks): fatto
[color=red]Scrittura delle informazioni dei super-blocchi e dell'accounting del file system: hp [/color]
in rosso ho evidenziato le parti dove trovo difficoltà
qui ho dato invio senza scrivere nulla
Are you sure? (Type uppercase yes): YES
[color=red]Inserire la passphrase:
Verifica passphrase:
qui ho scritto hp
pensando fosse l'account
Scrittura delle informazioni dei super-blocchi e dell'accounting del file system: hp
Va bene trigg, falla senza criptazione (...dovevi solo inserire una password...), usa questo comando:
sh iso2usb.sh -i ~/Scaricati/slackware64-live-plasma5-current.iso -o /dev/sdTQui:
CitazioneScrittura delle informazioni dei super-blocchi e dell'accounting del file system:
non devi scrivere niente, devi solo aspettare che lo script faccia il suo lavoro.