Page: Previous  1, 2, 3 ... 10, 11, 12, 13, 14  Next

techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I'm leaving the old ceni because it will work on squeeze, but I'm going to change the installer option to get either the old one or a current one for wheezy/sid systems.

Ceni is by kelmo, and as long as kelmo is in aptosid still, it's an aptosid project. I actually thought he'd get that into debian proper since he has a lot of real debian connections but it didn't happen. And if kelmo stops maintaining that, by the way, ceni will soon no longer be good.
Back to top
removing desktop environments
jiro
Status: Interested
Joined: 11 Jul 2009
Posts: 36
Reply Quote
I used KDE until I got fed up with KDE4, then switched to Gnome. Gnome 3 is unusable and clunky (for me) so I now switched to XFCE.

Feature request: a menu for deleting old desktop environments.

to remove gnome, I apt-get removed "gnome" then all "gnome-*" packages, then did an apt-get autoremove, then removed all orphans and installed XFCE, except that I wound up reinstalling the minimal gnome environment to get a working gdm3 (which btw is unconfigurable in debian, with a childish default background)

it would be great to automate this, not only for removing gnome but also for other desktop environments / window managers. (wms are easier using plain apt-get, though)
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
yeah, that's worth looking at. You can't automate orphan removal because a fair number of packages are seen by apt as orphans even though other apps need them to function, some multimedia codecs for example are like that.

But the other parts, yeah, makes sense.

Just for kde and gnome though, of course. Well, and xfce I guess.

How is autoremove now? is it reliable?
Back to top
jiro
Status: Interested
Joined: 11 Jul 2009
Posts: 36
Reply Quote
:: techAdmin wrote ::
How is autoremove now? is it reliable?


I have never had a problem with autoremove or orphan removal, for several years at least. OTOH, I don't do anything "blindly" but make sure I really want to delete whatever autoremove is set to delete. (Also, I use synaptic to configure all lib* files as automatically installed, which they are, and then they are autoremoved whenever they are no longer needed.)

sometimes you can remove a small package and the autoremove will offer to delete your entire desktop, for example. smxi is great, but there is no substitute for using common sense.

I have heard the multimedia concerns with removing orphans, but never had any problems myself.

I don't know if this make a difference, but I run pure sid, using only slh's kernel and ceni.
Back to top
aus9
Status: Assistant
Joined: 21 Sep 2008
Posts: 358
Location: Australia
Reply Quote
is there some way of getting closed source Nvidia to either not call
:: Code ::

nvidia-xconfig
after running a new or repeating nvidia thru smxi or sgfxi?

REASONS
1 Each time your DU replaces xorg you need to run nvidia,
which replaces your xorg.conf
2 Each time nvidia updates ....nvidia replaces your xorg.conf

RESEARCH
Yesterday's DU thru smxi claimed the script was last modified 30 Oct 11 so I was keen to look at all logs.

Before I just accepted xorg started and being lazy did not do any further research but today I tried this

:: Code ::

cat /var/log/Xorg.0.log | grep EE


it had errors for keyboard and mouse

Now for those who can remember a certain forum and the new udev rules etc for xorg we were advised to have a BASIC xorg.conf eg

:: Quote ::

Section "Device"
Identifier "Card0"
Driver "nv"
VendorName "nVidia Corporation"
BoardName "G96 [GeForce 9500 GT]"
BusID "PCI:1:0:0"
EndSection


but running nvidia-xconfig gives me

:: Quote ::

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "built-ins"
EndSection

Section "Module"
Load "record"
Load "dri2"
Load "extmod"
Load "glx"
Load "dbe"
# Load "dri"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "VideoKey" # <i>
#Option "WrappedFB" # [<bool>]
#Option "GLXVBlank" # [<bool>]
#Option "ZaphodHeads" # <str>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "nvidia"
Option "Coolbits" "1"
Option "AddARGBGLXVisuals" "true"
Option "TripleBuffer" "false"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "enable"
# Option "RENDER" "disable"
EndSection


So what I am currently doing is removing all lines of
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection


I could do it using a replacement xorg that replaces any existing in say...
etc/rc.local

anyhows re-running the grep for EE shows I have fixed the issue

