Recent Posts

Advanced search

Welcome, Guest. Please login or register.
Did you miss your activation email?
2019/03/26, 11:32:49

1 Hour 1 Day 1 Week 1 Month Forever

•    Debian Transitions
•    New/Byhand
•    Distrowatch
•    Google+

•      Help
•      Contact

1

Free Speech / Freie Rede / Re: Installations-Image KDE vermutlich zu alt

« Last post by axt on Today at 08:18:14 »

brannte es neu auf DVD

Mit dd auf einen USB-Stick.

Den Versuch machte ich damals an unterschiedlichen Tagen um Fehler von irgendeinem Server auszuschließen.

Du weißt aber schon, wozu sha256 da ist?

piper, on this occasion he can ask, when an official release can be expected again...

2

Free Speech / Freie Rede / Re: Installations-Image KDE vermutlich zu alt

« Last post by piper on Today at 02:07:24 »

Go to irc and ask for new build

3

Upgrade Warnings (DE / EN) / [solved] Re: NFS fails

« Last post by Penyelam on Yesterday at 22:42:36 »

Thanks a lot
it works 

4

Free Speech / Freie Rede / Installations-Image KDE vermutlich zu alt

« Last post by NochEinNeuer on Yesterday at 19:58:29 »

Hallo,
ich weis nicht ob es hier richtig rein passt.Leider bin ich auch etwas spät dran um auf dieses Problem hinzuweisen.
Als ich Ende 2018 siduction KDE installieren wollte, so gab es bei der Installation einen unüberwindlichen Fehler.
Im Laufe der Installation versuchte siduction automatisch den download von irgendwelchen Daten. Welche genau weis ich nicht mehr. Dies schlug fehl und die Installation wurde abgebrochen.Das Image holte ich mir damals neu und brannte es neu auf DVD und bei der Installation tauchte das gleiche Problem wieder auf. Den Versuch machte ich damals an unterschiedlichen Tagen um Fehler von irgendeinem Server auszuschließen.

Letztendlich behalf ich mich, in dem ich das gnome Image installierte, KDE nachinstallierte und gnome Pakete deinstallierte.
Wobei das leider nicht die sauberste und zufriedenstellenste Lösung war.
Vielleicht sollte sich das jemand, der etwas mehr Ahnung hat, mal bei Gelegenheit anschauen. Vielleicht lag der Fehler ja auf meiner Seite.
Viele Grüße,Jürgen

5

Software Support (EN) / Re: file ownership: fuse

« Last post by jyp on Yesterday at 19:04:11 »

@devil
Nothing happened in backintime yet because I did not run it, just exploring.
I am just wondering how the group id became _fuse_ as I, for sure, did not volontarily assign this group to the _directories/ subdirectories/files_ that I created. Now this group id is everywhere.

But when I create a new directory or a new file, it comes out with normal ownership. For instance

Code: [Select]

...:/hdd01/data$ ls -l
total 104
drwxr-xr-x  2 jy   jy    4096 mar 25 13:51 000-test

...:/hdd01/data/000-test$ ls -l
total 0
-rw-r--r-- 1 jy jy 0 mar 25 13:53 test-file.txt
I am the only _user_  (jy) on that machine.

Would it be better practice to get rid of the _fuse_ group and put back _jy_ ? Is there a reason that _fuse_ has been assigned?
Just trying to understand.

Thanks.

This is the state of my system.

Code: [Select]

...:$ inxi -F
System:    Host: omega Kernel: 4.20.16-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.14.5
           Distro: siduction 17.1.0 Patience - kde - (201703051755)
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: N/A
           Mobo: ASUSTeK model: SABERTOOTH Z87 v: Rev 1.xx serial: 130612993600174 BIOS: American Megatrends
           v: 1803 date: 02/17/2014
CPU:       Topology: Quad Core model: Intel Core i5-4670K bits: 64 type: MCP L2 cache: 6144 KiB
           Speed: 800 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
