Search
1000 results for “linux_mclinuxface”
-
Join #freesoftware enthusiasts at @piwo (Poznań Free Software Fest) 2026 in Poland May 30 for talks, workshops, and contests covering #programming, #DevOps, #security, #ethicalhacking #gaming, and more!
Join free and get 20% off exams with Linux Professional Institute (LPI), a proud Media Partner 🐧 💪
Learn more: https://lpi.org/8vwi
@hspoz @hspoz_group #piwo2026 #LPI #freesoftware #FOSS #opensource #linux #GNU #piwo #UAM #LAG #LAGPoznań #Poznań
-
Join #freesoftware enthusiasts at @piwo (Poznań Free Software Fest) 2026 in Poland May 30 for talks, workshops, and contests covering #programming, #DevOps, #security, #hacking, #gaming, and more!
Join free and get 20% off exams with Linux Professional Institute (LPI), a proud Media Partner 🐧 💪
Learn more: https://lpi.org/8vwi
@hspoz @hspoz_group #piwo2026 #LPI #freesoftware #FOSS #opensource #linux #GNU #piwo #UAM #LAG #LAGPoznań #Poznań
-
GT-IPNET Project: Integrated Graphical Interface for Linux Networking Tools
GT-IPNET v2.0 is an open-source desktop application that brings the most popular networking tools into an elegant graphical interface, featuring an advanced network controller, tray icon, and app lock.
🔗 https://salehgnutux.github.io/GT-NEWSTECH/en/gnutux-projects/gt-ipnet-v2/
-
Well, you can make the most of the long wait for the NAS hard drives to finish formatting by enjoying an authentic Viennese “Punschkrapferl” with a cup of tea for a sweet afternoon snack.
#linux #unix #opensource #freesoftware #nas #cloud #harddrive #vienna #wien
-
Well, you can make the most of the long wait for the NAS hard drives to finish formatting by enjoying an authentic Viennese “Punschkrapferl” with a cup of tea for a sweet afternoon snack.
#linux #unix #opensource #freesoftware #nas #cloud #harddrive #vienna #wien
-
Well, you can make the most of the long wait for the NAS hard drives to finish formatting by enjoying an authentic Viennese “Punschkrapferl” with a cup of tea for a sweet afternoon snack.
#linux #unix #opensource #freesoftware #nas #cloud #harddrive #vienna #wien
-
Well, you can make the most of the long wait for the NAS hard drives to finish formatting by enjoying an authentic Viennese “Punschkrapferl” with a cup of tea for a sweet afternoon snack.
#linux #unix #opensource #freesoftware #nas #cloud #harddrive #vienna #wien
-
RE: https://mastodon.social/@linuxiac/116607061786889778
Now, that's a disturbing logo, name and everything.
Should have been behind a content warning, really.
-
I found an old WD NAS buried in all my computer parts clutter in the basement. I had completely forgotten about it after switching to the great uGreen NAS.
With 2x 4 TB WD Red drives, this WD NAS will now serve as my personal cloud at home, while the uGreen NAS will no longer function as a cloud solution connecting my smartphones and computers on the go, but rather as pure file and document storage on the internal network. So I’m splitting these functions between two NAS devices.
I’d been thinking about this for a while, and I was even planning to spend a lot of money on another uGreen NAS... but with today’s storage prices, that’s a massive expense that needs careful consideration—and thank goodness I took my time with it until I made this discovery today.
#linux #unix #opensource #freesoftware #nas #ugreen #westerndigital #cloud
-
I found an old WD NAS buried in all my computer parts clutter in the basement. I had completely forgotten about it after switching to the great uGreen NAS.
With 2x 4 TB WD Red drives, this WD NAS will now serve as my personal cloud at home, while the uGreen NAS will no longer function as a cloud solution connecting my smartphones and computers on the go, but rather as pure file and document storage on the internal network. So I’m splitting these functions between two NAS devices.
I’d been thinking about this for a while, and I was even planning to spend a lot of money on another uGreen NAS... but with today’s storage prices, that’s a massive expense that needs careful consideration—and thank goodness I took my time with it until I made this discovery today.
#linux #unix #opensource #freesoftware #nas #ugreen #westerndigital #cloud
-
I found an old WD NAS buried in all my computer parts clutter in the basement. I had completely forgotten about it after switching to the great uGreen NAS.
With 2x 4 TB WD Red drives, this WD NAS will now serve as my personal cloud at home, while the uGreen NAS will no longer function as a cloud solution connecting my smartphones and computers on the go, but rather as pure file and document storage on the internal network. So I’m splitting these functions between two NAS devices.
I’d been thinking about this for a while, and I was even planning to spend a lot of money on another uGreen NAS... but with today’s storage prices, that’s a massive expense that needs careful consideration—and thank goodness I took my time with it until I made this discovery today.
#linux #unix #opensource #freesoftware #nas #ugreen #westerndigital #cloud
-
I found an old WD NAS buried in all my computer parts clutter in the basement. I had completely forgotten about it after switching to the great uGreen NAS.
With 2x 4 TB WD Red drives, this WD NAS will now serve as my personal cloud at home, while the uGreen NAS will no longer function as a cloud solution connecting my smartphones and computers on the go, but rather as pure file and document storage on the internal network. So I’m splitting these functions between two NAS devices.
I’d been thinking about this for a while, and I was even planning to spend a lot of money on another uGreen NAS... but with today’s storage prices, that’s a massive expense that needs careful consideration—and thank goodness I took my time with it until I made this discovery today.
#linux #unix #opensource #freesoftware #nas #ugreen #westerndigital #cloud
-
Deutsche bananenbahn des tages
Deutsche Bahn verweigert Auskunft für Linuxer
[…] „Es tut uns leid, bei diesem Vorgang ist leider ein Fehler aufgetreten. Das Verhalten Ihres Browsers ähnelt dem eines Bots.“ […]
Wer nun nicht unbedingt spontan das Betriebssystem wechseln mag, kann sich durch Setzen des User-Agents im Browser behelfen. Wer dort „Linux“ durch „Windows“ ersetzt, erhält doch wieder Einlass und kann sich eine Verbindung auf der Bahn-Webseite suchen und sie auch buchen. Der Gegentest lässt tief blicken. Verpasst man einem Firefox unter Windows 11 eine Linux-Kennung, tritt das Verhalten auch unter Windows auf. Der Support schlägt unter Umständen den Wechsel auf Chrome vor, aber auch da: Aussperrung, sofern „Linux“ im User-Agent enthalten ist, der Tipp hilft nicht. Das lässt sich sogar mit Safari unter macOS provozieren.
Die frage, wer denen ins gehirn geschissen hat, kann ich leider auch nicht beantworten. Ach, kunden stören nur den betrieb? Dann müsst ihr windohs aussperren, das ist noch besser! 😁️
#DB #Epic #Fail #Heise #Link #Linux -
Installing Mageia Linux 10 RC1 on VMware Workstation
The first release candidate of Mageia Linux 10 was announced yesterday, and it brought some awesome lock screen pictures, along with some updated packages, such as the Linux kernel. This release candidate was released after the beta version to add in some improvements. Mageia Linux was released as a fork of Mandriva Linux, which is a successor of Mandrake Linux.
In this article, we will showcase how to install Mageia Linux 10 RC1 to a VMware installation. First, we will configure the virtual machine as follows:
After that, open the virtual machine settings, navigate to New CD/DVD, and select the Mageia ISO file.
Then, we’ll go ahead and turn on the virtual machine. We’re greeted with a rather nice GRUB boot screen.
As soon as we press ENTER, the Mageia installer starts with this:
After that, the GUI version of the Mageia installer starts, asking us for a language to use.
After that, we’re greeted with the license agreement.
After the license agreement, you can choose the timezone. The default selection is New York.
After that, you can configure the clock, including the hardware clock configuration (local time or UTC), and choosing whether to sync with NTP server or not.
Then, you can choose the keyboard layout.
Now, we get into the partitioning stage. You can choose either the guided partitioning or custom partitioning. As we have no installed operating systems, we can choose to use the whole disk.
Media selection comes after the partitioning stage in the installer. The installer has automatically selected both the Core Release and the Nonfree Release media. Currently, we’ll be installing the base system entirely from the installation ISO file.
After this stage, the installer provides us with options for the desktop environment, with KDE as the default. We have chosen to go with the KDE Plasma environment.
Afterwards, the installation begins.
When the installation finishes, the user configuration comes afterwards. You can set the root password, the username of your account, and the password.
Afterwards, the display configuration comes. The installer asks us to choose a monitor. As we’re on a virtual machine, this is likely not relevant. So, we kept it at Plug-n-Play.
As soon as we go to the next step, the installer shows you the summary of the system configuration, just like below:
Before the configuration finishes, the installer asks us if we want to configure the online media. We have approved it. Then, we allowed the installer to automatically choose the best mirror and download method available.
After that, the installer is now finished.
Then, we let the system reboot to the GRUB menu.
We let the system boot to the simplistic-looking login screen.
After we log in to the newly-created account, we’re presented with a desktop and a welcome window.
Awesome! Now we’re on the Mageia Desktop!
We have checked for available package updates by going to the Update screen. It shows a list of packages that were available for updating.
We have selected all the packages to upgrade them. As soon as we clicked on Update, the software update manager starts downloading package files and installing them to the system.
Afterwards, we have restarted the virtual machine for the new kernel to be used.
Lock screen wallpapers
The Mageia 10 RC1 announcement has stated that there are awesome screensavers included in the release candidate. However, it was actually referring to the lock screen wallpapers.
You can find those 20 wallpapers (found in
/usr/share/mga/screensaver) through the lock screen settings.Once you apply the changes, you can now see the login screen with one of the 20 lock screen wallpapers chosen.
#Linux #Mageia #Mageia10 #Mageia10RC1 #MageiaLinux #MageiaLinux10 #MageiaLinux10RC1 #news #Tech #Technology #update #VMware #VMwareWorkstation #VMwareWorkstation26H1 #VMwareWorkstationPro -
Installing Mageia Linux 10 RC1 on VMware Workstation
The first release candidate of Mageia Linux 10 was announced yesterday, and it brought some awesome lock screen pictures, along with some updated packages, such as the Linux kernel. This release candidate was released after the beta version to add in some improvements. Mageia Linux was released as a fork of Mandriva Linux, which is a successor of Mandrake Linux.
In this article, we will showcase how to install Mageia Linux 10 RC1 to a VMware installation. First, we will configure the virtual machine as follows:
After that, open the virtual machine settings, navigate to New CD/DVD, and select the Mageia ISO file.
Then, we’ll go ahead and turn on the virtual machine. We’re greeted with a rather nice GRUB boot screen.
As soon as we press ENTER, the Mageia installer starts with this:
After that, the GUI version of the Mageia installer starts, asking us for a language to use.
After that, we’re greeted with the license agreement.
After the license agreement, you can choose the timezone. The default selection is New York.
After that, you can configure the clock, including the hardware clock configuration (local time or UTC), and choosing whether to sync with NTP server or not.
Then, you can choose the keyboard layout.
Now, we get into the partitioning stage. You can choose either the guided partitioning or custom partitioning. As we have no installed operating systems, we can choose to use the whole disk.
Media selection comes after the partitioning stage in the installer. The installer has automatically selected both the Core Release and the Nonfree Release media. Currently, we’ll be installing the base system entirely from the installation ISO file.
After this stage, the installer provides us with options for the desktop environment, with KDE as the default. We have chosen to go with the KDE Plasma environment.
Afterwards, the installation begins.
When the installation finishes, the user configuration comes afterwards. You can set the root password, the username of your account, and the password.
Afterwards, the display configuration comes. The installer asks us to choose a monitor. As we’re on a virtual machine, this is likely not relevant. So, we kept it at Plug-n-Play.
As soon as we go to the next step, the installer shows you the summary of the system configuration, just like below:
Before the configuration finishes, the installer asks us if we want to configure the online media. We have approved it. Then, we allowed the installer to automatically choose the best mirror and download method available.
After that, the installer is now finished.
Then, we let the system reboot to the GRUB menu.
We let the system boot to the simplistic-looking login screen.
After we log in to the newly-created account, we’re presented with a desktop and a welcome window.
Awesome! Now we’re on the Mageia Desktop!
We have checked for available package updates by going to the Update screen. It shows a list of packages that were available for updating.
We have selected all the packages to upgrade them. As soon as we clicked on Update, the software update manager starts downloading package files and installing them to the system.
Afterwards, we have restarted the virtual machine for the new kernel to be used.
Lock screen wallpapers
The Mageia 10 RC1 announcement has stated that there are awesome screensavers included in the release candidate. However, it was actually referring to the lock screen wallpapers.
You can find those 20 wallpapers (found in
/usr/share/mga/screensaver) through the lock screen settings.Once you apply the changes, you can now see the login screen with one of the 20 lock screen wallpapers chosen.
#Linux #Mageia #Mageia10 #Mageia10RC1 #MageiaLinux #MageiaLinux10 #MageiaLinux10RC1 #news #Tech #Technology #update #VMware #VMwareWorkstation #VMwareWorkstation26H1 #VMwareWorkstationPro -
Installing Mageia Linux 10 RC1 on VMware Workstation
The first release candidate of Mageia Linux 10 was announced yesterday, and it brought some awesome lock screen pictures, along with some updated packages, such as the Linux kernel. This release candidate was released after the beta version to add in some improvements. Mageia Linux was released as a fork of Mandriva Linux, which is a successor of Mandrake Linux.
In this article, we will showcase how to install Mageia Linux 10 RC1 to a VMware installation. First, we will configure the virtual machine as follows:
After that, open the virtual machine settings, navigate to New CD/DVD, and select the Mageia ISO file.
Then, we’ll go ahead and turn on the virtual machine. We’re greeted with a rather nice GRUB boot screen.
As soon as we press ENTER, the Mageia installer starts with this:
After that, the GUI version of the Mageia installer starts, asking us for a language to use.
After that, we’re greeted with the license agreement.
After the license agreement, you can choose the timezone. The default selection is New York.
After that, you can configure the clock, including the hardware clock configuration (local time or UTC), and choosing whether to sync with NTP server or not.
Then, you can choose the keyboard layout.
Now, we get into the partitioning stage. You can choose either the guided partitioning or custom partitioning. As we have no installed operating systems, we can choose to use the whole disk.
Media selection comes after the partitioning stage in the installer. The installer has automatically selected both the Core Release and the Nonfree Release media. Currently, we’ll be installing the base system entirely from the installation ISO file.
After this stage, the installer provides us with options for the desktop environment, with KDE as the default. We have chosen to go with the KDE Plasma environment.
Afterwards, the installation begins.
When the installation finishes, the user configuration comes afterwards. You can set the root password, the username of your account, and the password.
Afterwards, the display configuration comes. The installer asks us to choose a monitor. As we’re on a virtual machine, this is likely not relevant. So, we kept it at Plug-n-Play.
As soon as we go to the next step, the installer shows you the summary of the system configuration, just like below:
Before the configuration finishes, the installer asks us if we want to configure the online media. We have approved it. Then, we allowed the installer to automatically choose the best mirror and download method available.
After that, the installer is now finished.
Then, we let the system reboot to the GRUB menu.
We let the system boot to the simplistic-looking login screen.
After we log in to the newly-created account, we’re presented with a desktop and a welcome window.
Awesome! Now we’re on the Mageia Desktop!
We have checked for available package updates by going to the Update screen. It shows a list of packages that were available for updating.
We have selected all the packages to upgrade them. As soon as we clicked on Update, the software update manager starts downloading package files and installing them to the system.
Afterwards, we have restarted the virtual machine for the new kernel to be used.
Lock screen wallpapers
The Mageia 10 RC1 announcement has stated that there are awesome screensavers included in the release candidate. However, it was actually referring to the lock screen wallpapers.
You can find those 20 wallpapers (found in
/usr/share/mga/screensaver) through the lock screen settings.Once you apply the changes, you can now see the login screen with one of the 20 lock screen wallpapers chosen.
#Linux #Mageia #Mageia10 #Mageia10RC1 #MageiaLinux #MageiaLinux10 #MageiaLinux10RC1 #news #Tech #Technology #update #VMware #VMwareWorkstation #VMwareWorkstation26H1 #VMwareWorkstationPro -
Installing Mageia Linux 10 RC1 on VMware Workstation
The first release candidate of Mageia Linux 10 was announced yesterday, and it brought some awesome lock screen pictures, along with some updated packages, such as the Linux kernel. This release candidate was released after the beta version to add in some improvements. Mageia Linux was released as a fork of Mandriva Linux, which is a successor of Mandrake Linux.
In this article, we will showcase how to install Mageia Linux 10 RC1 to a VMware installation. First, we will configure the virtual machine as follows:
After that, open the virtual machine settings, navigate to New CD/DVD, and select the Mageia ISO file.
Then, we’ll go ahead and turn on the virtual machine. We’re greeted with a rather nice GRUB boot screen.
As soon as we press ENTER, the Mageia installer starts with this:
After that, the GUI version of the Mageia installer starts, asking us for a language to use.
After that, we’re greeted with the license agreement.
After the license agreement, you can choose the timezone. The default selection is New York.
After that, you can configure the clock, including the hardware clock configuration (local time or UTC), and choosing whether to sync with NTP server or not.
Then, you can choose the keyboard layout.
Now, we get into the partitioning stage. You can choose either the guided partitioning or custom partitioning. As we have no installed operating systems, we can choose to use the whole disk.
Media selection comes after the partitioning stage in the installer. The installer has automatically selected both the Core Release and the Nonfree Release media. Currently, we’ll be installing the base system entirely from the installation ISO file.
After this stage, the installer provides us with options for the desktop environment, with KDE as the default. We have chosen to go with the KDE Plasma environment.
Afterwards, the installation begins.
When the installation finishes, the user configuration comes afterwards. You can set the root password, the username of your account, and the password.
Afterwards, the display configuration comes. The installer asks us to choose a monitor. As we’re on a virtual machine, this is likely not relevant. So, we kept it at Plug-n-Play.
As soon as we go to the next step, the installer shows you the summary of the system configuration, just like below:
Before the configuration finishes, the installer asks us if we want to configure the online media. We have approved it. Then, we allowed the installer to automatically choose the best mirror and download method available.
After that, the installer is now finished.
Then, we let the system reboot to the GRUB menu.
We let the system boot to the simplistic-looking login screen.
After we log in to the newly-created account, we’re presented with a desktop and a welcome window.
Awesome! Now we’re on the Mageia Desktop!
We have checked for available package updates by going to the Update screen. It shows a list of packages that were available for updating.
We have selected all the packages to upgrade them. As soon as we clicked on Update, the software update manager starts downloading package files and installing them to the system.
Afterwards, we have restarted the virtual machine for the new kernel to be used.
Lock screen wallpapers
The Mageia 10 RC1 announcement has stated that there are awesome screensavers included in the release candidate. However, it was actually referring to the lock screen wallpapers.
You can find those 20 wallpapers (found in
/usr/share/mga/screensaver) through the lock screen settings.Once you apply the changes, you can now see the login screen with one of the 20 lock screen wallpapers chosen.
#Linux #Mageia #Mageia10 #Mageia10RC1 #MageiaLinux #MageiaLinux10 #MageiaLinux10RC1 #news #Tech #Technology #update #VMware #VMwareWorkstation #VMwareWorkstation26H1 #VMwareWorkstationPro -
Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.
Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*
(Script Begin)
#!/bin/bashset -ex
# check for mount
grep /backup /etc/mtab > /dev/null || exit 1# directory to backup
BDIR=/home/wilma_wein/# Destination dir for rsync
DDIR=/media/backup# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"export PATH=$PATH:/bin:/usr/bin:/usr/local/bin
# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.Folgende Laufwerke sind in meiner #fstab gemountet:
# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ??? -
Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.
Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*
(Script Begin)
#!/bin/bashset -ex
# check for mount
grep /backup /etc/mtab > /dev/null || exit 1# directory to backup
BDIR=/home/wilma_wein/# Destination dir for rsync
DDIR=/media/backup# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"export PATH=$PATH:/bin:/usr/bin:/usr/local/bin
# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.Folgende Laufwerke sind in meiner #fstab gemountet:
# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ??? -
Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.
Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*
(Script Begin)
#!/bin/bashset -ex
# check for mount
grep /backup /etc/mtab > /dev/null || exit 1# directory to backup
BDIR=/home/wilma_wein/# Destination dir for rsync
DDIR=/media/backup# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"export PATH=$PATH:/bin:/usr/bin:/usr/local/bin
# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.Folgende Laufwerke sind in meiner #fstab gemountet:
# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ??? -
Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.
Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*
(Script Begin)
#!/bin/bashset -ex
# check for mount
grep /backup /etc/mtab > /dev/null || exit 1# directory to backup
BDIR=/home/wilma_wein/# Destination dir for rsync
DDIR=/media/backup# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"export PATH=$PATH:/bin:/usr/bin:/usr/local/bin
# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.Folgende Laufwerke sind in meiner #fstab gemountet:
# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ??? -
#Linux wird auch woanders gemobbt. Letzte Woche: Großes #Hyundai Navikarten-Update für den Kona. Nur via USB. Die Software zum Bespielen der Daten auf Stick nur für Windows und Mac. An die Daten selber kommt man über Website gar nicht ran (z.B. um eigenen Stick zu erstellen). Und die Website zum Download der "Bespiel-Software" blockt Linux-Nutzer schon ab. Also nix "mal mit Wine probieren" oder so.
-
GNOME may rule Ubuntu Resolute Raccoon, but X.org isn't roadkill yet.
-
Haruna 1.8 porta una serie di miglioramenti concreti: nuove opzioni per playlist, OSD più informativo, gestione file avanzata e fix mirati. #Linux #Haruna #mpv #OpenSource #Software
-
Haruna 1.8 porta una serie di miglioramenti concreti: nuove opzioni per playlist, OSD più informativo, gestione file avanzata e fix mirati. #Linux #Haruna #mpv #OpenSource #Software
