Slackware 10.1 is released!
- Začetnik teme Corey
- Datum pokretanja
- Učlanjen(a)
- 18.07.2001
- Poruke
- 18,171
- Poena
- 1,445
Moja oprema
- CPU & Cooler
- Intel® Core™ i5-9500F, NZXT Kraken Z63
- GPU
- Asus GTX 2070 Super
- Storage
- Samsung 980 Pro NVMe 1 TB
- Kućište
- NZXT H210i
- Monitor
- LG C2 42"
- Miš & tastatura
- Logitech G502, Keychron K8, Nuphy Air75, Ducky TKL One 2
- Ostale periferije
- Glupi HP štampač
- Laptop
- Apple Macbook Pro 14" M1
- Tablet
- Apple iPad Pro 11"
- Mobilni telefon
- Apple iPhone 13 Pro Max
- Pametni uređaji
- Apple Watch Ultra
- Pristup internetu
- Kablovski internet
Ajmo iskustva...ako ih ima? 🙂
- Učlanjen(a)
- 06.06.2004
- Poruke
- 364
- Poena
- 620
Jedno pitanje: posto vidim da puno distribucija postoji na mirror.etf.bg.ac.yu,
zna li neko gde je taj racunar i da li mogu ja da se pojavim tamo sa 2 prazna CD-a pa da mi neko nareze Slack 10.1 (naravno uz nadoknadu)? Ovo pitam zbog toga da ne bi vukao 2 iso-a od 600 i kusur MB preko dial-upa (jos uvek dial-up 😡 ).
zna li neko gde je taj racunar i da li mogu ja da se pojavim tamo sa 2 prazna CD-a pa da mi neko nareze Slack 10.1 (naravno uz nadoknadu)? Ovo pitam zbog toga da ne bi vukao 2 iso-a od 600 i kusur MB preko dial-upa (jos uvek dial-up 😡 ).
Poslednja izmena:
homoludens
Čuven
- Učlanjen(a)
- 30.06.2003
- Poruke
- 202
- Poena
- 619
rc na etf-u, samo nadji nekog sa etf-a, ko ima neki nalog tamo
homoludens
Čuven
- Učlanjen(a)
- 30.06.2003
- Poruke
- 202
- Poena
- 619
rc na etf-u, samo nadji nekog sa etf-a, ko ima neki nalog tamo,
samo za rezanje na tvom cd-u traze valjda 80din....
bolje ti je da skidas iz univerzitetske biblioteke sa mirora na etf-u, traje jedno 30min. po CD-u, i odmah rezes.
samo za rezanje na tvom cd-u traze valjda 80din....
bolje ti je da skidas iz univerzitetske biblioteke sa mirora na etf-u, traje jedno 30min. po CD-u, i odmah rezes.
ja ga imam ali od mene ne ocekujte previse komentara 🙂 posto je uspeh da sam uspeo da ga instaliram :d i vec imam par pitanja |🙂
naime
1) nemam zvuk i pise mi da je mutovan ali u kde-u kad kliknem na kmixer trazi mi da izaberem device ali nemam ponudjeno nista,prazan combobox. u konzoli pise da je mutovan i da koristim alsamixer pa posle alsact1 (valjda) da spasim podesavanja al mi to nije uspelo. 2 stvar ne radi mi touch pad i skrol na misu.
2) Gde je u slaku nesto poput harddrakeu mdk-u tj gde mogu da podesavam hardver iz kde-a.
3) koja je komanda chkconfig za slack posto ova ne postoji 😀 tj kako da vidim koji su aktivni servisi i da ih poiskljucujem posto dize brdo necega pri bootu
4) kako da podesim gateway (tj podesio sam ga pri instalaciji) da bi mogao da koristim net sa desktopa. (kad smo vec kod toga kako se podesava static ip u konzoli posto kad ga podesim preko ifconfig eth0 posle restarta on se vrati na staro)
i za sad mislim da je to sve 🙂 malo li je. Hvala unapred svima koje ne bude mrzelo da mi objasnjava sve.
naime
1) nemam zvuk i pise mi da je mutovan ali u kde-u kad kliknem na kmixer trazi mi da izaberem device ali nemam ponudjeno nista,prazan combobox. u konzoli pise da je mutovan i da koristim alsamixer pa posle alsact1 (valjda) da spasim podesavanja al mi to nije uspelo. 2 stvar ne radi mi touch pad i skrol na misu.
2) Gde je u slaku nesto poput harddrakeu mdk-u tj gde mogu da podesavam hardver iz kde-a.
3) koja je komanda chkconfig za slack posto ova ne postoji 😀 tj kako da vidim koji su aktivni servisi i da ih poiskljucujem posto dize brdo necega pri bootu
4) kako da podesim gateway (tj podesio sam ga pri instalaciji) da bi mogao da koristim net sa desktopa. (kad smo vec kod toga kako se podesava static ip u konzoli posto kad ga podesim preko ifconfig eth0 posle restarta on se vrati na staro)
i za sad mislim da je to sve 🙂 malo li je. Hvala unapred svima koje ne bude mrzelo da mi objasnjava sve.
evo ti
The new Slackware 10.0
The fans of the oldest surviving Linux distribution once again had a reason to celebrate last week as Slackware Linux entered the double-digit release figures with version 10.0. If you haven't tried it yet, do yourself a favour and get the release; unless you insist on having graphical utilities for all configuration tasks, you won't be disappointed - Slackware 10.0 continues in its tradition of simplicity and reliability. It comes with KDE 3.2.3, GNOME 2.6.1, and many other up-to-date applications.
Some users might be disappointed about the fact that the Linux kernel in Slackware 10.0 remains at version 2.4. But as we have seen with other distributions, the 2.6 kernel still has a long way to go before it becomes a truly stable kernel that can be given the responsibility to power important servers and desktops. Trust Patrick Volkerding on this one - he has been developing Slackware for over 10 years and he knows. At Slackware, technical decisions usually take precedence over marketing ones, which is not always the case with the big commercial distributions.
Of course, many of the more advanced users are already running Slackware Linux 10.0 with kernel 2.6.7. The relevant package can be found in the testing/packages/linux-2.6.7 directory on the second CD. There is no option to select this kernel during installation so you will have to install it manually with 'installpkg':
installpkg kernel-generic-2.6.7-i486-1.tgz
You can also install the alsa-driver, kernel-headers and kernel-modules packages with the same command. Before you can boot the new kernel you will need to do two more things. Firstly, you will have to create initrd so that you can load certain kernel modules before mounting the root partition. The details are in the README.initrd file in the same directory as the kernel 2.6.7. The required command depends on the root partition's file system - you were given a choice between ReiserFS (default) and ext3; if you chose ext3, then navigate to the /boot directory and issue the following command:
mkinitrd -c -k 2.6.7 -m jbd:ext3 -f ext3 -r /dev/hdb3
The /dev/hdb3 in the above command should of course be replaced with the root partition of your Slackware installation. If you chose ReiserFS, you can achieve the same with this command:
mkinitrd -c -k 2.6.7 -m reiserfs
Secondly, you will have to update your /etc/lilo.conf file to look something like this:
image = /boot/vmlinuz-ide-2.4.26
root = /dev/hdb3
label = Linux-2.4
read-only
image = /boot/vmlinuz-generic-2.6.7
initrd = /boot/initrd.gz
root = /dev/hdb3
label = Linux-2.6
read-only
Again, you need to replace /dev/hdb3 with the root partition of your own Slackware installation. Don't forget to execute the 'lilo' command after saving the modified lilo.conf file.
When you reboot, the lilo prompt will give you a choice to select between the two kernels. While the majority of users are unlikely to experience problems with the newer one, some hardware combinations are known to cause problems. If this is your case, the tried and tested kernel 2.4 is still available for your booting pleasure.
The new Slackware 10.0
The fans of the oldest surviving Linux distribution once again had a reason to celebrate last week as Slackware Linux entered the double-digit release figures with version 10.0. If you haven't tried it yet, do yourself a favour and get the release; unless you insist on having graphical utilities for all configuration tasks, you won't be disappointed - Slackware 10.0 continues in its tradition of simplicity and reliability. It comes with KDE 3.2.3, GNOME 2.6.1, and many other up-to-date applications.
Some users might be disappointed about the fact that the Linux kernel in Slackware 10.0 remains at version 2.4. But as we have seen with other distributions, the 2.6 kernel still has a long way to go before it becomes a truly stable kernel that can be given the responsibility to power important servers and desktops. Trust Patrick Volkerding on this one - he has been developing Slackware for over 10 years and he knows. At Slackware, technical decisions usually take precedence over marketing ones, which is not always the case with the big commercial distributions.
Of course, many of the more advanced users are already running Slackware Linux 10.0 with kernel 2.6.7. The relevant package can be found in the testing/packages/linux-2.6.7 directory on the second CD. There is no option to select this kernel during installation so you will have to install it manually with 'installpkg':
installpkg kernel-generic-2.6.7-i486-1.tgz
You can also install the alsa-driver, kernel-headers and kernel-modules packages with the same command. Before you can boot the new kernel you will need to do two more things. Firstly, you will have to create initrd so that you can load certain kernel modules before mounting the root partition. The details are in the README.initrd file in the same directory as the kernel 2.6.7. The required command depends on the root partition's file system - you were given a choice between ReiserFS (default) and ext3; if you chose ext3, then navigate to the /boot directory and issue the following command:
mkinitrd -c -k 2.6.7 -m jbd:ext3 -f ext3 -r /dev/hdb3
The /dev/hdb3 in the above command should of course be replaced with the root partition of your Slackware installation. If you chose ReiserFS, you can achieve the same with this command:
mkinitrd -c -k 2.6.7 -m reiserfs
Secondly, you will have to update your /etc/lilo.conf file to look something like this:
image = /boot/vmlinuz-ide-2.4.26
root = /dev/hdb3
label = Linux-2.4
read-only
image = /boot/vmlinuz-generic-2.6.7
initrd = /boot/initrd.gz
root = /dev/hdb3
label = Linux-2.6
read-only
Again, you need to replace /dev/hdb3 with the root partition of your own Slackware installation. Don't forget to execute the 'lilo' command after saving the modified lilo.conf file.
When you reboot, the lilo prompt will give you a choice to select between the two kernels. While the majority of users are unlikely to experience problems with the newer one, some hardware combinations are known to cause problems. If this is your case, the tried and tested kernel 2.4 is still available for your booting pleasure.
