[INFO] Debian 6 Squeeze (Τesting): Συμβουλές, απορίες, συζητήσεις

[skiaxtro7]

ρε παιδια συγνωμη αλλα μπορειτε να μου πειτε πως μπορω να βαλω μια συντομευση στο desktop?Αρχικα δεν δουλευε καν το δεξι κλικ και δεν ειχε καμοια εικονα,το εφτιαξα αυτο αλλα τωρα εχω μονο το computer-home-thrash και σε δεξι κλικ δεν μου εμφανιζει create lancher...σε gnome

[jim_p]

Αν πιασεις μια συντομευση απο το μενου του gnome και την συρεις στην επιφανεια εργασιας, δεν μενει εκει?

Εδω κατι δειχνει με το gnome-tweak-tool, που αν καταλαβα καλα οριζει τον nautilus να χειριζεται το desktop.

http://www.youtube.com/watch?v=hy3r8H39-aU

 

Αν ουτε ετσι δεις προκοπη, κανεις ενα απλο cp και εχεις μια νεα συντομευση, πχ

>cp /usr/share/applications/emesene.desktop ~/Desktop

Ετσι το κανω στο lxde που ο pcmanfm (ο οποιος χειριζεται το desktop) δεν εχει κατι αναλογο, και στο kde που αν συρεις μια εφαρμογη στο desktop δημιουργει συντομευση-plasmoid της εφαρμογης (facepalm icon here).

 

http://distrowatch.com/weekly.php?issue=20120625#news

 

The Debian release team has announced that on 30 June, the Debian project will stop the automatic migration of packages from unstable to testing; with this move, the development of Debian 7.0 (Wheezy), which is currently being prepared in testing, will be frozen.

[skiaxtro7]

Ωραιος ο φιλος.επισης κατι αλλο.Πως μπορω να εγκαταστησω τον driver της καρτας γραφικων?Δοκιμασα οδηγιες απο το wiki αλλα εχω προβλημα..

01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M96 [Mobility Radeon HD 4650] αυτή είναι η κάρτα.

http://wiki.debian.org/ATIProprietary δοκίμασα αυτό αλλα τίποτα.Επίσης κατέβασα και ενα run file απο το site τους αλλα δεν ξέρω πως το τρέχουμε αυτό!

[miza]

Απλά δεν μπορείς να βάλεις Catalyst, ούτε θα μπορέσεις. Αυτή τη στιγμή ο 12.4 Catalyst driver που υποστηρίζει την κάρτα σου, δεν υποστηρίζει Xorg 1.12 που έχει το Testing.O Catalyst 12.6 που θα βγει σε λίγο καιρό, θα υποστηρίζει τον Xorg 1.12, αλλά δεν θα υποστηρίζει κάρτες κάτω από 5ΧΧΧ series. Μάλλον ο Linus πρέπει να κάνει ένα κoλοδάχτυλο και προς την AMD.

Επεξ/σία 25 Ιουνίου 2012 από miza

[jim_p]

Καλυτερα να μεινεις με radeon αν δεν εχεις προβληματα με υπερθερμανση. Και να βαλεις οπωσδηποτε το πακετο firmware-linux-nonfree.

[warlock9_0]

που είναι τα logs του shutdown/reboot?

όποτε κάνω reboot το server μένει κάπου για πάντα και δεν ξέρω που, και κλείνει μόνο από το κουμπί

shutdown κάνει κανονικά

στο /var/log/messages δε λέει κάτι

[jemadux]

μηπως καποιος mod πρεπει να το πει debian testing επειδη τωρα το squeeze ειναι stable και το testing ειναι wheezy και σε λιγο καιρο θα γινει wheezy stable ?

[magnaman]

γεια χαρα παιδες.. τα φωτα σας

προσπαθω να ενεργοποιησω το iscsi αλλα φαινεται καπωσ μπερδεμενη η κατασταση

 

 

 

root@db02:~# /etc/init.d/open-iscsi restart

Unmounting iscsi-backed filesystems: Unmounting all devices marked _netdev.

Disconnecting iSCSI targets:Logging out of session [sid: 1, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.1,3260]

Logging out of session [sid: 2, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.1,3260]

 

Message from syslogd@db02 at Aug 20 16:30:30 ...