...
Drives:    Local Storage: total: 3.75 TiB used: 928.14 GiB (24.2%)
           ID-1: /dev/sda vendor: Intel model: SSDSC2BW120A4 size: 111.79 GiB
           ID-2: /dev/sdb vendor: Western Digital model: WD2002FAEX-00MJRA0 size: 1.82 TiB
           ID-3: /dev/sdc vendor: Western Digital model: WD2002FAEX-00MJRA0 size: 1.82 TiB
Partition: ID-1: / size: 90.82 GiB used: 12.00 GiB (13.2%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 4.88 GiB used: 119.0 MiB (2.4%) fs: swap dev: /dev/sda3
...
Info:      Processes: 231 Uptime: 6d 22h 57m Memory: 15.54 GiB used: 7.68 GiB (49.4%) Shell: bash inxi: 3.0.32

 When I installed _siduction 17.1.0 Patience -kde_ on my homemade box, I structured it like this

Code: [Select]

...$ df -hT | sortFilesystem     Type      Size  Used Avail Use% Mounted on
/dev/sda2      ext4       91G   13G   75G  14% /
/dev/sdb1      ext4      394G  126G  249G  34% /hdd01/data
/dev/sdb2      ext4      739G  177G  524G  26% /hdd01/music-photos
/dev/sdb3      ext4      689G  156G  499G  24% /hdd01/videos
/dev/sdc1      ext4      394G  125G  250G  34% /hdd02/data_bu
/dev/sdc2      ext4       99G  1.4G   92G   2% /hdd02/home_bu
/dev/sdc3      ext4      689G  177G  477G  28% /hdd02/music-photos_bu
/dev/sdc4      ext4      640G  156G  452G  26% /hdd02/videos_bu...


Code: [Select]

...:/$ ls -l
total 112
drwxr-xr-x   2 root root 12288 Mar 18 13:54 bin
drwxr-xr-x   3 root root  4096 Mar 18 14:08 boot
drwxr-xr-x  20 root root  3900 Mar 25 07:33 dev
drwxr-xr-x   2 root root  4096 Mar 23  2017 disks
drwxr-xr-x 146 root root 12288 Mar 23 11:39 etc
drwxr-xr-x   2 root root  4096 Mar 23  2017 fll
drwxr-xr-x   5 root root  4096 Mar 23 11:27 hdd01
drwxr-xr-x   6 root root  4096 Mar 23 11:18 hdd02
drwxr-xr-x   3 root root  4096 Mar 23  2017 home
lrwxrwxrwx   1 root root    46 Mar 18 13:58 initrd.img -> boot/initrd.img-4.20.16-towo.1-siduction-amd64
lrwxrwxrwx   1 root root    46 Mar 18 13:58 initrd.img.old -> boot/initrd.img-4.20.13-towo.1-siduction-amd64
drwxr-xr-x  19 root root  4096 Mar  4 14:13 lib
drwxr-xr-x   2 root root  4096 Mar  4 14:05 lib64
drwx------   2 root root 16384 Mar 23  2017 lost+found
drwxr-xr-x   3 root root  4096 Mar 24  2017 media
drwxr-xr-x   2 root root  4096 Mar 23  2017 mnt
drwxr-xr-x   3 root root  4096 Nov 23  2017 opt
dr-xr-xr-x 241 root root     0 Mar 18 14:09 proc
drwx------  15 root root  4096 Mar 23 11:27 root
drwxr-xr-x  36 root root   960 Mar 18 14:09 run
drwxr-xr-x   2 root root 12288 Mar 18 13:58 sbin
drwxr-xr-x   2 root root  4096 Mar  5  2017 srv
dr-xr-xr-x  13 root root     0 Mar 18 14:09 sys
drwxrwxrwt  19 root root   760 Mar 25 09:38 tmp
drwxr-xr-x  11 root root  4096 Feb  4 17:09 usr
drwxr-xr-x  11 root root  4096 Mar  5  2017 var
lrwxrwxrwx   1 root root    43 Mar 18 13:58 vmlinuz -> boot/vmlinuz-4.20.16-towo.1-siduction-amd64
lrwxrwxrwx   1 root root    43 Mar 18 13:58 vmlinuz.old -> boot/vmlinuz-4.20.13-towo.1-siduction-amd64


Code: [Select]

...:/$ ls -l hdd01
total 12
drwxr-xr-x 24 jy fuse 4096 Mar 23 12:20 data
drwxr-xr-x  6 jy fuse 4096 Feb 24  2017 music-photos
drwxr-xr-x 30 jy fuse 4096 Apr 11  2018 videos


Code: [Select]

...:/# ls -l hdd02
total 16
drwxr-xr-x 21 jy fuse 4096 Jan 15 13:51 data_bu
drwx------ 23 jy jy   4096 Mar 22 17:34 home_bu
drwxr-xr-x  5 jy fuse 4096 Feb 24  2017 music-photos_bu
drwxr-xr-x 31 jy fuse 4096 Apr 11  2018 videos_bu


6

Upgrade Warnings (DE / EN) / Re: NFS fails

« Last post by bluelupo on Yesterday at 18:03:11 »

Hi Penyelam,
try this.... 

Code: [Select]

mount -t nfs -o nfsvers=4 siductionbox:/ /mnt

7

Upgrade Warnings (DE / EN) / [solved] NFS fails

« Last post by Penyelam on Yesterday at 12:12:59 »

Since the last DU I get an error when I try to mount a NFS

Code: [Select]

root@sidThinkpad:/var/log#  mount -t nfs4 siductionbox:/ /mnt
mount.nfs4: requested NFS version or transport protocol is not supported


Code: [Select]

root@sidThinkpad:/var/log# inxi -S
System:    Host: sidThinkpad Kernel: 5.0.4-towo.1-siduction-amd64 x86_64 bits: 64 Console: tty 1
           Distro: siduction 18.2.0 Patience - kde - (201803072323)
manfred@siductionbox:/var/log$ inxi -S
System:    Host: siductionbox Kernel: 5.0.4-towo.1-siduction-amd64 x86_64 bits: 64 Console: tty 1
           Distro: siduction 17.1.0 Patience - kde - (201703051755)
There is no entry in journalctl

8

Installation Support (EN) / Re: chromebook headache

« Last post by dibl on 2019/03/24, 22:52:27 »

...  I would like to know of any recommendations (laptop make/model) that anyone knows of, or has already installed siduction linux successfully on to ...

HP makes good laptops -- I have installed and run siduction on a couple of models.

9

Siduction News (DE) / siduction beim Linux-Infotag 2019 in Augsburg

« Last post by bluelupo on 2019/03/24, 15:38:17 »

Hallo Community,

wie in den vergangenen Jahren sind wir wieder mit einem Stand beim 18. Linux-Infotag in Augsburg vertreten.

Die Veranstaltung findet am Samstag den 6. April 2019 zwischen 9:30–17:30 Uhr in der Hochschule Augsburg (Fakultät für Informatik) statt.

Am Stand sind wieder anzutreffen:
Spike_DE
vindeliker
harley-peter
bluelupo

Wir freuen uns auf euren Besuch bei den Augsburger Linux-Infotag.

Detailinfos unter:
https://www.luga.de/Aktionen/LIT-2019/

Lageplan:
https://www.google.de/maps/place/48%C2%B021'29.5%22N+10%C2%B054'23.7%22E/@48.358196,10.9043913,725m/data=!3m2!1e3!4b1!4m5!3m4!1s0x0:0x0!8m2!3d48.358196!4d10.90658?hl=de

10

Installation Support (EN) / Re: chromebook headache

« Last post by ayla on 2019/03/24, 12:14:40 »

Machine:   Type: Laptop System: HP product: HP 250 G5 Notebook PC v: Type1ProductConfigId serial: <root required>
           Mobo: HP model: 81ED v: 62.36 serial: <root required> UEFI: Insyde v: F.21 date: 10/27/2016
CPU:       Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21696
           Speed: 2510 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 2510 2: 2930 3: 2908 4: 2514
Graphics:  Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
           Display: x11 server: X.Org 1.20.3 driver: intel resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3
           Sound Server: ALSA v: k4.20.13-towo.1-siduction-amd64
Network: Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: 3000 bus ID: 02:00.0
           IF: wlp2s0 state: up mac: 10:f0:05:07:b3:f4

Works fine with siduction since about 3 Years