You are not logged in.
mariannemarlow wrote:64 bit worked on my old netbook!
Yay!
Do you notice a speed boost?
64-bit is also significantly more secure than a 32-bit operating system thanks to the NX bit and the vastly increased effectiveness of stretch's ASLR/PIE combination
Yes it did seem faster. This is an old 32 bit netbook though, how come it even worked?!
Are you saying that was something to do with stretch? I'm already usng stretch (debian 9)
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
This is an old 32 bit netbook though, how come it even worked?!
Can we please see the output of:
lscpu | sed q
That should show your CPU architecture
Offline
Architecture: i686
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
^ That's 32-bit, was that output from dwmx?
I'm not sure what shows in /proc/cpuinfo if a 32-bit OS is used on a 64-bit processor, tbh.
Offline
No, that output was from Debian 9
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
@HoaS
On a 32 bit install with a 64 bit processor
$ lscpu | sed q
Architecture: i686
Since you asked,
beardy@debian:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
stepping : 10
<snip>
My Core2Quad is absolutely 64 bit (no VT-x hence my VM installs being 32 this is snipped from such)
I suspect @mariannemarlow's CPU may well actually be 64 bit, many netbooks are, even if they came new with a 32 bit OS because of low memory.
Maybe the output of
cat /proc/cpuinfo | grep model
One's favourite search engine could then turn up it's bitness.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
This is what it turns up for me.
root@marianne:/home/marianne# cat /proc/cpuinfo | grep model
model : 54
model name : Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
model : 54
model name : Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
model : 54
model name : Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
model : 54
model name : Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
I think you're right, it might be 64bit
root@marianne:/home/marianne# lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 54
Model name: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
Last edited by mariannemarlow (2017-08-30 22:54:36)
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
Then It's 64 bit
<omitted>
Intel® 64 ‡ Yes
Instruction Set 64-bit<omitted>
Security & Reliability
Intel® Trusted Execution Technology ‡ No
Execute Disable Bit ‡ Yes
So it is 64 bit, and as @HoaS pointed out running a 64 bit install will enhance security, though perhaps not as much as with a processor that supported Intel® Trusted Execution Technology.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
Well I guess I'll try some 64bit iso's then
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
I'm not offended at all.
But what "type of user" do you think I am? just curious!
The kind of user who likes XFCE.
Offline
mariannemarlow wrote:I'm not offended at all.
But what "type of user" do you think I am? just curious!
The kind of user who likes XFCE.
Meow!
I have an Eclectic taste. I don't only like one genre of music, one type of cuisine or one radio presenter. Why should I only like one Window Manager?
One sees different things that they like in every situation.
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
^Eclectic taste? How is that working with one husband/wife?
Btw love those colorful bird-pix. Quote: "They're like flying candies!"
Offline
^Eclectic taste? How is that working with one husband/wife?
Btw love those colorful bird-pix. Quote: "They're like flying candies!"
Um... what?
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
^I mean the fotos from Featheredfiends.
Offline
^Eclectic taste? How is that working with one husband/wife?
Btw love those colorful bird-pix. Quote: "They're like flying candies!"
at both sentences.
Offline
Is "they're like flying candies" from a film or something, just asking cos either that or you quoted yourself?
Anyway.. thanks.. I think.
"There is nothing to compare with a budgie’s look of triumph when they have thrown an object on to the floor for their slave to pick up."
(Rose Youd 09/06/2012)
Offline
^Oh, that's from Rocky - he said something like that in the pet shop where Adrian worked.
Offline
Getting settled in to my Alpine Linux box now, I'm liking it more the more I dig into it.
The init system is _much_ easier to manipulate than systemd, custom startup scripts are just that with no special syntax or format required beyond the start() function; here is one I've just made to save the backlight level on shutdown and restore it again on boot (systemd has a similar systemd-backlight@.service):
empty@alpine:~ $ cat /etc/init.d/backlight
#!/sbin/openrc-run
# Copyright 2017 HoaS
# Licensed under the GNU General Public License v3
description="Restore the backlight level."
start() {
ebegin "Restoring backlight level"
cp /etc/backlight.save /sys/class/backlight/intel_backlight/brightness
}
stop() {
ebegin "Saving backlight level"
cp /sys/class/backlight/intel_backlight/brightness /etc/backlight.save
}
empty@alpine:~ $
It's exceptionally crude but it works perfectly 8)
Offline
It's exceptionally crude but it works perfectly 8)
If it works, that's all that usually matters. You scratched an itch.
Last edited by KrunchTime (2017-09-22 21:20:26)
Offline
Sometimes I think systemd adds unnecessary layers of complication to things. When I need something to run as a service at periodic intervals, it seems much easier to add it to cron. I usually end up building systemd timers and service files anyway but realistically I could save time by just tossing the stuff into cron and scheduling it.
Openrc may be crude by systemd's standards but that also looks like something that a person could get some work done with. Is it capable of handling timed events or would you go to cron for that in openrc?
Offline