kernel:[4145648.563071] Oops: 0011 [#1] SMP

 

Message from syslogd@db02 at Aug 20 16:30:30 ...

kernel:[4145648.563112] last sysfs file: /sys/devices/virtual/block/dm-8/uevent

 

Message from syslogd@db02 at Aug 20 16:30:30 ...

kernel:[4145648.564668] Stack:

 

Message from syslogd@db02 at Aug 20 16:30:30 ...

kernel:[4145648.564947] Call Trace:

 

Message from syslogd@db02 at Aug 20 16:30:30 ...

kernel:[4145648.566017] Code: ff ff ff 20 8f d1 54 00 ea ff ff 24 00 00 00 00 0a 00 00 00 00 00 00 00 00 00 00 00 dc 8e 3b 18 88 ff ff f0 1d 9e 3a 08 88 ff ff <98> 90 cb 3b 18 88 ff ff 98 90 cb 3b 18 88 ff ff 00 00 00 00 00

 

Message from syslogd@db02 at Aug 20 16:30:30 ...

kernel:[4145648.566398] CR2: ffff88183bcb9098

Logout of [sid: 1, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.1,3260]: successful

Logout of [sid: 2, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.1,3260]: successful

.

Stopping iSCSI initiator service:.

Starting iSCSI initiator service: iscsid.

Setting up iSCSI targets:

Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.2,3260]

Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.1,3260]

Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.2,3260]

Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.1,3260]

Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.2,3260]

Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.1,3260]

iscsiadm: Could not login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.2,3260]:

iscsiadm: initiator reported error (8 - connection timed out)

Login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.1,3260]: successful

iscsiadm: Could not login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.2,3260]:

iscsiadm: initiator reported error (15 - already exists)

iscsiadm: Could not login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.1,3260]:

iscsiadm: initiator reported error (15 - already exists)

iscsiadm: Could not login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.1.2,3260]:

iscsiadm: initiator reported error (8 - connection timed out)

Login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.112512e760, portal: 10.0.0.1,3260]: successful

iscsiadm: Could not log into all portals. Err 8.

 

 

 

πριν παρω σβαρνα ολα τα φορουμ του ιντερνετ υπαρχει καποιος απλος οδηγος που θα με βοηθησει να εγκαταστησω η να παραμετροποιησω την ολη ιστορια ?

 

τρεχω debian squeeze 6.0.3 - amd netinstall 64

 

 

 

λοιπον παραθετω και το conf για να ειμαστε κομπλε ..

 

 

root@db02:~# vi /etc/iscsi/iscsid.conf

#node.session.auth.username = username

#node.session.auth.password = password

 

# To set a CHAP username and password for target(s)

# authentication by the initiator, uncomment the following lines:

#node.session.auth.username_in = username_in

#node.session.auth.password_in = password_in

 

# To enable CHAP authentication for a discovery session to the target

# set discovery.sendtargets.auth.authmethod to CHAP. The default is None.

#discovery.sendtargets.auth.authmethod = CHAP

 

# To set a discovery session CHAP username and password for the initiator

# authentication by the target(s), uncomment the following lines:

#discovery.sendtargets.auth.username = username

#discovery.sendtargets.auth.password = password

 

# To set a discovery session CHAP username and password for target(s)

# authentication by the initiator, uncomment the following lines:

#discovery.sendtargets.auth.username_in = username_in

#discovery.sendtargets.auth.password_in = password_in

 

# ********

# Timeouts

# ********

#

# See the iSCSI REAME's Advanced Configuration section for tips

# on setting timeouts when using multipath or doing root over iSCSI.

#

# To specify the length of time to wait for session re-establishment

# before failing SCSI commands back to the application when running

# the Linux SCSI Layer error handler, edit the line.

# The value is in seconds and the default is 120 seconds.

node.session.timeo.replacement_timeout = 120

 

# To specify the time to wait for login to complete, edit the line.

# The value is in seconds and the default is 15 seconds.

node.conn[0].timeo.login_timeout = 5

 

# To specify the time to wait for logout to complete, edit the line.

# The value is in seconds and the default is 15 seconds.

node.conn[0].timeo.logout_timeout = 15

 

# Time interval to wait for on connection before sending a ping.

node.conn[0].timeo.noop_out_interval = 5

 