If no-one understands what I am waffling on about...its ok I shall treat this as my online notes

regards
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
as far as I know, nvidia-xconfig is not called by the nvidia installer at all, at least, it never was in the past.

So sgfxi would never run that, or shouldn't.

sgfxi definitely does not change the keyboard/mouse stuff in any way, shape, or form.

I dont' test the stuff all the time, so of course, this could have changed.
Back to top
aus9
Status: Assistant
Joined: 21 Sep 2008
Posts: 358
Location: Australia
Reply Quote
hi

well I may be wrong again...groan but sgfxi line 4947 starts with

:: Code ::

if [ "$B_TESTING_6" != 'true' ];then
      log_function_data "Post Purge/Remove: nvidia.ko files: \n$( ls /lib/modules/*/kernel/drivers/video/nvidia.ko 2>/dev/null )"
      #rm -f /lib/modules/$KERNEL_FULL/kernel/drivers/video/nvidia.ko 1>> $LOG_FILE 2>> $LOG_FILE
      # for real driver installs, we need to remove ALL the existing nvidia driver .ko files
      rm -f /lib/modules/*/kernel/drivers/video/nvidia.ko 1>> $LOG_FILE 2>> $LOG_FILE
      # this is legacy stuff, not currently present
      rm -f /lib/modules/*/volatile/nvidia.ko >/dev/null 1>> $LOG_FILE 2>> $LOG_FILE
      rm -f /usr/local/bin/nvidia-settings /usr/local/bin/nvidia-xconfig 1>> $LOG_FILE 2>> $LOG_FILE
      rm -f /tmp/.X0-lock
      # double check, clean up anything left after uninstaller runs
      rm -f ${USRS}nvidia* 1>> $LOG_FILE 2>> $LOG_FILE
      rm -f ${SCRIPT_WORKING_DIR}/nvidia* 1>> $LOG_FILE 2>> $LOG_FILE
      rm -rf ${USRS}modules/nvidia* 1>> $LOG_FILE 2>> $LOG_FILE


I don't think I can mod this as I believe sgfxi updates itself

well it does if you call the -U option

I know smxi always replaces itself with the latest but not sure if it calls for the latest sgfxi

so I suppose the feature request becomes....
can you remove this line and will it still work ok for all people?

rm -f /usr/local/bin/nvidia-settings /usr/local/bin/nvidia-xconfig 1>> $LOG_FILE 2>> $LOG_FILE
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
rm -f /usr/local/bin/nvidia-settings /usr/local/bin/nvidia-xconfig

that is not the location of that file now. It was, briefly, and so I left in sgfxi the line to remove that in case it exists.

It does not exist, check for yourself, it's merely a legacy cleanup feature that costs very little and might now and then help an older system out.

/usr/local/bin is where alternate stuff like smxi and sgfxi go, /usr/bin is where nvidia-config goes.

which nvidia-xconfig
/usr/bin/nvidia-xconfig

see? sgfxi has been around so long that it has stuff in it from a distant bygone day, so you have to check to make sure what you are seeing is actually what is there now.

This is the downside of not adequately commenting every single thing in sgfxi, since every single thing there was put there to solve some issue in some distro at some point. Some of those things haven't been needed for a long time, but I leave them because it doesn't really cost much to leave them, and if I don't remember exactly why it's there, I leave it be.

Every smxi tool updates itself when started by itself, and smxi updates every tool if needed when you start that tool from smxi, including inxi if you used smxi to install inxi.

sgfxi -h will show how to turn off the autoupdate feature, -R I think it is.
Back to top
aus9
Status: Assistant
Joined: 21 Sep 2008
Posts: 358
Location: Australia
Reply Quote
oops I failed to read my own ......man sgfxi

sgfxi -C

will run and not create a new xorg.

As I refused to create a man page for sxmi..but looking at smxi -h....my eyesight can not spot a skip xorg step inside smxi.

cheers

FEATURE REQUEST withdrawn please
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
aus, this stuff got so much use, and so many user requests for features when it was really popular, that it got increasingly unlikely that a feature was missing.
Back to top
Display posts from previous:   
Page: Previous  1, 2, 3 ... 10, 11, 12, 13, 14  Next
All times are GMT - 8 Hours