1 |
DENIED
|
ROLE_USER
|
null |
|
Show voter details
|
2 |
DENIED
|
moderate
|
Proxies\__CG__\App\Entity\Entry {#1526
+user: Proxies\__CG__\App\Entity\User {#2363 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1597 …}
+slug: "Silverblue-Run-ostree-updates-at-shutdown"
+title: "Silverblue: Run ostree updates at shutdown?"
+url: null
+body: """
Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?\n
\n
I’m thinking of doing the same with Tony Walker’s [silverblue-update](https://github.com/tonywalker1/silverblue-update) service.\n
\n
I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this *should* help ensure I’ve always got the latest daily image at boot. Thoughts?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 4
+favouriteCount: 12
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1727478400 {#1741
date: 2024-09-28 01:06:40.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1617 …}
+votes: Doctrine\ORM\PersistentCollection {#1725 …}
+reports: Doctrine\ORM\PersistentCollection {#1721 …}
+favourites: Doctrine\ORM\PersistentCollection {#2380 …}
+notifications: Doctrine\ORM\PersistentCollection {#2364 …}
+badges: Doctrine\ORM\PersistentCollection {#1883 …}
+children: [
App\Entity\EntryComment {#1676
+user: App\Entity\User {#259 …}
+entry: Proxies\__CG__\App\Entity\Entry {#1526 …2}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+parent: null
+root: null
+body: """
I run the built-in automatic rpm-ostree upgrade service every 6 hours.\n
\n
If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?\n
\n
I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?
"""
+lang: "en"
+isAdult: false
+favouriteCount: 4
+score: 0
+lastActive: DateTime @1727476958 {#1606
date: 2024-09-28 00:42:38.0 +02:00
}
+ip: null
+tags: null
+mentions: [
"@thayer@lemmy.ca"
]
+children: Doctrine\ORM\PersistentCollection {#1564 …}
+nested: Doctrine\ORM\PersistentCollection {#1559 …}
+votes: Doctrine\ORM\PersistentCollection {#1567 …}
+reports: Doctrine\ORM\PersistentCollection {#1561 …}
+favourites: Doctrine\ORM\PersistentCollection {#1554 …}
+notifications: Doctrine\ORM\PersistentCollection {#1583 …}
-id: 329376
-bodyTs: "'6':14 'automat':7 'built':5 'built-in':4 'could':58 'doc':26 'everi':13 'experienc':47 'hour':15 'ineffici':22 'like':56 'm':44 'mayb':23 'ostre':10 'part':50 'proper':61 'read':24 'rpm':9 'rpm-ostre':8 'run':2,37,64 'see':30 'seem':55 'servic':12,40 'shutdown':42,67 'shutdown.target':28 'systemd':52 'thing':65 'think':18 'upgrad':11,39 'use':34 'way':62"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.sdf.org/comment/7577109"
+editedAt: null
+createdAt: DateTimeImmutable @1705872338 {#1752
date: 2024-01-21 22:25:38.0 +01:00
}
+"title": 329376
}
]
-id: 32227
-titleTs: "'ostre':3 'run':2 'shutdown':6 'silverblu':1 'updat':4"
-bodyTs: "'/tonywalker1/silverblue-update)':43 'alway':73,93 'autom':9 'behind':77 'boot':100 'check':81 'daili':51,97 'day':65,76 'differ':26 'ensur':90 'fedora':2 'fellow':1 'find':21 'forc':68 'get':56 'github.com':42 'github.com/tonywalker1/silverblue-update)':41 'got':94 'help':89 'imag':59,98 'immut':3 'latest':96 'm':28 'machin':50 'make':23 'mean':55 'near':72 'next':64 'occur':14 'often':54 'one':75 'practic':25 'reboot':70 'remain':74 'servic':44 'short':60 'shutdown':16,46,86 'silverblu':39 'silverblue-upd':38 'startup':62 'system':11 'think':29 'thought':101 'toni':35 'updat':12,40,58,79,83 'user':4 've':92 'walker':36"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1705916974
+visibility: "visible "
+apId: "https://lemmy.ca/post/13758040"
+editedAt: DateTimeImmutable @1727429051 {#1674
date: 2024-09-27 11:24:11.0 +02:00
}
+createdAt: DateTimeImmutable @1705868974 {#2447
date: 2024-01-21 21:29:34.0 +01:00
}
+__isInitialized__: true
…2
} |
|
Show voter details
|
3 |
DENIED
|
edit
|
Proxies\__CG__\App\Entity\Entry {#1526
+user: Proxies\__CG__\App\Entity\User {#2363 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1597 …}
+slug: "Silverblue-Run-ostree-updates-at-shutdown"
+title: "Silverblue: Run ostree updates at shutdown?"
+url: null
+body: """
Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?\n
\n
I’m thinking of doing the same with Tony Walker’s [silverblue-update](https://github.com/tonywalker1/silverblue-update) service.\n
\n
I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this *should* help ensure I’ve always got the latest daily image at boot. Thoughts?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 4
+favouriteCount: 12
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1727478400 {#1741
date: 2024-09-28 01:06:40.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1617 …}
+votes: Doctrine\ORM\PersistentCollection {#1725 …}
+reports: Doctrine\ORM\PersistentCollection {#1721 …}
+favourites: Doctrine\ORM\PersistentCollection {#2380 …}
+notifications: Doctrine\ORM\PersistentCollection {#2364 …}
+badges: Doctrine\ORM\PersistentCollection {#1883 …}
+children: [
App\Entity\EntryComment {#1676
+user: App\Entity\User {#259 …}
+entry: Proxies\__CG__\App\Entity\Entry {#1526 …2}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+parent: null
+root: null
+body: """
I run the built-in automatic rpm-ostree upgrade service every 6 hours.\n
\n
If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?\n
\n
I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?
"""
+lang: "en"
+isAdult: false
+favouriteCount: 4
+score: 0
+lastActive: DateTime @1727476958 {#1606
date: 2024-09-28 00:42:38.0 +02:00
}
+ip: null
+tags: null
+mentions: [
"@thayer@lemmy.ca"
]
+children: Doctrine\ORM\PersistentCollection {#1564 …}
+nested: Doctrine\ORM\PersistentCollection {#1559 …}
+votes: Doctrine\ORM\PersistentCollection {#1567 …}
+reports: Doctrine\ORM\PersistentCollection {#1561 …}
+favourites: Doctrine\ORM\PersistentCollection {#1554 …}
+notifications: Doctrine\ORM\PersistentCollection {#1583 …}
-id: 329376
-bodyTs: "'6':14 'automat':7 'built':5 'built-in':4 'could':58 'doc':26 'everi':13 'experienc':47 'hour':15 'ineffici':22 'like':56 'm':44 'mayb':23 'ostre':10 'part':50 'proper':61 'read':24 'rpm':9 'rpm-ostre':8 'run':2,37,64 'see':30 'seem':55 'servic':12,40 'shutdown':42,67 'shutdown.target':28 'systemd':52 'thing':65 'think':18 'upgrad':11,39 'use':34 'way':62"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.sdf.org/comment/7577109"
+editedAt: null
+createdAt: DateTimeImmutable @1705872338 {#1752
date: 2024-01-21 22:25:38.0 +01:00
}
+"title": 329376
}
]
-id: 32227
-titleTs: "'ostre':3 'run':2 'shutdown':6 'silverblu':1 'updat':4"
-bodyTs: "'/tonywalker1/silverblue-update)':43 'alway':73,93 'autom':9 'behind':77 'boot':100 'check':81 'daili':51,97 'day':65,76 'differ':26 'ensur':90 'fedora':2 'fellow':1 'find':21 'forc':68 'get':56 'github.com':42 'github.com/tonywalker1/silverblue-update)':41 'got':94 'help':89 'imag':59,98 'immut':3 'latest':96 'm':28 'machin':50 'make':23 'mean':55 'near':72 'next':64 'occur':14 'often':54 'one':75 'practic':25 'reboot':70 'remain':74 'servic':44 'short':60 'shutdown':16,46,86 'silverblu':39 'silverblue-upd':38 'startup':62 'system':11 'think':29 'thought':101 'toni':35 'updat':12,40,58,79,83 'user':4 've':92 'walker':36"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1705916974
+visibility: "visible "
+apId: "https://lemmy.ca/post/13758040"
+editedAt: DateTimeImmutable @1727429051 {#1674
date: 2024-09-27 11:24:11.0 +02:00
}
+createdAt: DateTimeImmutable @1705868974 {#2447
date: 2024-01-21 21:29:34.0 +01:00
}
+__isInitialized__: true
…2
} |
|
Show voter details
|
4 |
DENIED
|
moderate
|
Proxies\__CG__\App\Entity\Entry {#1526
+user: Proxies\__CG__\App\Entity\User {#2363 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1597 …}
+slug: "Silverblue-Run-ostree-updates-at-shutdown"
+title: "Silverblue: Run ostree updates at shutdown?"
+url: null
+body: """
Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?\n
\n
I’m thinking of doing the same with Tony Walker’s [silverblue-update](https://github.com/tonywalker1/silverblue-update) service.\n
\n
I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this *should* help ensure I’ve always got the latest daily image at boot. Thoughts?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 4
+favouriteCount: 12
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1727478400 {#1741
date: 2024-09-28 01:06:40.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1617 …}
+votes: Doctrine\ORM\PersistentCollection {#1725 …}
+reports: Doctrine\ORM\PersistentCollection {#1721 …}
+favourites: Doctrine\ORM\PersistentCollection {#2380 …}
+notifications: Doctrine\ORM\PersistentCollection {#2364 …}
+badges: Doctrine\ORM\PersistentCollection {#1883 …}
+children: [
App\Entity\EntryComment {#1676
+user: App\Entity\User {#259 …}
+entry: Proxies\__CG__\App\Entity\Entry {#1526 …2}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+parent: null
+root: null
+body: """
I run the built-in automatic rpm-ostree upgrade service every 6 hours.\n
\n
If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?\n
\n
I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?
"""
+lang: "en"
+isAdult: false
+favouriteCount: 4
+score: 0
+lastActive: DateTime @1727476958 {#1606
date: 2024-09-28 00:42:38.0 +02:00
}
+ip: null
+tags: null
+mentions: [
"@thayer@lemmy.ca"
]
+children: Doctrine\ORM\PersistentCollection {#1564 …}
+nested: Doctrine\ORM\PersistentCollection {#1559 …}
+votes: Doctrine\ORM\PersistentCollection {#1567 …}
+reports: Doctrine\ORM\PersistentCollection {#1561 …}
+favourites: Doctrine\ORM\PersistentCollection {#1554 …}
+notifications: Doctrine\ORM\PersistentCollection {#1583 …}
-id: 329376
-bodyTs: "'6':14 'automat':7 'built':5 'built-in':4 'could':58 'doc':26 'everi':13 'experienc':47 'hour':15 'ineffici':22 'like':56 'm':44 'mayb':23 'ostre':10 'part':50 'proper':61 'read':24 'rpm':9 'rpm-ostre':8 'run':2,37,64 'see':30 'seem':55 'servic':12,40 'shutdown':42,67 'shutdown.target':28 'systemd':52 'thing':65 'think':18 'upgrad':11,39 'use':34 'way':62"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.sdf.org/comment/7577109"
+editedAt: null
+createdAt: DateTimeImmutable @1705872338 {#1752
date: 2024-01-21 22:25:38.0 +01:00
}
+"title": 329376
}
]
-id: 32227
-titleTs: "'ostre':3 'run':2 'shutdown':6 'silverblu':1 'updat':4"
-bodyTs: "'/tonywalker1/silverblue-update)':43 'alway':73,93 'autom':9 'behind':77 'boot':100 'check':81 'daili':51,97 'day':65,76 'differ':26 'ensur':90 'fedora':2 'fellow':1 'find':21 'forc':68 'get':56 'github.com':42 'github.com/tonywalker1/silverblue-update)':41 'got':94 'help':89 'imag':59,98 'immut':3 'latest':96 'm':28 'machin':50 'make':23 'mean':55 'near':72 'next':64 'occur':14 'often':54 'one':75 'practic':25 'reboot':70 'remain':74 'servic':44 'short':60 'shutdown':16,46,86 'silverblu':39 'silverblue-upd':38 'startup':62 'system':11 'think':29 'thought':101 'toni':35 'updat':12,40,58,79,83 'user':4 've':92 'walker':36"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1705916974
+visibility: "visible "
+apId: "https://lemmy.ca/post/13758040"
+editedAt: DateTimeImmutable @1727429051 {#1674
date: 2024-09-27 11:24:11.0 +02:00
}
+createdAt: DateTimeImmutable @1705868974 {#2447
date: 2024-01-21 21:29:34.0 +01:00
}
+__isInitialized__: true
…2
} |
|
Show voter details
|
5 |
DENIED
|
ROLE_USER
|
null |
|
Show voter details
|
6 |
DENIED
|
moderate
|
App\Entity\EntryComment {#1676
+user: App\Entity\User {#259 …}
+entry: Proxies\__CG__\App\Entity\Entry {#1526
+user: Proxies\__CG__\App\Entity\User {#2363 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1597 …}
+slug: "Silverblue-Run-ostree-updates-at-shutdown"
+title: "Silverblue: Run ostree updates at shutdown?"
+url: null
+body: """
Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?\n
\n
I’m thinking of doing the same with Tony Walker’s [silverblue-update](https://github.com/tonywalker1/silverblue-update) service.\n
\n
I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this *should* help ensure I’ve always got the latest daily image at boot. Thoughts?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 4
+favouriteCount: 12
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1727478400 {#1741
date: 2024-09-28 01:06:40.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1617 …}
+votes: Doctrine\ORM\PersistentCollection {#1725 …}
+reports: Doctrine\ORM\PersistentCollection {#1721 …}
+favourites: Doctrine\ORM\PersistentCollection {#2380 …}
+notifications: Doctrine\ORM\PersistentCollection {#2364 …}
+badges: Doctrine\ORM\PersistentCollection {#1883 …}
+children: [
App\Entity\EntryComment {#1676}
]
-id: 32227
-titleTs: "'ostre':3 'run':2 'shutdown':6 'silverblu':1 'updat':4"
-bodyTs: "'/tonywalker1/silverblue-update)':43 'alway':73,93 'autom':9 'behind':77 'boot':100 'check':81 'daili':51,97 'day':65,76 'differ':26 'ensur':90 'fedora':2 'fellow':1 'find':21 'forc':68 'get':56 'github.com':42 'github.com/tonywalker1/silverblue-update)':41 'got':94 'help':89 'imag':59,98 'immut':3 'latest':96 'm':28 'machin':50 'make':23 'mean':55 'near':72 'next':64 'occur':14 'often':54 'one':75 'practic':25 'reboot':70 'remain':74 'servic':44 'short':60 'shutdown':16,46,86 'silverblu':39 'silverblue-upd':38 'startup':62 'system':11 'think':29 'thought':101 'toni':35 'updat':12,40,58,79,83 'user':4 've':92 'walker':36"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1705916974
+visibility: "visible "
+apId: "https://lemmy.ca/post/13758040"
+editedAt: DateTimeImmutable @1727429051 {#1674
date: 2024-09-27 11:24:11.0 +02:00
}
+createdAt: DateTimeImmutable @1705868974 {#2447
date: 2024-01-21 21:29:34.0 +01:00
}
+__isInitialized__: true
…2
}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+parent: null
+root: null
+body: """
I run the built-in automatic rpm-ostree upgrade service every 6 hours.\n
\n
If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?\n
\n
I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?
"""
+lang: "en"
+isAdult: false
+favouriteCount: 4
+score: 0
+lastActive: DateTime @1727476958 {#1606
date: 2024-09-28 00:42:38.0 +02:00
}
+ip: null
+tags: null
+mentions: [
"@thayer@lemmy.ca"
]
+children: Doctrine\ORM\PersistentCollection {#1564 …}
+nested: Doctrine\ORM\PersistentCollection {#1559 …}
+votes: Doctrine\ORM\PersistentCollection {#1567 …}
+reports: Doctrine\ORM\PersistentCollection {#1561 …}
+favourites: Doctrine\ORM\PersistentCollection {#1554 …}
+notifications: Doctrine\ORM\PersistentCollection {#1583 …}
-id: 329376
-bodyTs: "'6':14 'automat':7 'built':5 'built-in':4 'could':58 'doc':26 'everi':13 'experienc':47 'hour':15 'ineffici':22 'like':56 'm':44 'mayb':23 'ostre':10 'part':50 'proper':61 'read':24 'rpm':9 'rpm-ostre':8 'run':2,37,64 'see':30 'seem':55 'servic':12,40 'shutdown':42,67 'shutdown.target':28 'systemd':52 'thing':65 'think':18 'upgrad':11,39 'use':34 'way':62"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.sdf.org/comment/7577109"
+editedAt: null
+createdAt: DateTimeImmutable @1705872338 {#1752
date: 2024-01-21 22:25:38.0 +01:00
}
+"title": 329376
} |
|
Show voter details
|
7 |
DENIED
|
edit
|
App\Entity\EntryComment {#1676
+user: App\Entity\User {#259 …}
+entry: Proxies\__CG__\App\Entity\Entry {#1526
+user: Proxies\__CG__\App\Entity\User {#2363 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1597 …}
+slug: "Silverblue-Run-ostree-updates-at-shutdown"
+title: "Silverblue: Run ostree updates at shutdown?"
+url: null
+body: """
Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?\n
\n
I’m thinking of doing the same with Tony Walker’s [silverblue-update](https://github.com/tonywalker1/silverblue-update) service.\n
\n
I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this *should* help ensure I’ve always got the latest daily image at boot. Thoughts?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 4
+favouriteCount: 12
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1727478400 {#1741
date: 2024-09-28 01:06:40.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1617 …}
+votes: Doctrine\ORM\PersistentCollection {#1725 …}
+reports: Doctrine\ORM\PersistentCollection {#1721 …}
+favourites: Doctrine\ORM\PersistentCollection {#2380 …}
+notifications: Doctrine\ORM\PersistentCollection {#2364 …}
+badges: Doctrine\ORM\PersistentCollection {#1883 …}
+children: [
App\Entity\EntryComment {#1676}
]
-id: 32227
-titleTs: "'ostre':3 'run':2 'shutdown':6 'silverblu':1 'updat':4"
-bodyTs: "'/tonywalker1/silverblue-update)':43 'alway':73,93 'autom':9 'behind':77 'boot':100 'check':81 'daili':51,97 'day':65,76 'differ':26 'ensur':90 'fedora':2 'fellow':1 'find':21 'forc':68 'get':56 'github.com':42 'github.com/tonywalker1/silverblue-update)':41 'got':94 'help':89 'imag':59,98 'immut':3 'latest':96 'm':28 'machin':50 'make':23 'mean':55 'near':72 'next':64 'occur':14 'often':54 'one':75 'practic':25 'reboot':70 'remain':74 'servic':44 'short':60 'shutdown':16,46,86 'silverblu':39 'silverblue-upd':38 'startup':62 'system':11 'think':29 'thought':101 'toni':35 'updat':12,40,58,79,83 'user':4 've':92 'walker':36"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1705916974
+visibility: "visible "
+apId: "https://lemmy.ca/post/13758040"
+editedAt: DateTimeImmutable @1727429051 {#1674
date: 2024-09-27 11:24:11.0 +02:00
}
+createdAt: DateTimeImmutable @1705868974 {#2447
date: 2024-01-21 21:29:34.0 +01:00
}
+__isInitialized__: true
…2
}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+parent: null
+root: null
+body: """
I run the built-in automatic rpm-ostree upgrade service every 6 hours.\n
\n
If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?\n
\n
I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?
"""
+lang: "en"
+isAdult: false
+favouriteCount: 4
+score: 0
+lastActive: DateTime @1727476958 {#1606
date: 2024-09-28 00:42:38.0 +02:00
}
+ip: null
+tags: null
+mentions: [
"@thayer@lemmy.ca"
]
+children: Doctrine\ORM\PersistentCollection {#1564 …}
+nested: Doctrine\ORM\PersistentCollection {#1559 …}
+votes: Doctrine\ORM\PersistentCollection {#1567 …}
+reports: Doctrine\ORM\PersistentCollection {#1561 …}
+favourites: Doctrine\ORM\PersistentCollection {#1554 …}
+notifications: Doctrine\ORM\PersistentCollection {#1583 …}
-id: 329376
-bodyTs: "'6':14 'automat':7 'built':5 'built-in':4 'could':58 'doc':26 'everi':13 'experienc':47 'hour':15 'ineffici':22 'like':56 'm':44 'mayb':23 'ostre':10 'part':50 'proper':61 'read':24 'rpm':9 'rpm-ostre':8 'run':2,37,64 'see':30 'seem':55 'servic':12,40 'shutdown':42,67 'shutdown.target':28 'systemd':52 'thing':65 'think':18 'upgrad':11,39 'use':34 'way':62"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.sdf.org/comment/7577109"
+editedAt: null
+createdAt: DateTimeImmutable @1705872338 {#1752
date: 2024-01-21 22:25:38.0 +01:00
}
+"title": 329376
} |
|
Show voter details
|
8 |
DENIED
|
moderate
|
App\Entity\EntryComment {#1676
+user: App\Entity\User {#259 …}
+entry: Proxies\__CG__\App\Entity\Entry {#1526
+user: Proxies\__CG__\App\Entity\User {#2363 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1597 …}
+slug: "Silverblue-Run-ostree-updates-at-shutdown"
+title: "Silverblue: Run ostree updates at shutdown?"
+url: null
+body: """
Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?\n
\n
I’m thinking of doing the same with Tony Walker’s [silverblue-update](https://github.com/tonywalker1/silverblue-update) service.\n
\n
I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this *should* help ensure I’ve always got the latest daily image at boot. Thoughts?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 4
+favouriteCount: 12
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1727478400 {#1741
date: 2024-09-28 01:06:40.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1617 …}
+votes: Doctrine\ORM\PersistentCollection {#1725 …}
+reports: Doctrine\ORM\PersistentCollection {#1721 …}
+favourites: Doctrine\ORM\PersistentCollection {#2380 …}
+notifications: Doctrine\ORM\PersistentCollection {#2364 …}
+badges: Doctrine\ORM\PersistentCollection {#1883 …}
+children: [
App\Entity\EntryComment {#1676}
]
-id: 32227
-titleTs: "'ostre':3 'run':2 'shutdown':6 'silverblu':1 'updat':4"
-bodyTs: "'/tonywalker1/silverblue-update)':43 'alway':73,93 'autom':9 'behind':77 'boot':100 'check':81 'daili':51,97 'day':65,76 'differ':26 'ensur':90 'fedora':2 'fellow':1 'find':21 'forc':68 'get':56 'github.com':42 'github.com/tonywalker1/silverblue-update)':41 'got':94 'help':89 'imag':59,98 'immut':3 'latest':96 'm':28 'machin':50 'make':23 'mean':55 'near':72 'next':64 'occur':14 'often':54 'one':75 'practic':25 'reboot':70 'remain':74 'servic':44 'short':60 'shutdown':16,46,86 'silverblu':39 'silverblue-upd':38 'startup':62 'system':11 'think':29 'thought':101 'toni':35 'updat':12,40,58,79,83 'user':4 've':92 'walker':36"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1705916974
+visibility: "visible "
+apId: "https://lemmy.ca/post/13758040"
+editedAt: DateTimeImmutable @1727429051 {#1674
date: 2024-09-27 11:24:11.0 +02:00
}
+createdAt: DateTimeImmutable @1705868974 {#2447
date: 2024-01-21 21:29:34.0 +01:00
}
+__isInitialized__: true
…2
}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1566 …}
+image: null
+parent: null
+root: null
+body: """
I run the built-in automatic rpm-ostree upgrade service every 6 hours.\n
\n
If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?\n
\n
I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?
"""
+lang: "en"
+isAdult: false
+favouriteCount: 4
+score: 0
+lastActive: DateTime @1727476958 {#1606
date: 2024-09-28 00:42:38.0 +02:00
}
+ip: null
+tags: null
+mentions: [
"@thayer@lemmy.ca"
]
+children: Doctrine\ORM\PersistentCollection {#1564 …}
+nested: Doctrine\ORM\PersistentCollection {#1559 …}
+votes: Doctrine\ORM\PersistentCollection {#1567 …}
+reports: Doctrine\ORM\PersistentCollection {#1561 …}
+favourites: Doctrine\ORM\PersistentCollection {#1554 …}
+notifications: Doctrine\ORM\PersistentCollection {#1583 …}
-id: 329376
-bodyTs: "'6':14 'automat':7 'built':5 'built-in':4 'could':58 'doc':26 'everi':13 'experienc':47 'hour':15 'ineffici':22 'like':56 'm':44 'mayb':23 'ostre':10 'part':50 'proper':61 'read':24 'rpm':9 'rpm-ostre':8 'run':2,37,64 'see':30 'seem':55 'servic':12,40 'shutdown':42,67 'shutdown.target':28 'systemd':52 'thing':65 'think':18 'upgrad':11,39 'use':34 'way':62"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.sdf.org/comment/7577109"
+editedAt: null
+createdAt: DateTimeImmutable @1705872338 {#1752
date: 2024-01-21 22:25:38.0 +01:00
}
+"title": 329376
} |
|
Show voter details
|
9 |
DENIED
|
ROLE_ADMIN
|
null |
|
Show voter details
|
10 |
DENIED
|
ROLE_MODERATOR
|
null |
|
Show voter details
|