# To specify the time to wait for a Nop-out response before failing

# the connection, edit this line. Failing the connection will

# cause IO to be failed back to the SCSI layer. If using dm-multipath

# this will cause the IO to be failed to the multipath layer.

node.conn[0].timeo.noop_out_timeout = 5

 

# To specify the time to wait for abort response before

# failing the operation and trying a logical unit reset edit the line.

# The value is in seconds and the default is 15 seconds.

node.session.err_timeo.abort_timeout = 15

 

# To specify the time to wait for a logical unit response

# before failing the operation and trying session re-establishment

# edit the line.

# The value is in seconds and the default is 30 seconds.

node.session.err_timeo.lu_reset_timeout = 20

 

#******

# Retry

#******

 

# To specify the number of times iscsid should retry a login

# if the login attempt fails due to the node.conn[0].timeo.login_timeout

# expiring modify the following line. Note that if the login fails

# quickly (before node.conn[0].timeo.login_timeout fires) because the network

# layer or the target returns an error, iscsid may retry the login more than

# node.session.initial_login_retry_max times.

#

# This retry count along with node.conn[0].timeo.login_timeout

# determines the maximum amount of time iscsid will try to

# establish the initial login. node.session.initial_login_retry_max is

# multiplied by the node.conn[0].timeo.login_timeout to determine the

# maximum amount.

#

# The default node.session.initial_login_retry_max is 8 and

# node.conn[0].timeo.login_timeout is 15 so we have:

#

# node.conn[0].timeo.login_timeout * node.session.initial_login_retry_max =

# 120 seconds

#

# Valid values are any integer value. This only

# affects the initial login. Setting it to a high value can slow

# down the iscsi service startup. Setting it to a low value can

# cause a session to not get logged into, if there are distuptions

# during startup or if the network is not ready at that time.

node.session.initial_login_retry_max = 1

 

################################

# session and device queue depth

################################

 

# To control how many commands the session will queue set

# node.session.cmds_max to an integer between 2 and 2048 that is also

# a power of 2. The default is 128.

node.session.cmds_max = 128

 

# To control the device's queue depth set node.session.queue_depth

# to a value between 1 and 1024. The default is 32.

node.session.queue_depth = 32

 

##################################

# MISC SYSTEM PERFORMANCE SETTINGS

##################################

 

# For software iscsi (iscsi_tcp) and iser (ib_iser) each session

# has a thread used to transmit or queue data to the hardware. For

# cxgb3i you will get a thread per host.

#

# Setting the thread's priority to a lower value can lead to higher throughput

# and lower latencies. The lowest value is -20. Setting the priority to

# a higher value, can lead to reduced IO performance, but if you are seeing

# the iscsi or scsi threads dominate the use of the CPU then you may want

# to set this value higher.

#

# Note: For cxgb3i you must set all sessions to the same value, or the

# behavior is not defined.

#

# The default value is -20. The setting must be between -20 and 20.

node.session.xmit_thread_priority = -20

 

 

#***************

# iSCSI settings

#***************

 

# To enable R2T flow control (i.e., the initiator must wait for an R2T

# command before sending any data), uncomment the following line:

#

#node.session.iscsi.InitialR2T = Yes

#

# To disable R2T flow control (i.e., the initiator has an implied

# initial R2T of "FirstBurstLength" at offset 0), uncomment the following line:

#

# The defaults is No.

node.session.iscsi.InitialR2T = No

 

#

# To disable immediate data (i.e., the initiator does not send

# unsolicited data with the iSCSI command PDU), uncomment the following line:

#

#node.session.iscsi.ImmediateData = No

 

#

# To enable immediate data (i.e., the initiator sends unsolicited data

# with the iSCSI command packet), uncomment the following line:

#

# The default is Yes

node.session.iscsi.ImmediateData = Yes

 

# To specify the maximum number of unsolicited data bytes the initiator

# can send in an iSCSI PDU to a target, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the default is 262144

node.session.iscsi.FirstBurstLength = 262144

 

# To specify the maximum SCSI payload that the initiator will negotiate

# with the target for, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the defauls it 16776192

node.session.iscsi.MaxBurstLength = 16776192

 

# To specify the maximum number of data bytes the initiator can receive

# in an iSCSI PDU from a target, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the default is 262144

node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144

 

# To specify the maximum number of data bytes the initiator can receive

# in an iSCSI PDU from a target during a discovery session, edit the

# following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the default is 32768

#

discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768

 

# To allow the targets to control the setting of the digest checking,

# with the initiator requesting a preference of enabling the checking, uncomment# one or both of the following lines:

#node.conn[0].iscsi.HeaderDigest = CRC32C,None

#node.conn[0].iscsi.DataDigest = CRC32C,None

#

# To allow the targets to control the setting of the digest checking,

# with the initiator requesting a preference of disabling the checking,

# uncomment one or both of the following lines:

#node.conn[0].iscsi.HeaderDigest = None,CRC32C

#node.conn[0].iscsi.DataDigest = None,CRC32C

 

# To enable CRC32C digest checking for the header and/or data part of

# iSCSI PDUs, uncomment one or both of the following lines:

#node.conn[0].iscsi.HeaderDigest = CRC32C

#node.conn[0].iscsi.DataDigest = CRC32C

#

# To disable digest checking for the header and/or data part of

# iSCSI PDUs, uncomment one or both of the following lines:

#node.conn[0].iscsi.HeaderDigest = None

#node.conn[0].iscsi.DataDigest = None

#

# The default is to never use DataDigests or HeaderDigests.

#

 

 

#************

# Workarounds

#************

 

# Some targets like IET prefer after an initiator has sent a task

# management function like an ABORT TASK or LOGICAL UNIT RESET, that

# it does not respond to PDUs like R2Ts. To enable this behavior uncomment

# the following line (The default behavior is Yes):

node.session.iscsi.FastAbort = Yes

 

# Some targets like Equalogic prefer that after an initiator has sent

# a task management function like an ABORT TASK or LOGICAL UNIT RESET, that

# it continue to respond to R2Ts. To enable this uncomment this line

# node.session.iscsi.FastAbort = No

[jim_p]

Πως θα κανω το /etc/init.d/utserver να τρεχει στα 2,3,4 και 5? Το επελεξα στο sysv-rc-conf αλλα μαλλον με γειωσε.

Το /etc/rc2.d/S20utserver πχ υπαρχει κανονικα.

[warlock9_0]

και στο wiki αν θυμάμαι καλά με το sysv-rc-conf λέει οτι γίνεται

χαζή ερώτηση, είναι εκτελέσιμο?

 

δοκίμασε και με update-rc.d

[jim_p]

Ειναι εκτελεσιμο. Δοκιμασα και με το "updater-cs.d utserver defaults" αλλα τιποτα.

[SV8XXX]

Στην εγκατάσταση μου δεν έχω ορίσει swap, και όλα πάνε καλά...

Όταν πότε - πότε κοιτάω το bootlog βλέπω να ενεργοποιεί swap.

Δεν με πειράζει, αλλά αναρωτιέμαι μήπως μπορώ να το απενεργοποιήσω ?

 

[chris@debian ~]$ cat /var/log/boot | grep swap

Mon Sep 3 19:08:13 2012: [....] Activating swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.

Mon Sep 3 19:08:13 2012: [....] Activating lvm and md swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.

Mon Sep 3 19:08:13 2012: [....] Activating swapfile swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.

 

 

[chris@debian ~]$ free -m

total used free shared buffers cached

Mem: 7997 778 7219 0 34 337

-/+ buffers/cache: 405 7591

Swap: 0 0 0

 

 

 

[Επισκέπτης]

Καλησπέρα! Έχω ένα αρχείο .jpg πολύ μεγάλο γύρω στα 30 Mb και 15000 επι 21000 πίξελς περίπου. Το θέμα είναι ότι δέ μου ο ανοίγει καθόλου και μου κρασάρει ο Χ. Με βγάζει στη login screen. Να φταίνε λέτε τα χαραακτηριστικά του υπολογιστή; Dual core sta 2.6, 2 Gb RAM 64 bit kai GNOME3 Επίσης να πώ ότι δέν έχω τους οδηγους της NVIDIA αλλα το Νουβώ

[warlock9_0]

δοκίμασες με άλλο πρόγραμμα?

[jim_p]

Υπαρχει καποιος λογος για τον οποιο εισαι με nouveau?